Skip to content

chore: add openshift csv patching#828

Open
gpontejos-cs wants to merge 1 commit into
CrowdStrike:mainfrom
gpontejos-cs:openshift-csv-patching
Open

chore: add openshift csv patching#828
gpontejos-cs wants to merge 1 commit into
CrowdStrike:mainfrom
gpontejos-cs:openshift-csv-patching

Conversation

@gpontejos-cs

Copy link
Copy Markdown
Contributor

No description provided.

@gpontejos-cs gpontejos-cs marked this pull request as draft June 27, 2026 00:16
@gpontejos-cs gpontejos-cs force-pushed the openshift-csv-patching branch from 2a20d45 to 3b22e24 Compare July 7, 2026 16:51
@gpontejos-cs gpontejos-cs requested a review from mr-jungchoi July 7, 2026 16:56
@gpontejos-cs gpontejos-cs marked this pull request as ready for review July 7, 2026 16:56
@gpontejos-cs gpontejos-cs force-pushed the openshift-csv-patching branch from 9f6e6d1 to f2453fe Compare July 8, 2026 19:39
@redhatrises

Copy link
Copy Markdown
Contributor

You might be able to use kustomize and operator-sdk commands for some of this:

Patch Notes
SCC clusterPermissions (patch-openshift-scc.yaml) operator-sdk generates clusterPermissions from config/rbac roles. Add the securitycontextconstraints/use rule to a ClusterRole and it folds in — no CSV patch needed at all.
repository / support / valid-subscription annotations Belong in the CSV base (config/manifests/bases/*.clusterserviceversion.yaml) or a kustomize patch.
spec.skips (patch-openshift-skips.yaml) Static list → CSV base.
Channel annotations (alpha → certified-1.0) operator-sdk generate bundle --channels=certified-1.0 --default-channel=certified-1.0. The sed on annotations.yaml is avoidable.
spec.replaces Kustomize patch or CSV base (value still comes from PREVIOUS_VERSION).

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.

2 participants