Adding support for creating secrets using certmanager

[Nierhoff]

Hi,

A PR, which is a proposal that might require a bit of discussion and corrections.

I suggest to support that cert-manager create the secrets for deploy.ssl.endpointSecretName and transportSecretName.

A configuation could look like this

deploy:
  ssl:
    endpointSecretName: "test-certificate"
    transportSecretName: ""
    certmanager:
      enabled: true
      endpoint:
        enabled: true
        commonName: 'example-infinispan'
      transport:
        enabled: false

This will create the secret "test-certificate" by use of cert-manager, this example will not create a secret for transport.

[Nierhoff]

Du you have any feedback on this PR ?

[rigazilla]

From a user POV I like this feature, from the design POV I guess the point is that it introduces dependencies with external component and we may not want to add this kind of complexity.

If we decide to add this feature, I would like to have only the enabled flags in the values.yaml, something like:

• commonName be computed in certificate.yaml
• all the remaining values set to default in certificate.yaml

this to keep values.yaml clean from external spec