AshutoshNirkhe

> yes, every change should lead to an reevaluation. @frzifus we have existing user workloads (deployments) that are currently running with jaeger-agent sidecar (with v1.28). We did upgrade the jaeger...

> is there an ETA for this bug fix? We're facing the same issue Seems like they don't want us to disable those. See https://github.com/jaegertracing/helm-charts/pull/376 for details.

> lgtm @batazor appreciate if you could have a look too ?

I see there are 2 securityContext settings possible as per the current operator CRD https://github.com/jaegertracing/helm-charts/blob/main/charts/jaeger-operator/crds/crd.yaml 1. 'securityContext' present under each of the components like agent, query etc are actually podSecurityContext...

> Makes sense. We should definitely include the security settings in all of our `khcheck` specs deployed with the helm chart. > > As a workaround, you could use `helm...

> We merged in #768! > > As to address the other issue, you're right in that we should have all env vars configurable in helm. I think what we...

> This should be fixed in v2.7.0. @integrii @jonnydawg Thanks for fixing this. I had one query. Do we need to manually drop older crds and install new ones ?...

> Yes! You would have to manually wipe the CRDs unfortunately. > > The CRD changes I made from `v2.6.0` -> `v2.7.0` updates kuberhealthy CRDs to different k8s objects. Instead...

> Allowing special parameters for specific containers via map is interesting. It does have a "priority" problem... if a container could be matched by more than one key in the...

@fseldow will be great if you could take this to your team as an enhancement request, if that makes sense to you.