Add limitation about the first controller node #3485
Conversation
replicated-ci
added
type::docs
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| * Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles-beta) key is Beta. | ||
|
|
||
| * The first node added to the cluster is always a controller and cannot be assigned any custom roles. For more information about configuring node roles, see [roles](/reference/embedded-config#roles-beta) in _Embedded Cluster Config_. | ||
|
|
There was a problem hiding this comment.
^ this is in the "Manage Multi-Node Clusters" topic, which explains how to join nodes during/after install in the Admin Console/cli
| The Embedded Cluster Config lets you define several aspects of the Kubernetes cluster that will be created. | ||
|
|
||
| ### Limitation | ||
| ### Limitations |
There was a problem hiding this comment.
^ main limitations section of the Embedded Cluster Config reference. Making it clearer that there are additional limitations specific to the individual properties in the config
| * Defining node roles with the `roles` key is Beta. | ||
|
|
||
| * The first node added to the cluster is always a controller and cannot be assigned any custom roles. You can add custom labels to the first node by setting the `labels` field in the `roles.controller` key. | ||
|
|
There was a problem hiding this comment.
^ added these limitations to the roles key description in Embedded Cluster Config reference topic
Added a sentence about how you can still add labels by setting the roles.controller.labels key (not sure if this is helpful or not)
No description provided.