ECK operator on OpenShift does not take the created self-signed certificate after updating Elasticsearch instance yaml file

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

I have created a self-signed cert on our side, created the secret form the certs and added under spec: http: tls: certificate, but operator does not update the pod, so that elastic pod runs its own cert. Could you please help?

spec:
monitoring:
logs: {}
metrics: {}
http:
service:
metadata: {}
spec: {}
tls:
certificate:
secretName: Elasticsearch-instance1-es-http-cert

2

The operator should update the secret content with your certificate, and Elasticsearch is able to hot-reload the certificate files if they change. Pods don't need to be recreated/updated.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.