confluentinc / confluentinc/confluent-kubernetes-examples
kafka not able to connect to zookeeper
- Dominant language
- Shell
- Stars
- 72
- Forks
- 201
- Avg merge
- 10h 2m
- Merged PRs (30d)
- 2
Description
When this command executed:
kubectl apply -f https://raw.githubusercontent.com/confluentinc/confluent-kubernetes-examples/master/quickstart-deploy/confluent-platform.yaml
Confluent operator log:
{"level":"ERROR","time":"2023-04-28T21:01:11.301Z","name":"kafka","caller":"log/log.go:35","msg":"apply failed","name":"kafka","namespace":"mnk","error":"no zk endpoint or service discovery configuration found for dependency"}
Logs from 4/28/2023, 1:57:35 AM
So kafka installation do not start and other components as well waiting for kafka.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the referenced confluent-platform.yaml manifest and the Confluent operator log message about the missing ZooKeeper endpoint or service discovery configuration. Trace how Kafka's dependency is configured and verify the deployment with kubectl; done means Kafka starts successfully and dependent components no longer wait for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100