Prevent regenerating signing_key in kiali ConfigMap

1

I was able to upgrade from Istio 1.4.3 to 1.6.4. Now, I am working on CI/CD pipeline for any new changes in Istio resources.

So, I generate manifest files using istioctl manifest generate -f IstioOperator.yaml, and then push them up to main branch; CI/CD detects new changes and run istioctl manifest generate again. Since signing_key in kiali ConfigMap is always re-generated, my CI/CD keeps on running because it detects new change.

Is there a way to stop regenerating this signing_key in kiali ConfigMap? I see this ticket in kiali-operator github, but I don’t know how to implement it in IstioOperator.

I appreciate any helps, pointers or suggestions.

-Laurentius

2

I was able to configure this by using K8sObjectOverlay.

Detail information can be found here, and the example.