CrashLoopBackOff , ksqldb on k8s

Hello experts.

After deploying confluentinc/cp-ksql-server:latest image to k8s (1.22), running and falling 5 times and got a CrashLoopBackOff state.

Pod logs are:

[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka version: 5.4.6-ccs
[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka commitId: 8d7277002448f44d
[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka startTimeMs: 1642741492510
===> Launching ... 
===> Launching ksql-server ... 
SLF4J: A number (104) of logging calls during the initialization phase have been intercepted and are
SLF4J: now being replayed. These are subject to the filtering rules of the underlying logging system.
SLF4J: See also http://www.slf4j.org/codes.html#replay
Jan 21, 2022 5:05:09 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
WARNING: A provider io.confluent.ksql.rest.server.resources.streaming.StreamedQueryResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.ksql.rest.server.resources.streaming.StreamedQueryResource will be ignored. 
Jan 21, 2022 5:14:58 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
WARNING: A provider io.confluent.ksql.rest.server.resources.HealthCheckResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.ksql.rest.server.resources.HealthCheckResource will be ignored. 

any idea to solve thie issue ?
Thank you.

hey @mogitate.kyogo

nothing else in the logfile?

best
michael

This topic was automatically closed after 30 days. New replies are no longer allowed.