Conversation
Replace BuildConfig with Shipwright Build/BuildRun, install OpenShift Pipelines and Builds for OpenShift, and document the three-way git SHA pin for operator bumps. Closes #12 Co-authored-by: Cursor <cursoragent@cursor.com>
openshift-pipelines-operator-rh and builds latest channel match the redhat-operators catalog on ARO HCP 4.22. Co-authored-by: Cursor <cursoragent@cursor.com>
Build.spec.stepResources did not override the buildah strategy defaults on Builds 1.9; move CPU/memory limits to BuildRun so compile gets 2-4 CPU. Co-authored-by: Cursor <cursoragent@cursor.com>
…rces Shipwright Builds 1.9 ignores stepResources on Build/BuildRun; fork the cluster buildah strategy with 2–4 CPU and 4–8Gi for the FIPS go compile. Co-authored-by: Cursor <cursoragent@cursor.com>
Inject the service serving CA via a CABundle ConfigMap, override it on the Build, and pass --cert-dir to buildah so push to the cluster registry verifies. Co-authored-by: Cursor <cursoragent@cursor.com>
Use /tekton/creds-secrets/shipwright-registry-push/.dockerconfigjson instead of the merged creds file Tekton does not create here; add pushSecret, image- builder RBAC, and fail fast when the auth file is missing. Co-authored-by: Cursor <cursoragent@cursor.com>
Drop pushSecret; OpenShift creates shipwright-build-dockercfg for Tekton. The build strategy discovers auth under /tekton/creds-secrets/ so fresh Argo syncs need no bootstrap secret or token minting step. Co-authored-by: Cursor <cursoragent@cursor.com>
paulczar
marked this pull request as draft
September 15, 2026 05:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Status: draft spike — not merging for now
Spike for #12. BuildConfig remains the shipping path for the one-off bgp-cloud-connector operator image; it works well enough without Shipwright operator overhead.
This branch documents what it took to get Shipwright working on
aro-virt(Builds 1.9): namespacebuildah-heavystrategy, service CA injection, Tekton cred mounts, OLM catalog fixes, etc. Keeping as a draft reference if we revisit later (e.g. fleet-wide Builds platform, or Builds ≥ 1.10stepResources).Does not close #12.
Summary (spike)
Build/BuildRunfor bgp-cloud-connector operator image.BuildStrategyfork of CBSbuildah(CPU, TLS--cert-dir, SA dockercfg auth).aro-virt: BuildRun succeeded, manager Running,BGPCloudConfiguration/BGPRoutingReady.Why deferred
Test plan (completed on spike cluster)
make fmt lint testaro-virtwithGITOPS_REVISION=feat/bgp-shipwright-buildoperator:devBGPCloudConfigurationReady;BGPRoutingvirtReady