Updates slack URLs to CNCF instance (#5392)

* updates slack URLs to CNCF instance

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

* updates

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

* rest of the slack urls

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

* listing slack channels

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

* can't spell

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>

README.md

@@ -74,7 +74,7 @@ To help you get started, see the following resources:
 
 ### Getting help
 
-- [#docs on the Knative Slack](https://slack.knative.dev) -- The #docs channel
+- [#knative-documentation on the CNCF Slack](https://cloud-native.slack.com/archives/C04LY5G9ED7) -- The #knative-documentation channel
   is the best place to go if you have questions about making changes to the
   documentation. We're happy to help!
 
@@ -93,7 +93,7 @@ of the website pages, or by directly opening an
 If you have a question that you can't find an answer to, we would also like to
 hear about that too. In addition to our docs, you can also reach out to the
 community for assistance. For example, ask a documentation specific question on
-the `#docs` channel in [Slack](https://knative.slack.com/).
+the `#knative-documentation` channel in [Slack](https://cloud-native.slack.com/archives/C04LY5G9ED7).
 
 Also see the [Knative community resource pages](https://knative.dev/docs/community/)
 for a list of all the available community resources, including links to the

_index.html

@@ -91,7 +91,7 @@ title = "Knative"
 					</div>
 					<h4 >Talk to us on Slack</h4>
 					<p>
-						<a class="text-white" href="https://slack.knative.dev/">
+						<a class="text-white" href="https://slack.cncf.io/">
 							<button type="button" class="btn btn-secondary" style="width:150px; margin-top: 12px;">Talk</button>
 						</a>
 					</p>

blog/docs/articles/highlighting-value-knative-c-suite.md

@@ -139,7 +139,7 @@ Knative Eventing expands the possibilities for event-driven architecture. Applic
 <li><b>Conformance</b> Knative is now conformant, meaning that the latest version has validation tools available. It does what it says it can do and it can prove it.
 <li><b><a href="https://knative.dev/docs/about/case-studies/deepc/">Case Studies</a></b> Read about organizations using Knative, from platform developers to proven companies to innovative startups.
 <li><b><a href="https://knative.dev/docs/getting-started">View the getting started guide</a></b> to get up and running with Knative in an afternoon
-<li><b><a href="https://slack.knative.dev">Join the Knative Slack</a></b> to talk to the community.
+<li><b><a href="https://slack.cncf.io">Join the CNCF Slack</a></b> to talk to the community on the `#knative` channel.
 </ul>
 
 </td>

blog/docs/releases/_template-announcing-knative-v1-X-release.txt

@@ -138,5 +138,5 @@ Knative is an open source project that anyone in the [community](https://knative
 - [Knative Development Mailing List](https://groups.google.com/forum/#!forum/knative-dev)
 - Knative on Twitter [@KnativeProject](https://twitter.com/KnativeProject)
 - Knative on [StackOverflow](https://stackoverflow.com/questions/tagged/knative)
-- Knative [Slack](https://slack.knative.dev)
+- Knative [Slack](https://slack.cncf.io)
 - Knative on [YouTube](https://www.youtube.com/channel/UCq7cipu-A1UHOkZ9fls1N8A)

blog/mkdocs.yml

@@ -83,7 +83,7 @@ extra:
       link: https://github.com/knative/community
       name: Knative Community on Github
     - icon: fontawesome/brands/slack
-      link: https://slack.knative.dev
+      link: https://slack.cncf.io
       name: Slack
   # TODO: Replace with https://github.com/mkdocs/mkdocs/pull/2267 once mkdocs 1.2 is out.
   version_warning: !!python/object/apply:os.getenv ["VERSION_WARNING"]

contribute-to-docs/README.md

@@ -31,7 +31,7 @@
 You don't need to read the whole style guide before contributing to Knative documentation.
 Unpolished contributions delivered early are better than perfect contributions delivered late.
 
-If you notice gaps in the style guide or have queries, please post in [the Docs Slack channel](https://knative.slack.com/archives/C9CV04DNJ).
+If you notice gaps in the style guide or have queries, please post in [the #knative-documentation Slack channel](https://cloud-native.slack.com/archives/C04LY5G9ED7).
 
 - [Documenting code](style-guide/documenting-code.md)
 - [Formatting standard and conventions](style-guide/style-and-formatting.md)

contribute-to-docs/getting-started/README.md

@@ -1,7 +1,7 @@
 # Getting started contributing to Knative docs
 
 This folder contains information you need to get started contributing to Knative documentation.
-If you have any questions, contact us on the [#docs channel on Knative Slack](https://slack.knative.dev).
+If you have any questions, contact us on the [#knative-documentation channel on CNCF Slack](https://cloud-native.slack.com/archives/C04LY5G9ED7).
 We're happy to help!
 
 Table of contents:

contribute-to-docs/getting-started/becoming-a-contributor.md

@@ -57,7 +57,7 @@ Knative documentation:
 
 ## Get help from the community
 
-- [#docs on the Knative Slack](https://slack.knative.dev) -- The #docs channel
+- [#knative-documentation on the CNCF Slack](https://cloud-native.slack.com/archives/C04LY5G9ED7) -- The #docs channel
   is the best place to go if you have questions about making changes to the
   documentation. We're happy to help!
 

contribute-to-docs/getting-started/github-workflow.md

@@ -124,8 +124,8 @@ Here's what generally happens after you send the PR for review:
       clarity, and organization standards (see the [Knative style guide](../style-guide/README.md)).
 
 We appreciate contributions to the docs, so if you open a PR we will help you
-get it merged. You can also post in the `#docs`
-[Slack channel](https://knative.slack.com/) to get input on your ideas or find
+get it merged. You can also post in the `#knative-documentation`
+[Slack channel](https://cloud-native.slack.com/archives/C04LY5G9ED7) to get input on your ideas or find
 areas to contribute before creating a PR.
 
 
@@ -197,4 +197,4 @@ and instead the errors are related to timeouts, try re-running the test at a lat
 There are running tasks that could result in timeouts or rate limiting if your test runs at the same
 time.
 
-* Other Issues/Unsure -- reach out in the #docs Slack channel and someone will be happy to help out.
+* Other Issues/Unsure -- reach out in the `#knative-documentation` Slack channel and someone will be happy to help out.

contribute-to-docs/style-guide/README.md

@@ -5,7 +5,7 @@ This folder contains the style guidelines for the Knative documentation.
 You don't need to read the whole style guide before contributing to Knative documentation.
 Unpolished contributions delivered early are better than perfect contributions delivered late.
 
-If you notice gaps in the style guide or have queries, please post in [the Docs Slack channel](https://knative.slack.com/archives/C9CV04DNJ).
+If you notice gaps in the style guide or have queries, please post in [the #knative-documentation Slack channel](https://cloud-native.slack.com/archives/C04LY5G9ED7).
 
 Table of contents:
 

contribute-to-docs/what-to-contribute/creating-blog-posts.md

@@ -12,7 +12,7 @@ This section covers documentation, processes, and roles for the [Knative blog](h
 
 ## Contact
 
-- Slack: [#docs](https://knative.slack.com/archives/C9CV04DNJ)
+- Slack: [#knative-documentation](https://cloud-native.slack.com/archives/C04LY5G9ED7)
 
 ## Submit a Post
 
@@ -27,7 +27,7 @@ To submit a blog post:
 1. Update the navigation files as described on the [Updating the Blog](https://github.com/knative/docs/blob/main/blog/README.md) page.
 1. Open a pull request (PR) for your blog post.
 1. A reviewer is assigned to all pull requests automatically. The reviewer checks your submission, and works with you on feedback and final details. When the pull request is approved, the blog will be scheduled for publication.
-1. Ping editorial team members on Slack [#docs](https://knative.slack.com/archives/C9CV04DNJ) channel with a link to your recently created PR.
+1. Ping editorial team members on Slack [#knative-documentation](https://cloud-native.slack.com/archives/C04LY5G9ED7) channel with a link to your recently created PR.
 
 ## Blog Guidelines
 

docs/community/README.md

@@ -27,9 +27,9 @@ community repo](https://github.com/knative/community/tree/main/ADOPTERS.MD).
 
 ## Questions
 
-For the fastest response, you can ask questions on the [`#general`, `#serving`,
-`#eventing`, or `#functions` channels of the Knative
-Slack](https://slack.knative.dev/).
+For the fastest response, you can ask questions on the [`#knative`, `#knative-serving`,
+`#knative-eventing`, or `#knative-functions` channels of the CNCF
+Slack](https://slack.cncf.io/).
 
 We also have a [Stack Overflow topic,
 `knative`](https://stackoverflow.com/questions/tagged/knative) (as well as
@@ -68,7 +68,16 @@ and following us on [Twitter](https://twitter.com/KnativeProject).
 
 ## Communication Channels
 
-Much of the community meets on [the Knative Slack](https://slack.knative.dev/).
+Much of the community meets on [the CNCF Slack](https://slack.cncf.io/), using the following channels:
+* [#knative](https://cloud-native.slack.com/archives/C04LGHDR9K7): Geenral discussion about Knative usage
+* [#knative-contributors](https://cloud-native.slack.com/archives/C04LN0620E8): General discussion channel for folks contributing to the Knative project in any capacity
+* [#knative-documentation](https://cloud-native.slack.com/archives/C04LY5G9ED7): Knative documentation and website user experience
+* [#knative-eventing](https://cloud-native.slack.com/archives/C04LMU33V1S): Discussion for Knative Eventing
+* [#knative-productivity](https://cloud-native.slack.com/archives/C04LY4M2G49): Discussion around Knative integration with test infrastructure, Prow and other tooling on GitHub
+* [#knative-release](https://cloud-native.slack.com/archives/C04LY4Y3EHF): Coordinating and managing Knative releases
+* [#knative-security](https://cloud-native.slack.com/archives/C04LGJ0D5FF): Discussion area for security issues affecting Knative components
+* [#knative-serving](https://cloud-native.slack.com/archives/C04LMU0AX60): Discussion area for Knative Serving and related areas (networking / autoscaling)
+
 
 We also have user
 ([`knative-users@googlegroups.com`](https://groups.google.com/forum/#!forum/knative-users))

docs/community/contributing.md

@@ -75,7 +75,7 @@ Discussion and help from your fellow users.
 - [Knative developers group](https://groups.google.com/forum/#!forum/knative-dev)
 Discussion and help from Knative developers.
 
-- [Knative Slack](https://slack.knative.dev):
+- [Knative Slack](https://slack.cncf.io):
 Ping @serving-help or @eventing-help if you run into issues using Knative Serving
 or Eventing and chat with other project developers. See also the [Knative Slack guidelines](https://github.com/knative/community/blob/main/SLACK-GUIDELINES.md).
 

docs/community/governance.md

@@ -91,7 +91,7 @@ contains events that provide the opportunity to learn more about Knative and mee
 Events don't have to be organized by the Knative project to be added to the calendar.
 If you want to add an event to the calendar please send an email to
 [knative-steering@googlegroups.com](mailto:knative-steering@googlegroups.com)
-or post to the #community channel in the Knative [Slack](https://slack.knative.dev) workspace.
+or post to the `#knative` channel in the CNCF [Slack](https://slack.cncf.io) workspace.
 
 <iframe src="https://calendar.google.com/calendar/embed?src=knative.team_9q83bg07qs5b9rrslp5jor4l6s%40group.calendar.google.com&ctz=America%2FLos_Angeles" style="border: 0" width="800" height="600" frameborder="0" scrolling="no"></iframe>
 

docs/eventing/custom-event-source/custom-event-source/README.md

@@ -5,7 +5,7 @@ If you want to create a custom event source for a specific event producer type,
 This type of integration requires more effort than using some simpler integration types, such as [SinkBinding](../sinkbinding/README.md) or [ContainerSource](../containersource/README.md); however, this provides the most polished result and is the easiest integration type for users to consume. By providing a custom resource definition (CRD) for your source rather than a general container definition, it is easier to expose meaningful configuration options and documentation to users and hide implementation details.
 
 !!! note
-    If you have created a new event source type that is not a part of the core Knative project, you can open a pull request to add it to the list of [Third-Party Sources](../../sources/#third-party-sources), and announce the new source in one of the [Knative Slack](https://slack.knative.dev/) channels.
+    If you have created a new event source type that is not a part of the core Knative project, you can open a pull request to add it to the list of [Third-Party Sources](../../sources/#third-party-sources), and announce the new source in the [#knative-eventing Slack channel](https://cloud-native.slack.com/archives/C04LMU33V1S).
 
     You can also add your event source to the [`knative-sandbox`](https://github.com/knative-sandbox) organization, by following the instructions to [create a sandbox repository](https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md).
 

docs/getting-started/next-steps.md

@@ -2,7 +2,7 @@
 
 This topic provides a list of resources to help you continue your Knative journey.
 
-[![Knative Slack Link](images/slack-button.svg)](https://slack.knative.dev/){target=_blank}
+[![Knative Slack Link](images/slack-button.svg)](https://slack.cncf.io/){target=_blank}
 
 ## :test_tube: Knative samples
 

docs/serving/app-security/security-guard-about.md

@@ -42,7 +42,7 @@ Security-Guard can also be configured to operate in other modes of operation, su
 * Move from auto learning to manual micro-rules management after the initial learning period
 * Block requests/responses when they do not conform to the micro-rules
 
-For more information or for troubleshooting help, see the [#security](https://knative.slack.com/archives/CBYV1E0TG) channel in Knative Slack.
+For more information or for troubleshooting help, see the [#knative-security](https://cloud-native.slack.com/archives/C04LGJ0D5FF) channel in Knative Slack.
 
 ## Security-Guard Use Cases
 

mkdocs.yml

@@ -74,7 +74,7 @@ extra:
       link: https://github.com/knative/community
       name: Knative Community on Github
     - icon: fontawesome/brands/slack
-      link: https://slack.knative.dev
+      link: https://slack.cncf.io
       name: Slack
   # TODO: Replace with https://github.com/mkdocs/mkdocs/pull/2267 once mkdocs 1.2 is out.
   version_warning: !!python/object/apply:os.getenv ["VERSION_WARNING"]