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

Installing on a cluster with an existing udp-services ConfigMap fails #164

Closed
donovanmuller opened this issue Aug 17, 2020 · 2 comments · Fixed by #354
Closed

Installing on a cluster with an existing udp-services ConfigMap fails #164

donovanmuller opened this issue Aug 17, 2020 · 2 comments · Fixed by #354
Labels
bug Something isn't working
Milestone

Comments

@donovanmuller
Copy link
Contributor

donovanmuller commented Aug 17, 2020

If you attempt to install k8gb on a cluster with an existing udp-services ConfigMap via the make deploy-gslb-operator target, it will fail as below:

$ make deploy-gslb-operator ...
kubectl apply -f deploy/namespace.yaml
namespace/k8gb unchanged
cd chart/k8gb && helm dependency update
walk.go:74: found symbolic link in path: /Users/donovan/.../k8gb/deploy/crds/k8gb.absa.oss_gslbs_crd.yaml
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "kuberhealthy" chart repository
...Successfully got an update from the "codecentric" chart repository
...Successfully got an update from the "jetstack" chart repository
...Successfully got an update from the "crossplane-alpha" chart repository
...Successfully got an update from the "elastic" chart repository
...Successfully got an update from the "jfrog" chart repository
...Successfully got an update from the "banzaicloud-stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 2 charts
Downloading coredns from repo https://kubernetes-charts.storage.googleapis.com
Downloading etcd-operator from repo https://kubernetes-charts.storage.googleapis.com
Deleting outdated charts
helm -n k8gb upgrade -i k8gb chart/k8gb -f avaf-nonprod-sdc.yml
Release "k8gb" does not exist. Installing it now.
walk.go:74: found symbolic link in path: /Users/donovan/.../k8gb/deploy/crds/k8gb.absa.oss_gslbs_crd.yaml
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "udp-services" in namespace "ingress-nginx" 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 "k8gb"
make: *** [deploy-gslb-operator] Error 1
@donovanmuller donovanmuller added the bug Something isn't working label Aug 17, 2020
@donovanmuller
Copy link
Contributor Author

One workaround is to follow the Helm prompts and annotate and label the existing ConfigMap accordingly:

$ kubectl -n ingress-nginx annotate --overwrite \
  cm/udp-services meta.helm.sh/release-name=k8gb \
  meta.helm.sh/release-namespace=k8gb
configmap/udp-services annotated
$ kubectl -n ingress-nginx label --overwrite cm/udp-services \
  app.kubernetes.io/managed-by=Helm
configmap/udp-services labeled

or alternatively, you could delete the existing ConfigMap, assuming it is empty.

@ytsarev ytsarev added this to the 0.8 milestone Jan 11, 2021
@ytsarev
Copy link
Member

ytsarev commented Mar 16, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants