[che-dev] Using of cluster default TLS certificate for Che ingresses

[Mykola Morhun <mmorhun@xxxxxxxxxx>]

Hello.

In terms of the issue [1], Deploy team is going to slightly change the behaviour of `spec.k8s.tlsSecretName` property of Che custom resource.




Current behaviour:

 - if field is set, then operator checks if the secret exists and use it, otherwise creates it with the provided name.

 - if the field isn't set, then operator uses the default value `che-tls` and sets this value back to the CR.




New behaviour:

 - if field isn't set, then the default ingress controller certificate will be used.





We changed the default value of the property in Che CR from empty to `che-tls` to not to affect current behaviour. Here is proposed changes on Che operator side [2]. If someone has concerns, please let us know.




[1] https://github.com/eclipse/che/issues/18079

[2] https://github.com/eclipse/che-operator/pull/508

--

Mykola Morhun

Software engineer

Red Hat