Feature OCPSTRAT-3156: Configurable log levels for hosted control plane components

[rutvik23]

Why

HyperShift administrators and support engineers cannot adjust log
verbosity for hosted control plane components during troubleshooting.
Standard OCP has this via operatorv1.LogLevel, but HyperShift has no
equivalent except an ad-hoc, unvalidated annotation for kube-apiserver.
This was reported as RFE-7777 and accepted as crucial for minimal
troubleshooting.

What

Enhancement proposal introducing structured per-component log level
configuration for CPO-managed components via the HostedCluster CR:

• New ComponentLogLevelSpec type with Normal/Debug/Trace/TraceAll
  enum (matching operatorv1.LogLevel)
• New optional pointer fields in OperatorConfiguration for 8 core
  control plane components
• Phased delivery: KAS first (Phase 1), remaining 7 components
  (Phase 2), all remaining CPO-managed components documented
  holistically (Phase 3)
• Deprecation path for existing kube-apiserver-verbosity-level
  annotation
• Ships ungated, GA in target release

References

• Tracking: OCPSTRAT-3156
• RFE: RFE-7777
• Implementation: CNTRLPLANE-3290
• Docs: OSDOCS-19157

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@rutvik23: This pull request references OCPSTRAT-3156 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Why

HyperShift administrators and support engineers cannot adjust log
verbosity for hosted control plane components during troubleshooting.
Standard OCP has this via operatorv1.LogLevel, but HyperShift has no
equivalent except an ad-hoc, unvalidated annotation for kube-apiserver.
This was reported as RFE-7777 and accepted as crucial for minimal
troubleshooting.

What

Enhancement proposal introducing structured per-component log level
configuration for CPO-managed components via the HostedCluster CR:

• New ComponentLogLevelSpec type with Normal/Debug/Trace/TraceAll
  enum (matching operatorv1.LogLevel)
• New optional pointer fields in OperatorConfiguration for 8 core
  control plane components
• Phased delivery: KAS first (Phase 1), remaining 7 components
  (Phase 2), all remaining CPO-managed components documented
  holistically (Phase 3)
• Deprecation path for existing kube-apiserver-verbosity-level
  annotation
• Ships ungated, GA in target release

References

• Tracking: OCPSTRAT-3156
• RFE: RFE-7777
• Implementation: CNTRLPLANE-3290
• Docs: OSDOCS-19157

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign csrwng 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:

• enhancements/hypershift/OWNERS

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