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
Disable helm CRD installation for disable-helm-controller #8702
Disable helm CRD installation for disable-helm-controller #8702
Conversation
The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses k3s-io#8701 Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com>
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.
Thanks for the PR!
We try to avoid passing in both a struct, and a field on that struct. Just pass in the Config struct, and use the forServer
flag to determine which config to use.
Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com>
Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com>
LGTM! We can squash when merging. |
Hi @brandond, lemme know if this require any further work. Feel free to merge it |
You're all set.We're in code freeze pending release of last week's patches. We will merge things again once the releases are out. |
arm and s390x are flaking; merging |
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses k3s-io#8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses k3s-io#8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses k3s-io#8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses #8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses #8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
* Disable helm CRD installation for disable-helm-controller The NewContext package requires config as input which would require all third-party callers to update when the new go module is published. This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server. Addresses #8701 * address review comments * remove redundant check Signed-off-by: Harsimran Singh Maan <maan.harry@gmail.com> (cherry picked from commit abc2efd) Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
The NewContext package requires config as input which would require all third-party callers to update when the new go module is published.
This change only affects the behaviour of installation of helm CRDs. Existing helm crds installed in a cluster would not be removed when disable-helm-controller flag is set on the server.
Addresses #8701
Proposed Changes
Disable helm CRD installation for disable-helm-controller
Types of Changes
Breaking Change (for sdk) not for k3s service
Verification
Testing
Linked Issues
User-Facing Change
Further Comments
Closes #8701