-
Notifications
You must be signed in to change notification settings - Fork 23
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
nodeSelector support during deployment for mixed node clusters #278
Comments
This might solve the use case: submariner-io/enhancements#149 |
Which pods do you mean exactly? Or are you simply trying to limit all submariner pods to Linux nodes only? |
Idea is to implement this through a generic option to take a yaml file as input, probably take |
Isn’t this done @vthapar? |
submariner-io/enhancements#149 is done and it adds support for node selector for submariner pods. But it doesn't add any means in subctl to set this and only provides option to modify in SubmarinerCR. As mentioned in comment this would be better implemented by providing a generic way to pass submariner CR yaml as input to subctl join. |
@mikenorgate can you clarify the query from @mkolesnik. |
The need is to limit all submariner pods to Linux nodes |
Okay. Please be aware that in order to achieve connectivity from a worker node to remote clusters, especially when using the kubeproxy based handlers, Submariner RouteAgent Pods should be running on every worker node. We can probably add necessary support in Submariner to limit scheduling of the RA pods (along with other DaemonSets) only to Linux nodes, but it might limit inter-connectivity only to those nodes. Is this something okay for you? |
Given that the constraint stems from Submariner’s implementation, it might be best to always add a pod selector specifying |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
What would you like to be added:
Add ability to specify
nodeSelector
during deploymentWhy is this needed:
When deploying into a cluster container a mixture of Windows and Linux nodes I would like to be able to specify a
nodeSelector
with a value ofkubernetes.io/os: linux
to make sure the submariner pods are scheduled to the correct nodesThe text was updated successfully, but these errors were encountered: