the kv-sidecar pod remains in CrashLoopBackOff. about vault-kubernetes-workshop HOT 2 CLOSED

This error corresponds to when there's no configuration for the Kubernetes auth method. Can you share more about what steps you took and where you got stuck?

from vault-kubernetes-workshop.

Hey. was able to sort that out, there was some problem with rbac permission, so now stuck to this. It says that the certificate is signed by unknown authority. I am using ca.crt .. That said, I have configmap and secrets configured properly already. This certificate is self-signed, hence it is showing as invalid. I have configured as shown in this slide.

kubectl get secret vault-tls

kubectl get configmap vault

https://codelabs.developers.google.com/codelabs/vault-on-gke/index.html?index=..%2F..cloud#8

kubectl logs kv-sidecar-5459db6969-228s2 vault-authenticator

019/09/25 14:08:25 failed to get successful response: &http.Response{Status:"500 Internal Server Error", StatusCode:500, Proto:"HTTP/2.0", ProtoMajor:2, ProtoMinor:0, {"errors":["Post h
ttps://<K8s_host>/apis/authentication.k8s.io/v1/tokenreviews: x509: certificate signed by unknown authority"]}

PS: The stage I'm stuck on, is same.

from vault-kubernetes-workshop.