-
Notifications
You must be signed in to change notification settings - Fork 89
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
Make traefik CRD installation flaggable #855
Comments
Sounds reasonable to me. Is there any way to catch and warn about cases where folks disable it, but it's not installed already? |
AFAIK it will break the helm install, as the cluster will not have the CRD definition that we try to upload. |
There are various strategies to provide CRDs for heln charts i think.
I'm not confident on what makes sense etc, but the key is to overview if putting them as templates is relevant for existing users and/or new users, and how people should migrate etc between strategies. |
I agree on the value of being able to opt-out at least on anything traefik-related, as they arent required to be deployed specifically by this chart - and since its a cluster-wide resource it will conflict with other traefik CRDs |
Can one opt-out of installing a charts CRDs in the crds folder, using a helm CLI flag? If so, one could first opt out during the initial install, and then manually apply yhe dask-gateway specific CRDs as a workaround if better options aren't available for us. |
I will make a PR with the ability to turn on and off traefik and can test how it works etc:) It will take a few days before I can do it. |
I made a PR to make traefik installation optional. With the built in mechanisms of helm with regards to skipping installation of CRDs, I did not find a nice solution for opting out of traefik CRD installation while keeping the installation of the |
I'd like to make it possible to disable the CRD installation for traefik in the helmchart. This is for installation in clusters that already has traefik installed.
Is this a feature that would be accepted?
The text was updated successfully, but these errors were encountered: