Skip to content

Allow to deploy latest openstack-operator - #136

Open
cjeanner wants to merge 1 commit into
mainfrom
example/unpin-openstack-operator
Open

cjeanner wants to merge 1 commit into
mainfrom
example/unpin-openstack-operator

Conversation

@cjeanner

Copy link
Copy Markdown
Collaborator

Replace the architecture-repo based OLM deployment with a local, self-contained component so that the openstack-operator Subscription is unpinned and tracks the cluster's own catalog.

Motivation: the previous approach pulled
openstack-k8s-operators/architecture's olm-openstack-subscriptions overlay, whose replacements hard-require the olm-values ConfigMap keys provided by example/openstack-operator/catalog (values) and pin-version (openstack-operator-version). Simply dropping pin-version therefore breaks kustomize ("fieldPath data.openstack-operator-version is missing"), and dropping the catalog resource breaks it even earlier ("nothing selected by ... data.openstack-operator-image"). There is no way to consume that overlay unpinned.

Changes:

  • Add components/dependencies/openstack-operator: a plain Component shipping the openstack-operators/openstack Namespaces, the OperatorGroup and the openstack-operator Subscription. The Subscription has no spec.startingCSV (unpinned: OLM resolves the latest CSV in the stable-v1.0 channel) and references the built-in redhat-operators CatalogSource instead of pinning a redhat-operator-index image to a specific OCP version, so the catalog always matches the cluster. Its README documents the subscribed-cluster/disconnected-mirror requirement and how to patch or overlay the component (e.g. to pin a startingCSV).
  • Slim example/openstack-operator down to the new local component plus utilities/approve-installplan; no remote component fetch remains.
  • Drop example/openstack-operator/catalog and pin-version, which only existed to feed the architecture overlay's replacements.

The rhoso-gitops validated pattern's override patches (OperatorGroup and shared Namespace removal, InstallPlan approval Job relocation) still apply: resource kinds and names are unchanged.

Validated locally with kustomize build, both standalone and with the pattern's kustomize patches applied.

Assisted-by: pi coding agent (model rits/zai-org/glm-5-3)

Replace the architecture-repo based OLM deployment with a local,
self-contained component so that the openstack-operator Subscription
is unpinned and tracks the cluster's own catalog.

Motivation: the previous approach pulled
openstack-k8s-operators/architecture's olm-openstack-subscriptions
overlay, whose replacements hard-require the olm-values ConfigMap keys
provided by example/openstack-operator/catalog (values) and pin-version
(openstack-operator-version). Simply dropping pin-version therefore
breaks kustomize ("fieldPath data.openstack-operator-version is
missing"), and dropping the catalog resource breaks it even earlier
("nothing selected by ... data.openstack-operator-image"). There is no
way to consume that overlay unpinned.

Changes:
- Add components/dependencies/openstack-operator: a plain Component
  shipping the openstack-operators/openstack Namespaces, the
  OperatorGroup and the openstack-operator Subscription. The
  Subscription has no spec.startingCSV (unpinned: OLM resolves the
  latest CSV in the stable-v1.0 channel) and references the built-in
  redhat-operators CatalogSource instead of pinning a
  redhat-operator-index image to a specific OCP version, so the
  catalog always matches the cluster. Its README documents the
  subscribed-cluster/disconnected-mirror requirement and how to patch
  or overlay the component (e.g. to pin a startingCSV).
- Slim example/openstack-operator down to the new local component plus
  utilities/approve-installplan; no remote component fetch remains.
- Drop example/openstack-operator/catalog and pin-version, which only
  existed to feed the architecture overlay's replacements.

The rhoso-gitops validated pattern's override patches (OperatorGroup
and shared Namespace removal, InstallPlan approval Job relocation)
still apply: resource kinds and names are unchanged.

Validated locally with kustomize build, both standalone and with the
pattern's kustomize patches applied.

Assisted-by: pi coding agent (model rits/zai-org/glm-5-3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant