-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.0
-
None
-
No
-
False
-
Description of problem:
The cluster-bootstrap component does not today support filtering resources by capability, featureset or cluster profile annotations, all of which are supported by CVO and other bootstrappers. We need to teach the cluster bootstrap to understand these filters to allow us to continue combing down the payload and creating clusters with a slimmer waistline. At present, no CRD that is required at bootstrap can contain a capability, nor can it vary by featureset of cluster profile. This hasn't caused many bugs yet (though we have had at least one), but as things move on, we expect this will be a ticking time bomb if we don't fix it. At present we are working around this within the render steps, but at some point, someone will need to use one of these features in combination with cluster-bootstrap, at which point they will become stuck. Until we handle the conditional on manifests consistently across components, we will be susceptible to inconsistent clusters, where manifests may get applied that are then hard to notice that they were accidentally applied.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- relates to
-
OCPBUGS-33882 Cluster Bootstrap does not account for capabilities in rendered manifests
- Closed