From d4637c03c4564fb48b76e534aa4c0b378a5b9dd8 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 12:54:34 +0100 Subject: [PATCH 01/20] Add v0.24 blog release notes --- .../announcing-knative-v0-24-release.md | 302 ++++++++++++++++++ 1 file changed, 302 insertions(+) create mode 100644 blog/releases/announcing-knative-v0-24-release.md diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md new file mode 100644 index 00000000000..f0f2cc2cf4c --- /dev/null +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -0,0 +1,302 @@ +--- +title: "v0.24 release" +linkTitle: "v0.24 release" +Author: "[Carlos Santana](https://twitter.com/csantanapr)" +Author handle: https://github.com/csantanapr +date: 2021-06-29 +description: "Knative v0.24 release announcement" +type: "blog" +image: knative-eventing.png +--- + + +### Announcing Knative v0.24 Release + +A new version of Knative is now available across multiple components. +Follow the instructions in the documentation +[Installing Knative](https://knative.dev/docs/admin/install/) for the respective component. + +#### Table of Contents +- [Serving v0.24](#serving-v024) +- [Eventing v0.24](#eventing-v024) +- Eventing Extensions + - [Apache Kafka Broker v0.24](#apache-kafka-broker-v024) + - [RabbitMQ Eventing v0.24](#rabbitmq-eventing-v024) +- `kn` [CLI v0.24](#client-v024) +- [Operator v0.24](#operator-v024) +- [Thank you contributors](#thank-you-contributors) + + + +### Highlights + +- +- +- + + +### Serving v0.24 + + + +#### ๐Ÿšจ Breaking or Notable Changes + +* **Renaming of some net-* components** + Related issue: [knative/networking#448](https://github.com/knative/networking/issues/448) + + As part of our efforts to GA/1.0 we've standardized on the naming of our networking plugins that + are installed along side Serving. If you're managing your Knative deployment manually with + `kubectl` **this will require a two-phase upgrade process**. Please see the below sections: + + Upgrade of [net-http01 to v0.24.0](https://github.com/knative-sandbox/net-http01/releases/tag/v0.24.0) + + ``` + # Apply the new release + $ kubectl apply -f net-http01.yaml + + # Once the deployment is ready delete the old resources + $ kubectl delete deployment http01-controller -n knative-serving + $ 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) + + ``` + # Apply the new release + $ kubectl apply -f net-certmanager.yaml + + # Once the deployment is ready apply the same file but + # prune the old resources + $ kubectl apply -f net-certmanager.yaml \ + --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) + + ``` + # Apply the new release + $ kubectl apply -f net-istio.yaml + + # Once the deployment is ready apply the same file but + # prune the old resources + $ kubectl apply -f net-istio.yaml \ + --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) + + ``` + # Apply the new release + $ kubectl apply -f net-contour.yaml + + # Once the deployment is ready apply the same file but + # prune the old resources + $ kubectl apply -f net-contour.yaml \ + --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) + 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. + Thus upgrading to v0.24.0 requires no special instructions. + +* **Kubernetes 1.19 is now required** + + As part of our + [Kubernetes Minimum Version Principle](https://github.com/knative/community/blob/main/mechanics/RELEASE-VERSIONING-PRINCIPLES.md#k8s-minimum-version-principle) + we now have a hard requirement on Kubernetes Version 1.19. + +* **Webhook/Controller RBAC changes** + + The recommended way to delete a Knative installation is to run + `kubectl delete -f serving-core.yaml` and other release YAMLs you may have applied. + There's been a misconception that deleting the `knative-serving` namespace will perform a + similar cleanup but this does not remove cluster scoped resources. + In prior releases the cluster state would have _prevented_ the reinstall of Knative Serving. + We've addressed this problem but it will require some RBAC permissions on namespaces and + finalizers. + + Please see the relevant issues & PRs: + + * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) + * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) + * `knative-serving-core` cluster role has requires permission for namespaces/finalizers: [#11517](https://github.com/knative/serving/pull/11517) + +* **DomainMapping feature is now BETA** + + This means it is built in to the main `serving-core` yaml by default. + It is still possible to opt out of the feature by setting replica count of the + domainmapping-controller to zero. + + As part of this transition the default value for autocreateClusterDomainClaims in the + `config-network` config map has been changed to false, meaning cluster-wide permissions are + required to delegate the ability to create particular DomainMappings to namespaces. + Single tenant clusters may wish to allow arbitrary users to create Domain Mappings by changing + this value back to `true`. ([#11573](https://github.com/knative/serving/pull/11573)) + +#### ๐Ÿ’ซ New Features & Changes + +* Allow dropping capabilities from a container's security context ([#11344](https://github.com/knative/serving/pull/11344)) +* 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 to 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 Contonr'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)) + +#### ๐Ÿž Bug Fixes + +* Fixed a bug where traffic would briefly be routed 'wrong', leading to errors due to exceeded +queues in deployments with a large activator count and a low service pod count. ([#11375](https://github.com/knative/serving/pull/11375)) +* Traffic status in Route is updated whenever traffic configuration was wrong. ([#11477](https://github.com/knative/serving/pull/11477)) +* Validates, consistently with other configmaps, that the `_example` section of the features +configmap is not accidentally modified. ([#11391](https://github.com/knative/serving/pull/11391)) + + +### Eventing v0.24 + + + +#### ๐Ÿšจ Breaking or Notable Changes + +* You need to run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. ([#5381](https://github.com/knative/eventing/pull/5381)) + +#### ๐Ÿ’ซ New Features & Changes + +We're glad to announce that we have introduced a new process to test and develop new features, +called the [experimental features process](https://github.com/knative/eventing/blob/a574b7ba95b9c8d4743ba3ee12184c39e0415d87/docs/experimental-features.md). + +Thanks to this process, you will be able to try out the new amazing features and provide feedback back to the project! + +We're introducing two experimental features to begin with: + +* `kreference-group`: When using `ref`, refer to resources using only the API Group, and not the full API Version. +* `delivery-timeout`: When using the `delivery`, define per request timeout. + +You can read more about how to enable these features and their usage in the +[experimental feature documentation](https://dev-knative.netlify.app/development/eventing/experimental-features/). + +* `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520) +* Added `DeliverySpec.Timeout` ([#5149](https://github.com/knative/eventing/pull/5149)) +* Added the experimental feature kreference-group. +By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (e.g. v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) +* Remaining HA Control Plane pods (via the operator) are now labelled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) + + +#### ๐Ÿž Bug Fixes + +* Fixed a race condition with apiserversources reported ready before they have begun listening for events ([#5446](https://github.com/knative/eventing/pull/5446)) +* Imc-controller cluster role now has update permission for namespaces/finalizers. ([#5539](https://github.com/knative/eventing/pull/5539)) +* Knative-eventing-webhook cluster role has update permission for namespaces/finalizers. ([#5501](https://github.com/knative/eventing/pull/5501)) + + +#### ๐Ÿงน Clean up + +* Subscription.Spec.Channel now uses KReference and the spec.channel CRD schema is less permissive and matches the supported usage of KReference fields. +Subscription's users creating their resources with YAMLs are not affected. ([#5412](https://github.com/knative/eventing/pull/5412)) +* The PingSource adapter now generates a normal event instead of a warning when the source is not ready. Rename the event to PingSourceSkipped. + * The PingSource adapter now generates the normal event PingSourceSynchronized when it has been synchronized. ([#5549](https://github.com/knative/eventing/pull/5549)) + + +### Eventing Extensions + +#### 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) +- Bump Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) +- Bump protobuf to v3.17.x [#946](https://github.com/knative-sandbox/eventing-kafka-broker/pull/946) +- Bumped vert.x to v4.1 [#900](https://github.com/knative-sandbox/eventing-kafka-broker/pull/900) + + +#### RabbitMQ Eventing v0.24 + + + +#### ๐Ÿšจ Breaking or Notable Changes + +#### ๐Ÿž Bug Fixes + + +### Client v0.24 + + + +#### ๐Ÿ’ซ New Features & Changes + +- Prettify printing of webhook warnings [#1353](https://github.com/knative/client/pull/1353) +- Update Kubernetes dependencies to v0.20.7 [#1344](https://github.com/knative/client/pull/1344) +- Increase code coverage for Sources [#1343](https://github.com/knative/client/pull/1343) +- Make e2e test run over other networks [#1339](https://github.com/knative/client/pull/1339) +- Add env-value-from flag & keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) + +#### ๐Ÿž Bug Fixes + +- Fix Subscription's Channel to use KRefence type [#1326](https://github.com/knative/client/pull/1326) + + +### Operator v0.24 + + + +#### ๐Ÿ’ซ New Features & Changes + +- Add the manifests of the eventing sources [#641](https://github.com/knative/operator/pull/641) +- Change the APIs for eventing sources [#613](https://github.com/knative/operator/pull/613) +- Add the logic to install sources [#645](https://github.com/knative/operator/pull/645) +- Drop use of pkg/test.KubeClient [#655](https://github.com/knative/operator/pull/655) +- Install the webhooks after installing the deployments and services [#674](https://github.com/knative/operator/pull/674) + +#### ๐Ÿž Bug Fixes + +- Improve fetcher by supporting version parameter [#613](https://github.com/knative/operator/pull/613) +- Add a 20-second timeout before running the post upgrade tests [#623](https://github.com/knative/operator/pull/623) +- Add $KO_FLAGS to e2e test [#649](https://github.com/knative/operator/pull/649) +- Make e2e test run over other networks [#650](https://github.com/knative/operator/pull/650) +- Allow to set NodeSelector via spec.deployments.nodeSelector [#658](https://github.com/knative/operator/pull/658) +- Gracefully handle net-* deployment rename [#669](https://github.com/knative/operator/pull/669) + +### Thank you, contributors + +- [@BbolroC](https://github.com/BbolroC) +- [@aliok](https://github.com/aliok) +- [@benmoss](https://github.com/benmoss) +- [@dprotaso](https://github.com/dprotaso) +- [@dsimansk](https://github.com/dsimansk) +- [@houshengbo](https://github.com/houshengbo) +- [@howardjohn](https://github.com/howardjohn) +- [@itsmurugappan](https://github.com/itsmurugappan) +- [@izabelacg](https://github.com/izabelacg) +- [@julz](https://github.com/julz) +- [@lberk](https://github.com/lberk)) +- [@lionelvillard](https://github.com/lionelvillard) +- [@markusthoemmes](https://github.com/markusthoemmes) +- [@matzew](https://github.com/matzew) +- [@nak3](https://github.com/nak3) +- [@novahe](https://github.com/novahe) +- [@pierDipi](https://github.com/pierDipi) +- [@psschwei](https://github.com/psschwei) +- [@shinigambit](https://github.com/shinigambit) +- [@slinkydeveloper](https://github.com/slinkydeveloper) +- [@zroubalik](https://github.com/zroubalik) + + +### Learn more + +Knative is an open source project that anyone in the [community](https://knative.dev/community/) can use, improve, and enjoy. We'd love you to join us! + +- [Welcome to Knative](https://knative.dev/docs) +- [Getting started documentation](https://knative.dev/docs/getting-started) +- [Samples](https://knative.dev/docs/samples) +- [Knative working groups](https://github.com/knative/community/blob/main/working-groups/WORKING-GROUPS.md) +- [Questions and issues](https://knative.dev/contributing/#questions-and-issues) +- [Knative User Mailing List](https://groups.google.com/forum/#!forum/knative-users) +- [Knative Development Mailing List](https://groups.google.com/forum/#!forum/knative-dev) +- Knative on Twitter [@KnativeProject](https://twitter.com/KnativeProject) +- Knative on [StackOverflow](https://stackoverflow.com/questions/tagged/knative) +- Knative [Slack](https://slack.knative.dev) +- Knative on [YouTube](https://www.youtube.com/channel/UCq7cipu-A1UHOkZ9fls1N8A) From 4f75ca95e64a5025082608b9aaee5e020344468c Mon Sep 17 00:00:00 2001 From: Omer B Date: Wed, 7 Jul 2021 09:47:16 -0400 Subject: [PATCH 02/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 1 - 1 file changed, 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index f0f2cc2cf4c..1d5e1b4795d 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -293,7 +293,6 @@ Knative is an open source project that anyone in the [community](https://knative - [Getting started documentation](https://knative.dev/docs/getting-started) - [Samples](https://knative.dev/docs/samples) - [Knative working groups](https://github.com/knative/community/blob/main/working-groups/WORKING-GROUPS.md) -- [Questions and issues](https://knative.dev/contributing/#questions-and-issues) - [Knative User Mailing List](https://groups.google.com/forum/#!forum/knative-users) - [Knative Development Mailing List](https://groups.google.com/forum/#!forum/knative-dev) - Knative on Twitter [@KnativeProject](https://twitter.com/KnativeProject) From 9d14a119d494a66c0e4cd3821787bc7f3b7fbc2b Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 15:33:17 +0100 Subject: [PATCH 03/20] Add to v0.24 release notes --- .../announcing-knative-v0-24-release.md | 68 +++++++++++-------- 1 file changed, 40 insertions(+), 28 deletions(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 1d5e1b4795d..abf93c778c6 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -17,6 +17,7 @@ Follow the instructions in the documentation [Installing Knative](https://knative.dev/docs/admin/install/) for the respective component. #### Table of Contents + - [Serving v0.24](#serving-v024) - [Eventing v0.24](#eventing-v024) - Eventing Extensions @@ -30,8 +31,17 @@ Follow the instructions in the documentation ### Highlights -- -- +- Kubernetes v1.19 is now a hard minimum requirement. +- As part of our efforts to GA/1.0 we've standardized the naming of our networking plugins that are installed alongside Serving. +- For Serving, DomainMapping feature is now beta. +- For Serving, the recommended way to delete a Knative installation is to run +`kubectl delete -f serving-core.yaml` and other release YAMLs you might have applied. +- For Eventing, you must run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. +- For Eventing, there are new experimental features and a new process for trying them out. +- For Client, a new option `--env-value-from` was added to `kn service create` and +`kn service update` to allow referencing values from secrets and config maps. +The order of environment variables is now kept according to the order that `--env` related options +are provided on the command line. - @@ -45,8 +55,8 @@ Follow the instructions in the documentation Related issue: [knative/networking#448](https://github.com/knative/networking/issues/448) As part of our efforts to GA/1.0 we've standardized on the naming of our networking plugins that - are installed along side Serving. If you're managing your Knative deployment manually with - `kubectl` **this will require a two-phase upgrade process**. Please see the below sections: + 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) @@ -98,7 +108,7 @@ Follow the instructions in the documentation Upgrade of [net-kourier to v0.24.0](https://github.com/knative-sandbox/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. - Thus upgrading to v0.24.0 requires no special instructions. + Therefore upgrading to v0.24.0 requires no special instructions. * **Kubernetes 1.19 is now required** @@ -109,14 +119,14 @@ Follow the instructions in the documentation * **Webhook/Controller RBAC changes** The recommended way to delete a Knative installation is to run - `kubectl delete -f serving-core.yaml` and other release YAMLs you may have applied. - There's been a misconception that deleting the `knative-serving` namespace will perform a - similar cleanup but this does not remove cluster scoped resources. + `kubectl delete -f serving-core.yaml` and other release YAMLs you might have applied. + There's been a misconception that deleting the `knative-serving` namespace performs a + similar cleanup but this does not remove cluster-scoped resources. In prior releases the cluster state would have _prevented_ the reinstall of Knative Serving. - We've addressed this problem but it will require some RBAC permissions on namespaces and + We've addressed this problem, but it requires some RBAC permissions on namespaces and finalizers. - Please see the relevant issues & PRs: + See the relevant issues and PRs below: * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) @@ -124,12 +134,12 @@ Follow the instructions in the documentation * **DomainMapping feature is now BETA** - This means it is built in to the main `serving-core` yaml by default. + This means it is built in to the main `serving-core` YAML by default. It is still possible to opt out of the feature by setting replica count of the domainmapping-controller to zero. As part of this transition the default value for autocreateClusterDomainClaims in the - `config-network` config map has been changed to false, meaning cluster-wide permissions are + `config-network` config map was changed to false, meaning cluster-wide permissions are required to delegate the ability to create particular DomainMappings to namespaces. Single tenant clusters may wish to allow arbitrary users to create Domain Mappings by changing this value back to `true`. ([#11573](https://github.com/knative/serving/pull/11573)) @@ -146,11 +156,11 @@ Follow the instructions in the documentation #### ๐Ÿž Bug Fixes -* Fixed a bug where traffic would briefly be routed 'wrong', leading to errors due to exceeded -queues in deployments with a large activator count and a low service pod count. ([#11375](https://github.com/knative/serving/pull/11375)) +* Fixed a bug where traffic was briefly routed 'wrong', leading to errors due to exceeded +queues in deployments with a large activator count and a low service Pod count. ([#11375](https://github.com/knative/serving/pull/11375)) * Traffic status in Route is updated whenever traffic configuration was wrong. ([#11477](https://github.com/knative/serving/pull/11477)) * Validates, consistently with other configmaps, that the `_example` section of the features -configmap is not accidentally modified. ([#11391](https://github.com/knative/serving/pull/11391)) +ConfigMap is not accidentally modified. ([#11391](https://github.com/knative/serving/pull/11391)) ### Eventing v0.24 @@ -159,14 +169,14 @@ configmap is not accidentally modified. ([#11391](https://github.com/knative/ser #### ๐Ÿšจ Breaking or Notable Changes -* You need to run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. ([#5381](https://github.com/knative/eventing/pull/5381)) +* You must run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. ([#5381](https://github.com/knative/eventing/pull/5381)) #### ๐Ÿ’ซ New Features & Changes We're glad to announce that we have introduced a new process to test and develop new features, called the [experimental features process](https://github.com/knative/eventing/blob/a574b7ba95b9c8d4743ba3ee12184c39e0415d87/docs/experimental-features.md). -Thanks to this process, you will be able to try out the new amazing features and provide feedback back to the project! +Thanks to this process, you are able to try out the new amazing features and provide feedback back to the project! We're introducing two experimental features to begin with: @@ -176,11 +186,11 @@ We're introducing two experimental features to begin with: You can read more about how to enable these features and their usage in the [experimental feature documentation](https://dev-knative.netlify.app/development/eventing/experimental-features/). -* `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520) +* `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520)) * Added `DeliverySpec.Timeout` ([#5149](https://github.com/knative/eventing/pull/5149)) * Added the experimental feature kreference-group. -By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (e.g. v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) -* Remaining HA Control Plane pods (via the operator) are now labelled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) +By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (for example, v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) +* Remaining HA Control Plane Pods (through the operator) are now labeled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) #### ๐Ÿž Bug Fixes @@ -201,14 +211,15 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 ### Eventing Extensions #### 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) +- 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) -- Bump Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) +- Update Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) - Bump protobuf to v3.17.x [#946](https://github.com/knative-sandbox/eventing-kafka-broker/pull/946) - Bumped vert.x to v4.1 [#900](https://github.com/knative-sandbox/eventing-kafka-broker/pull/900) @@ -232,7 +243,7 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 - Update Kubernetes dependencies to v0.20.7 [#1344](https://github.com/knative/client/pull/1344) - Increase code coverage for Sources [#1343](https://github.com/knative/client/pull/1343) - Make e2e test run over other networks [#1339](https://github.com/knative/client/pull/1339) -- Add env-value-from flag & keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) +- Add env-value-from flag and keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) #### ๐Ÿž Bug Fixes @@ -245,8 +256,8 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 #### ๐Ÿ’ซ New Features & Changes -- Add the manifests of the eventing sources [#641](https://github.com/knative/operator/pull/641) -- Change the APIs for eventing sources [#613](https://github.com/knative/operator/pull/613) +- Add the manifests of the Eventing sources [#641](https://github.com/knative/operator/pull/641) +- Change the APIs for Eventing sources [#613](https://github.com/knative/operator/pull/613) - Add the logic to install sources [#645](https://github.com/knative/operator/pull/645) - Drop use of pkg/test.KubeClient [#655](https://github.com/knative/operator/pull/655) - Install the webhooks after installing the deployments and services [#674](https://github.com/knative/operator/pull/674) @@ -254,10 +265,10 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 #### ๐Ÿž Bug Fixes - Improve fetcher by supporting version parameter [#613](https://github.com/knative/operator/pull/613) -- Add a 20-second timeout before running the post upgrade tests [#623](https://github.com/knative/operator/pull/623) +- Add a 20-second timeout before running the post-upgrade tests [#623](https://github.com/knative/operator/pull/623) - Add $KO_FLAGS to e2e test [#649](https://github.com/knative/operator/pull/649) - Make e2e test run over other networks [#650](https://github.com/knative/operator/pull/650) -- Allow to set NodeSelector via spec.deployments.nodeSelector [#658](https://github.com/knative/operator/pull/658) +- Allow to set NodeSelector through spec.deployments.nodeSelector [#658](https://github.com/knative/operator/pull/658) - Gracefully handle net-* deployment rename [#669](https://github.com/knative/operator/pull/669) ### Thank you, contributors @@ -272,7 +283,7 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 - [@itsmurugappan](https://github.com/itsmurugappan) - [@izabelacg](https://github.com/izabelacg) - [@julz](https://github.com/julz) -- [@lberk](https://github.com/lberk)) +- [@lberk](https://github.com/lberk) - [@lionelvillard](https://github.com/lionelvillard) - [@markusthoemmes](https://github.com/markusthoemmes) - [@matzew](https://github.com/matzew) @@ -293,6 +304,7 @@ Knative is an open source project that anyone in the [community](https://knative - [Getting started documentation](https://knative.dev/docs/getting-started) - [Samples](https://knative.dev/docs/samples) - [Knative working groups](https://github.com/knative/community/blob/main/working-groups/WORKING-GROUPS.md) +- [Documentation issues](https://github.com/knative/docs/issues) - [Knative User Mailing List](https://groups.google.com/forum/#!forum/knative-users) - [Knative Development Mailing List](https://groups.google.com/forum/#!forum/knative-dev) - Knative on Twitter [@KnativeProject](https://twitter.com/KnativeProject) From 5f6c98641cc2fe4cc195d22e6fd3112395ce6c1b Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:27:01 +0100 Subject: [PATCH 04/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 1 - 1 file changed, 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index abf93c778c6..1120124dce4 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -42,7 +42,6 @@ Follow the instructions in the documentation `kn service update` to allow referencing values from secrets and config maps. The order of environment variables is now kept according to the order that `--env` related options are provided on the command line. -- ### Serving v0.24 From f04a4674bee7b00a649710ee773702abf4b8ab26 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:27:13 +0100 Subject: [PATCH 05/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 1120124dce4..645805d0618 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -242,7 +242,7 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 - Update Kubernetes dependencies to v0.20.7 [#1344](https://github.com/knative/client/pull/1344) - Increase code coverage for Sources [#1343](https://github.com/knative/client/pull/1343) - Make e2e test run over other networks [#1339](https://github.com/knative/client/pull/1339) -- Add env-value-from flag and keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) +- Add `env-value-from` flag and keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) #### ๐Ÿž Bug Fixes From f77e8426be657a0cfbc848b52d75bb187d145bea Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:27:28 +0100 Subject: [PATCH 06/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 645805d0618..7848c571487 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -50,7 +50,7 @@ are provided on the command line. #### ๐Ÿšจ Breaking or Notable Changes -* **Renaming of some net-* components** +* **Renaming of some `net-*` components** Related issue: [knative/networking#448](https://github.com/knative/networking/issues/448) As part of our efforts to GA/1.0 we've standardized on the naming of our networking plugins that From d2c32dc5c1ee8d5751aba05920b01df146c0b5bc Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:27:40 +0100 Subject: [PATCH 07/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 7848c571487..5167a92e025 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -150,7 +150,7 @@ are provided on the command line. * 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 to 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 Contonr's ClusterRole and ClusterRoleBinding to differ from existing contour installation ([net-contour#500](https://github.com/knative-sandbox/net-contour/pull/500)) +* 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)) #### ๐Ÿž Bug Fixes From ae1e37391c17bdafa89c5f6941e3d35df6d39570 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:27:54 +0100 Subject: [PATCH 08/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 5167a92e025..7a5fa7cc93c 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -175,7 +175,7 @@ ConfigMap is not accidentally modified. ([#11391](https://github.com/knative/ser We're glad to announce that we have introduced a new process to test and develop new features, called the [experimental features process](https://github.com/knative/eventing/blob/a574b7ba95b9c8d4743ba3ee12184c39e0415d87/docs/experimental-features.md). -Thanks to this process, you are able to try out the new amazing features and provide feedback back to the project! +Thanks to this process, you are able to try out the new amazing features and provide feedback to the project! We're introducing two experimental features to begin with: From c90a95cf9b03f47326375c9e00b5954cfadc9999 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:28:09 +0100 Subject: [PATCH 09/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 7a5fa7cc93c..ce968d515b2 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -37,7 +37,7 @@ Follow the instructions in the documentation - For Serving, the recommended way to delete a Knative installation is to run `kubectl delete -f serving-core.yaml` and other release YAMLs you might have applied. - For Eventing, you must run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. -- For Eventing, there are new experimental features and a new process for trying them out. +- For Eventing, there are new experimental features and a new process for trying them out. For more information, see [Experimental features](https://knative.dev/docs/eventing/experimental-features/). - For Client, a new option `--env-value-from` was added to `kn service create` and `kn service update` to allow referencing values from secrets and config maps. The order of environment variables is now kept according to the order that `--env` related options From 02644805c9d47d7dbab938c131ed9823853bf9f3 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:28:16 +0100 Subject: [PATCH 10/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index ce968d515b2..d97d21ea76c 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -187,7 +187,7 @@ You can read more about how to enable these features and their usage in the * `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520)) * Added `DeliverySpec.Timeout` ([#5149](https://github.com/knative/eventing/pull/5149)) -* Added the experimental feature kreference-group. +* Added the experimental feature `kreference-group`. By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (for example, v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) * Remaining HA Control Plane Pods (through the operator) are now labeled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) From 953b574d627ba08ddf933693724774620b02d1d7 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:28:23 +0100 Subject: [PATCH 11/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index d97d21ea76c..d5456d8b9fd 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -188,7 +188,7 @@ You can read more about how to enable these features and their usage in the * `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520)) * Added `DeliverySpec.Timeout` ([#5149](https://github.com/knative/eventing/pull/5149)) * Added the experimental feature `kreference-group`. -By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (for example, v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) +By enabling it, you can use `Subscriber.Ref.Group` instead of `Subscriber.Ref.APIVersion` to refer to another Resource, without being explicit about the resource version (for example, v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) * Remaining HA Control Plane Pods (through the operator) are now labeled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) From 758ed8b6aacb6e1d31ee3313b1db8f4e6b92f0fc Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:28:36 +0100 Subject: [PATCH 12/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index d5456d8b9fd..6eb74ea19ee 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -57,7 +57,7 @@ are provided on the command line. 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-sandbox/net-http01/releases/tag/v0.24.0) ``` # Apply the new release From be3fef6bd78d539fda635e8a5fcea2cfc18f01a5 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:28:49 +0100 Subject: [PATCH 13/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 6eb74ea19ee..5b2e1a7e620 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -201,7 +201,7 @@ By enabling it, you can use `Subscriber.Ref.Group` instead of `Subscriber.Ref.AP #### ๐Ÿงน Clean up -* Subscription.Spec.Channel now uses KReference and the spec.channel CRD schema is less permissive and matches the supported usage of KReference fields. +* `Subscription.Spec.Channel` now uses KReference and the `spec.channel` CRD schema is less permissive and matches the supported usage of KReference fields. Subscription's users creating their resources with YAMLs are not affected. ([#5412](https://github.com/knative/eventing/pull/5412)) * The PingSource adapter now generates a normal event instead of a warning when the source is not ready. Rename the event to PingSourceSkipped. * The PingSource adapter now generates the normal event PingSourceSynchronized when it has been synchronized. ([#5549](https://github.com/knative/eventing/pull/5549)) From 71567c9e2d84b9fc9d67636118132db2adbcf642 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:38:45 +0100 Subject: [PATCH 14/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 5b2e1a7e620..3a5e40014ad 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -68,7 +68,7 @@ are provided on the command line. $ 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-sandbox/net-certmanager/releases/tag/v0.24.0) ``` # Apply the new release From 1677647a23d5d2ea3ad2a9fe9d0bebc22a811160 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:38:53 +0100 Subject: [PATCH 15/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 3a5e40014ad..248cdd8dd2b 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -80,7 +80,7 @@ are provided on the command line. --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-sandbox/net-istio/releases/tag/v0.24.0) ``` # Apply the new release From 3babc2c47df19996e54ace17e0818e6baa996ec3 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:39:02 +0100 Subject: [PATCH 16/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 248cdd8dd2b..ecf6e3e5322 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -92,7 +92,7 @@ are provided on the command line. --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-sandbox/net-contour/releases/tag/v0.24.0) ``` # Apply the new release From 91346f979c138e104f80d03eef8cc4a8305f8ce1 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:39:10 +0100 Subject: [PATCH 17/20] Update blog/releases/announcing-knative-v0-24-release.md Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index ecf6e3e5322..c59503e1049 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -127,9 +127,9 @@ are provided on the command line. See the relevant issues and PRs below: - * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) - * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) - * `knative-serving-core` cluster role has requires permission for namespaces/finalizers: [#11517](https://github.com/knative/serving/pull/11517) + * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) + * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) + * `knative-serving-core` cluster role has requires permission for namespaces/finalizers: [#11517](https://github.com/knative/serving/pull/11517) * **DomainMapping feature is now BETA** From b6541bc18c383d2f0b34b3ee6745ecaf03d569b8 Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:40:45 +0100 Subject: [PATCH 18/20] Apply suggestions from code review Co-authored-by: Samia Nneji --- blog/releases/announcing-knative-v0-24-release.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index c59503e1049..0d89c2ad1b2 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -104,7 +104,7 @@ are provided on the command line. --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-sandbox/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. @@ -133,7 +133,7 @@ are provided on the command line. * **DomainMapping feature is now BETA** - This means it is built in to the main `serving-core` YAML by default. + This means it is built into the main `serving-core` YAML by default. It is still possible to opt out of the feature by setting replica count of the domainmapping-controller to zero. @@ -146,9 +146,9 @@ are provided on the command line. #### ๐Ÿ’ซ New Features & Changes * Allow dropping capabilities from a container's security context ([#11344](https://github.com/knative/serving/pull/11344)) -* DomainMapping can now specify a TLS secret to be used as the HTTPS certificate ([#11250](https://github.com/knative/serving/pull/11250) +* 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 to default routes to surface a URL scheme of your choice rather than the default "http". ([#11480](https://github.com/knative/serving/pull/11480)) +* `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)) From 0b12b7358f4f9530a1d0e5f0f9104c6456bf93df Mon Sep 17 00:00:00 2001 From: RichardJJG Date: Wed, 7 Jul 2021 17:42:43 +0100 Subject: [PATCH 19/20] Added TBD to RabbitMQ Eventing extension --- blog/releases/announcing-knative-v0-24-release.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index 0d89c2ad1b2..ca8e0560ac9 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -227,6 +227,8 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 +TBD + #### ๐Ÿšจ Breaking or Notable Changes #### ๐Ÿž Bug Fixes From 1c1c24c922ac3ab5cd00cf71df38acae94a85e8a Mon Sep 17 00:00:00 2001 From: Omer B Date: Thu, 8 Jul 2021 11:33:05 -0400 Subject: [PATCH 20/20] Fixes #3966 Adding correct md links, added RabbitMQ --- .../announcing-knative-v0-24-release.md | 137 +++++++++--------- 1 file changed, 69 insertions(+), 68 deletions(-) diff --git a/blog/releases/announcing-knative-v0-24-release.md b/blog/releases/announcing-knative-v0-24-release.md index ca8e0560ac9..d38c5b4e94b 100644 --- a/blog/releases/announcing-knative-v0-24-release.md +++ b/blog/releases/announcing-knative-v0-24-release.md @@ -1,8 +1,9 @@ +# 0.24 Release Notes --- title: "v0.24 release" linkTitle: "v0.24 release" -Author: "[Carlos Santana](https://twitter.com/csantanapr)" -Author handle: https://github.com/csantanapr +Author: "[Omer Bensaadon](https://twitter.com/omer_bensaadon)" +Author handle: https://github.com/omerbensaadon date: 2021-06-29 description: "Knative v0.24 release announcement" type: "blog" @@ -13,35 +14,31 @@ image: knative-eventing.png ### Announcing Knative v0.24 Release A new version of Knative is now available across multiple components. + Follow the instructions in the documentation [Installing Knative](https://knative.dev/docs/admin/install/) for the respective component. #### Table of Contents - -- [Serving v0.24](#serving-v024) -- [Eventing v0.24](#eventing-v024) -- Eventing Extensions - - [Apache Kafka Broker v0.24](#apache-kafka-broker-v024) - - [RabbitMQ Eventing v0.24](#rabbitmq-eventing-v024) -- `kn` [CLI v0.24](#client-v024) -- [Operator v0.24](#operator-v024) -- [Thank you contributors](#thank-you-contributors) +- [Highlights](#highlights) +- [Serving v0.24](#Serving-v024) +- [Eventing v0.24](#Eventing-v024) +- [Eventing Extensions](#Eventing-Extensions) + - [Apache Kafka Broker v0.24](#Apache-Kafka-Broker-v024) + - [RabbitMQ Eventing v0.24](#RabbitMQ-Eventing-v024) +- `kn` [CLI v0.24](#Client-v024) +- [Operator v0.24](#Operator-v024) +- [Thank you contributors](#Thank-you-contributors) ### Highlights - -- Kubernetes v1.19 is now a hard minimum requirement. -- As part of our efforts to GA/1.0 we've standardized the naming of our networking plugins that are installed alongside Serving. -- For Serving, DomainMapping feature is now beta. -- For Serving, the recommended way to delete a Knative installation is to run -`kubectl delete -f serving-core.yaml` and other release YAMLs you might have applied. -- For Eventing, you must run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. -- For Eventing, there are new experimental features and a new process for trying them out. For more information, see [Experimental features](https://knative.dev/docs/eventing/experimental-features/). -- For Client, a new option `--env-value-from` was added to `kn service create` and -`kn service update` to allow referencing values from secrets and config maps. -The order of environment variables is now kept according to the order that `--env` related options -are provided on the command line. +- The Knative site [has a brand new look!](https://knative.dev/docs/) We're built on [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/) +- A brand new Getting Started Tutorial has been added to the Knative site. Check it out here: https://knative.dev/docs/getting-started/ +- We've done some reorganization of the Docs and we now have a [Developer guide](https://knative.dev/doc/developer/) and [Administrator's guide](https://knative.dev/doc/admin/) +- The DomainMapping feature is now BETA +- In preparation for GA, some net-* components have been renamed (see Breaking Changes in Serving section) +- Eventing has a new Experimental Features process and two new experimental features for you to try +- The Minimum Kubernetes version is now 1.19 ### Serving v0.24 @@ -50,14 +47,14 @@ are provided on the command line. #### ๐Ÿšจ Breaking or Notable Changes -* **Renaming of some `net-*` components** +* **Renaming of some net-* components** Related issue: [knative/networking#448](https://github.com/knative/networking/issues/448) 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**. See the below sections: + are installed along side Serving. If you're managing your Knative deployment manually with + `kubectl` **this will require a two-phase upgrade process**. Please 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-sandbox/net-http01/releases/tag/v0.24.0) ``` # Apply the new release @@ -68,7 +65,7 @@ are provided on the command line. $ 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-sandbox/net-certmanager/releases/tag/v0.24.0) ``` # Apply the new release @@ -80,7 +77,7 @@ are provided on the command line. --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-sandbox/net-istio/releases/tag/v0.24.0) ``` # Apply the new release @@ -92,7 +89,7 @@ are provided on the command line. --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-sandbox/net-contour/releases/tag/v0.24.0) ``` # Apply the new release @@ -104,10 +101,10 @@ are provided on the command line. --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-sandbox/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. + Thus upgrading to v0.24.0 requires no special instructions. * **Kubernetes 1.19 is now required** @@ -118,27 +115,27 @@ are provided on the command line. * **Webhook/Controller RBAC changes** The recommended way to delete a Knative installation is to run - `kubectl delete -f serving-core.yaml` and other release YAMLs you might have applied. - There's been a misconception that deleting the `knative-serving` namespace performs a - similar cleanup but this does not remove cluster-scoped resources. + `kubectl delete -f serving-core.yaml` and other release YAMLs you may have applied. + There's been a misconception that deleting the `knative-serving` namespace will perform a + similar cleanup but this does not remove cluster scoped resources. In prior releases the cluster state would have _prevented_ the reinstall of Knative Serving. - We've addressed this problem, but it requires some RBAC permissions on namespaces and + We've addressed this problem but it will require some RBAC permissions on namespaces and finalizers. - See the relevant issues and PRs below: + Please see the relevant issues & PRs: - * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) - * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) - * `knative-serving-core` cluster role has requires permission for namespaces/finalizers: [#11517](https://github.com/knative/serving/pull/11517) + * Original issue: [knative/pkg#2044](https://github.com/knative/pkg/issues/2044) + * Workaround: [knative/pkg#2098](https://github.com/knative/pkg/pull/2098) + * `knative-serving-core` cluster role has requires permission for namespaces/finalizers: [#11517](https://github.com/knative/serving/pull/11517) * **DomainMapping feature is now BETA** - This means it is built into the main `serving-core` YAML by default. + This means it is built in to the main `serving-core` yaml by default. It is still possible to opt out of the feature by setting replica count of the domainmapping-controller to zero. As part of this transition the default value for autocreateClusterDomainClaims in the - `config-network` config map was changed to false, meaning cluster-wide permissions are + `config-network` config map has been changed to false, meaning cluster-wide permissions are required to delegate the ability to create particular DomainMappings to namespaces. Single tenant clusters may wish to allow arbitrary users to create Domain Mappings by changing this value back to `true`. ([#11573](https://github.com/knative/serving/pull/11573)) @@ -146,20 +143,20 @@ are provided on the command line. #### ๐Ÿ’ซ New Features & Changes * Allow dropping capabilities from a container's security context ([#11344](https://github.com/knative/serving/pull/11344)) -* DomainMapping can now specify a TLS secret to be used as the HTTPS certificate ([#11250](https://github.com/knative/serving/pull/11250)) +* 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)) +* `defaultExternalScheme` can now be used to 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)) +* Rename Contonr'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)) #### ๐Ÿž Bug Fixes -* Fixed a bug where traffic was briefly routed 'wrong', leading to errors due to exceeded -queues in deployments with a large activator count and a low service Pod count. ([#11375](https://github.com/knative/serving/pull/11375)) +* Fixed a bug where traffic would briefly be routed 'wrong', leading to errors due to exceeded +queues in deployments with a large activator count and a low service pod count. ([#11375](https://github.com/knative/serving/pull/11375)) * Traffic status in Route is updated whenever traffic configuration was wrong. ([#11477](https://github.com/knative/serving/pull/11477)) * Validates, consistently with other configmaps, that the `_example` section of the features -ConfigMap is not accidentally modified. ([#11391](https://github.com/knative/serving/pull/11391)) +configmap is not accidentally modified. ([#11391](https://github.com/knative/serving/pull/11391)) ### Eventing v0.24 @@ -168,14 +165,14 @@ ConfigMap is not accidentally modified. ([#11391](https://github.com/knative/ser #### ๐Ÿšจ Breaking or Notable Changes -* You must run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. ([#5381](https://github.com/knative/eventing/pull/5381)) +* You need to run the storage migration tool after the upgrade to migrate from v1beta2 to v1 `pingsources.sources.knative.dev` resources. ([#5381](https://github.com/knative/eventing/pull/5381)) #### ๐Ÿ’ซ New Features & Changes We're glad to announce that we have introduced a new process to test and develop new features, called the [experimental features process](https://github.com/knative/eventing/blob/a574b7ba95b9c8d4743ba3ee12184c39e0415d87/docs/experimental-features.md). -Thanks to this process, you are able to try out the new amazing features and provide feedback to the project! +Thanks to this process, you will be able to try out the new amazing features and provide feedback back to the project! We're introducing two experimental features to begin with: @@ -185,11 +182,11 @@ We're introducing two experimental features to begin with: You can read more about how to enable these features and their usage in the [experimental feature documentation](https://dev-knative.netlify.app/development/eventing/experimental-features/). -* `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520)) +* `KReference.Group` now can be used in `Subscription.Spec.Channel` as well ([#5520](https://github.com/knative/eventing/pull/5520) * Added `DeliverySpec.Timeout` ([#5149](https://github.com/knative/eventing/pull/5149)) -* Added the experimental feature `kreference-group`. -By enabling it, you can use `Subscriber.Ref.Group` instead of `Subscriber.Ref.APIVersion` to refer to another Resource, without being explicit about the resource version (for example, v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) -* Remaining HA Control Plane Pods (through the operator) are now labeled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) +* Added the experimental feature kreference-group. +By enabling it, you can use Subscriber.Ref.Group instead of Subscriber.Ref.APIVersion to refer to another Resource, without being explicit about the resource version (e.g. v1beta1, v1, ...) ([#5440](https://github.com/knative/eventing/pull/5440)) +* Remaining HA Control Plane pods (via the operator) are now labelled with podAntiAffinity to ensure there isn't a single point of failure. ([#5409](https://github.com/knative/eventing/pull/5409)) #### ๐Ÿž Bug Fixes @@ -201,7 +198,7 @@ By enabling it, you can use `Subscriber.Ref.Group` instead of `Subscriber.Ref.AP #### ๐Ÿงน Clean up -* `Subscription.Spec.Channel` now uses KReference and the `spec.channel` CRD schema is less permissive and matches the supported usage of KReference fields. +* Subscription.Spec.Channel now uses KReference and the spec.channel CRD schema is less permissive and matches the supported usage of KReference fields. Subscription's users creating their resources with YAMLs are not affected. ([#5412](https://github.com/knative/eventing/pull/5412)) * The PingSource adapter now generates a normal event instead of a warning when the source is not ready. Rename the event to PingSourceSkipped. * The PingSource adapter now generates the normal event PingSourceSynchronized when it has been synchronized. ([#5549](https://github.com/knative/eventing/pull/5549)) @@ -210,15 +207,14 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 ### Eventing Extensions #### 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) +- 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) -- Update Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) +- Bump Go to v1.16 [#886](https://github.com/knative-sandbox/eventing-kafka-broker/pull/886) - Bump protobuf to v3.17.x [#946](https://github.com/knative-sandbox/eventing-kafka-broker/pull/946) - Bumped vert.x to v4.1 [#900](https://github.com/knative-sandbox/eventing-kafka-broker/pull/900) @@ -227,11 +223,17 @@ Subscription's users creating their resources with YAMLs are not affected. ([#54 -TBD - -#### ๐Ÿšจ Breaking or Notable Changes +#### ๐Ÿ’ซ 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), [@vaikas](https://github.com/vaikas)) +- 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), [@vaikas](https://github.com/vaikas)) +- Add installation instructions for two kinds of brokers. ([#315](https://github.com/knative-sandbox/eventing-rabbitmq/pull/315), [@vaikas](https://github.com/vaikas)) #### ๐Ÿž Bug Fixes +- Fix Standalone Broker to support Trigger DeadLetterSink properly. ([#341](https://github.com/knative-sandbox/eventing-rabbitmq/pull/341), [@vaikas](https://github.com/vaikas)) +- Fix per trigger DeadLetterSink support. ([#337](https://github.com/knative-sandbox/eventing-rabbitmq/pull/337), [@vaikas](https://github.com/vaikas)) +- Fix #320 ([#325](https://github.com/knative-sandbox/eventing-rabbitmq/pull/325), [@vaikas](https://github.com/vaikas)) +- 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), [@vaikas](https://github.com/vaikas)) +- 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), [@vaikas](https://github.com/vaikas)) ### Client v0.24 @@ -244,7 +246,7 @@ TBD - Update Kubernetes dependencies to v0.20.7 [#1344](https://github.com/knative/client/pull/1344) - Increase code coverage for Sources [#1343](https://github.com/knative/client/pull/1343) - Make e2e test run over other networks [#1339](https://github.com/knative/client/pull/1339) -- Add `env-value-from` flag and keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) +- Add env-value-from flag & keep order of env vars as provided [#1328](https://github.com/knative/client/pull/1328) #### ๐Ÿž Bug Fixes @@ -257,8 +259,8 @@ TBD #### ๐Ÿ’ซ New Features & Changes -- Add the manifests of the Eventing sources [#641](https://github.com/knative/operator/pull/641) -- Change the APIs for Eventing sources [#613](https://github.com/knative/operator/pull/613) +- Add the manifests of the eventing sources [#641](https://github.com/knative/operator/pull/641) +- Change the APIs for eventing sources [#613](https://github.com/knative/operator/pull/613) - Add the logic to install sources [#645](https://github.com/knative/operator/pull/645) - Drop use of pkg/test.KubeClient [#655](https://github.com/knative/operator/pull/655) - Install the webhooks after installing the deployments and services [#674](https://github.com/knative/operator/pull/674) @@ -266,10 +268,10 @@ TBD #### ๐Ÿž Bug Fixes - Improve fetcher by supporting version parameter [#613](https://github.com/knative/operator/pull/613) -- Add a 20-second timeout before running the post-upgrade tests [#623](https://github.com/knative/operator/pull/623) +- Add a 20-second timeout before running the post upgrade tests [#623](https://github.com/knative/operator/pull/623) - Add $KO_FLAGS to e2e test [#649](https://github.com/knative/operator/pull/649) - Make e2e test run over other networks [#650](https://github.com/knative/operator/pull/650) -- Allow to set NodeSelector through spec.deployments.nodeSelector [#658](https://github.com/knative/operator/pull/658) +- Allow to set NodeSelector via spec.deployments.nodeSelector [#658](https://github.com/knative/operator/pull/658) - Gracefully handle net-* deployment rename [#669](https://github.com/knative/operator/pull/669) ### Thank you, contributors @@ -284,7 +286,7 @@ TBD - [@itsmurugappan](https://github.com/itsmurugappan) - [@izabelacg](https://github.com/izabelacg) - [@julz](https://github.com/julz) -- [@lberk](https://github.com/lberk) +- [@lberk](https://github.com/lberk)) - [@lionelvillard](https://github.com/lionelvillard) - [@markusthoemmes](https://github.com/markusthoemmes) - [@matzew](https://github.com/matzew) @@ -305,7 +307,6 @@ Knative is an open source project that anyone in the [community](https://knative - [Getting started documentation](https://knative.dev/docs/getting-started) - [Samples](https://knative.dev/docs/samples) - [Knative working groups](https://github.com/knative/community/blob/main/working-groups/WORKING-GROUPS.md) -- [Documentation issues](https://github.com/knative/docs/issues) - [Knative User Mailing List](https://groups.google.com/forum/#!forum/knative-users) - [Knative Development Mailing List](https://groups.google.com/forum/#!forum/knative-dev) - Knative on Twitter [@KnativeProject](https://twitter.com/KnativeProject)