Skip to content

fix(bundle): drop duplicate MulticlusterProxyAAE CRD (release-v0.79.x) - #4217

Merged
tekton-robot merged 1 commit into
tektoncd:release-v0.79.xfrom
jkhelil:fix/SRVKP-14944-drop-duplicate-multicluster-crd-release-v0.79.x
Oct 8, 2026
Merged

tekton-robot merged 1 commit into
tektoncd:release-v0.79.xfrom
jkhelil:fix/SRVKP-14944-drop-duplicate-multicluster-crd-release-v0.79.x

Conversation

@jkhelil

@jkhelil jkhelil commented Oct 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove stale OpenShift bundle CRD operator.tekton.dev_multiclusterproxyaaes.yaml that duplicates operator.tekton.dev_tektonmulticlusterproxyaaes.yaml (tektonmulticlusterproxyaaes.operator.tekton.dev).
  • OLMv1 rejects bundles with duplicate CRD definitions (see SRVKP-14944).
  • Same cleanup already landed on main in Rename TektonScheduler to TektonKueue #3809.

Test plan

  • Confirm OpenShift release-artifacts/bundle/manifests has exactly one CRD file for tektonmulticlusterproxyaaes.operator.tekton.dev
  • Bundle / OLMv1 install no longer reports duplicate CRD for MulticlusterProxyAAE

…undle

The OpenShift OLM bundle shipped both
operator.tekton.dev_multiclusterproxyaaes.yaml and
operator.tekton.dev_tektonmulticlusterproxyaaes.yaml, which define the
same CRD name tektonmulticlusterproxyaaes.operator.tekton.dev. OLMv1
rejects such bundles.

Keep the controller-gen CRD and drop the stale hand-written duplicate.
Matches the cleanup already on main (tektoncd#3809).

Related: SRVKP-14944

Signed-off-by: Jawed khelil <[email protected]>
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 8, 2026
@jkhelil

jkhelil commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

/release-note-none

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 8, 2026
@jkhelil

jkhelil commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

/approve

@tekton-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 8, 2026
@pratap0007

Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 8, 2026
@jkhelil

jkhelil commented Oct 8, 2026

Copy link
Copy Markdown
Member Author

/retest

@tekton-robot
tekton-robot merged commit d7c7b8a into tektoncd:release-v0.79.x Oct 8, 2026
18 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants