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.

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

Add new warning for kubernetes deb/RPM packages migration #44109

Merged
merged 2 commits into from
Dec 1, 2023
Merged

Add new warning for kubernetes deb/RPM packages migration #44109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
82665ea
update package deprecation with a warning that packages are going awa…
BenTheElder Nov 27, 2023
68047be
add a warning banner for package host shutdown
BenTheElder Nov 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/en/blog/_posts/2023-08-31-legacy-package-repository-deprecation/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,10 +100,12 @@ community-owned repositories (`pkgs.k8s.io`).

## Can I continue to use the legacy package repositories?

The existing packages in the legacy repositories will be available for the foreseeable
~~The existing packages in the legacy repositories will be available for the foreseeable
future. However, the Kubernetes project can't provide _any_ guarantees on how long
is that going to be. The deprecated legacy repositories, and their contents, might
be removed at any time in the future and without a further notice period.
be removed at any time in the future and without a further notice period.~~

**UPDATE**: The legacy packages are expected to go away in January 2024.

The Kubernetes project **strongly recommends** migrating to the new community-owned
repositories **as soon as possible**.
Expand Down
10 changes: 10 additions & 0 deletions data/announcements/scheduled.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,3 +207,13 @@ announcements:
message: |
4 days of incredible opportunities to collaborate, learn + share with the entire community!<br />
November 6 - November 9, 2023.

- name: Legacy package repositories shutdown
startTime: 2023-11-27T00:00:00
endTime: 2024-02-01T00:00:00
style: "background: #d95e00"
title: Changes to the location of Linux packages for Kubernetes
message: |
The legacy Linux package repositories (`apt.kubernetes.io` and `yum.kubernetes.io` AKA `packages.cloud.google.com`)<br/>
have been frozen starting from September 13, 2023 **and are going away in January 2024**, users *must* migrate.<br/>
Please read our [announcement](/blog/2023/08/31/legacy-package-repository-deprecation/) for more details.
Comment on lines +217 to +219
Copy link
Contributor

Choose a reason for hiding this comment

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

If we need this, can we schedule (and announce) some brownouts, where we briefly change the DNS domains to point to a simple thing returning a 5xx response?

I'd prefer to have a whole new blog article about the shutdown if needed and if feasible.

Copy link
Member Author

Choose a reason for hiding this comment

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

The *.kubernetes.io could have brownouts but there's not a lot of time left to implement this and we already urged users to switch.

The project took too long to move off of legacy rapture.

don't really have the bandwidth for a whole new post and this has all the info and already told users they should switch.

Copy link
Member Author

Choose a reason for hiding this comment

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

We also don't need the announcement if the project pivots to a static mirror but that work still isn't complete and we're cutting it terribly close at this point on warning people with a real deadline.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'll try to see what appetite the K8s infra SIG have for a smoother transition. I think lots of people like the idea, and only a few people would be willing to offer time to help.

Copy link
Member Author

@BenTheElder BenTheElder Nov 30, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

I'm concerned about the timeframe, leads from release and infra + anyone they/we looped in have known about the looming shutdown for O(months) and the need to migrate off for O(years), we only have ~1 month left to warn users in the case that a replacement is not working by then ...