You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: