Skip to content

fix readme and bundle script update#3277

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
mbpavan:fix-operator-bundle-build-errors
Mar 10, 2026
Merged

fix readme and bundle script update#3277
tekton-robot merged 1 commit intotektoncd:mainfrom
mbpavan:fix-operator-bundle-build-errors

Conversation

@mbpavan
Copy link
Contributor

@mbpavan mbpavan commented Mar 10, 2026

Changes

  • Enhance the current README for bundle generation on Kubernetes.

  • Enhance the bundle script to align with Community Operators CI requirements:

    1. config.yaml

      • Add/use min-kube-version so the bundle script can automatically set spec.minKubeVersion in the CSV.
      • This avoids manual edits and ensures compatibility with OperatorHub CI validation.
    2. bundle.py

      • Set spec.minKubeVersion using the value from config.yaml.
      • Add resource requests for operator containers:
        • lifecycle
        • cluster-operations
        • webhook
      • Set metadata.annotations.containerImage using the operator image (required for OperatorHub CI).

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Mar 10, 2026
@mbpavan
Copy link
Contributor Author

mbpavan commented Mar 10, 2026

/kind misc

@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. kind/misc Categorizes issue or PR as a miscellaneuous one. labels Mar 10, 2026
@mbpavan mbpavan force-pushed the fix-operator-bundle-build-errors branch from dae70bb to 9aac9d2 Compare March 10, 2026 11:34
@mbpavan
Copy link
Contributor Author

mbpavan commented Mar 10, 2026

/retest

@mbpavan mbpavan closed this Mar 10, 2026
@mbpavan mbpavan reopened this Mar 10, 2026
@jkhelil
Copy link
Member

jkhelil commented Mar 10, 2026

thanks @mbpavan
/approve

@tekton-robot
Copy link
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 Mar 10, 2026
@anithapriyanatarajan
Copy link
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@tekton-robot tekton-robot merged commit e8451e5 into tektoncd:main Mar 10, 2026
18 of 25 checks passed
@mbpavan
Copy link
Contributor Author

mbpavan commented Mar 11, 2026

/cherry-pick release-v0.79.x

@tekton-robot
Copy link
Contributor

Cherry-pick to release-v0.79.x failed!

The automatic cherry-pick to release-v0.79.x failed.

Output:

🤖 Starting cherry-pick process...
Fetching PR #3277 information...
Found merge commit: e8451e50ce0f34ce661357846319eec97b898526
PR title: fix readme and bundle script update
Fetching target branch: release-v0.79.x...
From https://github.com/tektoncd/operator
 * branch                release-v0.79.x -> FETCH_HEAD
Checking for existing cherry-pick PR...
Creating cherry-pick branch: cherry-pick-3277-to-release-v0.79.x...
Switched to a new branch 'cherry-pick-3277-to-release-v0.79.x'
branch 'cherry-pick-3277-to-release-v0.79.x' set up to track 'origin/release-v0.79.x'.
Fetching commits from PR #3277...
Found 1 commit(s) to cherry-pick
Cherry-picking commit 1/1: 9aac9d26dfa4215edc4c810dbae6c33f449b7686...
fatal: bad object 9aac9d26dfa4215edc4c810dbae6c33f449b7686
❌ ERROR: Cherry-pick failed for commit 9aac9d26dfa4215edc4c810dbae6c33f449b7686 due to conflicts or other errors

Next steps:

  • Check the action logs for complete details
  • If the PR is not merged, merge it first and try again
  • If there are conflicts, you'll need to manually cherry-pick this PR

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. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants