cp-helm-charts
cp-helm-charts copied to clipboard
/var/lib/kafka/data writable] FAILED
Rancher: 2.5 Kuberentes : 1.19.15 helm 3.7
Configrue the values.yaml with our storageclass and persistance enable and later tried disable i both cases I get
When I execute helm install confluentinc/cp-helm-charts --generate-name --version 0.6.1 --values values.yaml
I see all my pods in
cp-helm-charts-1638227758-cp-control-center-6c86f7bcd-sp676 0/1 CrashLoopBackOff 5 9m23s cp-helm-charts-1638227758-cp-kafka-0 1/2 CrashLoopBackOff 6 9m22s cp-helm-charts-1638227758-cp-kafka-1 1/2 CrashLoopBackOff 6 9m20s cp-helm-charts-1638227758-cp-kafka-2 1/2 CrashLoopBackOff 6 9m18s cp-helm-charts-1638227758-cp-kafka-connect-5fc589f9b4-qz9p2 1/2 CrashLoopBackOff 5 9m23s cp-helm-charts-1638227758-cp-kafka-rest-7b598b7c5-nhp4k 1/2 CrashLoopBackOff 6 9m23s cp-helm-charts-1638227758-cp-ksql-server-75c4bc58d8-tdl45 1/2 CrashLoopBackOff 4 9m23s cp-helm-charts-1638227758-cp-schema-registry-7bff9ccb56-tm2sh 1/2 CrashLoopBackOff 6 9m23s cp-helm-charts-1638227758-cp-zookeeper-0 1/2 CrashLoopBackOff 6 9m22s cp-helm-charts-1638227758-cp-zookeeper-1 1/2 CrashLoopBackOff 6 9m21s cp-helm-charts-1638227758-cp-zookeeper-2 1/2 CrashLoopBackOff 6 9m18s
k logs cp-helm-charts-1638227758-cp-kafka-0 -c cp-kafka-broker
- export KAFKA_BROKER_ID=0
- KAFKA_BROKER_ID=0
- export KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://cp-helm-charts-1638227758-cp-kafka-0.cp-helm-charts-1638227758-cp-kafka-headless.kafka-demo:9092,EXTERNAL://10.206.128.246:31090
- KAFKA_ADVERTISED_LISTENERS=PLAINTEXT://cp-helm-charts-1638227758-cp-kafka-0.cp-helm-charts-1638227758-cp-kafka-headless.kafka-demo:9092,EXTERNAL://10.206.128.246:31090
- exec /etc/confluent/docker/run ===> User uid=0(root) gid=0(root) groups=0(root),1(bin) ===> Configuring ... ===> Running preflight checks ... ===> Check if /var/lib/kafka/data is writable ... Command [/usr/local/bin/dub path /var/lib/kafka/data writable] FAILED !
zookeeper
/var/lib/zookeeper/data/myid] FAILED !
figure the issue, please close the request.
It had to do with securityContext: runAsUser: 0
We don't have root access so after setting it to
securityContext: runAsUser: 1000
we are good