k8s-config-connector: Can not refer to managed cert in ComputeSSLCertificate
Describe the bug
When creating a ComputeSSLCertificate there is no way to specify a domain-name so that I can get a manage certificate.
It is possible to declare a domain that should get a managed certificate in the REST documentation
"managed": {
"domains": [
string
],
"status": enum,
"domainStatus": {
object
}
},
and go to a shop to buy a domain name SSL certificate is unrealistic 5 years after LetsEncrypt.
ConfigConnector Version
1.9.2
To Reproduce Steps to reproduce the behavior:
YAML snippets:
apiVersion: compute.cnrm.cloud.google.com/v1beta1
kind: ComputeSSLCertificate
metadata:
name: my-domain-cert
spec:
location: global
It would be good to be able to refer to a DNSRecordSet
or a DNSManagedZone
CR.
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 17 (5 by maintainers)
@jcanseco - I am looking to understand where this in the backlog and if you have an ETA? This is actually a blocker for us at the moment, preventing us from full automating our application deployment stack.
Our company would like this as well. Relates to https://github.com/GoogleCloudPlatform/k8s-config-connector/issues/107 It seems like all the moving parts are there (managed certs CRD, and KCC ComputeSslCertificate) but missing some API glue; does that seem like a fair guess @kibbles-n-bytes ?