docs: doc to access OCP endpoint via CIS

[maheshwarishikha]

Description

Issue - https://github.ibm.com/GoldenEye/issues/issues/5390
It adds steps to access api endpoint deployed in OCP via CIS.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

• When merging, use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
• Merge by using "Squash and merge".

[maheshwarishikha]

/run pipeline

[maheshwarishikha]

/run pipeline

[SirSpidey]

Is this the content that will form the solution tutorial?

If so, we probably don't need it here, but can just point to the public cloud docs tutorial when that's ready (from the main readme or an example readme).

If it's different content, can you help me understand the difference?

[maheshwarishikha]

Is this the content that will form the solution tutorial?

If so, we probably don't need it here, but can just point to the public cloud docs tutorial when that's ready (from the main readme or an example readme).

If it's different content, can you help me understand the difference?

Its a different content. Here we are not talking about SLZ, it is just to close a loop to access any endpoint via CIS. We have taken example of OpenShift. SLZ tutorials will be quite different.

[maheshwarishikha]

/run pipeline

[SirSpidey]

Hi @maheshwarishikha. Here are my suggestions to improve the task topic.

• Start with an H1 in every file, and use sequentially headings
• Break up the long series of steps with sections (and renumber).
• Provide and introduction, context to the sections, and a conclusion.
• Make sure that you have all the prereqs.
• Check for missing articles (the, a).
• Add code highlighting to code samples (all shell here).

[maheshwarishikha]

/run pipeline

[SirSpidey]

Ran this through our style checker and committed changes here. Make sure everything is still accurate.

[maheshwarishikha]

/run pipeline

[maheshwarishikha]

/run pipeline

[maheshwarishikha]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