Does Nebari require node group names to be "general", "user", and "worker"? #2816
Adam-D-Lewis
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Does Nebari require node group names to be "general", "user", and "worker" or do we support arbitrary node group names? Stated differently, does a deployment have to have a "general", and "user" node group? I think I've heard of some users renaming some node groups in the past. I'm considering enforcing the "general", "user", "worker" node group names a bit in a PR I'm working on and wondering how big of an issue it'll be.
BTW, I don't have an issue with continuing to support additional arbitrary node group names beyond "general", "user", and "worker". My question is mostly around guaranteeing "general", "user", and "worker" node group names exist.
I did see this guide on pre-existing deployments says those should be the node group names - https://www.nebari.dev/docs/how-tos/nebari-kubernetes#creating-node-groups
Beta Was this translation helpful? Give feedback.
All reactions