fix: Openshift issues

[wnevis-cmyk]

• Fixes security context issues with minio-operator
• Adds flag for openshift for grafana-operator
• Adds support for fsGroup for strimzi-operator (and underlying kafka)
  • Forces fsGroup 0 (root) for local crc deployments. Openshift should (?) automatically assign this in a regular openshift cluster
• Abstracts openshift-specific settings into a separate overlay

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f68645a-d39a-4285-a218-65a6c71d0dbf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/openShiftIssues

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[danielpanzella]

is this something the user should be setting directly? it feels like a value we should be choosing.

[wnevis-cmyk]

No, you're right, it shouldn't be. It should be set to 0 if it's an openshift deployment, and nil if not (at least, that's what worked in my dev environment).

[wnevis-cmyk]

I've gone ahead and removed that from the API. Instead, I'm setting it via an environment variable which is configured via the overlay I'm using to push the podSecurityContext info for the controller-manager. Is that a better approach?