You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This adds `manifests/experimental.yaml`
The difference between the experimental manifest and the standard
manifest is the presence of the experimental CRD vs the standard CRD
(as of right now there is only a difference in annotations), and the
feature-gated components.
This change supports defining feature components in _exactly_ one place:
* GA'd features are put into `components/base/common`
* Feature-Gated/Experimental/TechPreview features are put into `components/base/experimental`
This adds new components to make constructing the overlays easier:
`components/base/common` includes everything but CRDs and experimental features:
* `base/catalog` (but not CRDs)
* `base/operator-controller` (but not CRDs)
* `base/common`
* GA'd features (currently none)
`components/base/standard` adds the standard CRD:
* `component/base/common` component
* standard CRDs
`components/base/experimental` includes the experimental CRDs and features:
* `component/base/common` component
* experimental CRDs
* experimental (non-GA'd) features:
- `components/features/synthetic-user-permissions`
- `components/features/webhook-provider-certmanager`
- `components/features/webhook-provider-openshift-serviceca`
By necessity, this removes the crd from the `config/base/.../kustomization.yaml`
files. These `kustomization.yaml` files define the namespace and prefix
for resources, so we need to continue to reference them. Since the CRDs
do not have a namespace, and do not use the prefix, the `crd` directory
can be removed.
Fix the basic-olm overlay to use the new standard component
Add new `run-experimental` target, to run with the experimental manifest.
This is part of the feature-gated API functionality.
Signed-off-by: Todd Short <tshort@redhat.com>
0 commit comments