OCPBUGS-122257: Discover OAuth route before generating cert in HCP OAuth procedure

[Patrickdsa00]

Rework the "Configuring OAuth server certificates for a hosted cluster" procedure so it no longer relies on a misleading placeholder hostname:

• Remove the api-custom-cert-sample-hosted.sample-hosted.example.com placeholder, which implied the OAuth route lives on the API endpoint domain. The route is served on the management cluster's apps wildcard domain, consistent with the HyperShift documentation.
• Reorder the steps so the OAuth route is discovered and stored in OAUTH_HOST before the test certificate is generated, so the certificate SAN uses the correct hostname and no certificate regeneration is needed.
• Normalize placeholder names to the module's convention (<management_cluster_name>, <base_domain>).
• Export OAUTH_HOST, add the missing shell prompt, fix the "kubconfig" typo, and clean up trailing whitespace.

Version(s):
4.20, 4.21, and 4.22

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-122257

Link to docs preview:

QE review:

• QE has approved this change.

[openshift-ci-robot]

@Patrickdsa00: This pull request references Jira Issue OCPBUGS-122257, which is invalid:

• expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Rework the "Configuring OAuth server certificates for a hosted cluster" procedure so it no longer relies on a misleading placeholder hostname:

• Remove the api-custom-cert-sample-hosted.sample-hosted.example.com placeholder, which implied the OAuth route lives on the API endpoint domain. The route is served on the management cluster's apps wildcard domain, consistent with the HyperShift documentation.
• Reorder the steps so the OAuth route is discovered and stored in OAUTH_HOST before the test certificate is generated, so the certificate SAN uses the correct hostname and no certificate regeneration is needed.
• Normalize placeholder names to the module's convention (<management_cluster_name>, <base_domain>).
• Export OAUTH_HOST, add the missing shell prompt, fix the "kubconfig" typo, and clean up trailing whitespace.

Version(s):
4.20, 4.21, and 4.22

Issue:
https://redhat.atlassian.net/browse/OCPBUGS-122257

Link to docs preview:

QE review:

• QE has approved this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @Patrickdsa00. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Patrickdsa00]

/jira refresh

[openshift-ci-robot]

@Patrickdsa00: This pull request references Jira Issue OCPBUGS-122257, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.