Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

solr-operator-zookeeper-operator-pre-delete gets scheduled on windows node #518

Closed
arogic opened this issue Dec 7, 2022 · 1 comment · Fixed by #520
Closed

solr-operator-zookeeper-operator-pre-delete gets scheduled on windows node #518

arogic opened this issue Dec 7, 2022 · 1 comment · Fixed by #520

Comments

@arogic
Copy link

arogic commented Dec 7, 2022

Description

We have an AKS Kubernetes Cluster with Linux and Windows Node Pools. We deploy the zookeeper-operator helm chart through the solr-operator helm chart. When we delete the solr-operator using helm, the "solr-operator-zookeeper-operator-pre-delete" job gets scheduled on the Windows NodePool which obviously fails. Is there a way to pass NodeSelector values over for the "solr-operator-zookeeper-operator-pre-delete" job to be scheduled on the Linux Node Pool?

Importance

Location

Suggestions for an improvement

Option in the helm chart values file to define nodeSelector for the "solr-operator-zookeeper-operator-pre-delete" job.

Thanks in advance.

@arogic
Copy link
Author

arogic commented Dec 8, 2022

I got around the issue by setting node taints on my AKS Windows Node Pool.

"node_taints": [ "app.kubernetes.io/name=solr:NoSchedule" ]

However it would be great, if NodeSelector would be carried over from the values file to the job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant