-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Ans : Enable readinessEndpoint validation of the Red Hat registry proxy resource (Cluster Network Operator) (registry.redhat.io)
2. What is the nature and description of the request?
Ans : The Cluster Network Operator started failing in May/June due to a change in the HTTP response from the Red Hat registry (registry.redhat.io) from 200 to 404. This occurred because a readinessEndpoint was configured on the proxy resource with its URL. In fact, this error led to the creation of this KB article: https://access.redhat.com/solutions/7129841. This KB article does not address the initial readinessEndpoint configuration with the Red Hat registry configured, which is a requirement for our organization, as we need to verify the availability of this registry using the proxy configured in the environment.
3. Why does the customer need this? (List the business requirements here)
Ans : It is necessary to verify the availability of access to the Red Hat registry via proxy in a restricted environment.
4. List any affected packages or components.
Ans : Degraded status in the Cluster Network Operator (due to a failure in the readinessEndpoint property of the proxy resource).