doc(openshift): rework structure

[leiicamundi]

Description

This PR adds documentation for configuring Ingress for Camunda 8 deployment on OpenShift. It provides instructions for both using Kubernetes Ingress and OpenShift Routes, along with prerequisites and considerations for each method. This documentation aims to guide users in exposing Camunda 8 services externally and ensuring proper setup for ingress components.

This work is related to https://github.com/camunda/team-infrastructure-experience/issues/239

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[christinaausley]

@leiicamundi I ran an npm run format to resolve most of the formatting errors flagged 👍 Before I do a complete review, is this still in draft because there are additional changes incoming?

[leiicamundi]

Hello @christinaausley,

Thank you for running the linter. The PR was in draft because it needed some adjustments.

It is now ready for review (cc @Langleu).

Please note that the change in the versions referenced as supported in the documentation is related to the versions we are now testing, linked to camunda/camunda-platform-helm#1816. For versions 4.12 and 4.13, support ends according to https://access.redhat.com/support/policy/updates/openshift on July 17, 2024 (Maintenance support ends) for 4.12 and November 17, 2024 for 4.13 : we do not have tested them since a while but we continue to support them until the indicated EOL.

[Langleu]

should we be more specific on sed?
The one on mac can be very different to whatever one find on e.g. debian.

[Langleu]

haven't tried it out yet whether it works the same on both mac and linux as the mac sed can be limited. Meaning maybe it doesn't matter too much.

[Langleu]

just tried it out, with mac sed it doesn't do anything not even throw an error and the values were still present.
On debian / Linux whatever gnu sed, worked correctly.

[leiicamundi]

Thanks for catching this @Langleu!

I've suggested a fix in camunda/camunda-platform-helm#1970, but it won't be effective until the next release of the Helm chart. Should we add a tooltip indicating that this feature will only work from the next release of our chart?

Additionally, I propose an alternative approach to eliminate the need for the post-render script altogether by utilizing a flag in the source control configuration (SCC) to remove the attribute. This would simplify the process for end-users, as demonstrated in the provided example here.

Should we explore in the flag-based solution? (cc @maxdanilov @hamza-m-masood)

[maxdanilov]

From my perspective camunda/camunda-platform-helm#1970 released would be the right approach.

[Langleu]

I like the tab approach 👍.
I only had look at next as I assume 8.5 is just copy / paste.
Left some comments but overall looks a lot cleaner!

[akeller]

Looks like this is in good shape, re-requesting a review from @conceptualshark to prep for merging!