-
Notifications
You must be signed in to change notification settings - Fork 114
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
There should be nothing that uses a node selector/affinity that is not easily configurable at deploy time #507
Comments
If you're here because of label pains, a breakfix for now.
You want everything in bindata. Blow all labels and affinites out or modify them to your needs. make your image: I don't feel like dissecting their vars, just retag it.
Push your image where ever. Then export and deploy.
|
Hi @ns-rlewkowicz , NodeSelector fields of the daemonsets are updated in
Can you be more specific about the problem you are having with your deploy? |
Hi @ns-rlewkowicz any update base on the comment from @zeeke ? |
I think this is just a docs gap. It leads with this make system and I'm just a goof I suppose. I can grep around and modify stuff without issue so I thought that was just my life with this product. |
This is an interesting project. I wonder what the reasoning was behind the need for an aggressive reconciliation loop over a slew of well established deployment models and tools.
It worked great in a dev env, trying to incorporate this into an existing environment has been a nightmare.
This fixes config daemon:
But even this is awkward. It doesn't seem to cycle the pods automatically after application.
Then the other DS won't launch. There's a bunch of hard coded node labels.
The text was updated successfully, but these errors were encountered: