🌱 Refactor envtest release process to update envtest index locally

[sbueringer]

Signed-off-by: Stefan Büringer [email protected]

controller-tools repo is now configured in a way that blocks creation of pull requests by actions (see https://github.com/kubernetes-sigs/controller-tools/actions/runs/12463704971).
This PR changes the process. Now it's necessary to run KUBERNETES_VERSION=v1.32.0 hack/envtest/update-envtest-releases.sh and open a PR manually

/hold
for now for further discussion. Maybe there's a better way

[sbueringer]

/assign @vincepri @chrischdi

[camilamacedo86]

/lgtm

[camilamacedo86]

/lgtm cancel

It seems OK for me, but as seen that you are looking for further options I will remove the lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 0e77f652bb54e6234cf6aaa38815b011978fc705

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, sbueringer, vincepri

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 [sbueringer,vincepri]

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

[sbueringer]

Asked in #github-management if they can allow creating PRs with GitHub actions again: https://kubernetes.slack.com/archives/C01672LSZL0/p1735546177638379

[sbueringer]

Looks like we might get a fix in Q1/Q2: kubernetes/org#5126

I'll keep this PR on hold for now (we can always use the script from this PR to update the index)

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[sbueringer]

/remove-lifecycle rotten