-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
Expose configuration for parameters in-cluster that require changes in control-plane
-
False
-
False
-
To Do
-
Impediment
-
0% To Do, 0% In Progress, 100% Done
-
0
-
0
-
0
Problem
Global configuration such as APIServer arguments, FeatureGates, OAuth, etc. are exposed in a standalone OCP cluster through cluster-scoped CRs.
Out of these, components that are available in the guest cluster but require changes n the control-plane are important to expose on the API. For example:
- Builds
- Cluster build config specifics some git http proxy
- Control plane config OCM config is updated in response
- git HTTP proxy info
- Networking
- Image
- OperatorHub
- Project
- Proxy
DoD
A minimum set of configuration paraters for in-cluster components should be configurable in HyperShift.
1.
|
QE Tracker |
|
Closed | 
|
Jie Zhao |
2.
|
TE Tracker |
|
Closed |
|
Unassigned |
3.
|
Docs Tracker |
|
Closed |
|
Unassigned |
