-
Notifications
You must be signed in to change notification settings - Fork 157
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
feat(helm): introduce new installation and CRD lifecycle #1065
feat(helm): introduce new installation and CRD lifecycle #1065
Conversation
✅ Deploy Preview for capsule-documentation canceled.
|
Hi @oliverbaehler, what do you think about the method with a job that giantswarm uses to update crds - https://github.com/giantswarm/kube-prometheus-stack-app/tree/a8315a8/helm/prometheus-operator-app/templates/crd-install. Seems like that will help to achieve what you want, but will be completely backward-compatible. |
+1 for @MaxFedotov approach, it's the same approach used by HAProxy Technologies for their Kubernetes Ingress Controller. |
7b2b19d
to
da8b89f
Compare
Signed-off-by: Oliver Bähler <[email protected]>
Signed-off-by: Oliver Bähler <[email protected]>
468793c
to
f239f47
Compare
Signed-off-by: Oliver Bähler <[email protected]>
f239f47
to
842eb3b
Compare
Signed-off-by: Oliver Bähler <[email protected]>
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.
LGTM
With this PR we are addressing the distribution of our CRDs and are trying to reconcile the Helm Chart as the main way of installing Capsule. With this change we can keep our overheads little and focus on one way of distribution. While implementing the CRDs i also did some refactoring of certain helm values.
Implements: