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

Getting Error: configmap "akv2k8s-ca" not found while upgrading AKS cluster #81

Open
sk066y opened this issue Sep 22, 2022 · 2 comments

Comments

@sk066y
Copy link

sk066y commented Sep 22, 2022

We recently upgraded our East region’s AKS cluster to latest supported version and we faced few issues and took help from Microsoft team, as suggested by Microsoft team we have updated the following changes :-

1.) We saw the issue wherein one node was not able to upgrade to version 1.22.6 due to PDP policy ,disruption allowed were zero so we took a backup and reinitiate after that all the nodes were updated.
2.) After that ingress controller pods were failing so we update the ingress version, after that ingress pods also came up.
3.) Now the MS pods are not coming up and are showing Error: configmap "akv2k8s-ca" not found. We believe While upgrading the AKS cluster our kv2k8s-ca cm file got overridden and we tried getting it back that but while upgrading we are getting this error :
$ helm upgrade -i azure-key-vault-env-injector spv-charts/azure-key-vault-env-injector --namespace extensions --wait --set webhook.logLevel=Trace --set replicaCount=1 --version 1.1.10 --set image.pullPolicy=Always --set configMapName=akv2k8s-ca
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/.kube/config
Error: failed to download "spv-charts/azure-key-vault-env-injector" at version "1.1.10

We need your suggestion and help to get the correct version of akv2k8s-cm installed.

@sk066y
Copy link
Author

sk066y commented Sep 23, 2022

Hi Git Team,
can someone look into our issue and provide some inputs?

@smauryaatt
Copy link

Hi git team, We need some help on this. We are stuck on this issue.

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

2 participants