Liveness / readiness for our components about cp-helm-charts HOT 7 CLOSED

you were added in that slack channel

from cp-helm-charts.

Even if you are not going to include probes by default - they might be optional.
At least let's collect all the ideas and best practices somewhere so people can for example vote for them.
For KSQL I've tried this but nothing actually worked since rest api turned off when queries file specified and ksql-print-metrics script is present in cp-ksql-server image but looks like some .jars are missing...
For Connect I use the following probe:

livenessProbe:
  exec:
    command:
      - bash
      - -c
      - curl -v --silent http://localhost:8083/connectors/PUT_CONNECTOR_NAME_HERE/status 2>&1 | grep \"RUNNING.*RUNNING\" 1>/dev/null

from cp-helm-charts.

@qshao-pivotal Interested in this discussion too, can you add me to slack discussion?
How does cp-helm-chart handle graceful-shutdown (controlled.shutdown.enable=true). Are there plans to use probes?

from cp-helm-charts.

We have it before, but after discussion with Confluent Cloud Team and doing some performance test, We decided to remove it. We may add it back once we figure out more reasonable parameter values.

from cp-helm-charts.

can give me a pointer to the discussions ?

from cp-helm-charts.

Haven't head anything. closing it.

from cp-helm-charts.

Would like to get added to this slack channel also.. i think re-adding probes needs to be given some high priority, and willing to contribute to this effort, I would like to open a new issue to track this.

from cp-helm-charts.