-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
-
1. Proposed title of this feature request
Enable full automation of the must-gather tool to support reliable log collection in all OpenShift environments. See RFE-5579 for previous discussion of this requirements.
2. What is the nature and description of the request?
This request aims to enhance the must-gather tool’s automation capabilities, ensuring that it can operate independently and reliably across OpenShift clusters. Currently, must-gather does not dynamically adjust to node states, such as when nodes are in NotReady status. This limitation prevents full automation in scenarios where customers deploy OpenShift clusters in air-gapped environments, as there is no easy way to configure must-gather to bypass nodes that cannot participate in log collection.
To achieve reliable automation, the must-gather tool should be modified to detect and adapt to the readiness state of nodes, automatically excluding any that are in NotReady status or otherwise unresponsive. This will enable the tool to be run automatically without requiring manual adjustments, allowing seamless log collection and transfer to Red Hat support in cases of cluster issues.
3. Why does the customer need this? (List the business requirements here)
Our partner requires a fully automated must-gather solution to facilitate log collection in air-gapped and managed OpenShift environments, where customer interaction with the clusters is restricted. This enhancement is essential for:
•Seamless Automation: Ensures must-gather can be used in a “set-and-forget” mode, adapting dynamically to varying node states within the cluster.
•Consistent Support Readiness: Enables logs to be gathered and transmitted automatically to Red Hat support, ensuring timely response and resolution of customer issues.
•Minimal Manual Intervention: Reduces reliance on manual monitoring or configuration, which is challenging in remote or air-gapped deployments.
•Operational Efficiency: Frees up resources by avoiding scheduling attempts on nodes that are unavailable or unfit for log collection, optimizing overall cluster performance.
4. List any affected packages or components
• must-gather tool
•OpenShift
- relates to
-
RFE-5579 Ensure that the must-gather pod is not deployed on nodes marked as NotReady
- Under Review