Benjamin Merot

I believe problem has been there all along. Forced to delete the Pods once in a while to ensure renewal process gets triggered.

BTW: If this is in an OCP cluster (@jpkrohling's test is vanilla K8s), Red Hat doesn't support DaemonSet Jaeger strategy, only side car injection. Was told that it was to...

I experience something similar while running the Jaeger Operator v 1.17.3 in OCP 4.3. If a Pod with the Jaeger sidecar also happens to have the Istio sidecar. Even with...

@starchx as I mentioned, the problem is that the module does not clean after itself if at some point it already created the file. So setting the value to false...

I wouldn't mind helping but Go isn't my strong suit and currently none of the rules are conditional so fixing this requires a new logic in the code.

Hey @crayfishx, your exec resource in profile.pp should have a unique name.

It's misleading to have a "zabbix_version" param but to only use it for setting the Yum repo then install the package with an "ensure" value coming from "zabbix::agent::zabbix_package_state".

@miksonx , that sounds like a Puppet problem (not the Zabbix module) parsing the output of the Yum provider. Even with manual upgrade working for you, I'd check the output...

I see a [suggestion](https://github.com/redhat-cop/keepalived-operator/issues/68#issuecomment-852398885) to not put KeepalivedGroup CRs in the same Namespace as the operator but that doesn't clarify any of the questions above. And yet the [README](https://github.com/redhat-cop/keepalived-operator/blob/master/README.md?plain=1#L152) gives...

Better documentation would also prevent running in this situation flagged in https://github.com/redhat-cop/keepalived-operator/issues/59