Incorrect Kyverno Key Pair Names
Bug
Description
I've been seeing these errors on the Kyverno pods in PBOPs staging environments:
kyverno-pre main.go:135 "msg"="failed to fetch root CA secret" "error"="secrets "kyverno-svc.kyverno.svc.kyverno-tls-ca" not found" "name"="kyverno-svc.kyverno.svc.kyverno-tls-ca" kyverno-pre main.go:144 "msg"="failed to fetch TLS Pair secret" "error"="secrets "kyverno-svc.kyverno.svc.kyverno-tls-pair" not found" "name"="kyverno-svc.kyverno.svc.kyverno-tls-pair"
and it's likely because the secret created has an extra kyverno in the name; on the cluster we have kyverno-kyverno-svc.kyverno.svc.kyverno-tls-ca and kyverno-kyverno-svc.kyverno.svc.kyverno-tls-pair
BigBang Version
1.56