Merge branch 'main' into blackboxai/route-base-url-to-knative-dev

Author: rohan-019

OWNERS_ALIASES

@@ -2,18 +2,15 @@
 # Do not modify this file, instead modify peribolos/knative.yaml
 
 aliases:
-  client-reviewers:
-  - itsmurugappan
+  client-reviewers: []
   client-wg-leads:
   - dsimansk
   client-writers:
   - dsimansk
-  - vyasgun
   docs-reviewers:
   - nainaz
   - skonto
   docs-writers:
-  - csantanapr
   - skonto
   eventing-reviewers:
   - Leo6Leo
@@ -28,7 +25,6 @@ aliases:
   - aliok
   - cali0707
   - creydr
-  - lionelvillard
   - matzew
   - pierDipi
   func-reviewers:
@@ -37,7 +33,6 @@ aliases:
   func-writers:
   - gauron99
   - jrangelramos
-  - lance
   - lkingland
   - matejvasek
   - matzew
@@ -47,6 +42,7 @@ aliases:
   - salaboy
   knative-admin:
   - aliok
+  - arsenetar
   - cardil
   - dprotaso
   - dsimansk
@@ -58,7 +54,6 @@ aliases:
   - knative-prow-updater-robot
   - knative-test-reporter-robot
   - matzew
-  - nrrso
   - skonto
   - upodroid
   knative-release-leads:
@@ -115,10 +110,10 @@ aliases:
   - skonto
   steering-committee:
   - aliok
+  - arsenetar
   - dprotaso
   - evankanderson
   - matzew
-  - nrrso
   ux-wg-leads:
   - Leo6Leo
   - cali0707

blog/docs/articles/distributed-tracing.md

@@ -1,5 +1,8 @@
 # Distributed tracing with Knative, OpenTelemetry and Jaeger
 
