The Google SSL cert is created at the moment the ingress is created. It could take 5+ minutes. Once the SSL is applied, you have to access it from HTTPS, as HTTP would fail. If you used alpha encryption on top of this, I would not even know how that would work, as it would be HTTPS within HTTPS…
When it does work, you chould be able to then access ratel (if you setup ratel in the ingress), e.g. https://ratel.mycompany.com. You could access alpha with curl, e.g.
If these fail then either the ingress setup is not working, dns not working, or ssl/tls is not working. If you like, you can send me helm chart values (redact any secrets) and the managed certificates manifest.
For troubleshooting managed google ssl cert, here’s some pointers. You can check the status of the certficate with this (replacing $MANAGED_CERT_NAME with named you used in metadata.name for ManagedCertificate):
kubectl describe \
It should say
Active for the certificate, under the
Domain Status: >
You can also use
gcloud command to verify as well (replacing DNS_NAME with what you use to access the ingress):
DNS_NAME="<dns-name-of-system>" # if ratel.mycompany.com, then ratel.
gcloud compute ssl-certificates list \
--filter "$DNS_NAME." \
This should show