You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Is your feature request related to a problem? Please describe.
We have skip_crds = true to our helm chart install because we need to patch the consul-k8s CRDs (related to #3520) and we created the CRDs more or less how they come from the consul-k8s release tarball. Unfortunately we got this error when installing the helm chart after creating the CRDs:
Error: Unable to continue with install: CustomResourceDefinition "exportedservices.consul.hashicorp.com" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "consul"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "consul-system"
Feature Description
We do manage CRDs outside of helm for many charts already and this is the first time we see the helm chart not wanting to skip_crds = true option charts should respect.
@komapa Would resolving #3520 also solve this issue?
Yes, I guess one of these will suffice but in general I am worrying that not being able to track CRDs separate from helm will be generally an anti-pattern for the consul helm chart. For our immediate needs, what of the two, yes :)
Is general, there are many reasons why you may not want to let helm install and manage your CRDs for you - it would be wonderful if that was possible for this consul chart, like it is for most other charts.
Community Note
Is your feature request related to a problem? Please describe.
We have
skip_crds = true
to our helm chart install because we need to patch the consul-k8s CRDs (related to #3520) and we created the CRDs more or less how they come from theconsul-k8s
release tarball. Unfortunately we got this error when installing the helm chart after creating the CRDs:Feature Description
We do manage CRDs outside of helm for many charts already and this is the first time we see the helm chart not wanting to
skip_crds = true
option charts should respect.Use Case(s)
Installing CRDs outside of the helm chart.
Contributions
We patch with kustomize like this:
The text was updated successfully, but these errors were encountered: