OCPBUGS-98986: [4.20] Stabilize telemetry config to prevent continuous console pod rollouts

[sg00dwin]

Summary

Backport of #1173 to release-4.20.

• OCPBUGS-90370: Stabilize telemetry config to prevent continuous console pod rollouts
• OCPBUGS-87348: Make GetAccessToken graceful when cloud.openshift.com is absent

The telemetry configuration was producing different ConfigMap key sets depending on telemeter-client availability, causing the operator to continuously reconcile the ConfigMap and trigger rolling console pod restarts.

Cherry-pick notes

• TestDeploymentProgressingByGeneration test dropped (from OCPBUGS-64688, not backported to 4.20)
• All telemetry tests included (4.20 has GetOrganizationMeta and rate-limit vars)

Test plan

• go build ./... passes
• go vet passes on changed packages
• Test compilation succeeds for changed packages
• CI e2e tests pass

/jira:cherrypick OCPBUGS-90370

🤖 Generated with Claude Code

[openshift-ci-robot]

@sg00dwin: This pull request references Jira Issue OCPBUGS-98986, which is invalid:

• expected the bug to target the "4.20.z" version, but no target version was set
• expected dependent Jira Issue OCPBUGS-97828 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead
• expected dependent Jira Issue OCPBUGS-97828 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead

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:

Summary

Backport of #1173 to release-4.20.

• OCPBUGS-90370: Stabilize telemetry config to prevent continuous console pod rollouts
• OCPBUGS-87348: Make GetAccessToken graceful when cloud.openshift.com is absent

The telemetry configuration was producing different ConfigMap key sets depending on telemeter-client availability, causing the operator to continuously reconcile the ConfigMap and trigger rolling console pod restarts.

Cherry-pick notes

• TestDeploymentProgressingByGeneration test dropped (from OCPBUGS-64688, not backported to 4.20)
• All telemetry tests included (4.20 has GetOrganizationMeta and rate-limit vars)

Test plan

• go build ./... passes
• go vet passes on changed packages
• Test compilation succeeds for changed packages
• CI e2e tests pass

/jira:cherrypick OCPBUGS-90370

🤖 Generated with Claude Code

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.

[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: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5a35d89b-60f5-4a9e-8844-e73d5cbfea33

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

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sg00dwin
Once this PR has been reviewed and has the lgtm label, please assign spadgett for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sg00dwin]

/jira refresh

[openshift-ci-robot]

@sg00dwin: This pull request references Jira Issue OCPBUGS-98986, which is invalid:

• expected dependent Jira Issue OCPBUGS-97828 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead
• expected dependent Jira Issue OCPBUGS-98987 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
• expected dependent Jira Issue OCPBUGS-97828 to target a version in 4.21.0, 4.21.z, but it targets "4.22.0" instead
• expected dependent Jira Issue OCPBUGS-98987 to target a version in 4.21.0, 4.21.z, 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.

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.

[openshift-ci]

@sg00dwin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-console	ec58675	link	true	/test e2e-aws-console

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.