pkalsi97 commented on issue #5857:
URL: https://github.com/apache/camel-k/issues/5857#issuecomment-3664629202
@squakez I am thinking of implementing this approach
1. To detect **Cert-Manager** we can use `cert-manager.io/v1` via
`ServerResourcesForGroupVersion()`, return `false` if CRD not found, no error.
2. Extend the **ingress-trait** -> `tlsIssuerName` , `tlsIssuerKind`
3. Automatic cert creation:
- Trigger conditions: TLSHosts set + TLSSecretName empty + TLSIssuerName
provided
- Check cert-manager availability at runtime, only when needed.
- Create `certmanagerv1.Certificate` with Secret name, Labels integration,
References issuer, DNSNames
4. Separate RBAC files for cert-manager resources (Certificates, Issuers,
ClusterIssuers)
```
user sets tls-issuer-name
|
v
ingress trait runs
|
v
cert-manager installed? ---no---> do nothing
|
yes
|
v
create Certificate CR
|
v
cert-manager issues secret
|
v
ingress uses secret for TLS
```
What do you think about this approach ? am I missing something ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
