Skip to content

Automatically fetch latest pre-release k8s version #1074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 28, 2025
Merged

Automatically fetch latest pre-release k8s version #1074

merged 1 commit into from
Aug 28, 2025

Conversation

erjavaskivuori
Copy link
Member

Fetch the latest pre-release Kubernetes version for a specified minor version. This is to require less manual changes.

@metal3-io-bot metal3-io-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 25, 2025
@erjavaskivuori
Copy link
Member Author

/test ?

@metal3-io-bot
Copy link
Collaborator

@erjavaskivuori: The following commands are available to trigger required jobs:

/test check-prow-config

/test markdownlint

/test metal3-ubuntu-e2e-integration-test-main

/test shellcheck

/test spellcheck

The following commands are available to trigger optional jobs:

/test metal3-bml-integration-test-centos

/test metal3-centos-e2e-basic-test-main

/test metal3-centos-e2e-basic-test-release-1-10

/test metal3-centos-e2e-basic-test-release-1-8

/test metal3-centos-e2e-basic-test-release-1-9

/test metal3-centos-e2e-capi-md-test-main

/test metal3-centos-e2e-feature-test-main-features

/test metal3-centos-e2e-feature-test-main-pivoting

/test metal3-centos-e2e-feature-test-main-remediation

/test metal3-centos-e2e-feature-test-release-1-10-features

/test metal3-centos-e2e-feature-test-release-1-10-pivoting

/test metal3-centos-e2e-feature-test-release-1-10-remediation

/test metal3-centos-e2e-feature-test-release-1-8-features

/test metal3-centos-e2e-feature-test-release-1-8-pivoting

/test metal3-centos-e2e-feature-test-release-1-8-remediation

/test metal3-centos-e2e-feature-test-release-1-9-features

/test metal3-centos-e2e-feature-test-release-1-9-pivoting

/test metal3-centos-e2e-feature-test-release-1-9-remediation

/test metal3-centos-e2e-integration-k8s-pre-release-test-main

/test metal3-centos-e2e-integration-test-main

/test metal3-centos-e2e-integration-test-release-1-10

/test metal3-centos-e2e-integration-test-release-1-8

/test metal3-centos-e2e-integration-test-release-1-9

/test metal3-ci-image-building

/test metal3-dev-env-integration-test-centos-main

/test metal3-dev-env-integration-test-centos-release-1-10

/test metal3-dev-env-integration-test-centos-release-1-8

/test metal3-dev-env-integration-test-centos-release-1-9

/test metal3-dev-env-integration-test-ubuntu-main

/test metal3-dev-env-integration-test-ubuntu-release-1-10

/test metal3-dev-env-integration-test-ubuntu-release-1-8

/test metal3-dev-env-integration-test-ubuntu-release-1-9

/test metal3-e2e-1-29-1-30-upgrade-test-main

/test metal3-e2e-1-29-1-30-upgrade-test-release-1-10

/test metal3-e2e-1-29-1-30-upgrade-test-release-1-8

/test metal3-e2e-1-29-1-30-upgrade-test-release-1-9

/test metal3-e2e-clusterctl-upgrade-test-main

/test metal3-e2e-clusterctl-upgrade-test-release-1-10

/test metal3-e2e-clusterctl-upgrade-test-release-1-8

/test metal3-e2e-clusterctl-upgrade-test-release-1-9

/test metal3-e2e-conformance-test-main

/test metal3-fullstack-build

/test metal3-node-image-building

/test metal3-ubuntu-e2e-basic-test-main

/test metal3-ubuntu-e2e-basic-test-release-1-10

/test metal3-ubuntu-e2e-basic-test-release-1-8

/test metal3-ubuntu-e2e-basic-test-release-1-9

/test metal3-ubuntu-e2e-capi-md-test-main

/test metal3-ubuntu-e2e-feature-test-main-features

/test metal3-ubuntu-e2e-feature-test-main-pivoting

/test metal3-ubuntu-e2e-feature-test-main-remediation

/test metal3-ubuntu-e2e-feature-test-release-1-10-features

/test metal3-ubuntu-e2e-feature-test-release-1-10-pivoting

/test metal3-ubuntu-e2e-feature-test-release-1-10-remediation

/test metal3-ubuntu-e2e-feature-test-release-1-8-features

/test metal3-ubuntu-e2e-feature-test-release-1-8-pivoting

/test metal3-ubuntu-e2e-feature-test-release-1-8-remediation

/test metal3-ubuntu-e2e-feature-test-release-1-9-features

/test metal3-ubuntu-e2e-feature-test-release-1-9-pivoting

/test metal3-ubuntu-e2e-feature-test-release-1-9-remediation

/test metal3-ubuntu-e2e-integration-k8s-pre-release-test-main

/test metal3-ubuntu-e2e-integration-test-release-1-10

/test metal3-ubuntu-e2e-integration-test-release-1-8

/test metal3-ubuntu-e2e-integration-test-release-1-9

Use /test all to run the following jobs that were automatically triggered:

check-prow-config

shellcheck

In response to this:

/test ?

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.

@erjavaskivuori
Copy link
Member Author

/test metal3-centos-e2e-integration-k8s-pre-release-test-main
/test metal3-ubuntu-e2e-integration-k8s-pre-release-test-main

@erjavaskivuori erjavaskivuori force-pushed the erja/autom-latest-k8s-pre-release branch from 2e00d0f to dd46c1b Compare August 26, 2025 06:12
@erjavaskivuori
Copy link
Member Author

/test metal3-centos-e2e-integration-k8s-pre-release-test-main
/test metal3-ubuntu-e2e-integration-k8s-pre-release-test-main

@metal3-io-bot
Copy link
Collaborator

metal3-io-bot commented Aug 26, 2025 •
edited
Loading

@erjavaskivuori: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
metal3-centos-e2e-integration-k8s-pre-release-test-main dd46c1b link false /test metal3-centos-e2e-integration-k8s-pre-release-test-main
metal3-ubuntu-e2e-integration-k8s-pre-release-test-main dd46c1b link false /test metal3-ubuntu-e2e-integration-k8s-pre-release-test-main

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@erjavaskivuori erjavaskivuori force-pushed the erja/autom-latest-k8s-pre-release branch from dd46c1b to 78be147 Compare August 26, 2025 06:41
@erjavaskivuori
Automatically fetch latest pre-release k8s version
e4cd939 
Fetch the latest pre-release k8s version for
a spesified minor version.

Signed-off-by: erjavaskivuori <erja.vaskivuori@est.tech>
@erjavaskivuori erjavaskivuori force-pushed the erja/autom-latest-k8s-pre-release branch from 78be147 to e4cd939 Compare August 26, 2025 10:26
@erjavaskivuori
Copy link
Member Author

erjavaskivuori commented Aug 26, 2025 •
edited
Loading

Since the pipeline changes can't be tested by running the tests from here, I have these two runs where I tested the pipeline changes by replacing the pipeline with my changes:

Centos just failed in post steps because of nohup issue

@erjavaskivuori
Copy link
Member Author

/cc @Sunnatillo

@adilGhaffarDev
Copy link
Member

Since the pipeline changes can't be tested by running the tests from here, I have these two runs where I tested the pipeline changes by replacing the pipeline with my changes:

Is this going to be a periodic or just a PR test?
I don't think we need this as periodic. We will run this test only when the k8s release cycle is in the pre-release phase.

Otherwise nice work
/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@erjavaskivuori
Copy link
Member Author

Is this going to be a periodic or just a PR test? I don't think we need this as periodic. We will run this test only when the k8s release cycle is in the pre-release phase.

We discussed this elsewhere already, but as a summary; the periodic is already there but we can discuss again if that is needed.

@Sunnatillo
Copy link
Member

Since the pipeline changes can't be tested by running the tests from here, I have these two runs where I tested the pipeline changes by replacing the pipeline with my changes:

Is this going to be a periodic or just a PR test? I don't think we need this as periodic. We will run this test only when the k8s release cycle is in the pre-release phase.

Otherwise nice work /lgtm

I agree with Adil here, we need this test only when new Kubernetes pre-releases are available. After GA release, we do not have to run. My suggestion to keep it in periodic table, and make it to run manually. Anyhow we need to set minor release version on new test, right?

Sunnatillo
Sunnatillo approved these changes Aug 28, 2025
View reviewed changes
Copy link
Member

@Sunnatillo Sunnatillo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Sunnatillo

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:

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

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2025
@Sunnatillo
Copy link
Member

/override metal3-ubuntu-e2e-integration-test-main

@metal3-io-bot
Copy link
Collaborator

@Sunnatillo: Overrode contexts on behalf of Sunnatillo: metal3-ubuntu-e2e-integration-test-main

In response to this:

/override metal3-ubuntu-e2e-integration-test-main

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.

@metal3-io-bot metal3-io-bot merged commit 3a89eea into metal3-io:main Aug 28, 2025
7 checks passed
@metal3-io-bot metal3-io-bot deleted the erja/autom-latest-k8s-pre-release branch August 28, 2025 08:40
@adilGhaffarDev
Copy link
Member

Since the pipeline changes can't be tested by running the tests from here, I have these two runs where I tested the pipeline changes by replacing the pipeline with my changes:

Is this going to be a periodic or just a PR test? I don't think we need this as periodic. We will run this test only when the k8s release cycle is in the pre-release phase.
Otherwise nice work /lgtm

I agree with Adil here, we need this test only when new Kubernetes pre-releases are available. After GA release, we do not have to run. My suggestion to keep it in periodic table, and make it to run manually. Anyhow we need to set minor release version on new test, right?

yes we can keep it in periodic and not run it, I am ok with that.

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

@adilGhaffarDev adilGhaffarDev Awaiting requested review from adilGhaffarDev

@tuminoid tuminoid Awaiting requested review from tuminoid

1 more reviewer

@Sunnatillo Sunnatillo Sunnatillo approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@erjavaskivuori @metal3-io-bot @adilGhaffarDev @Sunnatillo