Albert van 't Hart

@raghu-nandan-bs Would be great if you can provide an`amd64` image. Let me know, so that we can test this change.

This looks good: ``` time="2023-04-13T18:06:11Z" level=debug msg="albert/rfs-test service is upto date, no need to apply changes..." service=k8s.service src="client.go:71" time="2023-04-13T18:06:11Z" level=debug msg="albert/rfs-test configmap is upto date, no need to apply changes..."...

Any update on this one?

That would be great!

Operator running with your version: ```k get deploy -o wide NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR redis-operator 1/1 1 1 4m35s redis-operator raghunandanbs/redis-operator:700e8bd ``` Operators logs confirm that...

Any update @raghu-nandan-bs @ese @samof76?

We also encountered this issue with rbac-manager 1.7.0 ``` time="2024-03-14T05:09:12Z" level=info msg=---------------------------------- time="2024-03-14T05:09:12Z" level=info msg="rbac-manager 1.7.0 running" time="2024-03-14T05:09:12Z" level=info msg=---------------------------------- time="2024-03-14T05:09:12Z" level=info msg="Registering components" time="2024-03-14T05:09:12Z" level=info msg="Watching resources related to...

Currently it is possible to set the podSecurityContext but it is not possible to set the containerSecurityContext (e.g. drop all capabilities, allowPrivilegeEscalation to false).

Thanks. Will look into this!

/kind enhancement