-
Notifications
You must be signed in to change notification settings - Fork 33
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
Expose pod nodeSelector in the CRD #214
Comments
@roivaz: Yes, the current node selector can cause a problem on HyperShift based deployments. Can you please file an RFE for the NetworkEdge team? |
The feature request is now being tracked as RFE-5408 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
@alebedev87 Thank you! That would definitely solve the issue. Any idea of the release this fix will be shipped in? |
The deadline is the GA of OpenShift 4.17, so beginning of October. However this operator is off the main payload so it can be released earlier. |
Closing the issue as the reporter confirmed #219 should fix the issue. |
It would be nice if the field
spec.template.spec.nodeSelector
in the external-dns Deployment could be configurable by exposing this configuration via the ExternalDNS custom resource.I am using the external-dns-operator in a cluster provisioned via hypershift. In this scenario the scheduler is unable to run external-dns pods because there are no master nodes available, so the pods stay in
pending
forever. The node selector is hardcoded here.The workaround I'm appying is to remove the
node-role.kubernetes.io/master: ''
label from the nodeSelector in the Deployment object, as the operator seems to not reconcile this.The text was updated successfully, but these errors were encountered: