-
Notifications
You must be signed in to change notification settings - Fork 128
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
Packaged components list is out of date #246
Comments
Yeah, some of those things can technically be disabled, but will break other things if they are, so we don't document them. For example:
|
I understand, but maybe there should still be a list of reserved names. Or the advise should recommend prefixing additional manifests with some custom prefix? I noticed this because I was creating a It's not a big deal, as I wouldn't have checked the documentation until after I ran into problems anyways. 😄 Feel free to close if you think this is not worth the trouble. |
No I think you are correct that we should document this. There are also some nuances of how disable works - note that A lot of this is stuff that was thrown together early on and we have avoided changing to try to prevent breakage on upgrades; it's certainly not ideal. |
That's why I like the No need to worry if |
On https://docs.k3s.io/installation/packaged-components it says:
And later:
This requires that the list of packaged components is complete, but it is missing several names, like
ccm
,rolebindings
,runtimes
.The text was updated successfully, but these errors were encountered: