Add document for installing NGF on OpenShift through OperatorHub

[shaun-nx]

Proposed changes

This change adds a new page to the NGF Install section on how to install the NGF on OpenShift using the RedHat Operator Hub.

This guide also includes Operator specific configurations as well as troubleshooting.

Closes nginx/nginx-gateway-fabric#3911

Checklist

Before sharing this pull request, I completed the following checklist:

• I read the Contributing guidelines
• My branch adheres to the Git conventions
• My content changes adhere to the F5 NGINX Documentation style guide
• If my changes involve potentially sensitive information¹, I have assessed the possible impact
• I have waited to ensure my changes pass tests, and addressed any discovered issues

Footnotes

1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩

[github-actions]

✅ Deploy Preview will be available once build job completes!

Name	Link
😎 Deploy Preview	https://frontdoor-test-docs.nginx.com/previews/docs/1332/

---

[shaun-nx]

Changing the base branch to main as we need to wait until we have fully published the Operator to Openshift before making this doc available

[salonichf5]

mentioned a couple of nits but overall looks good. I think this branch needs a rebase with main

great job 🥳

[tataruty]

Changing the base branch to main as we need to wait until we have fully published the Operator to Openshift before making this doc available

Did you change base branch too? or only the aim of merge? I see many commits difference

[ADubhlaoich]

Broadly speaking, the new page needs to be restructured.

It doesn't adhere to our contemporary page standards:

• It's missing the documentation metadata
• The requirements section is not named correctly
• It uses the NGF three letter acronym: we do not use TLAs in public-facing documentation
• It uses bash as a formatting language, when shell has been the norm for months
• It doesn't use Hugo for list enumeration

Many of the structural issues could have been avoided by using Hugo archetypes, for which we maintain documentation which is part of the Contributing guidelines as the first item in the PR checklist.

Effectively no commits on this branch adhere to the Git conventions as the second item in the PR checklist, though this does not need to be fixed in retrospect as long as the eventual merge message is correct.

[JTorreG]

I have addressed everything except this in Slack.
leaving this one for @ADubhlaoich

The requirements section is not named correctly

This document doesn't have a requirements section at all, so it's not clear what you mean by this. Should we have a requirements section?

[ADubhlaoich]

LGTM!

[JTorreG]

Approved in principle, assuming the erroneous nd-docs value is removed

Changes made