1. Proposed title of this feature request:

Enable Configuration of Control Plane Component Log Levels in Hypershift HostedCluster CR

2. What is the nature and description of the request?

This is a request for a new feature enhancement for Hypershift/Hosted Control Plane (HCP). Currently, there is no supported method to increase the log verbosity (logLevel) for core OpenShift and Kubernetes control plane components directly through the HostedCluster Custom Resource. While this is a standard and straightforward procedure in a traditional OCP cluster using oc patch commands on operator resources, this capability is absent in the Hypershift architecture.

The request is to introduce a mechanism within the HostedCluster API to allow administrators to define and modify the log levels for these essential components like kube-apiserver, openshift-apiserver, etcd, kube-controller-manager,openshift-controller-manager, kube-scheduler etc. mirroring the functionality available in standard OCP. 

3. Why does the customer need this? (List the business requirements here)

• Accelerated Troubleshooting and Reduced Mean Time to Resolution (MTTR): The primary business need is to empower support engineers and administrators to diagnose issues more efficiently. Detailed logs are often the only way to understand obscure failures or incorrect behavior. Lacking this ability leads to longer investigation cycles and potentially extended service degradation or outages.
• Proactive Problem Identification: By temporarily increasing log verbosity, teams can proactively gather more data about component behavior in pre-production environments or during maintenance windows, helping to identify potential issues before they impact production.
• Improved Root Cause Analysis (RCA): Access to granular logs is fundamental for performing accurate and thorough root cause analysis. This ensures that fixes are effective and prevents the recurrence of issues, which is a critical requirement for maintaining stable and reliable production environments.
• Operational Parity with Standard OCP: Customers expect a consistent operational experience across different OpenShift deployment models. The absence of this basic debugging tool in Hypershift creates an operational gap, increasing the training burden and complexity for teams managing both traditional and hosted clusters.
• Enhanced Security Auditing and Analysis: While audit logging is separate, higher verbosity in component logs can sometimes provide correlational data that is useful for security investigations, helping to understand the sequence of events leading up to a security-relevant action.

4. List any affected packages or components.

HostedControlPlanes