💫 updates to reflect the v1beta shape of the KafkaSource (#2625)

Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
This commit is contained in:
Matthias Wessendorf 2020-07-02 20:13:41 +02:00 committed by GitHub
parent 92d46707fb
commit 88a3f2382d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 15 additions and 13 deletions

View File

@ -241,15 +241,17 @@ the next topic: How do we actually populate the registry in the first place?
like.
```yaml
apiVersion: sources.eventing.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-sample
namespace: default
spec:
consumerGroup: knative-group
bootstrapServers: my-cluster-kafka-bootstrap.kafka:9092
topics: knative-demo,news
bootstrapServers:
- my-cluster-kafka-bootstrap.kafka:9092
topics:
- knative-demo
- news
sink:
apiVersion: eventing.knative.dev/v1
kind: Broker

View File

@ -81,7 +81,7 @@ via Kafka Source
etc...:
```yaml
apiVersion: sources.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source
@ -120,7 +120,7 @@ Create the KafkaBinding that will inject kafka bootstrap information into select
1. Modify `kafka-binding.yaml` accordingly with bootstrap servers etc...:
```yaml
apiVersion: bindings.knative.dev/v1alpha1
apiVersion: bindings.knative.dev/v1beta1
kind: KafkaBinding
metadata:
name: kafka-binding-test
@ -232,7 +232,7 @@ These files are expected to be in pem format, if it is in other format like jks
2. Apply the kafkabinding-tls.yaml, change bootstrapServers accordingly.
```yaml
apiVersion: sources.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaBinding
metadata:
name: kafka-source-with-tls

View File

@ -28,7 +28,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/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaBinding
metadata:
name: kafka-binding

View File

@ -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/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source

View File

@ -95,7 +95,7 @@ Tutorial on how to build and deploy a `KafkaSource` [Eventing source](../../../s
etc...:
```yaml
apiVersion: sources.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source
@ -254,7 +254,7 @@ You can specify the key deserializer among four types:
To specify it, add the label `kafkasources.sources.knative.dev/key-type` to the `KafkaSource` definition like:
```yaml
apiVersion: sources.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source
@ -296,7 +296,7 @@ KafkaSource expects these files to be in pem format, if it is in other format li
2. Apply the KafkaSource, change bootstrapServers and topics accordingly.
```yaml
apiVersion: sources.knative.dev/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source-with-tls

View File

@ -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/v1alpha1
apiVersion: sources.knative.dev/v1beta1
kind: KafkaSource
metadata:
name: kafka-source