Repository navigation
✨ add ClusterObjectDeployment controller skeleton - #3032
Merged
openshift-merge-bot[bot] merged 1 commit intoOct 20, 2026
Merged
openshift-merge-bot[bot] merged 1 commit into
openshift-merge-bot[bot] merged 1 commit into
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lay the foundation for the ClusterObjectDeployment (COD) controller in the object-controller binary, following the ClusterObjectSet (COS) controller patterns. The COD API types were introduced in operator-framework#3018; this adds the controller that will reconcile ClusterObjectDeployment objects and own ClusterObjectSets. No reconciliation behavior is implemented yet. - Add ClusterObjectDeploymentReconciler with a no-op Reconcile and RBAC markers, gated by the experimental-only //go:build !standard tag. - SetupWithManager watches ClusterObjectDeployment and Owns ClusterObjectSet, plus a Watches mapping a ClusterObjectSet's spec.group to its owning ClusterObjectDeployment so not-yet-adopted (orphan) revisions are also surfaced. - Register the COD types in the object-controller scheme and wire the reconciler into the manager, adding ClusterObjectDeployment to the manager cache. - Ship the ClusterObjectDeployment CRD in the experimental manifests via a Helm CRD wrapper. The base CRD existed (from operator-framework#3018) but was never rendered into the chart, so the manager could not start an informer for the type (ReaderFailOnMissingInformer: true) and the object-controller deployment never became ready. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Per G. da Silva <pegoncal@redhat.com>
perdasilva
force-pushed
the
cod-controller-skeleton
branch
from
October 20, 2026 08:42
0335f59 to
e96a5f8
Compare
Contributor
Author
|
adding approval after two lgtms |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-merge-bot
Bot
merged commit Oct 20, 2026
09a7363
into
operator-framework:main
35 checks passed
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
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.
Description
Lays the foundation for the
ClusterObjectDeployment(COD) controller in theobject-controllerbinary, following the existingClusterObjectSet(COS) controller patterns. The COD API types were introduced in #3018; this PR adds the controller that will reconcileClusterObjectDeploymentobjects and ownClusterObjectSets.No reconciliation behavior is implemented yet — this is intentionally just the skeleton so behavior can be layered on in follow-ups.
What's included
ClusterObjectDeploymentReconcilerwith a no-opReconcileand+kubebuilder:rbacmarkers, gated by the experimental-only//go:build !standardtag (mirroring COS).SetupWithManagerthat:ForClusterObjectDeployment,Owns(&ClusterObjectSet{})for already-owned revisions, andWatches(&ClusterObjectSet{})mappingspec.group→ClusterObjectDeploymentname, so not-yet-adopted (orphan)ClusterObjectSets also enqueue their COD. This mirrors the reference orb-operator COD controller and pre-wires future adoption behavior.TrackingCache— COD owns a known child type, so plain controller-runtime watches are the natural fit.object-controllerscheme (internal/object-controller/scheme).ClusterObjectDeploymentadded to the manager cache (cmd/object-controller/main.go).spec.group→ COD mapping.Notes
object-controllerServiceAccount binds tocluster-admin, so the markers are forward-looking/documentary here (consistent with COS).make generateandmake manifestsproduce no diff: COD deepcopy/applyconfig/CRD already exist from ✨ OPRUN-4786: Add ClusterObjectDeployment API and admission validation #3018, and COD is an experimental-channel-only CRD.Testing
go test ./internal/object-controller/...passes (incl. new tests).golangci-lintclean,go vetclean,gofmtclean.🤖 Generated with Claude Code
Summary by CodeRabbit
ClusterObjectDeploymentAPI, available with thecodshort name.ClusterObjectSetresources through configured groups.