-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Break apart the kubernetes test tarball #714
Comments
/sig testing |
/stage beta |
Hey @ixdy 👋! I'm Naomi, a v1.14 docs release shadow. Does this enhancement require any new docs (or modifications)? Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions! |
It doesn't look like |
kubernetes/kubernetes#74065 has merged. |
So how exactly is now the URL to get the linux-amd64.tar release 1.14 ? |
@OlegLoewen I don't fully understand what you are asking. The release tarballs for 1.14 are in the same location as in previous releases, i.e. in the The difference starting in 1.14 is that there are also platform-specific tarballs for the tests, e.g. there's a |
Hello @ixdy , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly. /milestone clear |
@kacole2 there aren't really alpha/beta/stable stages for this change. The split test tarballs were implemented and the mondo test tarball was marked deprecated in v1.14, but no changes are planned for v1.15. |
/assign @ixdy |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale It's unlikely we're going to move this forward for v1.16. The next step would be removing the mondo tarball. At most I will announce its deprecation more loudly in anticipation of removing it in v1.17 |
/milestone v1.17 |
👋 @spiffxp -- 1.17 Enhancements lead here. I know there isn't really a direct alpha/beta/stable mapping for this Enhancement, but I wanted to check in and see if you think it'd be graduating or major work being done in 1.17? The current release schedule is:
Thanks! |
yes, 1.16 didn't happen, but I'd like to remove the mondo test tarball completely for 1.17. |
Thanks for the quick reply. I'll go ahead and add it to the tracking sheet 👍 |
kubernetes/kubernetes#83093 removes the deprecated mondo test tarball. |
I'm one of the v1.17 docs shadows. If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, Nov 8th, it can just be a placeholder PR at this time. Let me know if you have any questions! Thanks! |
@ixdy I believe this enhancement is autoclosed since the PR is merged. We still need this to be open. Can you please confirm if this enhancement requires docs? |
I don't think any docs changes are necessary. This pretty much only affects contributors, not end users, and likely most contributors won't notice this change at all. |
I don't see any references to the test tarball in k/website or k/community, so nothing to do here, I think. |
@ixdy Awesome! Thank you for the quick update |
/close |
@ixdy: Closing this issue. In response to this:
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/test-infra repository. |
Enhancement Description
kubernetes-test.tar.gz
which contained test binaries for all platforms is now deprecated. Test binaries are now distributed in platform-specific tarballs (such askubernetes-test-linux-amd64.tar.gz
).Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
The text was updated successfully, but these errors were encountered: