rename-sandbox

.github/workflows/mkdocs-strict-verify.yaml

@@ -12,8 +12,8 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# This file is automagically synced here from github.com/knative-sandbox/.github
-# repo by knobots: https://github.com/knative-sandbox/knobots and will be overwritten.
+# This file is automagically synced here from github.com/knative-extensions/.github
+# repo by knobots: https://github.com/knative-extensions/knobots and will be overwritten.
 
 name: Knative Verify
 

blog/docs/articles/eventing-rabbitmq-announcement.md

@@ -4,7 +4,7 @@
 
 **Date: 2022-07-26**
 
-We’re excited to announce that [Eventing RabbitMQ](https://github.com/knative-sandbox/eventing-rabbitmq) is now Generally Available (GA). With this milestone, the APIs provided will remain stable in future iterations.
+We’re excited to announce that [Eventing RabbitMQ](https://github.com/knative-extensions/eventing-rabbitmq) is now Generally Available (GA). With this milestone, the APIs provided will remain stable in future iterations.
 A quick start can be found [here](https://knative.dev/docs/eventing/broker/rabbitmq-broker/).
 
 # Key Features
@@ -13,19 +13,19 @@ A quick start can be found [here](https://knative.dev/docs/eventing/broker/rabbi
 
 Eventing RabbitMQ works well with RabbitMQ clusters that have been provisioned by using the [RabbitMQ Cluster Kubernetes Operator](https://github.com/rabbitmq/cluster-operator), but can also be configured to use RabbitMQ instances provisioned by other means.
 The RabbitMQ Broker and Source both contain a `rabbitmqClusterReference` field, which can either reference a RabbitMQ cluster that was created by using the Operator, or a `Secret` containing the credentials for a RabbitMQ instance.
-Full documentation can be found [here](https://github.com/knative-sandbox/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/samples/external-cluster).
+Full documentation can be found [here](https://github.com/knative-extensions/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/samples/external-cluster).
 
 ### Parallelism and event ordering
 
 RabbitMQ by default uses a first-in-first-out (FIFO) ordering mode for events. However, there can be use cases where ordering isn't required and higher throughput may be preferred.
 Both the RabbitMQ Broker and Source contain a `parallelism` annotation that can be configured to process more than one message in parallel.
-An example outlining both FIFO and high throughput modes can be found [here](https://github.com/knative-sandbox/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/samples/trigger-customizations).
+An example outlining both FIFO and high throughput modes can be found [here](https://github.com/knative-extensions/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/samples/trigger-customizations).
 
 ### Quorum queues
 
 Quorum queues are a fault tolerant, replicated queue type that are used in multi-node setups. RabbitMQ uses quorum queues by default.
 The queue type can be configured for RabbitMQ Brokers, and any Triggers subscribed to a Broker will inherit the queue type.
-Full documentation can be found [here](https://github.com/knative-sandbox/eventing-rabbitmq/tree/e6b6312a660698edf8daffa6b1c7274c1e3951a4/samples/quick-setup)
+Full documentation can be found [here](https://github.com/knative-extensions/eventing-rabbitmq/tree/e6b6312a660698edf8daffa6b1c7274c1e3951a4/samples/quick-setup)
 
 ### Metrics
 
@@ -49,12 +49,12 @@ RabbitMQSource objects can retrieve messages from a queue, convert them to Cloud
 
 ### Performance
 
-A suite of performance tests are run with each release to ensure adequate throughput and acceptable latency. The results of the latest run can be found [here](https://github.com/knative-sandbox/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/test/performance/results/release-v1.6).
+A suite of performance tests are run with each release to ensure adequate throughput and acceptable latency. The results of the latest run can be found [here](https://github.com/knative-extensions/eventing-rabbitmq/tree/49787466f88b21fe022216a13c8321b334f92dc4/test/performance/results/release-v1.6).
 
 ### Adopters
 
 Eventing RabbitMQ is currently in use by VMware Event Broker Appliance ([VEBA](https://flings.vmware.com/vmware-event-broker-appliance)), Cloud Native Runtimes ([CNR](https://docs.vmware.com/en/Cloud-Native-Runtimes-for-VMware-Tanzu/1.3/tanzu-cloud-native-runtimes/GUID-cnr-overview.html)).
 
 ### Feedback
 
-We will appreciate community feedback on trying this new release and reporting back any issues or queries that you might have. New issues can be created [here](https://github.com/knative-sandbox/eventing-rabbitmq/issues/new/choose).
+We will appreciate community feedback on trying this new release and reporting back any issues or queries that you might have. New issues can be created [here](https://github.com/knative-extensions/eventing-rabbitmq/issues/new/choose).

blog/docs/articles/from-cloudevent-to-apach-kafka-records-part-one.md

@@ -76,7 +76,7 @@ my-kafka-sink   http://kafka-sink-ingress.knative-eventing.svc.cluster.local/def
 
 At this point we could just use a pod inside the Kubernetes cluster with the `curl` program installed and send an event to the `URL` of the `KafkaSink`.
 
-However, we are instead using the [`kn` client CLI](https://github.com/knative/client) with its [event plugin](https://github.com/knative-sandbox/kn-plugin-event) for managing cloud events from command line:
+However, we are instead using the [`kn` client CLI](https://github.com/knative/client) with its [event plugin](https://github.com/knative-extensions/kn-plugin-event) for managing cloud events from command line:
 
 ```
 kn event send \

blog/docs/articles/from-cloudevent-to-apache-kafka-records-part-two.md

@@ -151,7 +151,7 @@ For `Trigger`s that are executed by a Knative Broker for Apache Kafka it is also
 
 ### Kn Event Plugin
 
-For sending an event we also do not need to make use of the Apache Kafka Producer API, since we are ingesting CloudEvents to the Broker, using HTTP. As one option we could use a `Pod` inside the Kubernetes cluster with the `curl` program installed and send an event to the `URL` of the `Broker`. However, instead we are using the [`kn` client CLI](https://github.com/knative/client) with its [event plugin](https://github.com/knative-sandbox/kn-plugin-event) for managing cloud events from command line:
+For sending an event we also do not need to make use of the Apache Kafka Producer API, since we are ingesting CloudEvents to the Broker, using HTTP. As one option we could use a `Pod` inside the Kubernetes cluster with the `curl` program installed and send an event to the `URL` of the `Broker`. However, instead we are using the [`kn` client CLI](https://github.com/knative/client) with its [event plugin](https://github.com/knative-extensions/kn-plugin-event) for managing cloud events from command line:
 
 ```
 kn event send \

blog/docs/articles/quickstart-with-knative.md

@@ -4,7 +4,7 @@
 
 **Date: 2021-09-17**
 
-We're pleased to announce that the [`quickstart` plugin](https://github.com/knative-sandbox/kn-plugin-quickstart) for the Knative client is now available. The plugin allows users to very easily set up a local Knative environment with just a single command using a local [KinD](https://kind.sigs.k8s.io/) or [minikube](https://minikube.sigs.k8s.io/) cluster.
+We're pleased to announce that the [`quickstart` plugin](https://github.com/knative-extensions/kn-plugin-quickstart) for the Knative client is now available. The plugin allows users to very easily set up a local Knative environment with just a single command using a local [KinD](https://kind.sigs.k8s.io/) or [minikube](https://minikube.sigs.k8s.io/) cluster.
 
 ```
 $ kn quickstart kind

blog/docs/articles/single-node-kafka-development.md

@@ -125,8 +125,8 @@ eventing-webhook-8db49d6cc-4f847           1/1     Running   0          2h1m
 As the next step we need to install the control- and data-plane for the Knative Kafka broker:
 
 ```bash
-kubectl apply --filename https://github.com/knative-sandbox/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-controller.yaml
-kubectl apply --filename https://github.com/knative-sandbox/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-broker.yaml
+kubectl apply --filename https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-controller.yaml
+kubectl apply --filename https://github.com/knative-extensions/eventing-kafka-broker/releases/download/knative-v1.8.4/eventing-kafka-broker.yaml
 ```
 
 Afterwards we have four new pods in our `knative-eventing` namespace, for our Knative Kafka Broker:

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

@@ -68,7 +68,7 @@ Follow the instructions in
 
 ### Apache Kafka Broker TODO-KNATIVE-VERSION
 
-<!-- Original notes are here: https://github.com/knative-sandbox/eventing-kafka-broker/releases/tag/knative-TODO-KNATIVE-VERSION -->
+<!-- Original notes are here: https://github.com/knative-extensions/eventing-kafka-broker/releases/tag/knative-TODO-KNATIVE-VERSION -->
 
 #### 💫 New Features & Changes
 
@@ -80,7 +80,7 @@ Follow the instructions in
 
 ### RabbitMQ Broker and Source TODO-KNATIVE-VERSION
 
-<!-- Original notes are here: https://github.com/knative-sandbox/eventing-rabbitmq/releases/tag/knative-TODO-KNATIVE-VERSION -->
+<!-- Original notes are here: https://github.com/knative-extensions/eventing-rabbitmq/releases/tag/knative-TODO-KNATIVE-VERSION -->
 
 
 #### 💫 New Features & Changes

blog/docs/releases/announcing-knative-v0-17-release.md

@@ -79,9 +79,9 @@ Kubernetes **1.16** remains as the minimum version.
 - [#8965](https://github.com/knative/serving/pull/8965) The default Kingress timeout is increased to 48 hours to prevent gRPC stream timeout (thanks [@tcnghia](https://github.com/tcnghia))
 - Code in knative/serving/pkg/network is completely moved to knative/networking repo (thanks [@tcnghia](https://github.com/tcnghia))
 - [#8798](https://github.com/knative/serving/pull/8798) Placeholder service's labels and annotations are propagated from Route (thanks [@nak3](https://github.com/nak3))
-- [knative-sandbox/net-istio#170](https://github.com/knative-sandbox/net-istio/pull/170) When auto TLS is enabled, now net-istio controller generates Istio TLS Gateway per Kingress instead of reconciling the knative-ingress-gateway Gateway (thanks [@ZhiminXiang](https://github.com/ZhiminXiang))
-- [knative-sandbox/net-istio#174](https://github.com/knative-sandbox/net-istio/pull/174) Kingress (net-istio) introduces RewriteHost feature (thanks [@julz](https://github.com/julz))
-- [knative-sandbox/net-istio##190](https://github.com/knative-sandbox/net-istio/pull/190) Kingress prober improvement for net-istio: probing a single host instead of every host to improve the throughput of the prober queue (thanks [@JRBANCEL](https://github.com/JRBANCEL))
+- [knative-extensions/net-istio#170](https://github.com/knative-extensions/net-istio/pull/170) When auto TLS is enabled, now net-istio controller generates Istio TLS Gateway per Kingress instead of reconciling the knative-ingress-gateway Gateway (thanks [@ZhiminXiang](https://github.com/ZhiminXiang))
+- [knative-extensions/net-istio#174](https://github.com/knative-extensions/net-istio/pull/174) Kingress (net-istio) introduces RewriteHost feature (thanks [@julz](https://github.com/julz))
+- [knative-extensions/net-istio##190](https://github.com/knative-extensions/net-istio/pull/190) Kingress prober improvement for net-istio: probing a single host instead of every host to improve the throughput of the prober queue (thanks [@JRBANCEL](https://github.com/JRBANCEL))
 </details>
 
 ### Eventing v0.17

blog/docs/releases/announcing-knative-v0-18-release.md

@@ -18,7 +18,7 @@ Follow the instructions in the documentation [Installing Knative](https://knativ
 - Kubernetes minimum version has changed to v1.17
   - See our [K8s minimum version principle](https://github.com/knative/community/blob/main/mechanics/RELEASE-VERSIONING-PRINCIPLES.md#k8s-minimum-version-principle)
 - Eventing APIs gradauted from v1beta1 to v1
-- Eventing Contribution sources are moved to a new github organization [knative-sandbox](https://github.com/knative-sandbox)
+- Eventing Contribution sources are moved to a new github organization [knative-extensions](https://github.com/knative-extensions)
 - The `kn` CLI now has alias for commands and other new features.
 
 Remember to check the [upgrade docs](https://knative.dev/docs/install/upgrade-installation/) for any concerns applicable to your current version before you upgrade to the latest version.
@@ -72,7 +72,7 @@ Remember to check the [upgrade docs](https://knative.dev/docs/install/upgrade-in
 - [knative/networking#129](https://github.com/knative/networking/pull/129),[knative/networking#132](https://github.com/knative/networking/pull/132),[knative/networking#137](https://github.com/knative/networking/pull/137) Deprecate retry, ingress.spec.visibility and ingress.status.LoadBalancer in Ingress
 - [knative/networking#107](https://github.com/knative/networking/pull/107) Rework RewriteHost to require splits.
 - [#8856](https://github.com/knative/serving/pull/8856) The `tagHeaderBasedRouting` flag in `config-network` is moved to `config-features` as `tag-header-based-routing`.
-- [knative-sandbox/net-istio#237](https://github.com/knative-sandbox/net-istio/pull/237) Add a new local gateway sharing same deployment as ingress Gateway for the future cluster local gateway deprecation
+- [knative-extensions/net-istio#237](https://github.com/knative-extensions/net-istio/pull/237) Add a new local gateway sharing same deployment as ingress Gateway for the future cluster local gateway deprecation
 
 ### Eventing v0.18
 
@@ -123,7 +123,7 @@ Eventing APIs graduated from v1beta1 to v1
 
 ### Eventing Contributions v0.18
 
-Code moved to the the [knative-sandbox](https://github.com/knative-sandbox/) Github organization
+Code moved to the the [knative-extensions](https://github.com/knative-extensions/) Github organization
 
 #### Action Required
 
@@ -148,15 +148,15 @@ Code moved to the the [knative-sandbox](https://github.com/knative-sandbox/) Git
 
 #### Code Moved to a different github organization
 
-- [#1576](https://github.com/knative/eventing-contrib/pull/1576) The AWSSQS source artifacts have moved to https://github.com/knative-sandbox/eventing-awssqs
-- [#1574](https://github.com/knative/eventing-contrib/pull/1574) The Camel artifacts have moved to https://github.com/knative-sandbox/eventing-camel
-- [#1585](https://github.com/knative/eventing-contrib/pull/1585) The Ceph source artifacts have moved to https://github.com/knative-sandbox/eventing-ceph
-- [#1583](https://github.com/knative/eventing-contrib/pull/1583) The CouchDB source artifacts have moved to https://github.com/knative-sandbox/eventing-couchdb
-- [#1573](https://github.com/knative/eventing-contrib/pull/1573) The GitHub artifacts have moved to https://github.com/knative-sandbox/eventing-github
-- [#1584](https://github.com/knative/eventing-contrib/pull/1584) The GitLab source artifacts have moved to https://github.com/knative-sandbox/eventing-gitlab
-- [#1587](https://github.com/knative/eventing-contrib/pull/1587) The Natss artifacts have moved to https://github.com/knative-sandbox/eventing-natss
-- [#1586](https://github.com/knative/eventing-contrib/pull/1586) The Prometheus source artifacts have moved to https://github.com/knative-sandbox/eventing-prometheus
-- [#1555](https://github.com/knative/eventing-contrib/pull/1555) Remove camel source from this repo. move it to https://github.com/knative-sandbox/eventing-camel
+- [#1576](https://github.com/knative/eventing-contrib/pull/1576) The AWSSQS source artifacts have moved to https://github.com/knative-extensions/eventing-awssqs
+- [#1574](https://github.com/knative/eventing-contrib/pull/1574) The Camel artifacts have moved to https://github.com/knative-extensions/eventing-camel
+- [#1585](https://github.com/knative/eventing-contrib/pull/1585) The Ceph source artifacts have moved to https://github.com/knative-extensions/eventing-ceph
+- [#1583](https://github.com/knative/eventing-contrib/pull/1583) The CouchDB source artifacts have moved to https://github.com/knative-extensions/eventing-couchdb
+- [#1573](https://github.com/knative/eventing-contrib/pull/1573) The GitHub artifacts have moved to https://github.com/knative-extensions/eventing-github
+- [#1584](https://github.com/knative/eventing-contrib/pull/1584) The GitLab source artifacts have moved to https://github.com/knative-extensions/eventing-gitlab
+- [#1587](https://github.com/knative/eventing-contrib/pull/1587) The Natss artifacts have moved to https://github.com/knative-extensions/eventing-natss
+- [#1586](https://github.com/knative/eventing-contrib/pull/1586) The Prometheus source artifacts have moved to https://github.com/knative-extensions/eventing-prometheus
+- [#1555](https://github.com/knative/eventing-contrib/pull/1555) Remove camel source from this repo. move it to https://github.com/knative-extensions/eventing-camel
 - [#3923](https://github.com/knative/eventing-contrib/pull/3923) versions of eventing.- resources from v1beta1 to v1
     - `brokers.eventing.knative.dev`
     - `triggers.eventing.knative.dev`