Skip to content
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

Can't deploy k8gb on cluster with existing externalDNS #1103

Closed
jhuynh08 opened this issue Mar 20, 2023 · 0 comments
Closed

Can't deploy k8gb on cluster with existing externalDNS #1103

jhuynh08 opened this issue Mar 20, 2023 · 0 comments

Comments

@jhuynh08
Copy link

Hello,

I can't seem to install k8gb if I have an existing install of externalDNS deployed on my cluster. I know this was fixed before by adding the prefix k8gb to the deployment but this time it seems like it won't deploy due to the CRD that's already deployed for externalDNS.

INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "dnsendpoints.externaldns.k8s.io" 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 "k8gb"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "services"

Please let me know if there is anything else I would need to provide for further troubleshooting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant