Issue 1: Verify output for Kafka Topic
Actual Behavior
$ k -n kafka get kafkatopics.kafka.strimzi.io
NAME CLUSTER PARTITIONS REPLICATION FACTOR
knative-demo-topic my-cluster 3 1
Expected Behavior
$ kubectl -n kafka get kafkatopics.kafka.strimzi.io
NAME AGE
knative-demo-topic 16s
Issue 2: Ensure Apache Kafka Event Source started with the necessary configuration
Actual Behavior
The label selector has changed from knative-eventing-source-name=kafka-source to eventing.knative.dev/SourceName=kafka-source
Expected Behavior
$ kubectl logs --selector='knative-eventing-source-name=kafka-source'
{"level":"info","ts":"2020-05-28T10:39:42.104Z","caller":"adapter/adapter.go:81","msg":"Starting with config: ","Topics":".","ConsumerGroup":"...","SinkURI":"...","Name":".","Namespace":"."}
Issue 3: The purpose of the sample
Actual Behavior
The example is about deploying a Kafka Source and configuring it.
Expected Behavior
Building a Kafka source from source code. I might have misunderstood the purpose, but this is was my expectation going through the sample.
Issue 4: Change log settings for the Kafka source
Actual Behavior
There were no new logs.
A message has to be resent to generate debug level logs. It might make sense to move the log configuring step above sending the message so its not as confusing.
Expected Behavior
Modify the log settings kubectl -n knative-sources edit cm/config-logging to debug
Deleting the Kafka Source deployment and re-fetching logs would have debug messages
Steps to Reproduce the Problem
- Follow guide here
Other considerations
This may be out of scope for the sample but it wasn't obvious what the implications of a namespace are on resources. I created the topic in a temp namespace kafka-ex and not where kafka was installed. Everything seemed to work fine, except when sending the message to the topic, I had to deploy the pod in the kafka namespace for things to work. So, should one never create a topic in another namespace than where Kafka is installed ?
Install information:
- Platform (GKE, IKS, AKS, etc.): GKE
- Knative Version: 0.19
Issue 1: Verify output for Kafka Topic
Actual Behavior
Expected Behavior
Issue 2: Ensure Apache Kafka Event Source started with the necessary configuration
Actual Behavior
The label selector has changed from
knative-eventing-source-name=kafka-sourcetoeventing.knative.dev/SourceName=kafka-sourceExpected Behavior
Issue 3: The purpose of the sample
Actual Behavior
The example is about deploying a Kafka Source and configuring it.
Expected Behavior
Building a Kafka source from source code. I might have misunderstood the purpose, but this is was my expectation going through the sample.
Issue 4: Change log settings for the Kafka source
Actual Behavior
There were no new logs.
A message has to be resent to generate debug level logs. It might make sense to move the log configuring step above sending the message so its not as confusing.
Expected Behavior
Modify the log settings
kubectl -n knative-sources edit cm/config-loggingtodebugDeleting the Kafka Source deployment and re-fetching logs would have
debugmessagesSteps to Reproduce the Problem
Other considerations
This may be out of scope for the sample but it wasn't obvious what the implications of a namespace are on resources. I created the topic in a temp namespace
kafka-exand not where kafka was installed. Everything seemed to work fine, except when sending the message to the topic, I had to deploy the pod in thekafkanamespace for things to work. So, should one never create a topic in another namespace than where Kafka is installed ?Install information: