diff --git a/.github/workflows/mkdocs-strict-verify.yaml b/.github/workflows/mkdocs-strict-verify.yaml index 23a0268f46..85365ad0a1 100644 --- a/.github/workflows/mkdocs-strict-verify.yaml +++ b/.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 diff --git a/blog/docs/articles/eventing-rabbitmq-announcement.md b/blog/docs/articles/eventing-rabbitmq-announcement.md index d148dbb68e..989c129665 100644 --- a/blog/docs/articles/eventing-rabbitmq-announcement.md +++ b/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,7 +49,7 @@ 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 @@ -57,4 +57,4 @@ Eventing RabbitMQ is currently in use by VMware Event Broker Appliance ([VEBA](h ### 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). diff --git a/blog/docs/articles/from-cloudevent-to-apach-kafka-records-part-one.md b/blog/docs/articles/from-cloudevent-to-apach-kafka-records-part-one.md index 790374d1ad..ab6c7d8944 100644 --- a/blog/docs/articles/from-cloudevent-to-apach-kafka-records-part-one.md +++ b/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 \ diff --git a/blog/docs/articles/from-cloudevent-to-apache-kafka-records-part-two.md b/blog/docs/articles/from-cloudevent-to-apache-kafka-records-part-two.md index 51c1d6ace1..1d59841cbe 100644 --- a/blog/docs/articles/from-cloudevent-to-apache-kafka-records-part-two.md +++ b/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 \ diff --git a/blog/docs/articles/quickstart-with-knative.md b/blog/docs/articles/quickstart-with-knative.md index 617bd4a3b1..4e228733b4 100644 --- a/blog/docs/articles/quickstart-with-knative.md +++ b/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 diff --git a/blog/docs/articles/single-node-kafka-development.md b/blog/docs/articles/single-node-kafka-development.md index 8a86bb2893..67080328d3 100644 --- a/blog/docs/articles/single-node-kafka-development.md +++ b/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: diff --git a/blog/docs/releases/_template-announcing-knative-v1-X-release.txt b/blog/docs/releases/_template-announcing-knative-v1-X-release.txt index a86b808476..4aca0e92c9 100644 --- a/blog/docs/releases/_template-announcing-knative-v1-X-release.txt +++ b/blog/docs/releases/_template-announcing-knative-v1-X-release.txt @@ -68,7 +68,7 @@ Follow the instructions in ### Apache Kafka Broker TODO-KNATIVE-VERSION - + #### πŸ’« New Features & Changes @@ -80,7 +80,7 @@ Follow the instructions in ### RabbitMQ Broker and Source TODO-KNATIVE-VERSION - + #### πŸ’« New Features & Changes diff --git a/blog/docs/releases/announcing-knative-v0-17-release.md b/blog/docs/releases/announcing-knative-v0-17-release.md index 5387d6d66f..511f0258fd 100644 --- a/blog/docs/releases/announcing-knative-v0-17-release.md +++ b/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)) ### Eventing v0.17 diff --git a/blog/docs/releases/announcing-knative-v0-18-release.md b/blog/docs/releases/announcing-knative-v0-18-release.md index 1cea89c86d..03398d01e7 100644 --- a/blog/docs/releases/announcing-knative-v0-18-release.md +++ b/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` diff --git a/blog/docs/releases/announcing-knative-v0-19-release.md b/blog/docs/releases/announcing-knative-v0-19-release.md index 3051c07776..4522d59c3c 100644 --- a/blog/docs/releases/announcing-knative-v0-19-release.md +++ b/blog/docs/releases/announcing-knative-v0-19-release.md @@ -97,52 +97,52 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### Eventing Kafka Broker v0.19 -Release Notes for [eventing-kafka-broker](https://github.com/knative-sandbox/eventing-kafka-broker) +Release Notes for [eventing-kafka-broker](https://github.com/knative-extensions/eventing-kafka-broker) **Actions Required (pre-upgrade)** - Run `kubectl delete configmap -n knative-eventing kafka-broker-brokers-triggers` 🚨 Breaking -- Default replication factor is 3 (1 previously) ([#375](https://github.com/knative-sandbox/eventing-kafka-broker/pull/375)) +- Default replication factor is 3 (1 previously) ([#375](https://github.com/knative-extensions/eventing-kafka-broker/pull/375)) πŸ’« New Features & Changes -- `eventing-kafka.yaml` can be used to install Broker and KafkaSink. ([#367](https://github.com/knative-sandbox/eventing-kafka-broker/pull/367)) -- Data plane pods expose server and client metrics in Prometheus format. ([#231](https://github.com/knative-sandbox/eventing-kafka-broker/pull/231) [#244](https://github.com/knative-sandbox/eventing-kafka-broker/pull/244)) +- `eventing-kafka.yaml` can be used to install Broker and KafkaSink. ([#367](https://github.com/knative-extensions/eventing-kafka-broker/pull/367)) +- Data plane pods expose server and client metrics in Prometheus format. ([#231](https://github.com/knative-extensions/eventing-kafka-broker/pull/231) [#244](https://github.com/knative-extensions/eventing-kafka-broker/pull/244)) - The receiver component exposes: - `http_requests_produce_total` - Number of accepted produce requests (200-level responses) - `http_requests_malformed_total` - Number of malformed produce requests (400-level responses) - The dispatcher component exposes: - `http_events_sent_total` - Number of events delivered to Apache Kafka -- The Broker retries sending events. ([#268](https://github.com/knative-sandbox/eventing-kafka-broker/pull/268) [#263](https://github.com/knative-sandbox/eventing-kafka-broker/pull/263) [#258](https://github.com/knative-sandbox/eventing-kafka-broker/pull/258)) +- The Broker retries sending events. ([#268](https://github.com/knative-extensions/eventing-kafka-broker/pull/268) [#263](https://github.com/knative-extensions/eventing-kafka-broker/pull/263) [#258](https://github.com/knative-extensions/eventing-kafka-broker/pull/258)) 🐞 Bug Fixes -- Remove config-logging volume from the controller ([#288](https://github.com/knative-sandbox/eventing-kafka-broker/pull/288)) -- Thread blocked when logging large configurations in debug mode ([#346](https://github.com/knative-sandbox/eventing-kafka-broker/pull/346) [#378](https://github.com/knative-sandbox/eventing-kafka-broker/pull/378)) +- Remove config-logging volume from the controller ([#288](https://github.com/knative-extensions/eventing-kafka-broker/pull/288)) +- Thread blocked when logging large configurations in debug mode ([#346](https://github.com/knative-extensions/eventing-kafka-broker/pull/346) [#378](https://github.com/knative-extensions/eventing-kafka-broker/pull/378)) 🧹 Clean up -- The container image's sizes are ~90MB instead of ~287MB. ([#265](https://github.com/knative-sandbox/eventing-kafka-broker/pull/265) [#306](https://github.com/knative-sandbox/eventing-kafka-broker/pull/306)) -- Gracefully clean up resources on shutdown ([#334](https://github.com/knative-sandbox/eventing-kafka-broker/pull/334)) +- The container image's sizes are ~90MB instead of ~287MB. ([#265](https://github.com/knative-extensions/eventing-kafka-broker/pull/265) [#306](https://github.com/knative-extensions/eventing-kafka-broker/pull/306)) +- Gracefully clean up resources on shutdown ([#334](https://github.com/knative-extensions/eventing-kafka-broker/pull/334)) - `KafkaSink` usage: https://gist.github.com/matzew/e2c2fcd2696a346f25b8bc9e64bfd0fa #### Eventing Gitlab v0.19 -Release Notes for [eventing-gitlab](https://github.com/knative-sandbox/eventing-gitlab) +Release Notes for [eventing-gitlab](https://github.com/knative-extensions/eventing-gitlab) πŸ’« New Features & Changes -- Declare event types emitted by a GitLabSource instance so they are propagated as Knative EventTypes. ([#24](https://github.com/knative-sandbox/eventing-gitlab/pull/24)) +- Declare event types emitted by a GitLabSource instance so they are propagated as Knative EventTypes. ([#24](https://github.com/knative-extensions/eventing-gitlab/pull/24)) 🐞 Bug Fixes -- Sanitize the type attribute of emitted CloudEvents so it doesn't contain spaces and capital letters. ([#24](https://github.com/knative-sandbox/eventing-gitlab/pull/24)) +- Sanitize the type attribute of emitted CloudEvents so it doesn't contain spaces and capital letters. ([#24](https://github.com/knative-extensions/eventing-gitlab/pull/24)) 🧹 Clean up -- Ensure the source attribute of emitted CloudEvents is stable and predictable. ([#24](https://github.com/knative-sandbox/eventing-gitlab/pull/24)) +- Ensure the source attribute of emitted CloudEvents is stable and predictable. ([#24](https://github.com/knative-extensions/eventing-gitlab/pull/24)) #### Eventing RabbitMQ v0.19 -Release Notes for [eventing-rabbitmq](https://github.com/knative-sandbox/eventing-rabbitmq) +Release Notes for [eventing-rabbitmq](https://github.com/knative-extensions/eventing-rabbitmq) πŸ’« New Features & Changes - Implement Dead Letter Queue diff --git a/blog/docs/releases/announcing-knative-v0-20-release.md b/blog/docs/releases/announcing-knative-v0-20-release.md index 3900d00569..9a6bf954a2 100644 --- a/blog/docs/releases/announcing-knative-v0-20-release.md +++ b/blog/docs/releases/announcing-knative-v0-20-release.md @@ -77,21 +77,21 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### Eventing Kafka Broker v0.20 -Release Notes for [eventing-kafka-broker](https://github.com/knative-sandbox/eventing-kafka-broker) +Release Notes for [eventing-kafka-broker](https://github.com/knative-extensions/eventing-kafka-broker) #### πŸ’« New Features & Changes -- `kafka-broker-receiver`, `kafka-broker-dispatcher`, and `kafka-sink-receiver` expose Kafka client metrics. ([#435](https://github.com/knative-sandbox/eventing-kafka-broker/pull/435)) -- `kafka-broker-receiver`, `kafka-broker-dispatcher`, and `kafka-sink-receiver` expose JVM metrics (disabled by default) ([#435](https://github.com/knative-sandbox/eventing-kafka-broker/pull/435)) -- Data plane pods produce distributed tracing spans. ([#421](https://github.com/knative-sandbox/eventing-kafka-broker/pull/421)) -- Receivers now specify anti-affinity so that replicas will not be colocated ([#483](https://github.com/knative-sandbox/eventing-kafka-broker/pull/483)) +- `kafka-broker-receiver`, `kafka-broker-dispatcher`, and `kafka-sink-receiver` expose Kafka client metrics. ([#435](https://github.com/knative-extensions/eventing-kafka-broker/pull/435)) +- `kafka-broker-receiver`, `kafka-broker-dispatcher`, and `kafka-sink-receiver` expose JVM metrics (disabled by default) ([#435](https://github.com/knative-extensions/eventing-kafka-broker/pull/435)) +- Data plane pods produce distributed tracing spans. ([#421](https://github.com/knative-extensions/eventing-kafka-broker/pull/421)) +- Receivers now specify anti-affinity so that replicas will not be colocated ([#483](https://github.com/knative-extensions/eventing-kafka-broker/pull/483)) #### 🐞 Bug Fixes -- Controllers resync state when managed resources change. ([#420](https://github.com/knative-sandbox/eventing-kafka-broker/pull/420)) -- Leader election transition improvements ([#449](https://github.com/knative-sandbox/eventing-kafka-broker/pull/449)) +- Controllers resync state when managed resources change. ([#420](https://github.com/knative-extensions/eventing-kafka-broker/pull/420)) +- Leader election transition improvements ([#449](https://github.com/knative-extensions/eventing-kafka-broker/pull/449)) #### 🧹 Clean up -- The data plane is completely non-blocking. ([#438](https://github.com/knative-sandbox/eventing-kafka-broker/pull/438)) -- Skip ConfigMap update when there are no changes ([#511](https://github.com/knative-sandbox/eventing-kafka-broker/pull/511)) -- Change release labels from eventing.knative.dev to kafka.eventing.knative.dev. ([#480](https://github.com/knative-sandbox/eventing-kafka-broker/pull/480)) +- The data plane is completely non-blocking. ([#438](https://github.com/knative-extensions/eventing-kafka-broker/pull/438)) +- Skip ConfigMap update when there are no changes ([#511](https://github.com/knative-extensions/eventing-kafka-broker/pull/511)) +- Change release labels from eventing.knative.dev to kafka.eventing.knative.dev. ([#480](https://github.com/knative-extensions/eventing-kafka-broker/pull/480)) ### Client v0.20 diff --git a/blog/docs/releases/announcing-knative-v0-21-release.md b/blog/docs/releases/announcing-knative-v0-21-release.md index b48959c605..bc30380590 100644 --- a/blog/docs/releases/announcing-knative-v0-21-release.md +++ b/blog/docs/releases/announcing-knative-v0-21-release.md @@ -59,8 +59,8 @@ Follow the instructions in the documentation [Installing Knative](https://knativ - A container's readiness probe FailureThreshold & TimeoutSeconds are now defaulted to 3 and 1 respectively when a user opts into non-aggressive probing (ie. PeriodTimeout > 1) ([#10700](https://github.com/knative/serving/pull/10700)) - Avoids implicitly adding an "Accept-Encoding: gzip" header to proxied requests if one was not already present. ([#10691](https://github.com/knative/serving/pull/10691)) - Gradual Rollout is possible to set on individual Revisions usingserving.knative.dev/rolloutDuration annotation, ([#10561](https://github.com/knative/serving/pull/10561)) -- Support Istio 1.9 (knative-sandbox/net-istio#515](https://github.com/knative-sandbox/net-istio/pull/515)) -- Support Contour 1.12 (knative-sandbox/net-contour#414](https://github.com/knative-sandbox/net-contour/pull/414)) +- Support Istio 1.9 (knative-extensions/net-istio#515](https://github.com/knative-extensions/net-istio/pull/515)) +- Support Contour 1.12 (knative-extensions/net-contour#414](https://github.com/knative-extensions/net-contour/pull/414)) #### 🐞 Bug Fixes @@ -107,68 +107,68 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### 🚨 Breaking or Notable - Kubernetes minimum version has changed to v1.18 - - Upgrade to v0.19.7 of k8s libraries. Minimum k8s version is now 1.18. ([#213](https://github.com/knative-sandbox/eventing-rabbitmq/pull/213)) + - Upgrade to v0.19.7 of k8s libraries. Minimum k8s version is now 1.18. ([#213](https://github.com/knative-extensions/eventing-rabbitmq/pull/213)) #### πŸ’« New Features & Changes -- Support new releases of rabbitmq cluster operator v1.0, v1.1, v1.2, v1.3 . ([#204](https://github.com/knative-sandbox/eventing-rabbitmq/pull/204)) +- Support new releases of rabbitmq cluster operator v1.0, v1.1, v1.2, v1.3 . ([#204](https://github.com/knative-extensions/eventing-rabbitmq/pull/204)) #### πŸ“– Documentation -- Added user-facing documentation for the RabbitMQ source ([#201](https://github.com/knative-sandbox/eventing-rabbitmq/pull/201)) +- Added user-facing documentation for the RabbitMQ source ([#201](https://github.com/knative-extensions/eventing-rabbitmq/pull/201)) #### 🧹 Clean up -- Update or clean up current behavior - Use go 1.15 in kind e2e tests. ([#196](https://github.com/knative-sandbox/eventing-rabbitmq/pull/196)) -- Update or clean up current behavior Use go 1.15 in go.mod ([#215](https://github.com/knative-sandbox/eventing-rabbitmq/pull/215)) -- Update the comments in cmd/failer/main.go to match reality. ([#210](https://github.com/knative-sandbox/eventing-rabbitmq/pull/210)) -- Use scripts from hack to determine pod readiness.([#209](https://github.com/knative-sandbox/eventing-rabbitmq/pull/209)) +- Update or clean up current behavior - Use go 1.15 in kind e2e tests. ([#196](https://github.com/knative-extensions/eventing-rabbitmq/pull/196)) +- Update or clean up current behavior Use go 1.15 in go.mod ([#215](https://github.com/knative-extensions/eventing-rabbitmq/pull/215)) +- Update the comments in cmd/failer/main.go to match reality. ([#210](https://github.com/knative-extensions/eventing-rabbitmq/pull/210)) +- Use scripts from hack to determine pod readiness.([#209](https://github.com/knative-extensions/eventing-rabbitmq/pull/209)) #### Eventing Kafka Source, Channel v0.21 #### πŸ’« New Features & Changes -- Adding new optional field named sasltype to default kafka-secret to enable other Kafka SASL Methods than PLAIN. Supports SCRAM-SHA-256 or SCRAM-SHA-512. ([#332](https://github.com/knative-sandbox/eventing-kafka/pull/332)) -- Adding tls.enabled flag for public cert usage and allowing skipping CA/User certs and key ([#359](https://github.com/knative-sandbox/eventing-kafka/pull/359)) -- KafkaSource and KafkaChannel will be default use the config-leader-election CM for configs ([#231](https://github.com/knative-sandbox/eventing-kafka/pull/231)) -- Removed support for pooling Azure EventHub Namespaces and now only support a single Namespace/Authentication which limits Azure EventHub usage to their constrained number of EventHubs (Kafka Topics). ([#297](https://github.com/knative-sandbox/eventing-kafka/pull/297)) -- The "distributed" KafkaChannel configuration YAML now includes the KafkaChannel WebHook which provides conversion. ([#187](https://github.com/knative-sandbox/eventing-kafka/pull/187)) -- The KafkaSource will be installed in the knative-eventing namespace, and the old controller in knative-sources is scalled to 0 ([#224](https://github.com/knative-sandbox/eventing-kafka/pull/224)) -- Add a new alternative KafkaSource implementation in which a single global StatefulSet handles all KafkaSource instances. ([#186](https://github.com/knative-sandbox/eventing-kafka/pull/186)) -- It is now possible to define Sarama config defaults for KafkaSource in config-kafka configmap with a sarama field. ([#337](https://github.com/knative-sandbox/eventing-kafka/pull/337)) -- It is now possible to define Sarama config defaults for consolidated channel in config-kafka configmap with a sarama field. ([#305](https://github.com/knative-sandbox/eventing-kafka/pull/305)) -- KafkaChannel CustomResourceDefinition now uses apiextensions.k8s.io/v1 APIs ([#132](https://github.com/knative-sandbox/eventing-kafka/pull/132)) -- The KafkaSource scale subresource can now be used to scale up and down the underlying deployment ([#138](https://github.com/knative-sandbox/eventing-kafka/pull/138)) -- Defaulting the connection args to a sane value ([#353](https://github.com/knative-sandbox/eventing-kafka/pull/353)) +- Adding new optional field named sasltype to default kafka-secret to enable other Kafka SASL Methods than PLAIN. Supports SCRAM-SHA-256 or SCRAM-SHA-512. ([#332](https://github.com/knative-extensions/eventing-kafka/pull/332)) +- Adding tls.enabled flag for public cert usage and allowing skipping CA/User certs and key ([#359](https://github.com/knative-extensions/eventing-kafka/pull/359)) +- KafkaSource and KafkaChannel will be default use the config-leader-election CM for configs ([#231](https://github.com/knative-extensions/eventing-kafka/pull/231)) +- Removed support for pooling Azure EventHub Namespaces and now only support a single Namespace/Authentication which limits Azure EventHub usage to their constrained number of EventHubs (Kafka Topics). ([#297](https://github.com/knative-extensions/eventing-kafka/pull/297)) +- The "distributed" KafkaChannel configuration YAML now includes the KafkaChannel WebHook which provides conversion. ([#187](https://github.com/knative-extensions/eventing-kafka/pull/187)) +- The KafkaSource will be installed in the knative-eventing namespace, and the old controller in knative-sources is scalled to 0 ([#224](https://github.com/knative-extensions/eventing-kafka/pull/224)) +- Add a new alternative KafkaSource implementation in which a single global StatefulSet handles all KafkaSource instances. ([#186](https://github.com/knative-extensions/eventing-kafka/pull/186)) +- It is now possible to define Sarama config defaults for KafkaSource in config-kafka configmap with a sarama field. ([#337](https://github.com/knative-extensions/eventing-kafka/pull/337)) +- It is now possible to define Sarama config defaults for consolidated channel in config-kafka configmap with a sarama field. ([#305](https://github.com/knative-extensions/eventing-kafka/pull/305)) +- KafkaChannel CustomResourceDefinition now uses apiextensions.k8s.io/v1 APIs ([#132](https://github.com/knative-extensions/eventing-kafka/pull/132)) +- The KafkaSource scale subresource can now be used to scale up and down the underlying deployment ([#138](https://github.com/knative-extensions/eventing-kafka/pull/138)) +- Defaulting the connection args to a sane value ([#353](https://github.com/knative-extensions/eventing-kafka/pull/353)) #### 🐞 Bug Fixes - A bug was fixed in the consolidated KafkaChannel where subscriptions would show up in the channel's status.subscribers before the dispatcher becomes ready to dispatch messages for those subscribers. - - Consolidated KafkaChannel dispatcher's horizontal scalability works now seamlessly with reconciler leader election. ([#182](https://github.com/knative-sandbox/eventing-kafka/pull/182)) -- Fix concurrent modification of consumer groups map, which causes undefined behaviours while running reconciliation in the dispatcher ([#352](https://github.com/knative-sandbox/eventing-kafka/pull/352), @slinkydeveloper) -- Fix crash in Kafka consumer when a rebalance occurs ([#263](https://github.com/knative-sandbox/eventing-kafka/pull/263), @lionelvillard) -- Fix race on error channel in consumer factory ([#364](https://github.com/knative-sandbox/eventing-kafka/pull/364)) -- The KafkaSource dispatchers now expose metrics and profiling information ([#221](https://github.com/knative-sandbox/eventing-kafka/pull/221)) -- The consolidated KafkaChannel now relies by default on SyncProducer for safer event production. ([#181](https://github.com/knative-sandbox/eventing-kafka/pull/181)) + - Consolidated KafkaChannel dispatcher's horizontal scalability works now seamlessly with reconciler leader election. ([#182](https://github.com/knative-extensions/eventing-kafka/pull/182)) +- Fix concurrent modification of consumer groups map, which causes undefined behaviours while running reconciliation in the dispatcher ([#352](https://github.com/knative-extensions/eventing-kafka/pull/352), @slinkydeveloper) +- Fix crash in Kafka consumer when a rebalance occurs ([#263](https://github.com/knative-extensions/eventing-kafka/pull/263), @lionelvillard) +- Fix race on error channel in consumer factory ([#364](https://github.com/knative-extensions/eventing-kafka/pull/364)) +- The KafkaSource dispatchers now expose metrics and profiling information ([#221](https://github.com/knative-extensions/eventing-kafka/pull/221)) +- The consolidated KafkaChannel now relies by default on SyncProducer for safer event production. ([#181](https://github.com/knative-extensions/eventing-kafka/pull/181)) #### Eventing Kafka Broker v0.21 #### πŸ’« New Features & Changes -- Add support for SASL and SSL. ([#534](https://github.com/knative-sandbox/eventing-kafka-broker/pull/534), @pierDipi) +- Add support for SASL and SSL. ([#534](https://github.com/knative-extensions/eventing-kafka-broker/pull/534), @pierDipi) - [Eventing Kafka Broker documentation](https://knative.dev/docs/eventing/broker/kafka-broker/#security) - [Eventing Kafka Sink documentation](https://knative.dev/docs/eventing/sink/kafka-sink/#security) -- Add support for Trigger.Spec.DeliverySpec ([#612](https://github.com/knative-sandbox/eventing-kafka-broker/pull/612)) -- Improve status fields description in KafkaSink CRD. ([#552](https://github.com/knative-sandbox/eventing-kafka-broker/pull/552)) -- Reduce error logging noise on clean shutdown. ([#625](https://github.com/knative-sandbox/eventing-kafka-broker/pull/625)) -- Support Kubernetes 1.20. ([#542](https://github.com/knative-sandbox/eventing-kafka-broker/pull/542)) +- Add support for Trigger.Spec.DeliverySpec ([#612](https://github.com/knative-extensions/eventing-kafka-broker/pull/612)) +- Improve status fields description in KafkaSink CRD. ([#552](https://github.com/knative-extensions/eventing-kafka-broker/pull/552)) +- Reduce error logging noise on clean shutdown. ([#625](https://github.com/knative-extensions/eventing-kafka-broker/pull/625)) +- Support Kubernetes 1.20. ([#542](https://github.com/knative-extensions/eventing-kafka-broker/pull/542)) #### 🐞 Bug Fixes -- Consume topic from the earliest offset ([#557](https://github.com/knative-sandbox/eventing-kafka-broker/pull/557)) -- Fix offset management ([#557](https://github.com/knative-sandbox/eventing-kafka-broker/pull/557)) -- Data plane reconciler handles failed reconciliation. ([#568](https://github.com/knative-sandbox/eventing-kafka-broker/pull/568)) -- Fix TimeoutException and DnsNameResolverTimeoutException. ([#539](https://github.com/knative-sandbox/eventing-kafka-broker/pull/539)) +- Consume topic from the earliest offset ([#557](https://github.com/knative-extensions/eventing-kafka-broker/pull/557)) +- Fix offset management ([#557](https://github.com/knative-extensions/eventing-kafka-broker/pull/557)) +- Data plane reconciler handles failed reconciliation. ([#568](https://github.com/knative-extensions/eventing-kafka-broker/pull/568)) +- Fix TimeoutException and DnsNameResolverTimeoutException. ([#539](https://github.com/knative-extensions/eventing-kafka-broker/pull/539)) ### Client v0.21 @@ -210,8 +210,8 @@ With release v0.21, Knative ships also it first set of kn plugins, that are alig The plugins included in version `v0.21` are: -- [kn-plugin-admin](https://github.com/knative-sandbox/kn-plugin-admin) for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-sandbox/kn-plugin-admin/releases/tag/v0.21.0) -- [kn-plugin-source-kafka](https://github.com/knative-sandbox/kn-plugin-source-kafka) for managing a Kafka Source that has been installed via [eventing-kafka](https://github.com/knative-sandbox/eventing-kafka) on the backend | [download](https://github.com/knative-sandbox/kn-plugin-source-kafka/releases/tag/v0.21.0) +- [kn-plugin-admin](https://github.com/knative-extensions/kn-plugin-admin) for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-extensions/kn-plugin-admin/releases/tag/v0.21.0) +- [kn-plugin-source-kafka](https://github.com/knative-extensions/kn-plugin-source-kafka) for managing a Kafka Source that has been installed via [eventing-kafka](https://github.com/knative-extensions/eventing-kafka) on the backend | [download](https://github.com/knative-extensions/kn-plugin-source-kafka/releases/tag/v0.21.0) To give those plugins a try, just download them and put the binary into your execution path. You then get help with kn admin --help and kn source kafka --help, respectively. diff --git a/blog/docs/releases/announcing-knative-v0-22-release.md b/blog/docs/releases/announcing-knative-v0-22-release.md index 79e44cad3d..34413edad5 100644 --- a/blog/docs/releases/announcing-knative-v0-22-release.md +++ b/blog/docs/releases/announcing-knative-v0-22-release.md @@ -34,7 +34,7 @@ Follow the instructions in the documentation [Installing Knative](https://knativ - 1.18 is now the minimum Kubernetes version required to use the Apache Kafka broker with Knative Eventing v0.22. - Apache Kafka broker now supports the ability to choose between ordered and unordered delivery - The CLI `kn` v0.22.0 comes with some bug fixes and minor feature enhancements. It's mostly a polishing release. If you are using the Client API, there is a breaking change that was needed to align with Kubernetes Client API's -- There are two new CLI plugins to align with the v0.22 release, [kn-plugin-admin](https://github.com/knative-sandbox/kn-plugin-admin) and [kn-plugin-source-kafka](https://github.com/knative-sandbox/kn-plugin-source-kafka) +- There are two new CLI plugins to align with the v0.22 release, [kn-plugin-admin](https://github.com/knative-extensions/kn-plugin-admin) and [kn-plugin-source-kafka](https://github.com/knative-extensions/kn-plugin-source-kafka) - The Knative Operator v0.22 release contains bug fixes and supports version v0.22 of Knative Serving and Eventing. @@ -53,7 +53,7 @@ Follow the instructions in the documentation [Installing Knative](https://knativ - Raised the resource request and limits of the autoscaler to 100m/100Mi, 1000m/1000Mi respectively. [#10865](https://github.com/knative/serving/pull/10865) - Fixed a regression where the latency of starting a pod could be 10s or more. [#10992](https://github.com/knative/serving/pull/10992) - Reduced required memory allocations in the activator significantly, particularly when tracing is turned off. [#11016](https://github.com/knative/serving/pull/11016), [#11013](https://github.com/knative/serving/pull/11013), [#11009](https://github.com/knative/serving/pull/11009), [#11008](https://github.com/knative/serving/pull/11008) -- Fixed the incorrect gateway name format for the domain mapping auto TLS feature for `net-istio` implementation. [net-istio#532](https://github.com/knative-sandbox/net-istio/pull/532) +- Fixed the incorrect gateway name format for the domain mapping auto TLS feature for `net-istio` implementation. [net-istio#532](https://github.com/knative-extensions/net-istio/pull/532) ### Eventing v0.22 @@ -85,18 +85,18 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### Apache Kafka Broker v0.22 - + #### 🚨 Breaking or Notable #### πŸ’« New Features & Changes -- The Kafka broker now supports ordered delivery. You can choose between ordered and unordered delivery by using the `kafka.eventing.knative.dev/delivery.order` label in the trigger spec. See the [Kafka broker](https://knative.dev/docs/eventing/broker/kafka-broker) documentation. [#589](https://github.com/knative-sandbox/eventing-kafka-broker/pull/) +- The Kafka broker now supports ordered delivery. You can choose between ordered and unordered delivery by using the `kafka.eventing.knative.dev/delivery.order` label in the trigger spec. See the [Kafka broker](https://knative.dev/docs/eventing/broker/kafka-broker) documentation. [#589](https://github.com/knative-extensions/eventing-kafka-broker/pull/) #### 🐞 Bug Fixes -- Added a producer interceptor, `io.cloudevents.kafka.PartitionKeyExtensionInterceptor`, to provide ordered delivery based on the partitioning extension of the CloudEvents spec. [#751](https://github.com/knative-sandbox/eventing-kafka-broker/pull/751) -- Fix unable to deploy KafkaSink without Kafka Broker installed. [#714](https://github.com/knative-sandbox/eventing-kafka-broker/pull/714) +- Added a producer interceptor, `io.cloudevents.kafka.PartitionKeyExtensionInterceptor`, to provide ordered delivery based on the partitioning extension of the CloudEvents spec. [#751](https://github.com/knative-extensions/eventing-kafka-broker/pull/751) +- Fix unable to deploy KafkaSink without Kafka Broker installed. [#714](https://github.com/knative-extensions/eventing-kafka-broker/pull/714) ### Client v0.22 @@ -133,8 +133,8 @@ To migrate to the updated API signature, you can pass an already existing contex The plugins that are released aligned with v0.22 are: -- [kn-plugin-admin](https://github.com/knative-sandbox/kn-plugin-admin) for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-sandbox/kn-plugin-admin/releases/tag/v0.22.0) -- [kn-plugin-source-kafka](https://github.com/knative-sandbox/kn-plugin-source-kafka) for managing a Kafka Source that has been installed via [eventing-kafka](https://github.com/knative-sandbox/eventing-kafka) on the backend | [download](https://github.com/knative-sandbox/kn-plugin-source-kafka/releases/tag/v0.22.0) +- [kn-plugin-admin](https://github.com/knative-extensions/kn-plugin-admin) for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-extensions/kn-plugin-admin/releases/tag/v0.22.0) +- [kn-plugin-source-kafka](https://github.com/knative-extensions/kn-plugin-source-kafka) for managing a Kafka Source that has been installed via [eventing-kafka](https://github.com/knative-extensions/eventing-kafka) on the backend | [download](https://github.com/knative-extensions/kn-plugin-source-kafka/releases/tag/v0.22.0) ### Minor CLI updates diff --git a/blog/docs/releases/announcing-knative-v0-23-release.md b/blog/docs/releases/announcing-knative-v0-23-release.md index a6567fddf5..e7e76dbcf7 100644 --- a/blog/docs/releases/announcing-knative-v0-23-release.md +++ b/blog/docs/releases/announcing-knative-v0-23-release.md @@ -95,23 +95,23 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### Apache Kafka Broker v0.23 - + #### πŸ’« New Features & Changes -- In Kafka Broker, now the Kafka producer will wait for all ISR replicas ack. [#824](https://github.com/knative-sandbox/eventing-kafka-broker/pull/824) -- In Kafka Sink, now the Kafka producer will wait for all ISR replicas ack. [#827](https://github.com/knative-sandbox/eventing-kafka-broker/pull/827) +- In Kafka Broker, now the Kafka producer will wait for all ISR replicas ack. [#824](https://github.com/knative-extensions/eventing-kafka-broker/pull/824) +- In Kafka Sink, now the Kafka producer will wait for all ISR replicas ack. [#827](https://github.com/knative-extensions/eventing-kafka-broker/pull/827) #### 🐞 Bug Fixes -- Fix out of bounds in unordered offset manager. [#814](https://github.com/knative-sandbox/eventing-kafka-broker/pull/814) -- Accept "PLAIN" as a valid sasl.mechanism secret value. [#855](https://github.com/knative-sandbox/eventing-kafka-broker/pull/855),[#840](https://github.com/knative-sandbox/eventing-kafka-broker/pull/840) +- Fix out of bounds in unordered offset manager. [#814](https://github.com/knative-extensions/eventing-kafka-broker/pull/814) +- Accept "PLAIN" as a valid sasl.mechanism secret value. [#855](https://github.com/knative-extensions/eventing-kafka-broker/pull/855),[#840](https://github.com/knative-extensions/eventing-kafka-broker/pull/840) #### RabbitMQ Eventing v0.23 - + #### 🚨 Breaking or Notable Changes @@ -120,7 +120,7 @@ Follow the instructions in the documentation [Installing Knative](https://knativ #### 🐞 Bug Fixes - Conformance tests for Broker now work -- If a Broker / Trigger is deleted but there's no secret to talk to the rabbit cluster, we now remove the resources and log that rabbitmq resources might have been leaked. This happens only when not using the Rabbit Cluster Operator. This left undeletable resources, so this change seems more user friendly. [#271](https://github.com/knative-sandbox/eventing-rabbitmq/pull/271) +- If a Broker / Trigger is deleted but there's no secret to talk to the rabbit cluster, we now remove the resources and log that rabbitmq resources might have been leaked. This happens only when not using the Rabbit Cluster Operator. This left undeletable resources, so this change seems more user friendly. [#271](https://github.com/knative-extensions/eventing-rabbitmq/pull/271) ### Client v0.23 diff --git a/blog/docs/releases/announcing-knative-v0-24-release.md b/blog/docs/releases/announcing-knative-v0-24-release.md index 00c09e8184..7f692c5212 100644 --- a/blog/docs/releases/announcing-knative-v0-24-release.md +++ b/blog/docs/releases/announcing-knative-v0-24-release.md @@ -52,7 +52,7 @@ Follow the instructions in the documentation are installed alongside Serving. If you're managing your Knative deployment manually with `kubectl` **this will require a two-phase upgrade process**. See the below sections: - * Upgrade of [net-http01 to v0.24.0](https://github.com/knative-sandbox/net-http01/releases/tag/v0.24.0) + * Upgrade of [net-http01 to v0.24.0](https://github.com/knative-extensions/net-http01/releases/tag/v0.24.0) ``` # Apply the new release @@ -63,7 +63,7 @@ Follow the instructions in the documentation $ kubectl delete service challenger -n knative-serving ``` - * Upgrade of [net-certmanager to v0.24.0](https://github.com/knative-sandbox/net-certmanager/releases/tag/v0.24.0) + * Upgrade of [net-certmanager to v0.24.0](https://github.com/knative-extensions/net-certmanager/releases/tag/v0.24.0) ``` # Apply the new release @@ -75,7 +75,7 @@ Follow the instructions in the documentation --prune -l networking.knative.dev/certificate-provider=cert-manager ``` - * Upgrade [net-istio to v0.24.0](https://github.com/knative-sandbox/net-istio/releases/tag/v0.24.0) + * Upgrade [net-istio to v0.24.0](https://github.com/knative-extensions/net-istio/releases/tag/v0.24.0) ``` # Apply the new release @@ -87,7 +87,7 @@ Follow the instructions in the documentation --prune -l networking.knative.dev/ingress-provider=istio ``` - * Upgrade of [net-contour to v0.24.0](https://github.com/knative-sandbox/net-contour/releases/tag/v0.24.0) + * Upgrade of [net-contour to v0.24.0](https://github.com/knative-extensions/net-contour/releases/tag/v0.24.0) ``` # Apply the new release @@ -99,7 +99,7 @@ Follow the instructions in the documentation --prune -l networking.knative.dev/ingress-provider=contour ``` - * Upgrade of [net-kourier to v0.24.0](https://github.com/knative-sandbox/net-kourier/releases/tag/v0.24.0). + * Upgrade of [net-kourier to v0.24.0](https://github.com/knative-extensions/net-kourier/releases/tag/v0.24.0). At this point we've deferred the renaming to net-kourier until the next release. We're looking to ensure there is no traffic disruption as part of the upgrade. Therefore upgrading to v0.24.0 requires no special instructions. @@ -144,9 +144,9 @@ Follow the instructions in the documentation * DomainMapping can now specify a TLS secret to be used as the HTTPS certificate ([#11250](https://github.com/knative/serving/pull/11250)) * Provides a feature gate that, when enabled, allows adding capabilities from a container's security context ([#11410](https://github.com/knative/serving/pull/11410)) * `defaultExternalScheme` can now be used for default routes to surface a URL scheme of your choice rather than the default "http". ([#11480](https://github.com/knative/serving/pull/11480)) -* Optimized generated routes to minimize Envoy configuration size ([net-istio#632](https://github.com/knative-sandbox/net-istio/pull/632)) -* Rename Contour's ClusterRole and ClusterRoleBinding to differ from existing contour installation ([net-contour#500](https://github.com/knative-sandbox/net-contour/pull/500)) -* Add a new ConfigMap `config-kourier`, with the initial `enable-service-access-logging` setting ([net-kourier#523](https://github.com/knative-sandbox/net-kourier/pull/523)) +* Optimized generated routes to minimize Envoy configuration size ([net-istio#632](https://github.com/knative-extensions/net-istio/pull/632)) +* Rename Contour's ClusterRole and ClusterRoleBinding to differ from existing contour installation ([net-contour#500](https://github.com/knative-extensions/net-contour/pull/500)) +* Add a new ConfigMap `config-kourier`, with the initial `enable-service-access-logging` setting ([net-kourier#523](https://github.com/knative-extensions/net-kourier/pull/523)) #### 🐞 Bug Fixes @@ -206,33 +206,33 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 #### Apache Kafka Broker v0.24 - + #### πŸ’« New Features & Changes -- Add some details in the existing Subscriber resolved condition about the delivery order. [#912](https://github.com/knative-sandbox/eventing-kafka-broker/pull/912) -- Receiver deployment uses all available CPUs. [#985](https://github.com/knative-sandbox/eventing-kafka-broker/pull/985) -- Now you can specify both in Broker and Trigger delivery specs the new timeout field, as part of the experimental feature delivery-timeout. For more information, see [Experimental features](https://knative.dev/docs/eventing/experimental-features/). [#1034](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1034) -- Updates Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) -- Updates protobuf to v3.17.x [#946](https://github.com/knative-sandbox/eventing-kafka-broker/pull/946) -- Updates vert.x to v4.1 [#900](https://github.com/knative-sandbox/eventing-kafka-broker/pull/900) +- Add some details in the existing Subscriber resolved condition about the delivery order. [#912](https://github.com/knative-extensions/eventing-kafka-broker/pull/912) +- Receiver deployment uses all available CPUs. [#985](https://github.com/knative-extensions/eventing-kafka-broker/pull/985) +- Now you can specify both in Broker and Trigger delivery specs the new timeout field, as part of the experimental feature delivery-timeout. For more information, see [Experimental features](https://knative.dev/docs/eventing/experimental-features/). [#1034](https://github.com/knative-extensions/eventing-kafka-broker/pull/1034) +- Updates Go to v1.16 [#886](https://github.com/knative-extensions/eventing-kafka-broker/pull/886) +- Updates protobuf to v3.17.x [#946](https://github.com/knative-extensions/eventing-kafka-broker/pull/946) +- Updates vert.x to v4.1 [#900](https://github.com/knative-extensions/eventing-kafka-broker/pull/900) #### RabbitMQ Eventing v0.24 - + #### πŸ’« New Features & Changes -- Add validating webhook that checks RabbitMQBroker class brokers for valid [secret, rabbitmqcluster] configurations. ([#324](https://github.com/knative-sandbox/eventing-rabbitmq/pull/324)) -- Provide an option for install that does not have dependency on rabbitmq cluster operator or messaging-topology-operator. That allows you to bring your own rabbitmq broker. ([#309](https://github.com/knative-sandbox/eventing-rabbitmq/pull/309)) -- Add installation instructions for two kinds of brokers. ([#315](https://github.com/knative-sandbox/eventing-rabbitmq/pull/315)) +- Add validating webhook that checks RabbitMQBroker class brokers for valid [secret, rabbitmqcluster] configurations. ([#324](https://github.com/knative-extensions/eventing-rabbitmq/pull/324)) +- Provide an option for install that does not have dependency on rabbitmq cluster operator or messaging-topology-operator. That allows you to bring your own rabbitmq broker. ([#309](https://github.com/knative-extensions/eventing-rabbitmq/pull/309)) +- Add installation instructions for two kinds of brokers. ([#315](https://github.com/knative-extensions/eventing-rabbitmq/pull/315)) #### 🐞 Bug Fixes -- Fix Standalone Broker to support Trigger DeadLetterSink properly. ([#341](https://github.com/knative-sandbox/eventing-rabbitmq/pull/341)) -- Fix per trigger DeadLetterSink support. ([#337](https://github.com/knative-sandbox/eventing-rabbitmq/pull/337)) -- Fix issue [#320](https://github.com/knative-sandbox/eventing-rabbitmq/issues/320): Fix incorrect links to both nightly and to-be-released standalone broker. ([#325](https://github.com/knative-sandbox/eventing-rabbitmq/pull/325)) -- Remove unnecessary keda permissions since that functionality was moved to https://github.com/knative-sandbox/eventing-autoscaler-keda ([#319](https://github.com/knative-sandbox/eventing-rabbitmq/pull/319)) -- Use better names for all RabbitMQ resources. Both k8s resources as well as RabbitMQ resources for standalone Broker. ([#344](https://github.com/knative-sandbox/eventing-rabbitmq/pull/344)) +- Fix Standalone Broker to support Trigger DeadLetterSink properly. ([#341](https://github.com/knative-extensions/eventing-rabbitmq/pull/341)) +- Fix per trigger DeadLetterSink support. ([#337](https://github.com/knative-extensions/eventing-rabbitmq/pull/337)) +- Fix issue [#320](https://github.com/knative-extensions/eventing-rabbitmq/issues/320): Fix incorrect links to both nightly and to-be-released standalone broker. ([#325](https://github.com/knative-extensions/eventing-rabbitmq/pull/325)) +- Remove unnecessary keda permissions since that functionality was moved to https://github.com/knative-extensions/eventing-autoscaler-keda ([#319](https://github.com/knative-extensions/eventing-rabbitmq/pull/319)) +- Use better names for all RabbitMQ resources. Both k8s resources as well as RabbitMQ resources for standalone Broker. ([#344](https://github.com/knative-extensions/eventing-rabbitmq/pull/344)) ### Client v0.24 diff --git a/blog/docs/releases/announcing-knative-v0-25-release.md b/blog/docs/releases/announcing-knative-v0-25-release.md index a6153de286..ec87cbffaf 100644 --- a/blog/docs/releases/announcing-knative-v0-25-release.md +++ b/blog/docs/releases/announcing-knative-v0-25-release.md @@ -50,7 +50,7 @@ Follow the instructions in the documentation As part of our efforts to GA/1.0 we've standardized on the naming of our networking plugins that are installed alongside Serving. If you're managing your Knative deployment manually with - `kubectl` **this will require a two-phase upgrade process**. In order to upgrade [net-kourier to v0.25.0](https://github.com/knative-sandbox/net-kourier/releases/tag/v0.25.0) using `kubectl` please follow the steps: + `kubectl` **this will require a two-phase upgrade process**. In order to upgrade [net-kourier to v0.25.0](https://github.com/knative-extensions/net-kourier/releases/tag/v0.25.0) using `kubectl` please follow the steps: ```bash # Apply the new release @@ -98,26 +98,26 @@ Follow the instructions in the documentation #### Apache Kafka Broker v0.25 - + #### πŸ’« New Features & Changes -- The Trigger status contains the resolved URL of the configured dead letter sink. ([#1092](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1092)) +- The Trigger status contains the resolved URL of the configured dead letter sink. ([#1092](https://github.com/knative-extensions/eventing-kafka-broker/pull/1092)) #### 🐞 Bug Fixes -- Fix to support subscribers that are a Kubernetes service. The service's endpoint doesn't contain a trailing slash. ([#1123](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1123)) +- Fix to support subscribers that are a Kubernetes service. The service's endpoint doesn't contain a trailing slash. ([#1123](https://github.com/knative-extensions/eventing-kafka-broker/pull/1123)) #### Apache Kafka Source and Channels v0.25 - + #### πŸ’« New Features & Changes -- Distributed KafkaChannel Dispatcher will now re-queue KafkaChannels after failed reconciliation which will improve various failure recovery scenarios, but could consume CPU resources if reconciliation is blocked by underlying system issues (bad Kafka Secret config, etc.) ([#795](https://github.com/knative-sandbox/eventing-kafka/pull/795)) -- Separated CRDs to extra, additional YAML manifest (similar to eventing) ([#799](https://github.com/knative-sandbox/eventing-kafka/pull/799)) -- Enabled support for ResetOffset CRD in distributed KafkaChannel, see config/command/resetoffset for details. ([#761](https://github.com/knative-sandbox/eventing-kafka/pull/761)) -- The consolidated KafkaChannel dispatcher is now owned by the controller. ([#798](https://github.com/knative-sandbox/eventing-kafka/pull/798)) +- Distributed KafkaChannel Dispatcher will now re-queue KafkaChannels after failed reconciliation which will improve various failure recovery scenarios, but could consume CPU resources if reconciliation is blocked by underlying system issues (bad Kafka Secret config, etc.) ([#795](https://github.com/knative-extensions/eventing-kafka/pull/795)) +- Separated CRDs to extra, additional YAML manifest (similar to eventing) ([#799](https://github.com/knative-extensions/eventing-kafka/pull/799)) +- Enabled support for ResetOffset CRD in distributed KafkaChannel, see config/command/resetoffset for details. ([#761](https://github.com/knative-extensions/eventing-kafka/pull/761)) +- The consolidated KafkaChannel dispatcher is now owned by the controller. ([#798](https://github.com/knative-extensions/eventing-kafka/pull/798)) ### Client v0.25 @@ -126,7 +126,7 @@ Follow the instructions in the documentation #### πŸ’« New Features & Changes -- The new plugin `kn-quickstart` is now part of the home-brew plugins suite. Install the plugin using `brew install knative-sandbox/kn-plugins/quickstart` then use it with `kn quickstart kind` this will create a kind cluster with knative installed. Make sure to update `kn` to `v0.25` for example using `brew upgrade kn` +- The new plugin `kn-quickstart` is now part of the home-brew plugins suite. Install the plugin using `brew install knative-extensions/kn-plugins/quickstart` then use it with `kn quickstart kind` this will create a kind cluster with knative installed. Make sure to update `kn` to `v0.25` for example using `brew upgrade kn` - Deprecate `lookup-path` as path lookup will always be enabled in the future ([#1422](https://github.com/knative/client/pull/1422)) - Add `--tls` option to domain create command ([#1419](https://github.com/knative/client/pull/1419)) diff --git a/blog/docs/releases/announcing-knative-v0-26-release.md b/blog/docs/releases/announcing-knative-v0-26-release.md index 13c87188f4..71e3c683f0 100644 --- a/blog/docs/releases/announcing-knative-v0-26-release.md +++ b/blog/docs/releases/announcing-knative-v0-26-release.md @@ -100,7 +100,7 @@ code). ([#11999](https://github.com/knative/serving/pull/11999)) #### Apache Kafka Broker v0.26 - + ##### 🚨 Breaking or Notable Changes @@ -108,40 +108,40 @@ code). ([#11999](https://github.com/knative/serving/pull/11999)) ##### 🐞 Bug Fixes -- The fields Broker.spec.delivery.deadLetterSink.ref.namespace and Trigger.spec.delivery.deadLetterSink.ref.namespace are optional. By default the controller uses the object namespace. ([#1254](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1254)) +- The fields Broker.spec.delivery.deadLetterSink.ref.namespace and Trigger.spec.delivery.deadLetterSink.ref.namespace are optional. By default the controller uses the object namespace. ([#1254](https://github.com/knative-extensions/eventing-kafka-broker/pull/1254)) #### Apache Kafka Source and Channels v0.26 - + ##### πŸ’« New Features & Changes -- KafkaChannel CRD Spec now includes a RetentionDuration field, allowing per-channel control over retention. A Post-Install Job (config/post-install/retentionupdate) is available to migrate existing KafkaChannels forward by populating this field. The "topic" configuration defaults which were not working have been removed from the config-kafka ConfigMap. ([#828](https://github.com/knative-sandbox/eventing-kafka/pull/828)) -- KafkaChannel ConfigMap now supports custom Labels and Annotations for dynamically generated resources. ([#806](https://github.com/knative-sandbox/eventing-kafka/pull/806)) -- Provide an option for the user to specify the initial offset for a consumer group in Kafka source, this field is honored only if there are no prior offsets committed for the consumer group. ([#779](https://github.com/knative-sandbox/eventing-kafka/pull/779)) -- KafkaSource now supports ceOverrides. ([#811](https://github.com/knative-sandbox/eventing-kafka/pull/811)) -- The Multi-tenant `KafkaSource` calculates an optimal maximum allowed replica number based on Kafka source partitions count so that scheduler does not schedule more vreplicas than the calculated number ([#822](https://github.com/knative-sandbox/eventing-kafka/pull/822)) -- Autoscaling annotations can now be automatically added to KafkaSource objects. See the documentation for more details. ([#855](https://github.com/knative-sandbox/eventing-kafka/pull/855)) +- KafkaChannel CRD Spec now includes a RetentionDuration field, allowing per-channel control over retention. A Post-Install Job (config/post-install/retentionupdate) is available to migrate existing KafkaChannels forward by populating this field. The "topic" configuration defaults which were not working have been removed from the config-kafka ConfigMap. ([#828](https://github.com/knative-extensions/eventing-kafka/pull/828)) +- KafkaChannel ConfigMap now supports custom Labels and Annotations for dynamically generated resources. ([#806](https://github.com/knative-extensions/eventing-kafka/pull/806)) +- Provide an option for the user to specify the initial offset for a consumer group in Kafka source, this field is honored only if there are no prior offsets committed for the consumer group. ([#779](https://github.com/knative-extensions/eventing-kafka/pull/779)) +- KafkaSource now supports ceOverrides. ([#811](https://github.com/knative-extensions/eventing-kafka/pull/811)) +- The Multi-tenant `KafkaSource` calculates an optimal maximum allowed replica number based on Kafka source partitions count so that scheduler does not schedule more vreplicas than the calculated number ([#822](https://github.com/knative-extensions/eventing-kafka/pull/822)) +- Autoscaling annotations can now be automatically added to KafkaSource objects. See the documentation for more details. ([#855](https://github.com/knative-extensions/eventing-kafka/pull/855)) ##### 🐞 Bug Fixes -- Fix bug: status.address of KafkaChannel is not required anymore, thus conditions are reflected successfully in case of an early stage error ([#857](https://github.com/knative-sandbox/eventing-kafka/pull/857)) -- Remove confusing error message `Kafka source is not ready`. This error is returned as an event regardless the Kafka source has any real issue or not and users should not see this error message unless it is a legitimate error or it is an error they can fix. ([#809](https://github.com/knative-sandbox/eventing-kafka/pull/809)) -- multi-tenant source webhook cluster role has update permission for namespaces/finalizers. ([#854](https://github.com/knative-sandbox/eventing-kafka/pull/854)) +- Fix bug: status.address of KafkaChannel is not required anymore, thus conditions are reflected successfully in case of an early stage error ([#857](https://github.com/knative-extensions/eventing-kafka/pull/857)) +- Remove confusing error message `Kafka source is not ready`. This error is returned as an event regardless the Kafka source has any real issue or not and users should not see this error message unless it is a legitimate error or it is an error they can fix. ([#809](https://github.com/knative-extensions/eventing-kafka/pull/809)) +- multi-tenant source webhook cluster role has update permission for namespaces/finalizers. ([#854](https://github.com/knative-extensions/eventing-kafka/pull/854)) ##### 🧹 Clean up -- Inherent immutability of KafkaChannel and ResetOffset spec fields is now enforced by the kafka-webhook. ([#863](https://github.com/knative-sandbox/eventing-kafka/pull/863)) -- Next generation Multi-Tenant Scheduler and Descheduler: uses a plugin interface to specify a Scheduler profile with predicates and priorities that run filtering and scoring of pods, respectively to compute the best vreplica placements. When the autoscaler adds new pods, scheduler performs a rebalancing of the already placed vreplicas along with the new vreplicas. A Descheduler profile must be installed when vreplicas need to be scaled down and placements removed. ([#768](https://github.com/knative-sandbox/eventing-kafka/pull/768)) -- The consolidated KafkaChannel dispatcher is now owned by the controller. ([#798](https://github.com/knative-sandbox/eventing-kafka/pull/798)) +- Inherent immutability of KafkaChannel and ResetOffset spec fields is now enforced by the kafka-webhook. ([#863](https://github.com/knative-extensions/eventing-kafka/pull/863)) +- Next generation Multi-Tenant Scheduler and Descheduler: uses a plugin interface to specify a Scheduler profile with predicates and priorities that run filtering and scoring of pods, respectively to compute the best vreplica placements. When the autoscaler adds new pods, scheduler performs a rebalancing of the already placed vreplicas along with the new vreplicas. A Descheduler profile must be installed when vreplicas need to be scaled down and placements removed. ([#768](https://github.com/knative-extensions/eventing-kafka/pull/768)) +- The consolidated KafkaChannel dispatcher is now owned by the controller. ([#798](https://github.com/knative-extensions/eventing-kafka/pull/798)) #### Eventing Kogito v0.26 - + ##### πŸ’« New Features & Changes -- Introduce the new Kogito Source CRD and add support to K_SINK environment variable to Kogito services ([#1](https://github.com/knative-sandbox/eventing-kogito/pull/1)) +- Introduce the new Kogito Source CRD and add support to K_SINK environment variable to Kogito services ([#1](https://github.com/knative-extensions/eventing-kogito/pull/1)) ### Client v0.26 @@ -150,14 +150,14 @@ code). ([#11999](https://github.com/knative/serving/pull/11999)) #### πŸ’« New Features & Changes - Add `--env-file` option to function create/update command ([#1433](https://github.com/knative/client/pull/1433)) -- New CLI plugin `kn-plugin-kamelet`, a Knative CLI plugin for managing Kamelets and KameletBindings as Knative event sources. Download latest release [here](https://github.com/knative-sandbox/kn-plugin-source-kamelet/releases) +- New CLI plugin `kn-plugin-kamelet`, a Knative CLI plugin for managing Kamelets and KameletBindings as Knative event sources. Download latest release [here](https://github.com/knative-extensions/kn-plugin-source-kamelet/releases) - List available Kamelets - Describe Kamelet and print detailed information (e.g. provider, support level, properties) - Bind Kamelet as source to a Knative sink (broker, channel, service) - List Kamelet bindings - Create Kamelet binding to bind source to Knative sink (broker, channel, service) -- New CLI experimental functions plugin `kn-plugin-func` Download latest release [here](https://github.com/knative-sandbox/kn-plugin-func/releases) -- New CLI experimental cloud event plugin `kn-plugin-event` Download latest release [here](https://github.com/knative-sandbox/kn-plugin-event/releases) +- New CLI experimental functions plugin `kn-plugin-func` Download latest release [here](https://github.com/knative-extensions/kn-plugin-func/releases) +- New CLI experimental cloud event plugin `kn-plugin-event` Download latest release [here](https://github.com/knative-extensions/kn-plugin-event/releases) #### 🧹 Clean up - Remove `DeprecatedImageDigest` field ([#1454](https://github.com/knative/client/pull/1454)) diff --git a/blog/docs/releases/announcing-knative-v1-0-release.md b/blog/docs/releases/announcing-knative-v1-0-release.md index a0732b0d71..d81739283f 100644 --- a/blog/docs/releases/announcing-knative-v1-0-release.md +++ b/blog/docs/releases/announcing-knative-v1-0-release.md @@ -104,32 +104,32 @@ kubernetes readiness propagates more quickly than the activator's probe. ([#1208 #### Apache Kafka Broker v1.0 - + ##### πŸ’« New Features & Changes -- ClusterRole `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- ServiceAccount `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- ClusterRoleBinding `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- ClusterRole `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- ServiceAccount `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- ClusterRoleBinding `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1315)) -- Set `status.deadLetterSinkUri` of Broker and Trigger to the resolved URI of `spec.delivery.deadLetterSink` ([#1349](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1349)) +- ClusterRole `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- ServiceAccount `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- ClusterRoleBinding `knative-kafka-data-plane` for KafkaBroker has been renamed to `knative-kafka-broker-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- ClusterRole `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- ServiceAccount `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- ClusterRoleBinding `knative-kafka-data-plane` for KafkaSink has been renamed to `knative-kafka-sink-data-plane` ([#1315](https://github.com/knative-extensions/eventing-kafka-broker/pull/1315)) +- Set `status.deadLetterSinkUri` of Broker and Trigger to the resolved URI of `spec.delivery.deadLetterSink` ([#1349](https://github.com/knative-extensions/eventing-kafka-broker/pull/1349)) #### RabbitMQ Broker and Source v1.0 - + ##### πŸ’« New Features & Changes -- A trigger will now send events to its subscriber in parallel, with the number of in-flight messages defaulting to 10 and configurable via the annotationrabbitmq.eventing.knative.dev/prefetchCount. ([#418](https://github.com/knative-sandbox/eventing-rabbitmq/pull/418)) -- Trigger filters are now enforced to be immutable, since the underlying RMQ binding is immutable ([#468](https://github.com/knative-sandbox/eventing-rabbitmq/pull/468)) +- A trigger will now send events to its subscriber in parallel, with the number of in-flight messages defaulting to 10 and configurable via the annotationrabbitmq.eventing.knative.dev/prefetchCount. ([#418](https://github.com/knative-extensions/eventing-rabbitmq/pull/418)) +- Trigger filters are now enforced to be immutable, since the underlying RMQ binding is immutable ([#468](https://github.com/knative-extensions/eventing-rabbitmq/pull/468)) ##### 🐞 Bug Fixes -- Brokers will no longer create a queue for dead-lettered events if no dead letter sink is defined ([#453](https://github.com/knative-sandbox/eventing-rabbitmq/pull/453)) +- Brokers will no longer create a queue for dead-lettered events if no dead letter sink is defined ([#453](https://github.com/knative-extensions/eventing-rabbitmq/pull/453)) ### Client v1.0 diff --git a/blog/docs/releases/announcing-knative-v1-1-release.md b/blog/docs/releases/announcing-knative-v1-1-release.md index a8e9fea4bf..6683f8314a 100644 --- a/blog/docs/releases/announcing-knative-v1-1-release.md +++ b/blog/docs/releases/announcing-knative-v1-1-release.md @@ -72,40 +72,40 @@ Follow the instructions in the documentation #### Apache Kafka Broker v1.1 - + #### 🚨 Breaking or Notable Changes -- Add a new implementation of the KafkaSource API ([#1415](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1415)) -- Kafka Broker event delivery is hundreds of times faster ([#1405](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1405)) -- `broker.spec.config` is now required ([#1555](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1555)) +- Add a new implementation of the KafkaSource API ([#1415](https://github.com/knative-extensions/eventing-kafka-broker/pull/1415)) +- Kafka Broker event delivery is hundreds of times faster ([#1405](https://github.com/knative-extensions/eventing-kafka-broker/pull/1405)) +- `broker.spec.config` is now required ([#1555](https://github.com/knative-extensions/eventing-kafka-broker/pull/1555)) #### πŸ’« New Features & Changes -- The kafka-controller deployment emits probe requests against the data plane (kafka-sink-receiver and kafka-broker-receiver) to determine Kafka Broker and KafkaSink readiness ([#1495](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1495)) -- You can now configure which header format (b3 multi header, b3 single header, and w3c trace-context) to be used while using Zipkin backend ([#1546](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1546)) +- The kafka-controller deployment emits probe requests against the data plane (kafka-sink-receiver and kafka-broker-receiver) to determine Kafka Broker and KafkaSink readiness ([#1495](https://github.com/knative-extensions/eventing-kafka-broker/pull/1495)) +- You can now configure which header format (b3 multi header, b3 single header, and w3c trace-context) to be used while using Zipkin backend ([#1546](https://github.com/knative-extensions/eventing-kafka-broker/pull/1546)) - Handle non-retryable HTTP status codes as reported in the spec. -For more information, see the [Eventing spec](https://github.com/knative/specs/blob/c348f501de9eb998b4fd010c54d9127033ee41be/specs/eventing/data-plane.md#event-acknowledgement-and-delivery-retry) in GitHub ([#1574](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1574)) +For more information, see the [Eventing spec](https://github.com/knative/specs/blob/c348f501de9eb998b4fd010c54d9127033ee41be/specs/eventing/data-plane.md#event-acknowledgement-and-delivery-retry) in GitHub ([#1574](https://github.com/knative-extensions/eventing-kafka-broker/pull/1574)) #### RabbitMQ Broker and Source v1.1 - + #### πŸ’« New Features & Changes -- Adds tracing with opencensus to the dispatcher and ingress ([#370](https://github.com/knative-sandbox/eventing-rabbitmq/pull/370)) -- RabbitMQ source now can use predefined queues instead of creating new ones ([#493](https://github.com/knative-sandbox/eventing-rabbitmq/pull/493)) -- Now the source Adapter processes messages concurrently depending on the `channel_config.prefetch_count` argument (default to 1) ([#522](https://github.com/knative-sandbox/eventing-rabbitmq/pull/522)) -- Do not expose the broker class that the controller operates on as an environment variable ([#512](https://github.com/knative-sandbox/eventing-rabbitmq/pull/512)) -- The RabbitMQ Source now translates RabbitMQ messages according to the RabbitMQ Protocol Binding Spec for CloudEvents ([#475](https://github.com/knative-sandbox/eventing-rabbitmq/pull/475)) +- Adds tracing with opencensus to the dispatcher and ingress ([#370](https://github.com/knative-extensions/eventing-rabbitmq/pull/370)) +- RabbitMQ source now can use predefined queues instead of creating new ones ([#493](https://github.com/knative-extensions/eventing-rabbitmq/pull/493)) +- Now the source Adapter processes messages concurrently depending on the `channel_config.prefetch_count` argument (default to 1) ([#522](https://github.com/knative-extensions/eventing-rabbitmq/pull/522)) +- Do not expose the broker class that the controller operates on as an environment variable ([#512](https://github.com/knative-extensions/eventing-rabbitmq/pull/512)) +- The RabbitMQ Source now translates RabbitMQ messages according to the RabbitMQ Protocol Binding Spec for CloudEvents ([#475](https://github.com/knative-extensions/eventing-rabbitmq/pull/475)) - Falls back to RabbitMQ message content type if it is not set on the CloudEvent data or headers - Avoids re-wrapping RabbitMQ messages that are already in the CloudEvent format #### 🐞 Bug Fixes -- The trigger dispatcher will now only retry deliveries when response status codes status are 5XX, 404, 409, 429, or -1 ([#486](https://github.com/knative-sandbox/eventing-rabbitmq/pull/486)) +- The trigger dispatcher will now only retry deliveries when response status codes status are 5XX, 404, 409, 429, or -1 ([#486](https://github.com/knative-extensions/eventing-rabbitmq/pull/486)) ### Client v1.1 diff --git a/blog/docs/releases/announcing-knative-v1-2-release.md b/blog/docs/releases/announcing-knative-v1-2-release.md index 87fe84b704..1db78559c8 100644 --- a/blog/docs/releases/announcing-knative-v1-2-release.md +++ b/blog/docs/releases/announcing-knative-v1-2-release.md @@ -89,16 +89,16 @@ For more information, see [Eventing v1.2](#eventing-v12). #### Apache Kafka Broker v1.2 - + #### πŸ’« New Features & Changes - An HTTP header will be supplied to your event consumers when the Broker it is communicating with supports reply events. -This will always be sent while using this Kafka Broker since it supports handling reply events. ([#1771](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1771)) +This will always be sent while using this Kafka Broker since it supports handling reply events. ([#1771](https://github.com/knative-extensions/eventing-kafka-broker/pull/1771)) -- Apply back-pressure by limiting the number of in-flight dispatch requests in the unordered event consumption. ([#1750](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1750)) +- Apply back-pressure by limiting the number of in-flight dispatch requests in the unordered event consumption. ([#1750](https://github.com/knative-extensions/eventing-kafka-broker/pull/1750)) -- Support TLS for the metrics server. Now, the receiver and the dispatcher accept the following environment variables ([#1707](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1707)): +- Support TLS for the metrics server. Now, the receiver and the dispatcher accept the following environment variables ([#1707](https://github.com/knative-extensions/eventing-kafka-broker/pull/1707)): - `METRICS_PEM_CERT_PATH`: TLS cert path - `METRICS_PEM_KEY_PATH`: TLS key path - `METRICS_HOST`: metrics server host @@ -106,26 +106,26 @@ This will always be sent while using this Kafka Broker since it supports handlin #### RabbitMQ Broker and Source v1.2 - + #### πŸ’« New Features & Changes -- Improved Broker's and Source's README docs, sample descriptions, and files. ([#555](https://github.com/knative-sandbox/eventing-rabbitmq/pull/555)) -- Add publisher confirms to ingress. Return 200 only when RabbitMQ confirms receiving and storing the message. ([#568](https://github.com/knative-sandbox/eventing-rabbitmq/pull/568)) -- Makefile-based workflow. Includes migrating GitHub Actions. ([#525](https://github.com/knative-sandbox/eventing-rabbitmq/pull/525), [#569](https://github.com/knative-sandbox/eventing-rabbitmq/pull/569), [#579](https://github.com/knative-sandbox/eventing-rabbitmq/pull/579)) -- Various code refactoring and code health improvements. ([#552](https://github.com/knative-sandbox/eventing-rabbitmq/pull/552), [#572](https://github.com/knative-sandbox/eventing-rabbitmq/pull/572)) +- Improved Broker's and Source's README docs, sample descriptions, and files. ([#555](https://github.com/knative-extensions/eventing-rabbitmq/pull/555)) +- Add publisher confirms to ingress. Return 200 only when RabbitMQ confirms receiving and storing the message. ([#568](https://github.com/knative-extensions/eventing-rabbitmq/pull/568)) +- Makefile-based workflow. Includes migrating GitHub Actions. ([#525](https://github.com/knative-extensions/eventing-rabbitmq/pull/525), [#569](https://github.com/knative-extensions/eventing-rabbitmq/pull/569), [#579](https://github.com/knative-extensions/eventing-rabbitmq/pull/579)) +- Various code refactoring and code health improvements. ([#552](https://github.com/knative-extensions/eventing-rabbitmq/pull/552), [#572](https://github.com/knative-extensions/eventing-rabbitmq/pull/572)) - Source adapter trigger dispatcher homologation. Now the Source Adapter and Broker Dispatcher's Prefetch Count behavior is the same. -Updated the Trigger's webhook to validate the following ([#536](https://github.com/knative-sandbox/eventing-rabbitmq/pull/536)): +Updated the Trigger's webhook to validate the following ([#536](https://github.com/knative-extensions/eventing-rabbitmq/pull/536)): - Has a default value of 1. FIFO behavior - Have limits: 1 ≀ prefetchCount ≀ 1000 -- All core Knative Eventing RabbitMQ Pods should now be able to run in the restricted Pod security standard profile. ([#541](https://github.com/knative-sandbox/eventing-rabbitmq/pull/541)) +- All core Knative Eventing RabbitMQ Pods should now be able to run in the restricted Pod security standard profile. ([#541](https://github.com/knative-extensions/eventing-rabbitmq/pull/541)) #### 🐞 Bug Fixes - Removing the dead letter sink on a Trigger will now properly fall back to the -Broker's dead letter sink, if one is defined. ([#533](https://github.com/knative-sandbox/eventing-rabbitmq/pull/533)) -- Messages sent to RabbitMQ are now marked as Persistent ([#560](https://github.com/knative-sandbox/eventing-rabbitmq/pull/560)): +Broker's dead letter sink, if one is defined. ([#533](https://github.com/knative-extensions/eventing-rabbitmq/pull/533)) +- Messages sent to RabbitMQ are now marked as Persistent ([#560](https://github.com/knative-extensions/eventing-rabbitmq/pull/560)): - Configuring messages sent into the RabbitMQ Broker to be persistent as the Queues used by the Broker are always durable. - Now if the user set the configuration of the RabbitMQ Source Exchange and diff --git a/blog/docs/releases/announcing-knative-v1-3-release.md b/blog/docs/releases/announcing-knative-v1-3-release.md index 76675f494a..2280af3adb 100644 --- a/blog/docs/releases/announcing-knative-v1-3-release.md +++ b/blog/docs/releases/announcing-knative-v1-3-release.md @@ -87,32 +87,32 @@ This helps to avoid hitting 503 errors during upgrade. ([#12617](https://github. ### Apache Kafka Broker v1.3 - + #### πŸ’« New Features & Changes -- Shows an error in the Broker and Channel status when resolving sink failures. ([#1833](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1833)) -- Added KafkaSource migration logic as a post-install job (`eventing-kafka-post-install.yaml`). ([#1889](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1889)) -- Added Storage-Version-Migrator for KafkaSource and KafkaChannel. ([#1869](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1869)) -- KafkaChannel is now conformant with the spec. Conformance tests are now run with every code change. ([#1825](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1825)) +- Shows an error in the Broker and Channel status when resolving sink failures. ([#1833](https://github.com/knative-extensions/eventing-kafka-broker/pull/1833)) +- Added KafkaSource migration logic as a post-install job (`eventing-kafka-post-install.yaml`). ([#1889](https://github.com/knative-extensions/eventing-kafka-broker/pull/1889)) +- Added Storage-Version-Migrator for KafkaSource and KafkaChannel. ([#1869](https://github.com/knative-extensions/eventing-kafka-broker/pull/1869)) +- KafkaChannel is now conformant with the spec. Conformance tests are now run with every code change. ([#1825](https://github.com/knative-extensions/eventing-kafka-broker/pull/1825)) #### 🐞 Bug Fixes -- Added support for Brokers with long namespace and name values. ([#1971](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1971)) -- KafkaChannel reconciler checks for empty subscriber URI. ([#1905](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1905)) +- Added support for Brokers with long namespace and name values. ([#1971](https://github.com/knative-extensions/eventing-kafka-broker/pull/1971)) +- KafkaChannel reconciler checks for empty subscriber URI. ([#1905](https://github.com/knative-extensions/eventing-kafka-broker/pull/1905)) #### Known issues -- The reference information for metrics is not built successfully for Kafka channels. ([#1824](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1824)) +- The reference information for metrics is not built successfully for Kafka channels. ([#1824](https://github.com/knative-extensions/eventing-kafka-broker/pull/1824)) ### RabbitMQ Broker and Source v1.3 - + #### πŸ’« New Features & Changes -- Broker URLs updated to be `http:////`. ([#587](https://github.com/knative-sandbox/eventing-rabbitmq/pull/587)) -- Short testing guide for contributors, converting from `.env` -> to `(direnv friendly).envrc` environment files. ([#599](https://github.com/knative-sandbox/eventing-rabbitmq/pull/599)) +- Broker URLs updated to be `http:////`. ([#587](https://github.com/knative-extensions/eventing-rabbitmq/pull/587)) +- Short testing guide for contributors, converting from `.env` -> to `(direnv friendly).envrc` environment files. ([#599](https://github.com/knative-extensions/eventing-rabbitmq/pull/599)) ## Client v1.3 diff --git a/blog/docs/releases/announcing-knative-v1-4-release.md b/blog/docs/releases/announcing-knative-v1-4-release.md index 119847ad33..2d93d78884 100644 --- a/blog/docs/releases/announcing-knative-v1-4-release.md +++ b/blog/docs/releases/announcing-knative-v1-4-release.md @@ -85,7 +85,7 @@ Follow the instructions in - Reduced duplication of observability.yaml config map which existed in multiple locations by symlinking "config/channels/in-memory-channel/configmaps/observability.yaml" to "config/core/configmaps/observability.yaml". ([#6301](https://github.com/knative/eventing/pull/6301)) - Reduced duplication of tracing.yaml config map which existed in multiple locations by symlinking "config/channels/in-memory-channel/configmaps/tracing.yaml" to "config/core/configmaps/tracing.yaml". ([#6295](https://github.com/knative/eventing/pull/6295)) -- The `sendevent` tool is not part of Eventing core anymore, an alternative is available as `kn` plugin https://github.com/knative-sandbox/kn-plugin-event ([#6284](https://github.com/knative/eventing/pull/6284)) +- The `sendevent` tool is not part of Eventing core anymore, an alternative is available as `kn` plugin https://github.com/knative-extensions/kn-plugin-event ([#6284](https://github.com/knative/eventing/pull/6284)) ### 🐞 Bug Fixes @@ -97,33 +97,33 @@ Follow the instructions in ### Apache Kafka Broker v1.4 - + #### πŸ’« New Features & Changes - - Handle host headers in dataplane for identification of channel instances ([#1990](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1990)) - - There is now auto-migration from old consolidated KafkaChannel to the new KafkaChannel. Low level configuration options such as Sarama settings are not migrated to the new channel. However, channel url and auth settings are migrated. ([#2004](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2004)) - - Discard Consumer records that are not CloudEvents ([#2066](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2066)) - - Dynamically set max.poll.interval.ms based on the delivery spec ([#2058](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2058)) + - Handle host headers in dataplane for identification of channel instances ([#1990](https://github.com/knative-extensions/eventing-kafka-broker/pull/1990)) + - There is now auto-migration from old consolidated KafkaChannel to the new KafkaChannel. Low level configuration options such as Sarama settings are not migrated to the new channel. However, channel url and auth settings are migrated. ([#2004](https://github.com/knative-extensions/eventing-kafka-broker/pull/2004)) + - Discard Consumer records that are not CloudEvents ([#2066](https://github.com/knative-extensions/eventing-kafka-broker/pull/2066)) + - Dynamically set max.poll.interval.ms based on the delivery spec ([#2058](https://github.com/knative-extensions/eventing-kafka-broker/pull/2058)) - The default request timeout is 10 minutes now, it was previously set to 10 seconds. - - It can be overridden using spec.delivery.timeout on Broker, Trigger, KafkaChannel and Subscription. ([#2057](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2057)) - - Add new new-trigger-filters experimental feature. When enabled, Triggers support a new filters field that conforms to the filters API field defined in the CloudEvents Subscriptions API. It allows you to specify a set of powerful filter expressions, where each expression evaluates to either true or false for each event. ([#1992](https://github.com/knative-sandbox/eventing-kafka-broker/pull/1992)) + - It can be overridden using spec.delivery.timeout on Broker, Trigger, KafkaChannel and Subscription. ([#2057](https://github.com/knative-extensions/eventing-kafka-broker/pull/2057)) + - Add new new-trigger-filters experimental feature. When enabled, Triggers support a new filters field that conforms to the filters API field defined in the CloudEvents Subscriptions API. It allows you to specify a set of powerful filter expressions, where each expression evaluates to either true or false for each event. ([#1992](https://github.com/knative-extensions/eventing-kafka-broker/pull/1992)) ### RabbitMQ Broker and Source v1.4 - + ### 🚨 Breaking or Notable Changes -- Remove support for managed RabbitMQ brokers ([#708](https://github.com/knative-sandbox/eventing-rabbitmq/pull/708)) +- Remove support for managed RabbitMQ brokers ([#708](https://github.com/knative-extensions/eventing-rabbitmq/pull/708)) #### πŸ’« New Features & Changes -- Now performance graphs for the RabbitMQ Broker are going to be generated for every mayor version release inside our performance test directories ([#668](https://github.com/knative-sandbox/eventing-rabbitmq/pull/668)) -- Now the RabbitMQ Source, when failing to send an event, does not get stuck in a cycle requeueing messages as they come. It follows a retries based backoff strategy (and does not reqeue them if the prefetchCount is 1) ([#614](https://github.com/knative-sandbox/eventing-rabbitmq/pull/614)) -- Now the RabbitMQ's Broker Ingress pod can recover from a closed Channel or Connection ([#648](https://github.com/knative-sandbox/eventing-rabbitmq/pull/648)) -- Changed prefetchCount env variable name to Parallelism in both Trigger and Source, to better reflect its functionality ([#676](https://github.com/knative-sandbox/eventing-rabbitmq/pull/676)) +- Now performance graphs for the RabbitMQ Broker are going to be generated for every mayor version release inside our performance test directories ([#668](https://github.com/knative-extensions/eventing-rabbitmq/pull/668)) +- Now the RabbitMQ Source, when failing to send an event, does not get stuck in a cycle requeueing messages as they come. It follows a retries based backoff strategy (and does not reqeue them if the prefetchCount is 1) ([#614](https://github.com/knative-extensions/eventing-rabbitmq/pull/614)) +- Now the RabbitMQ's Broker Ingress pod can recover from a closed Channel or Connection ([#648](https://github.com/knative-extensions/eventing-rabbitmq/pull/648)) +- Changed prefetchCount env variable name to Parallelism in both Trigger and Source, to better reflect its functionality ([#676](https://github.com/knative-extensions/eventing-rabbitmq/pull/676)) ## Client v1.4 @@ -143,11 +143,11 @@ Follow the instructions in - The kn-plugin-event plugin is now included since this release. - The plugins that are released in parallel and aligned with Knative v1.4.0 are: - - `kn-plugin-admin` for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-sandbox/kn-plugin-admin/releases/tag/knative-v1.4.0) - - `kn-plugin-quickstart` to quickly set up a local Knative environment from the command line. | [download](https://github.com/knative-sandbox/kn-plugin-quickstart/releases/tag/knative-v1.4.0) - - `kn-plugin-source-kafka` for managing a Kafka Source that has been installed via eventing-kafka on the backend | [download](https://github.com/knative-sandbox/kn-plugin-source-kafka/releases/tag/knative-v1.4.0) - - `kn-plugin-source-kamelet` for managing Kamelet Sources that has been installed via Camel-K on the backend | [download](https://github.com/knative-sandbox/kn-plugin-source-kamelet/releases/tag/knative-v1.4.0) - - `kn-plugin-event` for creating and sending CloudEvents from insider or outside the cluster | [download](https://github.com/knative-sandbox/kn-plugin-event/releases/tag/knative-v1.4.0) + - `kn-plugin-admin` for managing Knative installations that are running on Kubernetes | [download](https://github.com/knative-extensions/kn-plugin-admin/releases/tag/knative-v1.4.0) + - `kn-plugin-quickstart` to quickly set up a local Knative environment from the command line. | [download](https://github.com/knative-extensions/kn-plugin-quickstart/releases/tag/knative-v1.4.0) + - `kn-plugin-source-kafka` for managing a Kafka Source that has been installed via eventing-kafka on the backend | [download](https://github.com/knative-extensions/kn-plugin-source-kafka/releases/tag/knative-v1.4.0) + - `kn-plugin-source-kamelet` for managing Kamelet Sources that has been installed via Camel-K on the backend | [download](https://github.com/knative-extensions/kn-plugin-source-kamelet/releases/tag/knative-v1.4.0) + - `kn-plugin-event` for creating and sending CloudEvents from insider or outside the cluster | [download](https://github.com/knative-extensions/kn-plugin-event/releases/tag/knative-v1.4.0) Note: All those plugins are released separately and are technically not part of this knative/client release, however they are aligned to share the same Knative dependencies and can be targeted for inlining. diff --git a/blog/docs/releases/announcing-knative-v1-5-release.md b/blog/docs/releases/announcing-knative-v1-5-release.md index 2b8140b94b..1cb55ab6a0 100644 --- a/blog/docs/releases/announcing-knative-v1-5-release.md +++ b/blog/docs/releases/announcing-knative-v1-5-release.md @@ -61,8 +61,8 @@ Follow the instructions in [Installing Knative](https://knative.dev/docs/install #### πŸ’« New Features & Changes -- Cert-manager is now in version 1.8.0. ([#399](https://github.com/knative-sandbox/net-certmanager/issues/399)) -- Secrets automatically generated due to certificate creation are labeled with a special label key to support proper filtering from K8s informers in components that consume them. ([#402](https://github.com/knative-sandbox/net-certmanager/402)) +- Cert-manager is now in version 1.8.0. ([#399](https://github.com/knative-extensions/net-certmanager/issues/399)) +- Secrets automatically generated due to certificate creation are labeled with a special label key to support proper filtering from K8s informers in components that consume them. ([#402](https://github.com/knative-extensions/net-certmanager/402)) ### Istio plugin (net-istio) @@ -74,58 +74,58 @@ Secret informer in ingress controller can be enabled to filter secrets based on For special cases users are recommended to reach out to Knative community. - In case of AutoTLS provided by Knative net-certmanager this is done transparently. - To enable this behavior at net-istio set env var `ENABLE_SECRET_INFORMER_FILTERING_BY_CERT_UID` to `true`. - - This will be available by default in future releases. ([#920](https://github.com/knative-sandbox/net-istio/issues/920)) - - local-gateway.mesh: "mesh" option was dropped. ([#915](https://github.com/knative-sandbox/net-istio/issues/915)) + - This will be available by default in future releases. ([#920](https://github.com/knative-extensions/net-istio/issues/920)) + - local-gateway.mesh: "mesh" option was dropped. ([#915](https://github.com/knative-extensions/net-istio/issues/915)) ## Eventing Extensions ### Apache Kafka Broker - + #### πŸ’« New Features & Changes -- Deploy just the KafkaSource v2 controller and new statefulset dispatcher (no receiver) for users of KakfaSource ([#2089](https://github.com/knative-sandbox/eventing-kafka-broker/issues/2089)) -- With the `kafka.eventing.knative.dev/external.topic` annotation it is possible to use an externally managed Apache Kafka topic for the broker usage ([#1023](https://github.com/knative-sandbox/eventing-kafka-broker/issues/1023)) -- `vertx_*` metrics have been removed since they were causing unnecessary allocations. ([#2147](https://github.com/knative-sandbox/eventing-kafka-broker/issues/2147)) +- Deploy just the KafkaSource v2 controller and new statefulset dispatcher (no receiver) for users of KakfaSource ([#2089](https://github.com/knative-extensions/eventing-kafka-broker/issues/2089)) +- With the `kafka.eventing.knative.dev/external.topic` annotation it is possible to use an externally managed Apache Kafka topic for the broker usage ([#1023](https://github.com/knative-extensions/eventing-kafka-broker/issues/1023)) +- `vertx_*` metrics have been removed since they were causing unnecessary allocations. ([#2147](https://github.com/knative-extensions/eventing-kafka-broker/issues/2147)) - 🧽 Update or clean up current behavior - The control plane sends retry configurations to the data plane. ([#263](https://github.com/knative-sandbox/eventing-kafka-broker/issues/263/)) + The control plane sends retry configurations to the data plane. ([#263](https://github.com/knative-extensions/eventing-kafka-broker/issues/263/)) #### 🐞 Bug Fixes -- Receiver's prober targets services instead of pods directly to allow components to be part of an Istio mesh ([#2112](https://github.com/knative-sandbox/eventing-kafka-broker/issues/2112)) +- Receiver's prober targets services instead of pods directly to allow components to be part of an Istio mesh ([#2112](https://github.com/knative-extensions/eventing-kafka-broker/issues/2112)) ### RabbitMQ Broker and Source - + ### 🚨 Breaking or Notable -- With the removal of standalone-broker, Secret type is no longer a supported Broker.Config ([#773](https://github.com/knative-sandbox/eventing-rabbitmq/issues/773)) +- With the removal of standalone-broker, Secret type is no longer a supported Broker.Config ([#773](https://github.com/knative-extensions/eventing-rabbitmq/issues/773)) #### πŸ’« New Features & Changes -- A new type RabbitmqBrokerConfig can be used to configure a Broker ([#780](https://github.com/knative-sandbox/eventing-rabbitmq/issues/780)) -- Dispatcher will timeout after 30s when sending to the subscriber ([#687](https://github.com/knative-sandbox/eventing-rabbitmq/issues/687)) -- Now the docs are better organized and performance tests graphs are correct ([#721](https://github.com/knative-sandbox/eventing-rabbitmq/issues/721)) -- Resource requests for source controller increased ([#738](https://github.com/knative-sandbox/eventing-rabbitmq/issues/738)) +- A new type RabbitmqBrokerConfig can be used to configure a Broker ([#780](https://github.com/knative-extensions/eventing-rabbitmq/issues/780)) +- Dispatcher will timeout after 30s when sending to the subscriber ([#687](https://github.com/knative-extensions/eventing-rabbitmq/issues/687)) +- Now the docs are better organized and performance tests graphs are correct ([#721](https://github.com/knative-extensions/eventing-rabbitmq/issues/721)) +- Resource requests for source controller increased ([#738](https://github.com/knative-extensions/eventing-rabbitmq/issues/738)) - The Broker's Ingress and Dispatcher have deployment resource requests and limits - - The Source's Receive Adapter have deployment resources requests and limits ([#771](https://github.com/knative-sandbox/eventing-rabbitmq/issues/771)) + - The Source's Receive Adapter have deployment resources requests and limits ([#771](https://github.com/knative-extensions/eventing-rabbitmq/issues/771)) - The Broker's ingress uses the Binary representation of the CloudEvents - The Broker's Dispatcher uses the protocol binding to get a CloudEvent from a RabbitMQ Message - - Added performance tests for the source using the new Ingress CE Binary representation, that makes the Ingress plugable to the Source ([#751](https://github.com/knative-sandbox/eventing-rabbitmq/issues/751)) + - Added performance tests for the source using the new Ingress CE Binary representation, that makes the Ingress plugable to the Source ([#751](https://github.com/knative-extensions/eventing-rabbitmq/issues/751)) - Script to automate the generation of the performance results per release - - Complete performance results graph tests for the RabbitMQ's Broker and Source ([#767](https://github.com/knative-sandbox/eventing-rabbitmq/issues/767)) + - Complete performance results graph tests for the RabbitMQ's Broker and Source ([#767](https://github.com/knative-extensions/eventing-rabbitmq/issues/767)) #### 🐞 Bug Fixes - The backoffDelay env variable is parsed correctly on the Broker's and Trigger's Dispatcher - - The backoffDelay env variable is parsed correctly on the Source's receive adapter ([#750](https://github.com/knative-sandbox/eventing-rabbitmq/issues/750)) + - The backoffDelay env variable is parsed correctly on the Source's receive adapter ([#750](https://github.com/knative-extensions/eventing-rabbitmq/issues/750)) - BackoffDelay is used when defined in Broker or Trigger delivery spec - - dead letter messaging uses the same delivery spec ([#723](https://github.com/knative-sandbox/eventing-rabbitmq/issues/723)) -- Fixed bug in Trigger dispatcher deployment from getting updated too frequently ([#744](https://github.com/knative-sandbox/eventing-rabbitmq/issues/744)) -- Fixed bug where the broker ingress was not reconnecting after the connection or channel with RabbitMQ was closed ([#778](https://github.com/knative-sandbox/eventing-rabbitmq/issues/778)) + - dead letter messaging uses the same delivery spec ([#723](https://github.com/knative-extensions/eventing-rabbitmq/issues/723)) +- Fixed bug in Trigger dispatcher deployment from getting updated too frequently ([#744](https://github.com/knative-extensions/eventing-rabbitmq/issues/744)) +- Fixed bug where the broker ingress was not reconnecting after the connection or channel with RabbitMQ was closed ([#778](https://github.com/knative-extensions/eventing-rabbitmq/issues/778)) ## Client diff --git a/blog/docs/releases/announcing-knative-v1-6-release.md b/blog/docs/releases/announcing-knative-v1-6-release.md index 70ff4810bf..c549e37185 100644 --- a/blog/docs/releases/announcing-knative-v1-6-release.md +++ b/blog/docs/releases/announcing-knative-v1-6-release.md @@ -74,22 +74,22 @@ This release brings a number of smaller improvements to the core Knative Serving #### πŸ’« New Features & Changes -* Add a new experimental configuration parameter to separate internal traffic for different namespaces by TCP port. This should enable use of NetworkPolicy with Knative. [#852](https://github.com/knative-sandbox/net-kourier/pull/852) -* Experimentally enable filtered secret watches when using AutoTLS. This should provide performance improvements in large clusters. [#862](https://github.com/knative-sandbox/net-kourier/pull/862) +* Add a new experimental configuration parameter to separate internal traffic for different namespaces by TCP port. This should enable use of NetworkPolicy with Knative. [#852](https://github.com/knative-extensions/net-kourier/pull/852) +* Experimentally enable filtered secret watches when using AutoTLS. This should provide performance improvements in large clusters. [#862](https://github.com/knative-extensions/net-kourier/pull/862) ### 🐞 Bug Fixes -* Fix SNI when using `proxy_protocol`. [#869](https://github.com/knative-sandbox/net-kourier/pull/869) +* Fix SNI when using `proxy_protocol`. [#869](https://github.com/knative-extensions/net-kourier/pull/869) ### Gateway-API plugin #### πŸ’« New Features & Changes -* Adds support for AutoTLS [#316](https://github.com/knative-sandbox/net-gateway-api/pull/316) +* Adds support for AutoTLS [#316](https://github.com/knative-extensions/net-gateway-api/pull/316) ### 🐞 Bug Fixes -* Network programming probes now respect the Service port of the gateway. [#310](https://github.com/knative-sandbox/net-gateway-api/pull/310) +* Network programming probes now respect the Service port of the gateway. [#310](https://github.com/knative-extensions/net-gateway-api/pull/310) ## Eventing Extensions @@ -97,26 +97,26 @@ This release brings a number of smaller improvements to the core Knative Serving #### 🐞 Bug Fixes -* Deletion of KafkaSource resources now properly cleans up internal scheduling resources. [#1206](https://github.com/knative-sandbox/eventing-kafka/pull/1206) +* Deletion of KafkaSource resources now properly cleans up internal scheduling resources. [#1206](https://github.com/knative-extensions/eventing-kafka/pull/1206) ### RabbitMQ Broker and Source #### Breaking Changes -* Some deprecated fine-grained configuration options have been removed from RabbitMQSource. [#800](https://github.com/knative-sandbox/eventing-rabbitmq/pull/800) -* RabbitMQSource now uses a RabbitCluster reference like the Broker. [#801](https://github.com/knative-sandbox/eventing-rabbitmq/pull/801) -* RabbitMQSource parameters have been re-arranged into logical groups. [#810](https://github.com/knative-sandbox/eventing-rabbitmq/pull/810) +* Some deprecated fine-grained configuration options have been removed from RabbitMQSource. [#800](https://github.com/knative-extensions/eventing-rabbitmq/pull/800) +* RabbitMQSource now uses a RabbitCluster reference like the Broker. [#801](https://github.com/knative-extensions/eventing-rabbitmq/pull/801) +* RabbitMQSource parameters have been re-arranged into logical groups. [#810](https://github.com/knative-extensions/eventing-rabbitmq/pull/810) #### πŸ’« New Features & Changes -* Message pre-fetch is now automatically set to 100, increasing steady-state throughput. [#856](https://github.com/knative-sandbox/eventing-rabbitmq/pull/856) -* Added the ability to configure queue types in RabbitmqBrokerConfig. [#808](https://github.com/knative-sandbox/eventing-rabbitmq/pull/803) -* Support for RabbitMQ ClusterReference connection secrets. [#822](https://github.com/knative-sandbox/eventing-rabbitmq/pull/822) +* Message pre-fetch is now automatically set to 100, increasing steady-state throughput. [#856](https://github.com/knative-extensions/eventing-rabbitmq/pull/856) +* Added the ability to configure queue types in RabbitmqBrokerConfig. [#808](https://github.com/knative-extensions/eventing-rabbitmq/pull/803) +* Support for RabbitMQ ClusterReference connection secrets. [#822](https://github.com/knative-extensions/eventing-rabbitmq/pull/822) #### 🐞 Bug Fixes -* Fixed a bug where RabbitMQSource objects with `retries` configured could crash when receiving an error from the event destination. [#831](https://github.com/knative-sandbox/eventing-rabbitmq/pull/831) +* Fixed a bug where RabbitMQSource objects with `retries` configured could crash when receiving an error from the event destination. [#831](https://github.com/knative-extensions/eventing-rabbitmq/pull/831) ## Thank you, contributors diff --git a/blog/docs/releases/announcing-knative-v1-7-release.md b/blog/docs/releases/announcing-knative-v1-7-release.md index 386f9d41fd..f69a836803 100644 --- a/blog/docs/releases/announcing-knative-v1-7-release.md +++ b/blog/docs/releases/announcing-knative-v1-7-release.md @@ -68,7 +68,7 @@ This release brings a number of smaller improvements to the core Knative Serving #### πŸ’« New Features & Changes -* The timeout can be configured via stream-idle-timeout in config-kourier, the default value is set to "infinity" which means there is no timeout. Users can change this value in config-kourier with decimal numbers plus a unit suffix such as "ns", "us" (or "Β΅s"), "ms", "s", "m", "h". [#878](https://github.com/knative-sandbox/net-kourier/pull/878) +* The timeout can be configured via stream-idle-timeout in config-kourier, the default value is set to "infinity" which means there is no timeout. Users can change this value in config-kourier with decimal numbers plus a unit suffix such as "ns", "us" (or "Β΅s"), "ms", "s", "m", "h". [#878](https://github.com/knative-extensions/net-kourier/pull/878) ## Eventing Extensions @@ -76,12 +76,12 @@ This release brings a number of smaller improvements to the core Knative Serving #### πŸ’« New Features & Changes -* Changed partition strategy for rebalancing from default (`RangeAssignor`) to `StickyAssignor` . [#2299](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2299) -* Failed events are now decorated with Knative error extensions when routed to the `deadLetterSink` for more context. [#2374](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2374) +* Changed partition strategy for rebalancing from default (`RangeAssignor`) to `StickyAssignor` . [#2299](https://github.com/knative-extensions/eventing-kafka-broker/pull/2299) +* Failed events are now decorated with Knative error extensions when routed to the `deadLetterSink` for more context. [#2374](https://github.com/knative-extensions/eventing-kafka-broker/pull/2374) #### 🐞 Bug Fixes -* Kafka Broker and KafkaSink ignore a trailing slash in the HTTP path. [#2462](https://github.com/knative-sandbox/eventing-kafka-broker/pull/2462) +* Kafka Broker and KafkaSink ignore a trailing slash in the HTTP path. [#2462](https://github.com/knative-extensions/eventing-kafka-broker/pull/2462) ## Thank you, contributors diff --git a/blog/docs/releases/announcing-knative-v1-8-release.md b/blog/docs/releases/announcing-knative-v1-8-release.md index 0cacd8ff87..023c7ef78b 100644 --- a/blog/docs/releases/announcing-knative-v1-8-release.md +++ b/blog/docs/releases/announcing-knative-v1-8-release.md @@ -32,7 +32,7 @@ This release brings a number of smaller improvements to the core Knative Serving ### πŸ’« New Release -* [Security-Guard Alpha](https://github.com/knative-sandbox/security-guard/releases/tag/v0.2.0) is now released to allow cyber monitoring and control of knative services. +* [Security-Guard Alpha](https://github.com/knative-extensions/security-guard/releases/tag/v0.2.0) is now released to allow cyber monitoring and control of knative services. ## Serving diff --git a/code-samples/eventing/github-source/README.md b/code-samples/eventing/github-source/README.md index 125f62ce43..0cb333df07 100644 --- a/code-samples/eventing/github-source/README.md +++ b/code-samples/eventing/github-source/README.md @@ -12,11 +12,11 @@ by a Knative Service. ### Install GitHub Event Source -GitHub Event source lives in [knative-sandbox/eventing-github](https://github.com/knative-sandbox/eventing-github). Head to the releases page, find the latest release with the `github.yaml` +GitHub Event source lives in [knative-extensions/eventing-github](https://github.com/knative-extensions/eventing-github). Head to the releases page, find the latest release with the `github.yaml` artifact and replace `` with the version tag: ```bash -kubectl apply -f https://github.com/knative-sandbox/eventing-github/releases/download//github.yaml +kubectl apply -f https://github.com/knative-extensions/eventing-github/releases/download//github.yaml ``` Check that the manager is running: diff --git a/code-samples/eventing/gitlab-source/README.md b/code-samples/eventing/gitlab-source/README.md index 24412a9069..26723648ee 100644 --- a/code-samples/eventing/gitlab-source/README.md +++ b/code-samples/eventing/gitlab-source/README.md @@ -17,11 +17,11 @@ You will need: ### Install GitLab Event Source -GitLab Event source lives in the [knative-sandbox/eventing-gitlab](https://github.com/knative-sandbox/eventing-gitlab). Head to the releases page, find the latest release with `gitlab.yaml` +GitLab Event source lives in the [knative-extensions/eventing-gitlab](https://github.com/knative-extensions/eventing-gitlab). Head to the releases page, find the latest release with `gitlab.yaml` artifact and replace the `` with version tag: ```bash -kubectl apply -f https://github.com/knative-sandbox/eventing-gitlab/releases/download//gitlab.yaml +kubectl apply -f https://github.com/knative-extensions/eventing-gitlab/releases/download//gitlab.yaml ``` Check that the manager is running: diff --git a/code-samples/eventing/kafka/binding/README.md b/code-samples/eventing/kafka/binding/README.md index 7db75ffc98..ce2340f44c 100644 --- a/code-samples/eventing/kafka/binding/README.md +++ b/code-samples/eventing/kafka/binding/README.md @@ -143,7 +143,7 @@ In this case, we will bind any `Job` with the labels `kafka.topic: "logs"`. 1. Source code for kafka-publisher service Get the source code of kafka-publisher container image from - [here](https://github.com/knative-sandbox/eventing-kafka/blob/main/test/test_images/kafka-publisher/main.go) + [here](https://github.com/knative-extensions/eventing-kafka/blob/main/test/test_images/kafka-publisher/main.go) 1. Now we will use the kafka-publisher container to send events to kafka topic when the Job runs. diff --git a/code-samples/eventing/kafka/channel/README.md b/code-samples/eventing/kafka/channel/README.md index 599bfd0eb5..aec662f231 100644 --- a/code-samples/eventing/kafka/channel/README.md +++ b/code-samples/eventing/kafka/channel/README.md @@ -247,4 +247,4 @@ KafkaChannel provides various configuration options, such as: - The brokers string for your Kafka connection For detailed information on configuration options, see the -[KafkaChannel README](https://github.com/knative-sandbox/eventing-kafka-broker/blob/main/docs/channel/README.md). +[KafkaChannel README](https://github.com/knative-extensions/eventing-kafka-broker/blob/main/docs/channel/README.md). diff --git a/config/redirects.yml b/config/redirects.yml index cdff8b8877..fb2a9b9f4d 100644 --- a/config/redirects.yml +++ b/config/redirects.yml @@ -94,7 +94,7 @@ plugins: developer/eventing/sources/creating-event-sources/writing-event-source/04-reconciler.md: eventing/custom-event-source/custom-event-source/receive-adapter.md developer/eventing/sources/creating-event-sources/writing-event-source/05-receive-adapter.md: eventing/custom-event-source/custom-event-source/receive-adapter.md developer/eventing/sources/creating-event-sources/writing-event-source/06-yaml.md: eventing/custom-event-source/custom-event-source/publish-event-source.md - developer/eventing/sources/creating-event-sources/writing-event-source/07-knative-sandbox.md: eventing/custom-event-source/custom-event-source/README.md + developer/eventing/sources/creating-event-sources/writing-event-source/07-knative-extensions.md: eventing/custom-event-source/custom-event-source/README.md developer/eventing/sources/creating-event-sources/writing-event-source/README.md: eventing/custom-event-source/custom-event-source/README.md developer/eventing/sources/kafka-source/README.md: eventing/sources/kafka-source/README.md developer/eventing/sources/ping-source/README.md: eventing/sources/ping-source/README.md diff --git a/docs/client/kn-plugins.md b/docs/client/kn-plugins.md index 014725d867..3d5085376f 100644 --- a/docs/client/kn-plugins.md +++ b/docs/client/kn-plugins.md @@ -15,22 +15,22 @@ An event source plugin has the following characteristics: ## List of Knative plugins -You can view all available `kn` plugins in the [Knative Sandbox repository](https://github.com/orgs/knative-sandbox/repositories?q=kn+plugin&type=all&language=&sort=). +You can view all available `kn` plugins in the [Knative Sandbox repository](https://github.com/orgs/knative-extensions/repositories?q=kn+plugin&type=all&language=&sort=). | Plugin | Description | Available via Homebrew? | | --- | --- | :---: | -| [kn-plugin-admin](https://github.com/knative-sandbox/kn-plugin-admin) | `kn` plugin for managing a Kubernetes based Knative installation | Y | -| [kn-plugin-diag](https://github.com/knative-sandbox/kn-plugin-diag) | `kn` plugin for diagnosing issues by exposing detailed information for different layers of Knative objects | N | -| [kn-plugin-event](https://github.com/knative-sandbox/kn-plugin-event) | `kn` plugin for sending events to Knative sinks | Y | +| [kn-plugin-admin](https://github.com/knative-extensions/kn-plugin-admin) | `kn` plugin for managing a Kubernetes based Knative installation | Y | +| [kn-plugin-diag](https://github.com/knative-extensions/kn-plugin-diag) | `kn` plugin for diagnosing issues by exposing detailed information for different layers of Knative objects | N | +| [kn-plugin-event](https://github.com/knative-extensions/kn-plugin-event) | `kn` plugin for sending events to Knative sinks | Y | | [kn-plugin-func](https://github.com/knative/func) | `kn` plugin for functions | Y | -| [kn-plugin-migration](https://github.com/knative-sandbox/kn-plugin-migration) | `kn` plugin for migrating Knative Services from one cluster to another | N | -| [kn-plugin-operator](https://github.com/knative-sandbox/kn-plugin-operator) | `kn` plugin for managing Knative with Knative Operator | N | -| [kn-plugin-quickstart](https://github.com/knative-sandbox/kn-plugin-quickstart) | `kn` plugin for developers to install a quickstart Knative cluster for experimentation purposes | Y | -| [kn-plugin-service-log](https://github.com/knative-sandbox/kn-plugin-service-log) | `kn` plugin for showing the standard output of Knative Services | N | -| [kn-plugin-source-kafka](https://github.com/knative-sandbox/kn-plugin-source-kafka) | `kn` plugin for managing Kafka event sources | Y | -| [kn-plugin-source-kamelet](https://github.com/knative-sandbox/kn-plugin-source-kamelet) | `kn` plugin for managing Kamelets and KameletBindings | Y | +| [kn-plugin-migration](https://github.com/knative-extensions/kn-plugin-migration) | `kn` plugin for migrating Knative Services from one cluster to another | N | +| [kn-plugin-operator](https://github.com/knative-extensions/kn-plugin-operator) | `kn` plugin for managing Knative with Knative Operator | N | +| [kn-plugin-quickstart](https://github.com/knative-extensions/kn-plugin-quickstart) | `kn` plugin for developers to install a quickstart Knative cluster for experimentation purposes | Y | +| [kn-plugin-service-log](https://github.com/knative-extensions/kn-plugin-service-log) | `kn` plugin for showing the standard output of Knative Services | N | +| [kn-plugin-source-kafka](https://github.com/knative-extensions/kn-plugin-source-kafka) | `kn` plugin for managing Kafka event sources | Y | +| [kn-plugin-source-kamelet](https://github.com/knative-extensions/kn-plugin-source-kamelet) | `kn` plugin for managing Kamelets and KameletBindings | Y | ## Manually install a plugin @@ -43,7 +43,7 @@ You can manually install all plugins. To manually install a plugin: ## Install a plugin by using Homebrew -You can install some plugins can be installed using the [Knative plugins Homebrew Tap](https://github.com/knative-sandbox/homebrew-kn-plugins/). For example, you can install the `kn-admin` plugin by running `brew install knative-sandbox/kn-plugins/admin`. +You can install some plugins can be installed using the [Knative plugins Homebrew Tap](https://github.com/knative-extensions/homebrew-kn-plugins/). For example, you can install the `kn-admin` plugin by running `brew install knative-extensions/kn-plugins/admin`. ## List available plugins diff --git a/docs/community/governance.md b/docs/community/governance.md index a085ccb1a1..64cc776ac8 100644 --- a/docs/community/governance.md +++ b/docs/community/governance.md @@ -66,7 +66,7 @@ election process for our technical oversight committee. how we create and remove core repositories. - [Sandbox repo process](https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md): -how to create a repo in the [`knative-sandbox`](https://github.com/knative-sandbox) GitHub org. +how to create a repo in the [`knative-extensions`](https://github.com/knative-extensions) GitHub org. - [Feature tracks](https://github.com/knative/community/blob/main/mechanics/FEATURE-TRACKS.md): outlines the process for adding non-trivial features. diff --git a/docs/eventing/brokers/broker-types/README.md b/docs/eventing/brokers/broker-types/README.md index 72468591a3..0782aaa436 100644 --- a/docs/eventing/brokers/broker-types/README.md +++ b/docs/eventing/brokers/broker-types/README.md @@ -21,4 +21,4 @@ This Broker implementation uses [Apache Kafka](https://kafka.apache.org/) as its ### RabbitMQ broker The RabbitMQ Broker uses [RabbitMQ](https://www.rabbitmq.com/) for its underlying implementation. -For more information, see [RabbitMQ Broker](./rabbitmq-broker/README.md) or [the docs available on GitHub](https://github.com/knative-sandbox/eventing-rabbitmq). +For more information, see [RabbitMQ Broker](./rabbitmq-broker/README.md) or [the docs available on GitHub](https://github.com/knative-extensions/eventing-rabbitmq). diff --git a/docs/eventing/brokers/broker-types/kafka-broker/README.md b/docs/eventing/brokers/broker-types/kafka-broker/README.md index 1d6ee278b1..bf2ce5a32f 100644 --- a/docs/eventing/brokers/broker-types/kafka-broker/README.md +++ b/docs/eventing/brokers/broker-types/kafka-broker/README.md @@ -26,13 +26,13 @@ The Knative Kafka Broker stores incoming CloudEvents as Kafka records, using the 1. Install the Kafka controller by entering the following command: ```bash - kubectl apply --filename {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} + kubectl apply --filename {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} ``` 1. Install the Kafka Broker data plane by entering the following command: ```bash - kubectl apply --filename {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-broker.yaml") }} + kubectl apply --filename {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-broker.yaml") }} ``` 1. Verify that `kafka-controller`, `kafka-broker-receiver` and `kafka-broker-dispatcher` are running, @@ -447,4 +447,4 @@ All the configuration mechanisms that are available for the `Kafka` Broker class ## Additional information -- To report a bug or request a feature, open an issue in the [eventing-kafka-broker repository](https://github.com/knative-sandbox/eventing-kafka-broker). +- To report a bug or request a feature, open an issue in the [eventing-kafka-broker repository](https://github.com/knative-extensions/eventing-kafka-broker). diff --git a/docs/eventing/brokers/broker-types/rabbitmq-broker/README.md b/docs/eventing/brokers/broker-types/rabbitmq-broker/README.md index 2d76672ff9..6223e067f8 100644 --- a/docs/eventing/brokers/broker-types/rabbitmq-broker/README.md +++ b/docs/eventing/brokers/broker-types/rabbitmq-broker/README.md @@ -14,7 +14,7 @@ This topic describes how to create a RabbitMQ Broker. 1. Install the RabbitMQ controller by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-rabbitmq", file="rabbitmq-broker.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-rabbitmq", file="rabbitmq-broker.yaml") }} ``` 1. Verify that `rabbitmq-broker-controller` and `rabbitmq-broker-webhook` are running: @@ -110,5 +110,5 @@ metadata: ## Additional information -- For more samples visit the [`eventing-rabbitmq` Github repository samples directory](https://github.com/knative-sandbox/eventing-rabbitmq/tree/main/samples) -- To report a bug or request a feature, open an issue in the [`eventing-rabbitmq` Github repository](https://github.com/knative-sandbox/eventing-rabbitmq). +- For more samples visit the [`eventing-rabbitmq` Github repository samples directory](https://github.com/knative-extensions/eventing-rabbitmq/tree/main/samples) +- To report a bug or request a feature, open an issue in the [`eventing-rabbitmq` Github repository](https://github.com/knative-extensions/eventing-rabbitmq). diff --git a/docs/eventing/channels/channels-crds.md b/docs/eventing/channels/channels-crds.md index 92327f6282..18051147e3 100644 --- a/docs/eventing/channels/channels-crds.md +++ b/docs/eventing/channels/channels-crds.md @@ -18,7 +18,7 @@ This is a non-exhaustive list of the available Channels for Knative Eventing. Name | Status | Maintainer | Description --- | --- | --- | --- [InMemoryChannel](https://github.com/knative/eventing/tree/{{ branch }}/config/channels/in-memory-channel/README.md) | Stable | Knative | In-memory channels are a best effort Channel. They should NOT be used in Production. They are useful for development. -[KafkaChannel](https://github.com/knative-sandbox/eventing-kafka-broker/tree/{{ branch }}/README.md) | Beta | Knative | Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics. -[NatssChannel](https://github.com/knative-sandbox/eventing-natss/tree/{{ branch }}/config/README.md) | Alpha | Knative | Channels are backed by [NATS Streaming](https://github.com/nats-io/nats-streaming-server#configuring). +[KafkaChannel](https://github.com/knative-extensions/eventing-kafka-broker/tree/{{ branch }}/README.md) | Beta | Knative | Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics. +[NatssChannel](https://github.com/knative-extensions/eventing-natss/tree/{{ branch }}/config/README.md) | Alpha | Knative | Channels are backed by [NATS Streaming](https://github.com/nats-io/nats-streaming-server#configuring). diff --git a/docs/eventing/channels/channels.yaml b/docs/eventing/channels/channels.yaml index 37bdcab3de..fa69841efb 100644 --- a/docs/eventing/channels/channels.yaml +++ b/docs/eventing/channels/channels.yaml @@ -7,13 +7,13 @@ channels: description: > In-memory channels are a best effort Channel. They should NOT be used in Production. They are useful for development. - name: KafkaChannel - url: https://github.com/knative-sandbox/eventing-kafka-broker/tree/{{ branch }}/README.md + url: https://github.com/knative-extensions/eventing-kafka-broker/tree/{{ branch }}/README.md status: Beta maintainer: Knative description: > Channels are backed by [Apache Kafka](http://kafka.apache.org/) topics. - name: NatssChannel - url: https://github.com/knative-sandbox/eventing-natss/tree/{{ branch }}/config/README.md + url: https://github.com/knative-extensions/eventing-natss/tree/{{ branch }}/config/README.md status: Alpha maintainer: Knative description: > diff --git a/docs/eventing/custom-event-source/custom-event-source/README.md b/docs/eventing/custom-event-source/custom-event-source/README.md index 90db4c019c..e535d1d0a2 100644 --- a/docs/eventing/custom-event-source/custom-event-source/README.md +++ b/docs/eventing/custom-event-source/custom-event-source/README.md @@ -7,7 +7,7 @@ This type of integration requires more effort than using some simpler integratio !!! 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 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). + You can also add your event source to the [`knative-extensions`](https://github.com/knative-extensions) organization, by following the instructions to [create a sandbox repository](https://github.com/knative/community/blob/main/mechanics/CREATING-A-SANDBOX-REPO.md). ## Required components diff --git a/docs/eventing/custom-event-source/custom-event-source/controller.md b/docs/eventing/custom-event-source/custom-event-source/controller.md index e57fa7f2a2..befc08d9db 100644 --- a/docs/eventing/custom-event-source/custom-event-source/controller.md +++ b/docs/eventing/custom-event-source/custom-event-source/controller.md @@ -1,6 +1,6 @@ # Create a controller -You can use the sample repository [`update-codegen.sh`](https://github.com/knative-sandbox/sample-source/blob/main/hack/update-codegen.sh) script to generate and inject the required components (the `clientset`, `cache`, `informers`, and `listers`) into your custom controller. +You can use the sample repository [`update-codegen.sh`](https://github.com/knative-extensions/sample-source/blob/main/hack/update-codegen.sh) script to generate and inject the required components (the `clientset`, `cache`, `informers`, and `listers`) into your custom controller. **Example controller:** diff --git a/docs/eventing/custom-event-source/custom-event-source/receive-adapter.md b/docs/eventing/custom-event-source/custom-event-source/receive-adapter.md index 4987557a23..01a0f10280 100644 --- a/docs/eventing/custom-event-source/custom-event-source/receive-adapter.md +++ b/docs/eventing/custom-event-source/custom-event-source/receive-adapter.md @@ -92,7 +92,7 @@ new adapter with passed variables via the `EnvConfigAccessor`. The created adapt ``` !!! note - The exact arguments may change based on functional requirements. Create the underlying deployment from the arguments provided, matching pod templates, labels, owner references, etc as needed to fill out the deployment. Example: [pkg/reconciler/sample/resources/receive_adapter.go](https://github.com/knative-sandbox/sample-source/blob/main/pkg/reconciler/sample/resources/receive_adapter.go) + The exact arguments may change based on functional requirements. Create the underlying deployment from the arguments provided, matching pod templates, labels, owner references, etc as needed to fill out the deployment. Example: [pkg/reconciler/sample/resources/receive_adapter.go](https://github.com/knative-extensions/sample-source/blob/main/pkg/reconciler/sample/resources/receive_adapter.go) 1. Fetch the existing receive adapter deployment: diff --git a/docs/eventing/custom-event-source/custom-event-source/sample-repo.md b/docs/eventing/custom-event-source/custom-event-source/sample-repo.md index 182d1e253a..3b0ca34c7d 100644 --- a/docs/eventing/custom-event-source/custom-event-source/sample-repo.md +++ b/docs/eventing/custom-event-source/custom-event-source/sample-repo.md @@ -1,13 +1,13 @@ # Using the Knative sample repository -The Knative project provides a [sample repository](https://github.com/knative-sandbox/sample-source) that contains a template for a basic event source controller and a receive adapter. +The Knative project provides a [sample repository](https://github.com/knative-extensions/sample-source) that contains a template for a basic event source controller and a receive adapter. ## Prerequisites - You are familiar with Kubernetes and Go development. - You have installed Git. - You have installed Go. -- You have cloned the [`sample-source` repository](https://github.com/knative-sandbox/sample-source). +- You have cloned the [`sample-source` repository](https://github.com/knative-extensions/sample-source). Optional: diff --git a/docs/eventing/experimental-features/eventtype-auto-creation.md b/docs/eventing/experimental-features/eventtype-auto-creation.md index 949633a817..43f439d5c4 100644 --- a/docs/eventing/experimental-features/eventtype-auto-creation.md +++ b/docs/eventing/experimental-features/eventtype-auto-creation.md @@ -72,7 +72,7 @@ container in a cluster. 1. Setup `kn event` plugin ```bash - brew install knative-sandbox/kn-plugins/event + brew install knative-extensions/kn-plugins/event ``` 1. Send event diff --git a/docs/eventing/sinks/README.md b/docs/eventing/sinks/README.md index 497216c755..9e2f1b984a 100644 --- a/docs/eventing/sinks/README.md +++ b/docs/eventing/sinks/README.md @@ -133,7 +133,7 @@ The `svc` in `http://event-display.svc.cluster.local` determines that the sink i | Name | Maintainer | Description | | -- | -- | -- | | [KafkaSink](kafka-sink.md) | Knative | Send events to a Kafka topic | -| [RedisSink](https://github.com/knative-sandbox/eventing-redis/tree/main/sink) | Knative | Send events to a Redis Stream | +| [RedisSink](https://github.com/knative-extensions/eventing-redis/tree/main/sink) | Knative | Send events to a Redis Stream | [kubernetes-kinds]: diff --git a/docs/eventing/sinks/kafka-sink.md b/docs/eventing/sinks/kafka-sink.md index 70c5874a52..9aea7611fd 100644 --- a/docs/eventing/sinks/kafka-sink.md +++ b/docs/eventing/sinks/kafka-sink.md @@ -11,13 +11,13 @@ You must have access to a Kubernetes cluster with [Knative Eventing installed](. 1. Install the Kafka controller: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} ``` 1. Install the KafkaSink data plane: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-sink.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-sink.yaml") }} ``` 1. Verify that `kafka-controller` and `kafka-sink-receiver` Deployments are running: diff --git a/docs/eventing/sources/README.md b/docs/eventing/sources/README.md index a5da3244bd..3b00235e8b 100644 --- a/docs/eventing/sources/README.md +++ b/docs/eventing/sources/README.md @@ -30,15 +30,15 @@ All Sources are part of the `sources` category. | Name | Status | Maintainer | Description | | -- | -- | -- | -- | | [APIServerSource](apiserversource/README.md) | Stable | Knative | Brings Kubernetes API server events into Knative. The APIServerSource fires a new event each time a Kubernetes resource is created, updated or deleted. | -| [Apache CouchDB](https://github.com/knative-sandbox/eventing-couchdb/blob/main/source) | Alpha | Knative | Brings [Apache CouchDB](https://couchdb.apache.org/) messages into Knative. | -| [Apache Kafka](kafka-source/README.md) | Stable | Knative | Brings [Apache Kafka](https://kafka.apache.org/) messages into Knative. The KafkaSource reads events from an Apache Kafka Cluster, and passes these events to a sink so that they can be consumed. See the [Kafka Source](https://github.com/knative-sandbox/eventing-kafka/blob/main/pkg/source) example for more details. | +| [Apache CouchDB](https://github.com/knative-extensions/eventing-couchdb/blob/main/source) | Alpha | Knative | Brings [Apache CouchDB](https://couchdb.apache.org/) messages into Knative. | +| [Apache Kafka](kafka-source/README.md) | Stable | Knative | Brings [Apache Kafka](https://kafka.apache.org/) messages into Knative. The KafkaSource reads events from an Apache Kafka Cluster, and passes these events to a sink so that they can be consumed. See the [Kafka Source](https://github.com/knative-extensions/eventing-kafka/blob/main/pkg/source) example for more details. | | [ContainerSource](../custom-event-source/containersource/README.md) | Stable | Knative | The ContainerSource instantiates container image(s) that can generate events until the ContainerSource is deleted. This may be used, for example, to poll an FTP server for new files or generate events at a set time interval. Given a `spec.template` with at least a container image specified, the ContainerSource keeps a Pod running with the specified image(s). `K_SINK` (destination address) and `KE_CE_OVERRIDES` (JSON CloudEvents attributes) environment variables are injected into the running image(s). It is used by multiple other Sources as underlying infrastructure. Refer to the [Container Source](../custom-event-source/containersource/README.md) example for more details. | | [GitHub](https://github.com/knative/docs/tree/main/code-samples/eventing/github-source) | Beta | Knative | Registers for events of the specified types on the specified GitHub organization or repository, and brings those events into Knative. The GitHubSource fires a new event for selected [GitHub event types](https://developer.github.com/v3/activity/events/types/). See the [GitHub Source](https://github.com/knative/docs/tree/main/code-samples/eventing/github-source) example for more details. | | [GitLab](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) | Beta | Knative | Registers for events of the specified types on the specified GitLab repository, and brings those events into Knative. The GitLabSource creates a webhooks for specified [event types](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#events), listens for incoming events, and passes them to a consumer. See the [GitLab Source](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) example for more details. | -| [KogitoSource](https://github.com/knative-sandbox/eventing-kogito) | Alpha | Knative | An implementation of the [Kogito Runtime](https://docs.jboss.org/kogito/release/latest/html_single/#proc-kogito-deploying-on-kubernetes_kogito-deploying-on-openshift) custom resource managed by the [Kogito Operator](https://github.com/kiegroup/kogito-operator). | +| [KogitoSource](https://github.com/knative-extensions/eventing-kogito) | Alpha | Knative | An implementation of the [Kogito Runtime](https://docs.jboss.org/kogito/release/latest/html_single/#proc-kogito-deploying-on-kubernetes_kogito-deploying-on-openshift) custom resource managed by the [Kogito Operator](https://github.com/kiegroup/kogito-operator). | | [PingSource](ping-source/README.md) | Stable | Knative | Produces events with a fixed payload on a specified [Cron](https://en.wikipedia.org/wiki/Cron) schedule. See the [Ping Source](ping-source/README.md) example for more details. | -| [RabbitMQ](https://github.com/knative-sandbox/eventing-rabbitmq) | Stable | Knative | Brings [RabbitMQ](https://www.rabbitmq.com/) messages into Knative. -[RedisSource](https://github.com/knative-sandbox/eventing-redis/tree/{{version}}/source) | Alpha | Knative | Brings Redis Stream into Knative. +| [RabbitMQ](https://github.com/knative-extensions/eventing-rabbitmq) | Stable | Knative | Brings [RabbitMQ](https://www.rabbitmq.com/) messages into Knative. +[RedisSource](https://github.com/knative-extensions/eventing-redis/tree/{{version}}/source) | Alpha | Knative | Brings Redis Stream into Knative. | [SinkBinding](../custom-event-source/sinkbinding/README.md) | Stable | Knative | The SinkBinding can be used to author new event sources using any of the familiar compute abstractions that Kubernetes makes available (e.g. Deployment, Job, DaemonSet, StatefulSet), or Knative abstractions (e.g. Service, Configuration). SinkBinding provides a framework for injecting `K_SINK` (destination address) and `K_CE_OVERRIDES` (JSON cloudevents attributes) environment variables into any Kubernetes resource which has a `spec.template` that looks like a Pod (aka PodSpecable). See the [SinkBinding](../custom-event-source/sinkbinding/README.md) example for more details. | ## Third-Party Sources diff --git a/docs/eventing/sources/kafka-source/README.md b/docs/eventing/sources/kafka-source/README.md index 5b416f4be1..2da7c216b7 100644 --- a/docs/eventing/sources/kafka-source/README.md +++ b/docs/eventing/sources/kafka-source/README.md @@ -11,13 +11,13 @@ stored in the topic partitions. It does this by waiting for a successful respons 1. Install the `KafkaSource` controller by entering the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} ``` 1. Install the Kafka Source data plane by entering the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-source.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-source.yaml") }} ``` 1. Verify that `kafka-controller` and `kafka-source-dispatcher` are running, diff --git a/docs/eventing/sources/rabbitmq-source/README.md b/docs/eventing/sources/rabbitmq-source/README.md index 5ec44e6832..f1213c9c70 100644 --- a/docs/eventing/sources/rabbitmq-source/README.md +++ b/docs/eventing/sources/rabbitmq-source/README.md @@ -18,7 +18,7 @@ For more information about configuring the `RabbitmqCluster` CRD, see the [Rabbi 1. Install the RabbitMQSource controller by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-rabbitmq", file="rabbitmq-source.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-rabbitmq", file="rabbitmq-source.yaml") }} ``` 1. Verify that `rabbitmq-controller-manager` and `rabbitmq-webhook` are running: @@ -128,5 +128,5 @@ It might take a while for the Source to start sending events to the Sink. ## Additional information -- For more samples visit the [`eventing-rabbitmq` Github repository samples directory](https://github.com/knative-sandbox/eventing-rabbitmq/tree/main/samples) -- To report a bug or request a feature, open an issue in the [`eventing-rabbitmq` Github repository](https://github.com/knative-sandbox/eventing-rabbitmq). +- For more samples visit the [`eventing-rabbitmq` Github repository samples directory](https://github.com/knative-extensions/eventing-rabbitmq/tree/main/samples) +- To report a bug or request a feature, open an issue in the [`eventing-rabbitmq` Github repository](https://github.com/knative-extensions/eventing-rabbitmq). diff --git a/docs/eventing/sources/redis/getting-started.md b/docs/eventing/sources/redis/getting-started.md index 9ed3b3de9a..95160adcf1 100644 --- a/docs/eventing/sources/redis/getting-started.md +++ b/docs/eventing/sources/redis/getting-started.md @@ -11,7 +11,7 @@ This topic describes how to create a `RedisStreamSource` object. 1. Install RedisStreamSource by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox", repo="eventing-redis", file="redis-source.yaml") }} + kubectl apply -f {{ artifact(org="knative-extensions", repo="eventing-redis", file="redis-source.yaml") }} ``` 1. Verify that `redis-controller-manager`is running: @@ -101,4 +101,4 @@ Where: ## Additional information -* For more information about Redis Stream source, see the [`eventing-redis` Github repository](https://github.com/knative-sandbox/eventing-redis/tree/main/config/source) +* For more information about Redis Stream source, see the [`eventing-redis` Github repository](https://github.com/knative-extensions/eventing-redis/tree/main/config/source) diff --git a/docs/functions/language-packs.md b/docs/functions/language-packs.md index 896e1135cc..b5d0ceb4dc 100644 --- a/docs/functions/language-packs.md +++ b/docs/functions/language-packs.md @@ -7,12 +7,12 @@ For more information see the [language pack](https://github.com/knative/func/blo ## Using external Git repositories When creating a new function, a Git repository can be specified as the source -for the template files. The Knative Sandbox maintains a set of [example templates](https://github.com/knative-sandbox/func-tastic){target=_blank} which can be used during project creation. +for the template files. The Knative Sandbox maintains a set of [example templates](https://github.com/knative-extensions/func-tastic){target=_blank} which can be used during project creation. For example, you can run the following command to use the [`metacontroller`](https://metacontroller.github.io/metacontroller/){target=_blank} template for Node.js: ```{ .console } -func create myfunc -l nodejs -t metacontroller --repository https://github.com/knative-sandbox/func-tastic +func create myfunc -l nodejs -t metacontroller --repository https://github.com/knative-extensions/func-tastic ``` ## Installing language packs locally @@ -22,7 +22,7 @@ Language packs can be installed locally by using the [`func repository`](https:/ For example, to add the Knative Sandbox example templates, you can run the following command: ```{ .console } -func repository add knative https://github.com/knative-sandbox/func-tastic +func repository add knative https://github.com/knative-extensions/func-tastic ``` After the Knative Sandbox example templates are installed, you can use the `metacontroller` template by specifying the `knative` prefix in the `create` command: diff --git a/docs/install/installing-istio.md b/docs/install/installing-istio.md index 54beb7b8b4..5efd3797af 100644 --- a/docs/install/installing-istio.md +++ b/docs/install/installing-istio.md @@ -17,7 +17,7 @@ You need: ## Supported Istio versions -You can view the latest tested Istio version on the [Knative Net Istio releases page](https://github.com/knative-sandbox/net-istio/releases). +You can view the latest tested Istio version on the [Knative Net Istio releases page](https://github.com/knative-extensions/net-istio/releases). ## Installing Istio diff --git a/docs/install/operator/knative-with-operator-cli.md b/docs/install/operator/knative-with-operator-cli.md index dbaa891ae4..a4382ea5ec 100644 --- a/docs/install/operator/knative-with-operator-cli.md +++ b/docs/install/operator/knative-with-operator-cli.md @@ -13,7 +13,7 @@ Before you install the Knative Operator CLI Plugin, first install the [Knative C === "MacOS" - 1. Download the binary `kn-operator-darwin-amd64` for your system from the [release page](https://github.com/knative-sandbox/kn-plugin-operator/releases/tag/knative-v1.7.1). + 1. Download the binary `kn-operator-darwin-amd64` for your system from the [release page](https://github.com/knative-extensions/kn-plugin-operator/releases/tag/knative-v1.7.1). 1. Rename the binary to `kn-operator`: @@ -23,7 +23,7 @@ Before you install the Knative Operator CLI Plugin, first install the [Knative C === "Linux" - 1. Download the binary `kn-operator-linux-amd64` for your system from the [release page](https://github.com/knative-sandbox/kn-plugin-operator/releases/tag/knative-v1.7.1). + 1. Download the binary `kn-operator-linux-amd64` for your system from the [release page](https://github.com/knative-extensions/kn-plugin-operator/releases/tag/knative-v1.7.1). 1. Rename the binary to `kn-operator`: diff --git a/docs/install/uninstall.md b/docs/install/uninstall.md index 63cb1ce42e..2087910ba2 100644 --- a/docs/install/uninstall.md +++ b/docs/install/uninstall.md @@ -134,13 +134,13 @@ Uninstall any Eventing extensions you have installed by following the relevant p 1. Uninstall the Kafka Sink data plane: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-sink.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-sink.yaml") }} ``` 1. Uninstall the Kafka controller: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} ``` @@ -160,13 +160,13 @@ Uninstall any Eventing extensions you have installed by following the relevant p Uninstall a single-tenant GitHub source by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-github", file="github.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-github", file="github.yaml") }} ``` Uninstall a multi-tenant GitHub source by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-github", file="mt-github.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-github", file="mt-github.yaml") }} ``` @@ -176,7 +176,7 @@ Uninstall any Eventing extensions you have installed by following the relevant p Uninstall the Apache Kafka source by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-source.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-source.yaml") }} ``` @@ -196,7 +196,7 @@ Uninstall any Eventing extensions you have installed by following the relevant p Uninstall the Apache CouchDB source by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-couchdb", file="couchdb.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-couchdb", file="couchdb.yaml") }} ``` @@ -226,13 +226,13 @@ Uninstall a Broker (Eventing) layer, if you installed one: 1. Uninstall the Kafka Broker data plane by running the following command: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-broker.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-broker.yaml") }} ``` 1. Uninstall the Kafka controller by running the following command: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-kafka-broker", file="eventing-kafka-controller.yaml") }} ``` @@ -263,7 +263,7 @@ Uninstall each channel layer you have installed: Uninstall the Apache Kafka Channel by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-channel.yaml")}} + kubectl delete -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-channel.yaml")}} ``` @@ -295,10 +295,10 @@ Uninstall each channel layer you have installed: 1. Uninstall the NATS Streaming channel by running: ```bash - kubectl delete -f {{ artifact(org="knative-sandbox", repo="eventing-natss", file="eventing-natss.yaml") }} + kubectl delete -f {{ artifact(org="knative-extensions", repo="eventing-natss", file="eventing-natss.yaml") }} ``` - 1. Uninstall NATS Streaming for Kubernetes. For more information, see the [eventing-natss](https://github.com/knative-sandbox/eventing-natss/tree/main/config) repository in GitHub. + 1. Uninstall NATS Streaming for Kubernetes. For more information, see the [eventing-natss](https://github.com/knative-extensions/eventing-natss/tree/main/config) repository in GitHub. diff --git a/docs/install/yaml-install/eventing/install-eventing-with-yaml.md b/docs/install/yaml-install/eventing/install-eventing-with-yaml.md index 3520ef6272..460ff0a2bf 100644 --- a/docs/install/yaml-install/eventing/install-eventing-with-yaml.md +++ b/docs/install/yaml-install/eventing/install-eventing-with-yaml.md @@ -57,19 +57,19 @@ Follow the procedure for the Channel of your choice: 1. Install the Kafka controller by running the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} ``` 1. Install the KafkaChannel data plane by running the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-channel.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-channel.yaml")}} ``` 1. If you're upgrading from the previous version, run the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} ``` === "In-Memory (standalone)" @@ -85,12 +85,12 @@ Follow the procedure for the Channel of your choice: === "NATS Channel" - 1. [Install NATS Streaming for Kubernetes](https://github.com/knative-sandbox/eventing-natss/tree/main/config). + 1. [Install NATS Streaming for Kubernetes](https://github.com/knative-extensions/eventing-natss/tree/main/config). 1. Install the NATS Streaming Channel by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-natss",file="eventing-natss.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-natss",file="eventing-natss.yaml")}} ``` @@ -111,19 +111,19 @@ Follow the procedure for the Broker of your choice: 1. Install the Kafka controller by running the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} ``` 1. Install the Kafka Broker data plane by running the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-broker.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-broker.yaml")}} ``` 1. If you're upgrading from the previous version, run the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} ``` For more information, see the [Kafka Broker](../../../eventing/brokers/broker-types/kafka-broker/README.md) documentation. @@ -203,9 +203,9 @@ Follow the procedure for the Broker of your choice: === "RabbitMQ Broker" * Install the RabbitMQ Broker by following the instructions in the - [RabbitMQ Knative Eventing Broker README](https://github.com/knative-sandbox/eventing-rabbitmq/tree/main/broker). + [RabbitMQ Knative Eventing Broker README](https://github.com/knative-extensions/eventing-rabbitmq/tree/main/broker). - For more information, see the [RabbitMQ Broker](https://github.com/knative-sandbox/eventing-rabbitmq) in GitHub. + For more information, see the [RabbitMQ Broker](https://github.com/knative-extensions/eventing-rabbitmq) in GitHub. ## Install optional Eventing extensions @@ -217,13 +217,13 @@ The following tabs expand to show instructions for installing each Eventing exte 1. Install the Kafka controller by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-controller.yaml")}} ``` 1. Install the Kafka Sink data plane by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-sink.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-sink.yaml")}} ``` For more information, see the [Kafka Sink](../../../eventing/sinks/kafka-sink.md) documentation. @@ -263,13 +263,13 @@ The following tabs expand to show instructions for installing each Eventing exte * To install a single-tenant GitHub source run the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-github",file="github.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-github",file="github.yaml")}} ``` * To install a multi-tenant GitHub source run the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-github",file="mt-github.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-github",file="mt-github.yaml")}} ``` To learn more, try the [GitHub source sample](https://github.com/knative/docs/tree/main/code-samples/eventing/github-source) @@ -279,13 +279,13 @@ The following tabs expand to show instructions for installing each Eventing exte 1. Install the Apache Kafka Source by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-source.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-source.yaml")}} ``` 1. If you're upgrading from the previous version, run the following command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-kafka-broker",file="eventing-kafka-post-install.yaml")}} ``` To learn more, try the [Apache Kafka source sample](../../../eventing/sources/kafka-source/README.md). @@ -295,10 +295,10 @@ The following tabs expand to show instructions for installing each Eventing exte * Install the Apache CouchDB Source by running the command: ```bash - kubectl apply -f {{ artifact(org="knative-sandbox",repo="eventing-couchdb",file="couchdb.yaml")}} + kubectl apply -f {{ artifact(org="knative-extensions",repo="eventing-couchdb",file="couchdb.yaml")}} ``` - To learn more, read the [Apache CouchDB source](https://github.com/knative-sandbox/eventing-couchdb/blob/main/source/README.md) documentation. + To learn more, read the [Apache CouchDB source](https://github.com/knative-extensions/eventing-couchdb/blob/main/source/README.md) documentation. === "VMware Sources and Bindings" diff --git a/docs/install/yaml-install/serving/install-serving-with-yaml.md b/docs/install/yaml-install/serving/install-serving-with-yaml.md index 71fd0d2f3a..ab4ddfc0cc 100644 --- a/docs/install/yaml-install/serving/install-serving-with-yaml.md +++ b/docs/install/yaml-install/serving/install-serving-with-yaml.md @@ -96,7 +96,7 @@ Follow the procedure for the networking layer of your choice: ```bash kubectl apply -f {{ artifact(repo="net-contour",file="contour.yaml")}} ``` - + 1. Install the Knative Contour controller by running the command: ```bash diff --git a/docs/serving/app-security/security-guard-install.md b/docs/serving/app-security/security-guard-install.md index 89da336c69..695ffd2065 100644 --- a/docs/serving/app-security/security-guard-install.md +++ b/docs/serving/app-security/security-guard-install.md @@ -20,7 +20,7 @@ To start this tutorial, after installing Knative Serving, run the following proc === "Install from source" - 1. Clone the Security-Guard repository using `git clone git@github.com:knative-sandbox/security-guard.git` + 1. Clone the Security-Guard repository using `git clone git@github.com:knative-extensions/security-guard.git` 1. Do `cd security-guard` @@ -35,7 +35,7 @@ To start this tutorial, after installing Knative Serving, run the following proc An easy way to do that is using: ``` - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/deploy/config-features.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/deploy/config-features.yaml ``` 1. Set the deployment parameter `queue-sidecar-image` to `gcr.io/knative-releases/knative.dev/security-guard/cmd/queue` in the config-deployment ConfigMap. @@ -43,15 +43,15 @@ To start this tutorial, after installing Knative Serving, run the following proc An easy way to do that is using: ``` - kubectl apply -f https://github.com/knative-sandbox/security-guard/releases/download/v0.4.0/queue-proxy.yaml + kubectl apply -f https://github.com/knative-extensions/security-guard/releases/download/v0.4.0/queue-proxy.yaml ``` 1. Add the necessary Security-Guard resources to your cluster using: ``` - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/resources/gateAccount.yaml - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/resources/serviceAccount.yaml - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/resources/guardiansCrd.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/resources/gateAccount.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/resources/serviceAccount.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/resources/guardiansCrd.yaml ``` 1. Deploy `guard-service` on your system to enable automated learning of micro-rules. @@ -59,7 +59,7 @@ To start this tutorial, after installing Knative Serving, run the following proc An easy way to do that is using: ``` - kubectl apply -f https://github.com/knative-sandbox/security-guard/releases/download/v0.4.0/guard-service.yaml + kubectl apply -f https://github.com/knative-extensions/security-guard/releases/download/v0.4.0/guard-service.yaml ``` === "Install using the Knative Operator" @@ -92,7 +92,7 @@ To start this tutorial, after installing Knative Serving, run the following proc ingress.class: "kourier.ingress.networking.knative.dev" EOF - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/resources/gateAccount.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/resources/gateAccount.yaml ``` ## Per Namespace Setup @@ -100,7 +100,7 @@ To start this tutorial, after installing Knative Serving, run the following proc In order to deploy guard protected services in a namespace, provide `guard-gate` with the necessary permissions on each namespace used: ``` -kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/security-guard/release-0.4/config/resources/gateAccount.yaml +kubectl apply -f https://raw.githubusercontent.com/knative-extensions/security-guard/release-0.4/config/resources/gateAccount.yaml ``` ## Additional Production Configuration diff --git a/docs/serving/architecture.md b/docs/serving/architecture.md index 71f3bd7a81..f74039bf69 100644 --- a/docs/serving/architecture.md +++ b/docs/serving/architecture.md @@ -26,9 +26,9 @@ and [the Request Flow](./request-flow.md) for additional information. Knative Serving depends on a `Networking Layer` that fulfils the [Knative Networking Specification](https://github.com/knative/networking). For this, Knative Serving defines an internal `KIngress` resource, which acts as an abstraction for different multiple pluggable networking layers. Currently, three networking layers are available and supported by the community: -* [net-kourier](https://github.com/knative-sandbox/net-kourier) -* [net-contour](https://github.com/knative-sandbox/net-contour) -* [net-istio](https://github.com/knative-sandbox/net-istio) +* [net-kourier](https://github.com/knative-extensions/net-kourier) +* [net-contour](https://github.com/knative-extensions/net-contour) +* [net-istio](https://github.com/knative-extensions/net-istio) ## Traffic flow and DNS diff --git a/docs/serving/using-auto-tls.md b/docs/serving/using-auto-tls.md index f796791a1e..e92863ec7c 100644 --- a/docs/serving/using-auto-tls.md +++ b/docs/serving/using-auto-tls.md @@ -181,7 +181,7 @@ This selects all namespaces where the label value is not in the set `"true"`. ### Configure config-certmanager ConfigMap -Update your [`config-certmanager` ConfigMap](https://github.com/knative-sandbox/net-certmanager/blob/main/config/config.yaml) +Update your [`config-certmanager` ConfigMap](https://github.com/knative-extensions/net-certmanager/blob/main/config/config.yaml) in the `knative-serving` namespace to reference your new `ClusterIssuer`. 1. Run the following command to edit your `config-certmanager` ConfigMap: diff --git a/docs/snippets/collecting-metrics.md b/docs/snippets/collecting-metrics.md index 2a72c77b27..f015729e0e 100644 --- a/docs/snippets/collecting-metrics.md +++ b/docs/snippets/collecting-metrics.md @@ -44,15 +44,15 @@ aggregating timeseries metrics and alerting. It can also be used to scrape the O 1. Apply the ServiceMonitors/PodMonitors to collect metrics from Knative. ```bash - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/monitoring/main/servicemonitor.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/monitoring/main/servicemonitor.yaml ``` -1. Grafana dashboards can be imported from the [`knative-sandbox` repository](https://github.com/knative-sandbox/monitoring/tree/main/grafana). +1. Grafana dashboards can be imported from the [`knative-extensions` repository](https://github.com/knative-extensions/monitoring/tree/main/grafana). 1. If you are using the Grafana Helm Chart with the Dashboard Sidecar enabled, you can load the dashboards by applying the following configmaps. ```bash - kubectl apply -f https://raw.githubusercontent.com/knative-sandbox/monitoring/main/grafana/dashboards.yaml + kubectl apply -f https://raw.githubusercontent.com/knative-extensions/monitoring/main/grafana/dashboards.yaml ``` ### Access the Prometheus instance locally @@ -87,7 +87,7 @@ In the following example, you can configure a single collector instance using a For more complex deployments, you can automate some of these steps by using the [OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator). !!! caution - The Grafana dashboards at https://github.com/knative-sandbox/monitoring/tree/main/grafana don't work with metrics scraped from OpenTelemetry Collector. + The Grafana dashboards at https://github.com/knative-extensions/monitoring/tree/main/grafana don't work with metrics scraped from OpenTelemetry Collector. ![Diagram of components reporting to collector, which is scraped by Prometheus](system-diagram.svg) diff --git a/docs/snippets/install-func-CLI.md b/docs/snippets/install-func-CLI.md index ae138652e2..08ce674ce4 100644 --- a/docs/snippets/install-func-CLI.md +++ b/docs/snippets/install-func-CLI.md @@ -7,7 +7,7 @@ To install `func` using Homebrew, run the following commands: ```bash - brew tap knative-sandbox/kn-plugins + brew tap knative-extensions/kn-plugins ``` ```bash diff --git a/docs/snippets/quickstart-install.md b/docs/snippets/quickstart-install.md index b1ced9a39f..40c195c624 100644 --- a/docs/snippets/quickstart-install.md +++ b/docs/snippets/quickstart-install.md @@ -13,12 +13,12 @@ To get started, install the Knative `quickstart` plugin: - To install the `quickstart` plugin by using [Homebrew](https://brew.sh){target=_blank}, run the command (Use `brew upgrade` instead if you are upgrading from a previous version): ```bash - brew install knative-sandbox/kn-plugins/quickstart + brew install knative-extensions/kn-plugins/quickstart ``` === "Using a binary" - 1. Download the binary for your system from the [`quickstart` release page](https://github.com/knative-sandbox/kn-plugin-quickstart/releases){target=_blank}. + 1. Download the binary for your system from the [`quickstart` release page](https://github.com/knative-extensions/kn-plugin-quickstart/releases){target=_blank}. 1. Rename the file to remove the OS and architecture information. For example, rename `kn-quickstart-amd64` to `kn-quickstart`. @@ -40,7 +40,7 @@ To get started, install the Knative `quickstart` plugin: 1. Check out the `kn-plugin-quickstart` repository: ```bash - git clone https://github.com/knative-sandbox/kn-plugin-quickstart.git + git clone https://github.com/knative-extensions/kn-plugin-quickstart.git cd kn-plugin-quickstart/ ``` diff --git a/golang/async-component.html b/golang/async-component.html index 64149ccb6b..20e4cde820 100644 --- a/golang/async-component.html +++ b/golang/async-component.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/container-freezer.html b/golang/container-freezer.html index f6406f311c..ecb63590d7 100644 --- a/golang/container-freezer.html +++ b/golang/container-freezer.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/control-protocol.html b/golang/control-protocol.html index 8d5738c8bb..c15b0accb3 100644 --- a/golang/control-protocol.html +++ b/golang/control-protocol.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/discovery.html b/golang/discovery.html index f8a91111b8..8139b20d03 100644 --- a/golang/discovery.html +++ b/golang/discovery.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-autoscaler-keda.html b/golang/eventing-autoscaler-keda.html index 958740848d..577109cd4b 100644 --- a/golang/eventing-autoscaler-keda.html +++ b/golang/eventing-autoscaler-keda.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-awssqs.html b/golang/eventing-awssqs.html index 5251ed0d1d..8f9fb8c313 100644 --- a/golang/eventing-awssqs.html +++ b/golang/eventing-awssqs.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-ceph.html b/golang/eventing-ceph.html index bdf8693b3b..2862de8fbe 100644 --- a/golang/eventing-ceph.html +++ b/golang/eventing-ceph.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-couchdb.html b/golang/eventing-couchdb.html index 11e09e4c7e..c6723bb335 100644 --- a/golang/eventing-couchdb.html +++ b/golang/eventing-couchdb.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-github.html b/golang/eventing-github.html index 736567746b..bd9b3c3152 100644 --- a/golang/eventing-github.html +++ b/golang/eventing-github.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-gitlab.html b/golang/eventing-gitlab.html index 470786b858..f901ef706d 100644 --- a/golang/eventing-gitlab.html +++ b/golang/eventing-gitlab.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-istio.html b/golang/eventing-istio.html index 6d1fbc9c44..856155d5ef 100644 --- a/golang/eventing-istio.html +++ b/golang/eventing-istio.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-kafka-broker.html b/golang/eventing-kafka-broker.html index ad2ec0a911..fe904df85b 100644 --- a/golang/eventing-kafka-broker.html +++ b/golang/eventing-kafka-broker.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-kafka.html b/golang/eventing-kafka.html index d908c38195..429dbd86f7 100644 --- a/golang/eventing-kafka.html +++ b/golang/eventing-kafka.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-kogito.html b/golang/eventing-kogito.html index 510ecbd5a2..61cbb7af09 100644 --- a/golang/eventing-kogito.html +++ b/golang/eventing-kogito.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-natss.html b/golang/eventing-natss.html index 7fa0bad910..b00a9f9be9 100644 --- a/golang/eventing-natss.html +++ b/golang/eventing-natss.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-prometheus.html b/golang/eventing-prometheus.html index 943cbf156a..5bd40c9715 100644 --- a/golang/eventing-prometheus.html +++ b/golang/eventing-prometheus.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-rabbitmq.html b/golang/eventing-rabbitmq.html index 57dcf3a45c..7559ba05e8 100644 --- a/golang/eventing-rabbitmq.html +++ b/golang/eventing-rabbitmq.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/eventing-redis.html b/golang/eventing-redis.html index 0747d93976..192f9ab972 100644 --- a/golang/eventing-redis.html +++ b/golang/eventing-redis.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/func-go.html b/golang/func-go.html index 34d2bd44f1..1b22ce48b7 100644 --- a/golang/func-go.html +++ b/golang/func-go.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/func-tastic.html b/golang/func-tastic.html index daa4223275..4c410df27b 100644 --- a/golang/func-tastic.html +++ b/golang/func-tastic.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/homebrew-kn-plugins.html b/golang/homebrew-kn-plugins.html index 99e03f67c7..cd4139e711 100644 --- a/golang/homebrew-kn-plugins.html +++ b/golang/homebrew-kn-plugins.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-admin.html b/golang/kn-plugin-admin.html index 8ac1671700..f46b2c45ab 100644 --- a/golang/kn-plugin-admin.html +++ b/golang/kn-plugin-admin.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-diag.html b/golang/kn-plugin-diag.html index b5886e9f6c..143eff0599 100644 --- a/golang/kn-plugin-diag.html +++ b/golang/kn-plugin-diag.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-event.html b/golang/kn-plugin-event.html index ecfc62ae7a..c29c641667 100644 --- a/golang/kn-plugin-event.html +++ b/golang/kn-plugin-event.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-func.html b/golang/kn-plugin-func.html index a18cdaefe7..789061e0b3 100644 --- a/golang/kn-plugin-func.html +++ b/golang/kn-plugin-func.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-migration.html b/golang/kn-plugin-migration.html index 0d3b37def6..efa3812789 100644 --- a/golang/kn-plugin-migration.html +++ b/golang/kn-plugin-migration.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-operator.html b/golang/kn-plugin-operator.html index be0311790a..b6aa0f8d37 100644 --- a/golang/kn-plugin-operator.html +++ b/golang/kn-plugin-operator.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-quickstart.html b/golang/kn-plugin-quickstart.html index 67ef92c78b..3629bdb6cc 100644 --- a/golang/kn-plugin-quickstart.html +++ b/golang/kn-plugin-quickstart.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-sample.html b/golang/kn-plugin-sample.html index 4ef085f154..7ca8f06334 100644 --- a/golang/kn-plugin-sample.html +++ b/golang/kn-plugin-sample.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-service-log.html b/golang/kn-plugin-service-log.html index 129ebad3a4..69e558a007 100644 --- a/golang/kn-plugin-service-log.html +++ b/golang/kn-plugin-service-log.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-source-kafka.html b/golang/kn-plugin-source-kafka.html index 7a3d7cabe3..200d948320 100644 --- a/golang/kn-plugin-source-kafka.html +++ b/golang/kn-plugin-source-kafka.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kn-plugin-source-kamelet.html b/golang/kn-plugin-source-kamelet.html index 4fed232a01..ecc85f3fac 100644 --- a/golang/kn-plugin-source-kamelet.html +++ b/golang/kn-plugin-source-kamelet.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/knobots.html b/golang/knobots.html index 43213ee8ee..37effd3157 100644 --- a/golang/knobots.html +++ b/golang/knobots.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/kperf.html b/golang/kperf.html index 9fc15f1eed..839ae91886 100644 --- a/golang/kperf.html +++ b/golang/kperf.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/monitoring.html b/golang/monitoring.html index 75e4e7aec9..0dd2fc8f98 100644 --- a/golang/monitoring.html +++ b/golang/monitoring.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-certmanager.html b/golang/net-certmanager.html index a7d73a4e49..447fc906b7 100644 --- a/golang/net-certmanager.html +++ b/golang/net-certmanager.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-contour.html b/golang/net-contour.html index c013f69e6d..ca72083c75 100644 --- a/golang/net-contour.html +++ b/golang/net-contour.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-gateway-api.html b/golang/net-gateway-api.html index 39c45240bd..e01f2daf7d 100644 --- a/golang/net-gateway-api.html +++ b/golang/net-gateway-api.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-http01.html b/golang/net-http01.html index 6ee8daf183..1c50bc5833 100644 --- a/golang/net-http01.html +++ b/golang/net-http01.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-istio.html b/golang/net-istio.html index 6e0b5108a3..f0c3795bb3 100644 --- a/golang/net-istio.html +++ b/golang/net-istio.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/net-kourier.html b/golang/net-kourier.html index d020a8ade9..bc746febe0 100644 --- a/golang/net-kourier.html +++ b/golang/net-kourier.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/reconciler-test.html b/golang/reconciler-test.html index cade4d8f28..1211a7063b 100644 --- a/golang/reconciler-test.html +++ b/golang/reconciler-test.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/sample-controller.html b/golang/sample-controller.html index 772b8a6c9a..903f448599 100644 --- a/golang/sample-controller.html +++ b/golang/sample-controller.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/sample-source.html b/golang/sample-source.html index 8b665ab1ab..e5ec9d9be8 100644 --- a/golang/sample-source.html +++ b/golang/sample-source.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/scaling-group.html b/golang/scaling-group.html index 59521aeb87..5fec07bcab 100644 --- a/golang/scaling-group.html +++ b/golang/scaling-group.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/security-guard.html b/golang/security-guard.html index b6c0febf33..79493ff303 100644 --- a/golang/security-guard.html +++ b/golang/security-guard.html @@ -1,4 +1,4 @@ - - + + diff --git a/golang/wg-repository.html b/golang/wg-repository.html index dae98924e9..09b055e938 100644 --- a/golang/wg-repository.html +++ b/golang/wg-repository.html @@ -1,4 +1,4 @@ - - + + diff --git a/tools/redir-gen/main.go b/tools/redir-gen/main.go index 87956dc163..3ce8354381 100644 --- a/tools/redir-gen/main.go +++ b/tools/redir-gen/main.go @@ -26,7 +26,7 @@ import ( ) var ( - knativeOrgs = []string{"knative", "knative-sandbox"} + knativeOrgs = []string{"knative", "knative-extensions"} allowedRepoRe = regexp.MustCompile("^[a-z][-a-z0-9]+$") archivedExceptions = []string{"eventing-contrib"} ignoreRepos = []string{