Closed jacobwoffenden closed 3 years ago
Hi @jacobwoffenden,
You need to delete kubemod-crt-job
before re-applying (or upgrading) KubeMod’s manifests.
Please see instructions here: https://github.com/kubemod/kubemod#upgrade
This is necessary because re-deploying the KubeMod resources, such as web hooks configurations, wipes out the TLS certs, but the job that generates the certs won’t restart if it’s already there and is in “complete” state. Note that the job is the only resource you need to delete before re-applying KubeMod manifests.
Cool, thanks @vassilvk! I'd ignored that because I wasn't upgrading KubeMod
Hey đź‘‹
I'm currently working on an Ansible role to bootstrap a Kubernetes cluster, and I've come across an issue while reapplying the KubeMod manifest, it seems to break it's TLS.
I am applying a copy of https://raw.githubusercontent.com/kubemod/kubemod/v0.13.0/bundle.yaml and then deploying some rules, however if I reapply the bundle.yml and then my rules, I get the following
This is the output of reapplying bundle.yml
After a reapply, I cannot see any change in the
kubemod-crt-job
podAnd finally, here are the logs from
kubemod-operator
podTo remedy this, I just delete the resources created by bundle.yml and reinstall.
I just wanted to check if I'm doing something wrong
Kubernetes Version 1.21.3