+!!! note
+    Knative Release 1.19 and higher supports emitting OpenTelemetry traces. So the contents of this post are out of date.
+
 **Author: [Ben Moss](https://twitter.com/mossity), Software Engineer @ [VMware](http://vmware.com)**
 
 When trying to understand and diagnose our systems, one of the most basic tools

blog/docs/articles/orchestrating-cloud-events-with.md

@@ -1,6 +1,6 @@
 # Orchestrating CloudEvents with Knative and Zeebe
 
-**Author: [Mauricio Salatino (Salaboy)](https://twitter.com/salaboy), Principal Software Engineer @ [Camunda](http://camunda.com) and [LearnK8s](http://learnk8s.io) Instructor**
+**Author: [Mauricio Salatino (Salaboy)](https://twitter.com/salaboy), Principal Software Engineer @ [Camunda](http://camunda.com) and [LearnKube](http://learnkube.com) Instructor**
 
 A couple of weeks ago, I presented at the **Knative Meetup** ([Video](https://www.youtube.com/watch?v=msDDdqmyEFA&list=PLQjzPfIiEQLIEpoCPxBYAVrjqy6LxLtQ8), [Slides](https://www.slideshare.net/salaboy/orchestrating-cloud-events-knative-meetup-2020)) about how you can leverage the Cloud Native workflow engine [Zeebe](http://zeebe.io) to understand, enhance and orchestrate your applications that are already using [CloudEvents](https://cloudevents.io).
 

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

@@ -10,6 +10,9 @@ type: "blog"
 
 ## Announcing Knative v1.19 Release
 
+!!! note
+    We've discovered severe issues with the OpenTelemetry Prometheus Exporter (see: https://github.com/knative/pkg/issues/3224). We advise users to hold off upgrading until we have new patch releases out.
+
 A new version of Knative is now available across multiple components.
 
 Follow the instructions in

config/nav.yml

@@ -157,7 +157,6 @@ nav:
       # Serving - admin docs
       - Administrator Topics:
         - Kubernetes services: serving/knative-kubernetes-services.md
-        - Accessing request traces: serving/accessing-traces.md
         - Enabling requests to Knative services when additional authorization policies are enabled: serving/istio-authorization.md
         - Exclude namespaces from the Knative webhook: serving/webhook-customizations.md
         - Configuring high-availability components: serving/config-ha.md
@@ -184,6 +183,7 @@ nav:
         - Security-Guard example alerts: serving/app-security/security-guard-example-alerts.md
       # Serving - observability
       - Observability:
+        - Request traces: serving/observability/accessing-traces.md
         - Collecting logs: serving/observability/logging/collecting-logs.md
         - Configuring logging: serving/observability/logging/config-logging.md
         - Configuring Request logging: serving/observability/logging/request-logging.md
@@ -303,7 +303,7 @@ nav:
           - Configure KEDA Autoscaling of Knative Kafka Resources: eventing/configuration/keda-configuration.md
       # Eventing - observability
       - Observability:
-        - Accessing CloudEvent traces: eventing/accessing-traces.md
+        - Accessing CloudEvent traces: eventing/observability/accessing-traces.md
         - Collecting logs: eventing/observability/logging/collecting-logs.md
         - Configuring logging: eventing/observability/logging/config-logging.md
         - Collecting metrics: eventing/observability/metrics/collecting-metrics.md

docs/eventing/accessing-traces.md renamed to docs/eventing/observability/accessing-traces.md

@@ -8,22 +8,25 @@ function: how-to
 
 # Accessing CloudEvent traces
 
-Depending on the request tracing tool that you have installed on your Knative
-Eventing cluster, see the corresponding section for details about how to
-visualize and trace your requests.
+Traces give us the big picture of how events traverse through the system and applications.
+Knative Eventing is instrumented with [OpenTelemetry](https://opentelemetry.io/docs/what-is-opentelemetry/) which can emit traces to a multitude of different backends.
 
-## Before you begin
+## Backends
 
-You must have a Knative cluster running with the Eventing component installed. [Learn more](../install/README.md).
+### Jaeger V2
 
-## Configuring tracing
+Following [these instructions](https://github.com/jaegertracing/jaeger-operator?tab=readme-ov-file#jaeger-v2-operator) to setup Jaeger V2 on Kubernetes and access your traces.
+
+## Configuring Eventing Tracing
+
+You can update the configuration for tracing in using the [`config-observability` ConfigMap](https://github.com/knative/eventing/blob/main/config/core/configmaps/observability.yaml).
 
 With the exception of importers, the Knative Eventing tracing is configured through the
-`config-tracing` ConfigMap in the `knative-eventing` namespace.
+`config-observability` ConfigMap in the `knative-eventing` namespace.
 
 Most importers do _not_ use the ConfigMap and instead, use a static 1% sampling rate.
 
-You can use the `config-tracing` ConfigMap to configure the following Eventing components:
+You can use the `config-observability` ConfigMap to configure the following Eventing components:
 
  - Brokers
  - Triggers
@@ -36,59 +39,61 @@ You can use the `config-tracing` ConfigMap to configure the following Eventing c
 
 **Example:**
 
-The following example `config-tracing` ConfigMap samples 10% of all CloudEvents:
+The following example `config-observability` ConfigMap samples 10% of all CloudEvents:
 
 ```yaml
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: config-tracing
+  name: config-observability
   namespace: knative-eventing
 data:
-  backend: "zipkin"
-  zipkin-endpoint: "http://zipkin.istio-system.svc.cluster.local:9411/api/v2/spans"
-  sample-rate: "0.1"
+  tracing-protocol: "grpc"
+  tracing-endpoint: "http://jaeger-collector.observability:4318/v1/traces"
+  tracing-sampling-rate: "0.1"
 ```
 
 ### Configuration options
 
-You can configure your `config-tracing` with following options:
+You can configure your `config-observability` with following options:
 
- * `backend`: Valid values are `zipkin` or `none`. The default is `none`.
+ * `tracing-protocol`: Valid values are `grpc` or `http/protobuf`. The default is `none`.
 
- * `zipkin-endpoint`: Specifies the URL to the zipkin collector where you want to send the traces.
-   Must be set if backend is set to `zipkin`.
+ * `tracing-endpoint`: Specifies the URL to the backend where you want to send the traces.
+   Must be set if backend is set to `grpc` or `http/protobuf`.
 
- * `sample-rate`: Specifies the sampling rate. Valid values are decimals from `0` to `1`
+ * `tracing-sampling-rate`: Specifies the sampling rate. Valid values are decimals from `0` to `1`
    (interpreted as a float64), which indicate the probability that any given request is sampled.
    An example value is `0.5`, which gives each request a 50% sampling probablity.
 
- * `debug`: Enables debugging. Valid values are `true` or `false`. Defaults to `false` when not specified.
-   Set to `true` to enable debug mode, which forces the `sample-rate` to `1.0` and sends all spans to
-   the server.
-
-### Viewing your `config-tracing` ConfigMap
+### Viewing your `config-observability` ConfigMap
 
 To view your current configuration:
 
 ```bash
-kubectl -n knative-eventing get configmap config-tracing -oyaml
+kubectl -n knative-eventing get configmap config-observability -oyaml
 ```
 
-### Editing and deploying your `config-tracing` ConfigMap
+### Editing and deploying your `config-observability` ConfigMap
 
 To edit and then immediately deploy changes to your ConfigMap, run the following command:
 
 ```bash
-kubectl -n knative-eventing edit configmap config-tracing
+kubectl -n knative-eventing edit configmap config-observability
 ```
 
-## Accessing traces in Eventing
 
-To access the traces, you use either the Zipkin or Jaeger tool. Details about using these tools to access traces are provided in the Knative Serving observability section:
+<!--
+TODO - Renable and redo the images when the following test is enabled again
+       https://github.com/knative/eventing/blob/main/test/conformance/broker_tracing_test.go#L31
+
+	t.Skip("needs to be reworked for OTel (eventing#8637)")
 
- - [Zipkin](../serving/accessing-traces.md#zipkin)
- - [Jaeger](../serving/accessing-traces.md#jaeger)
+## Accessing traces 
+
+To access the traces, you use either the Zipkin or Jaeger tool.
+
+ - [Zipkin](../serving/observability/accessing-traces.md)
 
 ### Example
 
@@ -132,3 +137,5 @@ This is the same screenshot without the annotations.
 ![Raw Trace](images/RawTrace.png)
 
 If you are interested, here is the [raw JSON](data/2e571e6948ff981283825bb2bf51c87d.json) of the trace.
+
+-->

docs/install/uninstall.md

@@ -33,20 +33,6 @@ Uninstall any Serving extensions you have installed by performing the steps in t
     kubectl delete -f {{ artifact( repo="serving", file="serving-hpa.yaml") }}
     ```
 
-
-
-=== "TLS with cert-manager"
-
-    1. Uninstall the component that integrates Knative with cert-manager:
-
-        ```bash
-        kubectl delete -f {{ artifact( repo="net-certmanager", file="release.yaml") }}
-        ```
-
-    1. Optional: if you no longer need cert-manager, uninstall it by following the steps in the
-    [cert-manager documentation](https://cert-manager.io/docs/installation/uninstall/kubernetes/).
-
-
 ### Uninstalling a networking layer
 
 Follow the relevant procedure to uninstall the networking layer you installed:

docs/serving/accessing-traces.md

@@ -44,7 +44,6 @@ that are active when running Knative Serving.
      activator                    1         1         1            1           1h
      autoscaler                   1         1         1            1           1h
      controller                   1         1         1            1           1h
-     net-certmanager-controller   1         1         1            1           1h
      net-istio-controller         1         1         1            1           1h
      webhook                      1         1         1            1           1h
      ```
@@ -78,10 +77,6 @@ The webhook intercepts all Kubernetes API calls as well as all CRD insertions
 and updates. It sets default values, rejects inconsistent and invalid objects,
 and validates and mutates Kubernetes API calls.
 
-### Deployment: net-certmanager-controller
-
-The certmanager reconciles cluster ingresses into cert manager objects.
-
 ### Deployment: net-istio-controller
 
 The net-istio-controller deployment reconciles a cluster's ingress into an