Skip to content
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.

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

Promote arm64-linux to Tier 1 #2647

Open
ameukam opened this issue Oct 21, 2024 · 10 comments
Open

Promote arm64-linux to Tier 1 #2647

ameukam opened this issue Oct 21, 2024 · 10 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@ameukam
Copy link
Member

ameukam commented Oct 21, 2024

What would you like to be added:

Ensure arm64-linuxis promoted to Tier 1.

Why is this needed:

@ameukam ameukam added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Oct 21, 2024
@ameukam
Copy link
Member Author

ameukam commented Oct 21, 2024

@ameukam
Copy link
Member Author

ameukam commented Oct 21, 2024

@kubernetes/release-managers Do we still need specific tests for this ?

@saschagrunert
Copy link
Member

@kubernetes/release-managers Do we still need specific tests for this ?

I would say so, yes. The question is where do we draw the baseline? We could define a minimum set of tests which need to run on the platform directly in kubernetes/website#48457

@ameukam
Copy link
Member Author

ameukam commented Oct 21, 2024

Equivalent master-blocking prowjobs (mostly conformance and build) running on aarch64 hardware as a starter ?

@saschagrunert
Copy link
Member

Equivalent master-blocking prowjobs (mostly conformance and build) running on aarch64 hardware as a starter ?

Yes this sounds like a great start!

@xmudrii
Copy link
Member

xmudrii commented Oct 21, 2024

+1, that sounds like a great start!

@mkumatag
Copy link
Member

Right now, the arm64 conformance job is listed only in informing and not in blocking. (Is it mature enough for blocking? If yes, then promote it.)

Additionally, I don’t see any unit test runs for this platform.

The next step could be to identify the gaps and address them.

@saschagrunert
Copy link
Member

@mkumatag we have to follow the procedure outlined in https://github.com/kubernetes/sig-release/blob/master/release-blocking-jobs.md#promoting-or-demoting-jobs to promote a job :)

@saschagrunert
Copy link
Member

Let's hold on this for our ongoing discussion in https://docs.google.com/document/d/1QnT2LJ1dNYFyvOCt_X6F8ry0KgAg8H2MjoZnt5Xgtog/edit?tab=t.0

@ameukam
Copy link
Member Author

ameukam commented Dec 6, 2024

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

5 participants