-
Notifications
You must be signed in to change notification settings - Fork 25
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
Add EC --config-values flag and update automated install docs #2830
Conversation
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
After you get the ConfigValues file for your application using the `kots get config` command, Replicated recommends that you do the following to edit the contents of the ConfigValues file before sharing it with users: | ||
Before sharing a sample ConfigValues with users, Replicated recommends that you edit the sample file in the following ways: | ||
|
||
* Remove any configuration fields that have `readonly` set to `true`. Users cannot edit read only fields. For more information, see [readonly](/reference/custom-resource-config#readonly) in _Config_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hate this readonly and hidden stuff—it confuses me so much. But looking at the table for randomstring, it seems like readonly
true is what makes it persistent. False is ephemeral. So just wondering if this should be "remove the false ones."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This content is old enough that I'll make a separate docs story to investigate/confirm... I'm not even sure if the reason that this bullet point appears here actually has to do with ephemeral/persistent values or if it's more like "don't imply to your users that they can set a value for read-only fields"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ajp-io thank you! comments addressed and also linked to a followup story for that readonly value item |
EC install command reference doc: https://deploy-preview-2830--replicated-docs-upgrade.netlify.app/reference/embedded-cluster-install#flags
Added online and air gap EC install steps to the Installing with the CLI topic: https://deploy-preview-2830--replicated-docs-upgrade.netlify.app/enterprise/installing-existing-cluster-automation
Update the steps on how to get the ConfigValues file to account for EC users (previously it just included the kots get config command for kots existing cluster): https://deploy-preview-2830--replicated-docs-upgrade.netlify.app/vendor/releases-configvalues