From 107bc3aa803b784fa40a928ac3412c1efd0c70b3 Mon Sep 17 00:00:00 2001 From: Josh Berkus Date: Sat, 14 Jun 2025 17:11:28 -0700 Subject: [PATCH 1/4] Add placeholder for 6/25 blog post Signed-off-by: Josh Berkus --- .../_posts/2025-06-16-Change-To-Kubernetes-Slack.md | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md diff --git a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md new file mode 100644 index 0000000000..f5ef72447f --- /dev/null +++ b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md @@ -0,0 +1,11 @@ +--- +layout: blog +title: "Placeholder" +date: 2025-06-16 +draft: false +slug: placeholder0625 +Author: > + [Josh Berkus](https://github.com/jberkus) +--- + +Placeholder block post while we work on the final text \ No newline at end of file From 046bddde7b51444f045237a4ed12e4e352ba92c1 Mon Sep 17 00:00:00 2001 From: Josh Berkus Date: Sun, 15 Jun 2025 22:12:04 -0700 Subject: [PATCH 2/4] Final text of Slack changes blog post. Signed-off-by: Josh Berkus --- .../2025-06-16-Change-To-Kubernetes-Slack.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md index f5ef72447f..09fa27e131 100644 --- a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md +++ b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md @@ -1,6 +1,6 @@ --- layout: blog -title: "Placeholder" +title: "Changes to Kubernetes Slack" date: 2025-06-16 draft: false slug: placeholder0625 @@ -8,4 +8,14 @@ Author: > [Josh Berkus](https://github.com/jberkus) --- -Placeholder block post while we work on the final text \ No newline at end of file +Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20. Sometime later this year, our community will likely move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can. + +For the last decade, Slack has supported our project with a free customized enterprise account. They have let us know that they can no longer do so, particularly since our Slack is one of the largest and more active ones on the platform. As such, they will be downgrading it to a standard free Slack while we decide on, and implement, other options. + +On Friday, June 20, we will be subject to the [feature limitations of free Slack] . The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations. + +Responsible channel owners, members of private channels, and members of User Groups should [take some actions](link) to prepare for the upgrade and preserve information as soon as possible. + +The CNCF Projects Staff have proposed that our community look at migrating to Discord. Because of existing issues where we have been pushing the limits of Slack, they have already explored what a Kubernetes Discord would look like. Discord would allow us to implement new tools and integrations which would help the community, such as GitHub group membership synchronization. The Steering Committee will discuss and decide on our future platform. + +Please see our [FAQ](https://github.com/kubernetes/community/blob/master/communication/slack-migration-faq.md), and check the [kubernetes-dev mailing list](https://groups.google.com/a/kubernetes.io/g/dev/) and the [#announcements channel](https://kubernetes.slack.com/archives/C9T0QMNG4) for further news. If you have specific feedback on our Slack status join the [discussion on GitHub](https://github.com/kubernetes/community/issues/8490). From cdf104814da7ca1067384c1b3f935e9daf019661 Mon Sep 17 00:00:00 2001 From: Josh Berkus Date: Sun, 15 Jun 2025 22:23:00 -0700 Subject: [PATCH 3/4] Added missing link to actions required. Signed-off-by: Josh Berkus --- content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md index 09fa27e131..3640d05265 100644 --- a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md +++ b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md @@ -14,7 +14,7 @@ For the last decade, Slack has supported our project with a free customized ente On Friday, June 20, we will be subject to the [feature limitations of free Slack] . The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations. -Responsible channel owners, members of private channels, and members of User Groups should [take some actions](link) to prepare for the upgrade and preserve information as soon as possible. +Responsible channel owners, members of private channels, and members of User Groups should [take some actions](https://github.com/kubernetes/community/blob/master/communication/slack-migration-faq.md#what-actions-do-channel-owners-and-user-group-members-need-to-take-soon) to prepare for the upgrade and preserve information as soon as possible. The CNCF Projects Staff have proposed that our community look at migrating to Discord. Because of existing issues where we have been pushing the limits of Slack, they have already explored what a Kubernetes Discord would look like. Discord would allow us to implement new tools and integrations which would help the community, such as GitHub group membership synchronization. The Steering Committee will discuss and decide on our future platform. From 5f836813d7687ae0d82aed2bda4571a98122d521 Mon Sep 17 00:00:00 2001 From: Tim Bannister <193443691+lmktfy@users.noreply.github.com> Date: Mon, 16 Jun 2025 10:00:33 +0100 Subject: [PATCH 4/4] Apply fixes from code review --- .../en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md index 3640d05265..7e7245abeb 100644 --- a/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md +++ b/content/en/blog/_posts/2025-06-16-Change-To-Kubernetes-Slack.md @@ -2,8 +2,8 @@ layout: blog title: "Changes to Kubernetes Slack" date: 2025-06-16 -draft: false -slug: placeholder0625 +canonicalUrl: https://www.kubernetes.dev/blog/2025/06/16/changes-to-kubernetes-slack-2025/ +slug: changes-to-kubernetes-slack Author: > [Josh Berkus](https://github.com/jberkus) --- @@ -12,7 +12,7 @@ Kubernetes Slack will lose its special status and will be changing into a standa For the last decade, Slack has supported our project with a free customized enterprise account. They have let us know that they can no longer do so, particularly since our Slack is one of the largest and more active ones on the platform. As such, they will be downgrading it to a standard free Slack while we decide on, and implement, other options. -On Friday, June 20, we will be subject to the [feature limitations of free Slack] . The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations. +On Friday, June 20, we will be subject to the [feature limitations of free Slack](https://slack.com/help/articles/27204752526611-Feature-limitations-on-the-free-version-of-Slack). The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations. Responsible channel owners, members of private channels, and members of User Groups should [take some actions](https://github.com/kubernetes/community/blob/master/communication/slack-migration-faq.md#what-actions-do-channel-owners-and-user-group-members-need-to-take-soon) to prepare for the upgrade and preserve information as soon as possible.