Closed carslen closed 9 months ago
According to suggested backup of kyverno policies, we do not have any deployed policies yet in any environment.
I'll first remove and reinstall Kyverno on our devsecop-testing cluster.
CORE
ArgoCDadmissionreports.kyverno.io
backgroundscanreports.kyverno.io
clusteradmissionreports.kyverno.io
clusterbackgroundscanreports.kyverno.io
clusterpolicies.kyverno.io
clusterpolicyreports.wgpolicyk8s.io
generaterequests.kyverno.io
policies.kyverno.io
policyreports.wgpolicyk8s.io
updaterequests.kyverno.io
kyverno
for safety reasons. Will be recreated during deployment of Kyverno.Next up: Update k8s-cluster-stack Helm Chart for Kyverno installation.
Kyverno 1.10.3 using Helm Chart v3.0.5 successful deployed to DevSecOps Cluster.
All Kyverno instances upgraded to Helm Chart v3.05
@carslen I tried to use Kyverno on the devsecops cluster but seems it's not operational. ArgoCD shows it failed to apply HA change.
@carslen I tried to use Kyverno on the devsecops cluster but seems it's not operational. ArgoCD shows it failed to apply HA change.
catenax-ng/k8s-cluster-stack#431
HA deployment on all environments done.
Dashboards available. LGTM :)
Kyverno needs to be upgraded to implement #105. Kyverno introduced breaking changes with version (AppVersion/Helm Chart Version) 1.10.0/3.0.0 and documentation is based on v1.10.0.
Current deployed Kyverno Version in our envs
Resources
As we've not yet deployed any policies we'll follow the recommended upgrade option 1 (uninstall - reinstall).