✨ Upgrade the k8s to 1.26.1 and controller-runtime to 0.14.2

[yashsingh74]

Upgrade the version and the respective dependencies

• k8s version from 1.26.0 to 1.26.1
• controller-runtime from 0.14.1 to 0.14.2

Fixes: #3195

[k8s-ci-robot]

Hi @yashsingh74. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[yashsingh74]

cc: @varshaprasad96

[camilamacedo86]

/ok-to-test

[camilamacedo86]

You probably need to ensure that your branch is rebase with master and run make generate to update the samples, Could you please to do that to sorted out the CI that is failing?

[yashsingh74]

I did the rebase but it doesn't show git conflicts. Also, I ran the make generate and pushed the changes.

[camilamacedo86]

/test pull-kubebuilder-test
/test pull-kubebuilder-e2e-k8s-1-23-13
/test pull-kubebuilder-e2e-k8s-1-24-7

[camilamacedo86]

/lgtm

[varshaprasad96]

Thanks for the PR @yashsingh74! Everything looks good. There is just one suggestion on bumping the controller-tools version since we haven't merged this PR yet and there is already a patch release with a bug fix in c-t (0.11.3).

[varshaprasad96]

Since we haven't merged this PR yet, and controller-tools has a v0.11.3 release (https://github.com/kubernetes-sigs/controller-tools/blob/v0.11.3/go.mod#L16) that uses k8s 1.26.1, it would be nice to bump it here too. We can do it in a follow up as well, but would be helpful to track it with a comment or an issue.

[camilamacedo86]

@varshaprasad96, I think we can do the bump in a follow up wdyt?
Shows that we also have a new controller-runtime version.

[varshaprasad96]

Sounds good!

[varshaprasad96]

I'll go ahead and merge this!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, varshaprasad96, yashsingh74

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [camilamacedo86,varshaprasad96]

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

[varshaprasad96]

The APIDiff test is expected to fail. Once the controller-tools comment is addressed, I can override the test and merge it.

[varshaprasad96]

/override go-apidiff

[k8s-ci-robot]

@varshaprasad96: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

• go-apidiff

Only the following failed contexts/checkruns were expected:

• EasyCLA
• netlify/kubebuilder/deploy-preview
• pull-kubebuilder-e2e-k8s-1-23-13
• pull-kubebuilder-e2e-k8s-1-24-7
• pull-kubebuilder-e2e-k8s-1-25-3
• pull-kubebuilder-e2e-k8s-1-26-0
• pull-kubebuilder-test
• tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override go-apidiff

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/test-infra repository.