-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
scope/k8sK8s or helm stuff (really annoying)K8s or helm stuff (really annoying)status/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedtype/enhancementEn enhancement to an already existing featureEn enhancement to an already existing feature
Milestone
Description
Describe the bug
If we enable SSL in kafka-ui backend, and deploy into k8s using the helm chart, the deployment creates the livenessProbe and readinessProbe configuration with the default value of HTTP.
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes
In the current Deployment.yaml there is not way to specify the scheme field for probes
Set up
Steps to Reproduce
Steps to reproduce the behavior:
- Enable SSL in Kafka-ui. (SERVER_SSL_ENABLED=true, SERVER_SSL_KEY_STORE='myserver.keystore', SERVER_SSL_KEY_STORE_PASSWORD='mypassword'
- Deploy the application in kubernetes using the helm chart.
- Kubernetes restart the pods, since there is not valid certificate for that operation.
Expected behavior
Make able to configure the deployment telling to kubernetes to skipping the certificate verification.
Metadata
Metadata
Assignees
Labels
scope/k8sK8s or helm stuff (really annoying)K8s or helm stuff (really annoying)status/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedtype/enhancementEn enhancement to an already existing featureEn enhancement to an already existing feature