Skip to content

updating kubebuilder to 4.10.1#7021

Open
acornett21 wants to merge 1 commit intooperator-framework:masterfrom
acornett21:update_kubebuilder
Open

updating kubebuilder to 4.10.1#7021
acornett21 wants to merge 1 commit intooperator-framework:masterfrom
acornett21:update_kubebuilder

Conversation

@acornett21
Copy link
Contributor

Description of the change:

Motivation for the change:
To keep K8s and scaffolding updated

Checklist

If the pull request includes user-facing changes, extra documentation is required:

Signed-off-by: Adam D. Cornett <adc@redhat.com>
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 19, 2026
@camilamacedo86
Copy link
Contributor

Hi @acornett21

Any reason for we not get this merged?
It is marked as WIP
But is really missing something?

@acornett21
Copy link
Contributor Author

/lifecycle frozen

@openshift-ci
Copy link

openshift-ci bot commented Feb 19, 2026

@acornett21: The lifecycle/frozen label cannot be applied to Pull Requests.

Details

In response to this:

/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@acornett21
Copy link
Contributor Author

@camilamacedo86 This does not have the ansible changes with it,

Which is blocked by k8s python library issue(s) mentioned in the above. It doesn't seem they are doing a backport, or it's taking very long. 🤷🏻

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 3, 2026
@openshift-merge-robot
Copy link

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants