Skip to content

Update schedule.yaml and eol.yaml for v1.33 - #56364

Open
azlkiniue wants to merge 1 commit into
kubernetes:mainfrom
azlkiniue:patch-1
Open

Update schedule.yaml and eol.yaml for v1.33#56364
azlkiniue wants to merge 1 commit into
kubernetes:mainfrom
azlkiniue:patch-1

Conversation

@azlkiniue

Copy link
Copy Markdown

Description

Remove EOL 1.33 from schedule.yaml and add it to eol.yaml with final patch release 1.33.13.

Issue

None

Remove EOL 1.33 from schedule.yaml and add it to eol.yaml with final patch release 1.33.13.
@linux-foundation-easycla

linux-foundation-easycla Bot commented Jul 2, 2026

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: azlkiniue / name: Ahmada Yusril (bd4ed21)

@kubernetes-prow kubernetes-prow Bot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jul 2, 2026
@kubernetes-prow

Copy link
Copy Markdown
Contributor

Welcome @azlkiniue!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@kubernetes-prow kubernetes-prow Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 2, 2026
@kubernetes-prow
kubernetes-prow Bot requested a review from lmktfy July 2, 2026 11:24
@kubernetes-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nate-double-u for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@kubernetes-prow kubernetes-prow Bot added the area/release-eng Issues or PRs related to the Release Engineering subproject label Jul 2, 2026
@kubernetes-prow kubernetes-prow Bot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Jul 2, 2026
@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit bd4ed21
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/6a464a7233ae780009cf1e94
😎 Deploy Preview https://deploy-preview-56364--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@kubernetes-prow kubernetes-prow Bot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Jul 2, 2026
@Caesarsage

Copy link
Copy Markdown
Contributor

Thank you @azlkiniue

checking: is this data updated using the "schedule-builder" tool mentioned at the top of the file?

It is important it is used

@azlkiniue

Copy link
Copy Markdown
Author

Thank you for checking @Caesarsage. I tried the schedule-builder tool in current main branch but the result is not changing anything. Therefore this change was done manually.
image
Is this actually an intended result?

@azlkiniue

Copy link
Copy Markdown
Author

I have a new finding @Caesarsage. If I checkout to main branch before this PR #56216, the schedule-builder correctly moved 1.33 to eol.yaml. Is this a bug in that tool because the next release was not set?
image

@Caesarsage

Copy link
Copy Markdown
Contributor

I have a new finding @Caesarsage. If I checkout to main branch before this PR #56216, the schedule-builder correctly moved 1.33 to eol.yaml. Is this a bug in that tool because the next release was not set? image

Could it be that PR did not update the file with the tool and that's what caused the drifts ?

@azlkiniue

Copy link
Copy Markdown
Author

I have a new finding @Caesarsage. If I checkout to main branch before this PR #56216, the schedule-builder correctly moved 1.33 to eol.yaml. Is this a bug in that tool because the next release was not set?

Could it be that PR did not update the file with the tool and that's what caused the drifts ?

That is a possibility, but I'm not sure about that since this is my first ever contribution.

@palnabarun

Copy link
Copy Markdown
Member

There is no reason for #56216 to also update eol.yaml as at that point in time (before end of June) when the PR was merged, 1.33 was still not EOL.

@azlkiniue

Copy link
Copy Markdown
Author

@lmktfy @SayakMukhopadhyay could you please review this PR? Currently schedule-builder cannot move release v1.33 to eol.yaml due to a bug I tried to fix in kubernetes/release#4462, therefore in the meantime this should be done manually.

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

Labels

area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/release Categorizes an issue or PR as relevant to SIG Release. 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