-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Improvement
-
False
-
-
False
-
100% To Do, 0% In Progress, 0% Done
-
0
Feature Overview (aka. Goal Summary)
Today, when the HyperShift Operator (HO) is installed, CRDs from any supported platform are installed regardless of the intended HostedClusters (HCs) planned to be managed from the HO installation (for example, the HO installed on a mgmt cluster for ROSA HCP also installs CRDs for Azure, Kubevirt, Agent, etc.).
It would be an improvement, in the interest of kube api server (KAS) CPU/memory, to provide an optional mechanism to limit the CRDs installed when installing the HO.
Goals (aka. expected user outcomes)
A user of the HO can specify which platforms they plan to create HCs for, off of the HO installation (for example, a user can install the HO so that only AWS and Azure related CRDs are installed, a user can install the HO so that only AWS and Agent related CRDs are installed, etc.)
Requirements (aka. Acceptance Criteria):
The installation of the HO can be limited to the installation of only one or more platform related CRDs.
Upstream documentation is provided on how to use this new functionality.
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | Both |
| Classic (standalone cluster) | N/A |
| Hosted control planes | Yes |
| Multi node, Compact (three node), or Single node (SNO), or all | N/A |
| Connected / Restricted Network | N/A |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | N/A |
| Operator compatibility | N/A |
| Backport needed (list applicable versions) | N/A |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | N/A |
| Other (please specify) | N/A |
Use Cases (Optional):
- Managed services - management clusters hosting only ROSA HCPs only install CRDs related to AWS when installing the HO on the management cluster
- Self-managed services - users can limit platform related CRDs when they install the HO on their management cluster.
Questions to Answer (Optional):
None at the moment.
Out of Scope
Any API, HostedCluster, or HostedControlPlane changes.
Background
N/A
Customer Considerations
N/A
Documentation Considerations
Upstream docs will be provided by engineering.
Interoperability Considerations
ROSA HCP
ARO HCP
ACM/MCE/Self-managed
- is related to
-
OCPBUGS-50938 HyperShift generates broken deployment file
-
- Closed
-
