Synchronize automatically kube-proxy images

[juanluisvaladas]

Reason for PR:

Currently the build-kube-proxy-images.yml workflow must be triggered manually, this PR automates that task so that it's made automatically for every new version. We only check versions starting on 1.33 because it's the oldest maintained branch.

This was tested here: https://github.com/juanluisvaladas/sig-windows-tools/actions/runs/22623814294/job/65555151567#step:4:62

In this test we can see the images for 1.35 not being triggered because they existed from previous execution runs and we see the workflows dispatched for the missing images.

Requirements

• Sqaush commits
• Documentation
• Tests

Notes:

Tested manually and I don't think docs are required for this change.

[k8s-ci-robot]

Welcome @juanluisvaladas!

It looks like this is your first PR to kubernetes-sigs/sig-windows-tools 🎉. 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-sigs/sig-windows-tools 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. 😃

[juanluisvaladas]

This logic is a direct translation from test-kube-proxy-images.ps1

[juanluisvaladas]

This shouldn't be necessary, but I added it to prevent rate limiting just in case. I don't know if rate limiting is a real potential issue but the cost is mininal anyway.

[marosset]

@juanluisvaladas - Can you disable the cron schedule for https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/.github/workflows/test-kube-proxy-images.yaml too?

We can keep the workflow around for a few weeks but it shouldn't be needed with these changes!

[zylxjtu]

/lgtm, just wondering if we will need to add clean up the old version of kubeproxy images? the doc hub we used is a free plan so it might have strict quota limitation?

[marosset]

/lgtm, just wondering if we will need to add clean up the old version of kubeproxy images? the doc hub we used is a free plan so it might have strict quota limitation?

I believe the quota is for image pulls and not image storage.
If we do need to add some sort of image cleanup I think it is OK to do that as a follow-up PR

[zylxjtu]

/lgtm, just wondering if we will need to add clean up the old version of kubeproxy images? the doc hub we used is a free plan so it might have strict quota limitation?

I believe the quota is for image pulls and not image storage. If we do need to add some sort of image cleanup I think it is OK to do that as a follow-up PR

agree

[zylxjtu]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: juanluisvaladas, zylxjtu

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:

• OWNERS [zylxjtu]

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

[juanluisvaladas]

@juanluisvaladas - Can you disable the cron schedule for https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/.github/workflows/test-kube-proxy-images.yaml too?

We can keep the workflow around for a few weeks but it shouldn't be needed with these changes!

Hey, sure I'm out of office but I'll do it next week.