Elastic operator TLS self-signed certificates


Using ECK we have set up a cluster with a self-signed certificate.
However the documentation (TLS certificates | Elastic Cloud on Kubernetes [1.5] | Elastic) is not clear how to set/install this certificate in the cluster so it'll be valid for calling clients within the cluster (java, .net, which are failing as they cannot validate the self-signed certificates).

Can you please provide guidance what should be the step for establishing the self-signed certificate as one that can be recognized by clients? For example, should we be validating it in the client code (Encrypted communication | Java REST Client [7.12] | Elastic). Or, must we generate a 'real' certificate to be used for this to work (as specified here: TLS certificates | Elastic Cloud on Kubernetes [1.5] | Elastic)

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