Drop capabilities are still wrong

[davoszabo]

Describe the bug

This fix didn't solve the issue regarding drop capabilities in release v1.18.1: #1067

Currently it needs to be updated manually after installation.

To Reproduce

Steps to reproduce the behavior:

1. Download v1.18.1 messaging-topology-operator-with-certmanager.yaml or messaging-topology-operator.yaml
2. Check the Deployment manifest
3. 'All' still present instead of 'ALL' in capabilities section
4. Unable to start pod

Expected behavior
Make sure 'All' is replace everywhere to 'ALL'.

Version and environment information

• Messaging Topology Operator: v1.18.1

[Zerpet]

Indeed, some patches were still setting a wrong security context. Thank you for reporting this issue!

[davoszabo]

Thanks for the fix! Is it possible that it will be released in the upcoming days?

[Zerpet]

We will release around mid-December. This issue has a feasible workaround, I don't think it requires an emergency release.