From ace4da92efb39f6b7cdd9308b2cf42abf879bb23 Mon Sep 17 00:00:00 2001 From: Pierangelo Di Pilato Date: Tue, 21 Jan 2025 16:47:35 +0100 Subject: [PATCH] Document KafkaSource v1 API Signed-off-by: Pierangelo Di Pilato --- .../eventing/kafka/binding/event-source.yaml | 2 +- docs/eventing/event-registry/README.md | 2 +- docs/eventing/sinks/job-sink.md | 2 +- docs/eventing/sources/kafka-source/README.md | 14 +++++++------- .../sources/kafka-source/event-source.yaml | 2 +- 5 files changed, 11 insertions(+), 11 deletions(-) diff --git a/code-samples/eventing/kafka/binding/event-source.yaml b/code-samples/eventing/kafka/binding/event-source.yaml index 835275157c6..c2a13701240 100644 --- a/code-samples/eventing/kafka/binding/event-source.yaml +++ b/code-samples/eventing/kafka/binding/event-source.yaml @@ -29,7 +29,7 @@ # KAFKA_TLS_CA_CERT_SECRET_NAME: Name of secret containing server CA cert to use when connecting with TLS (optional) # KAFKA_TLS_CA_CERT_SECRET_KEY: Key within secret containing server CA cert to use when connecting with TLS (optional) -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source diff --git a/docs/eventing/event-registry/README.md b/docs/eventing/event-registry/README.md index 9f6e0170d8e..7206362bda2 100644 --- a/docs/eventing/event-registry/README.md +++ b/docs/eventing/event-registry/README.md @@ -124,7 +124,7 @@ After your event source is instantiated, EventTypes are added to the registry. Given the following KafkaSource sample to populate the registry: ```yaml -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-sample diff --git a/docs/eventing/sinks/job-sink.md b/docs/eventing/sinks/job-sink.md index 6d2623ab027..95fbb2854ca 100644 --- a/docs/eventing/sinks/job-sink.md +++ b/docs/eventing/sinks/job-sink.md @@ -131,7 +131,7 @@ For example, you can trigger a `Job` when a Kafka record is sent to a Kafka topi a [`KafkaSource`](./../sources/kafka-source): ```yaml -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source diff --git a/docs/eventing/sources/kafka-source/README.md b/docs/eventing/sources/kafka-source/README.md index 9fdd2278ca2..fc0c0246c57 100644 --- a/docs/eventing/sources/kafka-source/README.md +++ b/docs/eventing/sources/kafka-source/README.md @@ -133,7 +133,7 @@ If you are using Strimzi: 1. Modify `source/event-source.yaml` accordingly with bootstrap servers, topics, and so on: ```yaml - apiVersion: sources.knative.dev/v1beta1 + apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source @@ -187,7 +187,7 @@ Alternatively, if you are using a GitOps approach, you can add the `consumers` k ```yaml - apiVersion: sources.knative.dev/v1beta1 + apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source @@ -253,7 +253,7 @@ The `KafkaSource` implements the `Delivery` Specificiation, allowing you to conf ```yaml - apiVersion: sources.knative.dev/v1beta1 + apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source @@ -298,7 +298,7 @@ To specify the key deserializer, add the label `kafkasources.sources.knative.dev `KafkaSource` definition, as shown in the following example: ```yaml -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source @@ -323,7 +323,7 @@ By default the `KafkaSource` starts consuming from the latest offset in each par to consume from the earliest offset, set the initialOffset field to `earliest`, for example: ```yaml -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source @@ -368,7 +368,7 @@ KafkaSource expects these files to be in PEM format. If they are in another form 2. Apply the KafkaSource. Modify the `bootstrapServers` and `topics` fields accordingly. ```yaml - apiVersion: sources.knative.dev/v1beta1 + apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source-with-tls @@ -431,7 +431,7 @@ Simple Authentication and Security Layer (SASL) is used by Apache Kafka for auth 1. Create or modify a KafkaSource so that it contains the following spec options: ```yaml - apiVersion: sources.knative.dev/v1beta1 + apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: example-source diff --git a/docs/eventing/sources/kafka-source/event-source.yaml b/docs/eventing/sources/kafka-source/event-source.yaml index 16558473aae..a417b666091 100644 --- a/docs/eventing/sources/kafka-source/event-source.yaml +++ b/docs/eventing/sources/kafka-source/event-source.yaml @@ -30,7 +30,7 @@ # KAFKA_TLS_CA_CERT_SECRET_KEY: Key within secret containing server CA cert to use when connecting with TLS (optional) # KAFKA_INITIAL_OFFSET initial offset for the consumer group, should be one of 'earliest' or 'latest' (optional) -apiVersion: sources.knative.dev/v1beta1 +apiVersion: sources.knative.dev/v1 kind: KafkaSource metadata: name: kafka-source