Merge branch 'knative:main' into upload-blog-post-3

Author: Leo6Leo

.github/workflows/knative-go-test.yaml

@@ -15,3 +15,5 @@ on:
 jobs:
   test:
     uses: knative/actions/.github/workflows/reusable-go-test.yaml@main
+    secrets:
+      CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.gitignore

@@ -20,7 +20,7 @@ hack/__pycache__
 !/blog/overrides/partials/source-file.html
 !/blog/overrides/partials/content.html
 /blog/docs/stylesheets/
-/node_modules/
+node_modules
 venv/
 
 # TODO clean up images copied between blog/ and docs/
@@ -36,4 +36,3 @@ maven-wrapper.jar
 
 # Ignore Python virtual environments
 .venv
-/code-samples/eventing/bookstore-sample-app/db/bookstore-eda/node_modules/*

OWNERS

@@ -9,3 +9,4 @@ approvers:
 reviewers:
 - docs-writers
 - docs-reviewers
+- ux-wg-leads

OWNERS_ALIASES

@@ -52,38 +52,22 @@ aliases:
   - lkingland
   - salaboy
   knative-admin:
-  - Cali0707
-  - Leo6Leo
-  - ReToCode
   - aliok
   - cardil
-  - creydr
   - davidhadas
   - dprotaso
   - dsimansk
   - evankanderson
-  - izabelacg
   - knative-automation
   - knative-prow-releaser-robot
   - knative-prow-robot
   - knative-prow-updater-robot
   - knative-test-reporter-robot
-  - krsna-m
   - nainaz
-  - pierDipi
   - psschwei
   - salaboy
-  - skonto
   - upodroid
-  knative-release-leads:
-  - Cali0707
-  - Leo6Leo
-  - ReToCode
-  - creydr
-  - dsimansk
-  - izabelacg
-  - pierDipi
-  - skonto
+  knative-release-leads: []
   knative-robots:
   - knative-automation
   - knative-prow-releaser-robot
@@ -113,7 +97,6 @@ aliases:
   - upodroid
   productivity-writers:
   - cardil
-  - krsna-m
   - upodroid
   security-wg-leads:
   - davidhadas
@@ -122,6 +105,7 @@ aliases:
   - davidhadas
   - evankanderson
   serving-approvers:
+  - ReToCode
   - skonto
   serving-reviewers:
   - izabelacg
@@ -134,6 +118,7 @@ aliases:
   serving-wg-leads:
   - dprotaso
   serving-writers:
+  - ReToCode
   - dprotaso
   - skonto
   steering-committee:
@@ -145,7 +130,6 @@ aliases:
   - davidhadas
   - dprotaso
   - dsimansk
-  - krsna-m
   - psschwei
   ux-wg-leads:
   - cali0707

blog/config/nav.yml

@@ -15,6 +15,7 @@ nav:
     - Blog:
       - index.md
       - Releases:
+          - releases/announcing-knative-v1-14-release.md
           - releases/announcing-knative-v1-13-release.md
           - releases/announcing-knative-v1-12-release.md
           - releases/announcing-knative-v1-11-release.md
@@ -46,6 +47,7 @@ nav:
           - releases/announcing-knative-v0-3-release.md
           - releases/announcing-knative-v0-2-release.md
       - Articles:
+          - articles/knative-meets-apache-camel.md
           - articles/knative-backstage-plugins.md
           - articles/demystifying-activator-on-path.md
           - articles/knative-eventing-vision.md

blog/docs/articles/knative-meets-apache-camel.md

@@ -0,0 +1,99 @@
+# Event Sourcing with Apache Camel K and Knative Eventing
+
+**Author: Matthias Weßendorf, Senior Principal Software Engineer @ Red Hat**
+
+## Why Apache Camel K?
+
+The [Apache Camel](https://camel.apache.org/){:target="_blank"} is a popular Open Source integration framework that empowers you to quickly and easily integrate various systems consuming or producing data. With [Apache Camel K](https://camel.apache.org/camel-k/latest){:target="_blank"} the project provides a lightweight integration framework built from Apache Camel that runs natively on Kubernetes and is specifically designed for serverless and microservice architectures.
+
+The Camel K framework also supports Knative, allowing developers to [bind](https://camel.apache.org/camel-k/latest/kamelets/kamelets-user.html#kamelets-usage-binding){:target="_blank"} any Kamelet to a Knative component. A Kamelet can act as "source" of data or alternatively as "sink". There are several Kamelets available for integrating and connecting to 3rd party services or products, such as Amazon Web Services (AWS), Google Cloud or even tradition message systems like AMQP 1.0 or JMS brokers like Apache Artemis. The full list of Kamelets can be found in the [documentation](https://camel.apache.org/camel-kamelets/latest/index.html){:target="_blank"}.
+
+## Installation
+
+The [Installation](https://camel.apache.org/camel-k/next/installation/installation.html) from Apache Camel K offers a few choices, such as CLI, Kustomize, OLM or Helm. Example of Helm installation:
+
+```
+$ helm repo add camel-k https://apache.github.io/camel-k/charts/
+$ helm install my-camel-k camel-k/camel-k
+```
+
+Besides Camel K we also need to have Knative Eventing installed, as described in the [documentation](https://knative.dev/docs/install/yaml-install/eventing/install-eventing-with-yaml/){:target="_blank"}.
+
+## Creating a Knative Broker instance
+
+We are using a Knative Broker as the heart of our system, acting as an [Event Mesh](https://knative.dev/docs/eventing/event-mesh/){:target="_blank"} for both event producers and event consumers:
+
+```yaml
+apiVersion: eventing.knative.dev/v1
+kind: Broker
+metadata:
+  namespace: default
+  name: demo-broker
+```
+
+Now event producers can send events to it and event consumers can receive events.
+
+## Using Kamelets as Event Sources
+
+In order to bind a Kamelet to a Knative component, like the above broker, we are using the `Pipe` API. A Pipe allows to declaratively move data from a system described by a Kamelet _towards_ a Knative destination **or** _from_ a Knative destination to another (external) system described by a Kamelet.
+
+Below is a `Pipe` that uses a ready-to-use `Kamelet`, a `timer-source`
+
+```yaml
+apiVersion: camel.apache.org/v1
+kind: Pipe
+metadata:
+  name: timer-source-pipe
+spec:
+  source:
+    ref:
+      kind: Kamelet
+      apiVersion: camel.apache.org/v1
+      name: timer-source
+    properties:
+      message: Hello Knative Eventing!
+  sink:
+    properties:
+      cloudEventsType: com.corp.my.timer.source
+    ref:
+      kind: Broker
+      apiVersion: eventing.knative.dev/v1
+      name: demo-broker
+```
+
+The `timer-source` Kamelet is referenced as the `source` of the `Pipe` and sends periodically (default is `1000ms`) the value of its `message` property to the outbound `sink`. Here we use the Knative Broker, which accepts CloudEvents. The conversion of the message payload to CloudEvents format is done by Apache Camel for us. On the `sink` we can also define the `type` of the CloudEvent to be send.
+
+## Using Kamelets as Event Consumers
+
+In order to consume messages from the Knative broker, using Apache Camel K, we need a different `Pipe` where the above Broker acts as the source of events and a Kamelet is used as sink to receive the CloudEvents: 
+
+```yaml
+apiVersion: camel.apache.org/v1
+kind: Pipe
+metadata:
+  name: log-sink-pipe
+spec:
+  source:
+    ref:
+      kind: Broker
+      apiVersion: eventing.knative.dev/v1
+      name: demo-broker
+    properties:
+      type: com.corp.my.timer.source
+  sink:
+    ref:
+      kind: Kamelet
+      apiVersion: camel.apache.org/v1
+      name: log-sink
+```
+
+The `demo-broker` is referenced as the `source` of the `Pipe` and within the `properties` we define which CloudEvent `type` we are interested in. On a matching CloudEvent, the event is routed to the referenced `sink`. In this example we are using a simple `log-sink` Kamelet, which will just print the received data on its standard out log.
+
+
+!!! note
+
+    In order for the above to work, the Apache Camel K operator will indeed create a Knative `Trigger` from the `Pipe` data, where the `spec.broker` will match our `demo-broker` and the `spec.filter.attributes.types` field will be set to `com.corp.my.timer.source` to ensure only matching CloudEvent types are being forwarded.
+
+## Conclusion
+
+With Apache Camel K the Knative Eventing ecosystem benefits from a huge number of predefined Kamelets for integration with a lot of services and products. Sending events from Google Cloud to AWS is possible. Knative Eventing acts as the heart of the routing, with the Knative Broker and Trigger APIs as the Event Mesh for your Kubernetes cluster!

blog/docs/index.md

@@ -22,16 +22,21 @@ Follow this blog to keep up-to-date with Knative.
 
 ## Featured Posts
 
+### Knative 1.14 is out!
+Details on the 1.14 release of the Knative project.
+
+[Read more :octicons-arrow-right-24:](releases/announcing-knative-v1-14-release.md){ .md-button }
+
+### Knative meets Apache Camel K!
+Event Sourcing with Apache Camel K and Knative Eventing.
+
+[Read more :octicons-arrow-right-24:](articles/knative-meets-apache-camel.md){ .md-button }
+
 ### Knative Completes Third-Party Security Audit
 A third-party audit by Ada Logics found a small number of issues, including [one CVE](https://github.com/knative/serving/security/advisories/GHSA-qmvj-4qr9-v547).
 
 [Read more :octicons-arrow-right-24:](events/security-audit-2023.md){ .md-button }
 
-### Knative 1.13 is out!
-Details on the 1.13 release of the Knative project.
-
-[Read more :octicons-arrow-right-24:](releases/announcing-knative-v1-13-release.md){ .md-button }
-
 ### Knative at KubeCon + CloudNativeCon Europe 2023
 
 We are looking forward to seeing you all there.

blog/docs/releases/announcing-knative-v1-14-release.md

@@ -0,0 +1,111 @@
+---
+title: "v1.14 release"
+linkTitle: "v1.14 release"
+author: "[Izabela Gomes (Broadcom)](https://github.com/izabelacg), [David Simansky (Red Hat)](https://github.com/dsimansk), [Calum Murray (Red Hat)](https://github.com/Cali0707), [Christoph Stäbler (Red Hat)](https://github.com/creydr)"
+author handle: https://github.com/izabelacg https://github.com/dsimansk https://github.com/Cali0707 https://github.com/creydr
+
+date: 2024-5-3
+description: "Knative v1.14 release announcement"
+type: "blog"
+---
+
+# Announcing Knative 1.14 Release
+
+A new version of Knative is now available across multiple components. Follow the instructions in [Installing Knative](https://knative.dev/docs/install/) to install the components you require.
+
+This release brings a number of smaller improvements to the core Knative Serving and Eventing components, and several improvements to specific plugins.
+
+## Table of Contents
+- [Serving](#serving)
+- [Eventing](#eventing)
+- [kn CLI](#kn-cli)
+- [Functions](#functions)
+- [Knative Operator](#knative-operator)
+
+### Serving
+**Release Notes:** [Knative Serving 1.14](https://github.com/knative/serving/releases/tag/knative-v1.14.0)
+
+#### 💫 New Features & Changes
+- A new feature (`multi-container-probing`) is introduced to enable liveness and readiness probes for Knative Services with multiple containers ([#14853](https://github.com/knative/serving/pull/14853), @ReToCode)
+- Add support for multiple wildcard certificate domains in domain config ([#14543](https://github.com/knative/serving/pull/14543), @arsenetar)
+- Certificate generation errors are bubbled up to its parent Route. ([#14962](https://github.com/knative/serving/pull/14543), @ckcd)
+- Check all container's status when calculating revision ContainerHealthy condition ([#14744](https://github.com/knative/serving/pull/14744), @seongpyoHong)
+- Serving now supports the experimental feature `cluster-local-domain-tls` and creates the necessary `KnativeCertificates` ([#14610](https://github.com/knative/serving/pull/14610), @ReToCode)
+- The autoscaler now keeps the desiredScale of a PodAutoscaler at its current value while it initializes and therefore has not yet metrics ([#14866](https://github.com/knative/serving/pull/14866), @SaschaSchwarze0)
+- Don't drop traffic when upgrading a deployment fails ([#14795](https://github.com/knative/serving/pull/14795), @dprotaso)
+- Add upstream TLS trust from CM bundles ([#14717](https://github.com/knative/serving/pull/14717), @ReToCode)
+- Make route domain error specific ([#15082](https://github.com/knative/serving/pull/15082), @skonto)
+
+### Eventing
+**Release Notes:** [Knative Eventing 1.14](https://github.com/knative/eventing/releases/tag/knative-v1.14.0)
+
+#### 💫 New Features & Changes
+- EventType Autocreate is now a non blocking operation ([#7709](https://github.com/knative/eventing/pull/7709), @Cali0707)
+- EventTypes are now autocreated on Triggers and Subscriptions when there is a reply event sent to them ([#7733](https://github.com/knative/eventing/pull/7733), @Cali0707)
+- Added the ability to configure a `nodeSelector` when deploying an ApiServerSource ([#7584](https://github.com/knative/eventing/pull/7584), @sadath-12)
+- Replace YAML merge tags, to comply with YAML 1.2 ([#7662](https://github.com/knative/eventing/pull/7662), @converge)
+- StatefulSet scheduling now makes fewer API server requests, reducing APIServer load. ([#7651](https://github.com/knative/eventing/pull/7651), @Cali0707)
+
+#### 🐞 Bug Fixes
+- Reduce the scope for the Config validation webhook to only the `knative-eventing` namespace. ([#7792](https://github.com/knative/eventing/pull/7792), @pierDipi)
+
+### Client
+**Release Notes:** [Knative Client 1.14](https://github.com/knative/client/releases/tag/knative-v1.14.0)
+
+#### 💫 New Features & Changes
+- Add completion support for fish and PowerShell shells ([#1929](https://github.com/knative/client/pull/1929), @tuhtah)
+
+#### 🐞 Bug Fixes
+
+- Fix client-pkg import paths ([#1931](https://github.com/knative/client/pull/1931), @dsimansk)
+- Fix wait-loop in domain E2E test ([#1919](https://github.com/knative/client/pull/1919), @dsimansk)
+
+### Functions
+**Release Notes:** [Knative func 1.14](https://github.com/knative/func/releases/tag/knative-v1.14.0)
+
+#### 💫 New Features & Changes
+
+- Functions built with the experimental "Host" builder include FUNC_CREATED and FUNC_VERSION metadata environment variables. ([#2195](https://github.com/knative/func/pull/2195), @lkingland)
+
+#### 🐞 Bug Fixes
+
+- Func invoke now correctly handles data with contenttype application/json ([#2256](https://github.com/knative/func/pull/2256), @Cali0707)
+- Fix: "no main packages to build" on darwin/aarch64 ([#2148](https://github.com/knative/func/pull/2148), @matejvasek)
+- Func deploy --username=func --*** get password registry.example.com) ([#2242](https://github.com/knative/func/pull/2242), @lkingland)
+- The prototype host builder now supports nonregular files such as symlinks ([#2156](https://github.com/knative/func/pull/2195), @lkingland)
+- Fix typo in run cmd ([#2168](https://github.com/knative/func/pull/2168), @Sanket-0510)
+- Update docs ([#2169](https://github.com/knative/func/pull/2169), @matzew)
+- Bump go-func to v0.20.0 ([#2170](https://github.com/knative/func/pull/2170), @matzew)
+- Remove discontinued tanzu builder image ([#2178](https://github.com/knative/func/pull/2178), @matzew)
+- Using upstream lifecycle image that has multi-arch support ([#2196](https://github.com/knative/func/pull/2196), @matzew)
+- Fix make was not called ([#2245](https://github.com/knative/func/pull/2245), @matzew)
+- Usage of only proper handler API, no longer need for redundant Context ([#2249](https://github.com/knative/func/pull/2249), @matzew)
+
+
+### Operator
+**Release Notes:** [Knative Operator 1.14](https://github.com/knative/operator/releases/tag/knative-v1.14.0)
+
+Only dependency update
+
+## Thank you, contributors
+**Release Leads:**
+
+- [@izabelacg](https://github.com/izabelacg)
+
+- [@dsimansk](https://github.com/dsimansk)
+
+- [@Cali0707](https://github.com/Cali0707)
+
+- [@creydr](https://github.com/creydr)
+
+## Learn more
+- [Knative docs](https://knative.dev/docs/)
+- [Quickstart tutorial](https://knative.dev/docs/getting-started/)
+- [Samples](https://knative.dev/docs/samples/)
+- [Knative Working Groups](https://knative.dev/community/contributing/working-groups/)
+- [Knative User Mailing List](https://groups.google.com/g/knative-users)
+- [Knative Development Mailing List](https://groups.google.com/g/knative-dev)
+- [Knative on Twitter @KnativeProject](https://twitter.com/KnativeProject)
+- [Knative on StackOverflow](https://stackoverflow.com/questions/tagged/knative)
+- [#knative on CNCF Slack](https://slack.knative.dev/)
+- [Knative on YouTube](https://www.youtube.com/c/KnativeProject)