3 years ago

Category: Kubernetes

So you have all your load running in a state-of-the-art Kubernetes cluster, and everything is running smoother than ever. That is true at some level: If everything was configured correctly, there can be no external access to the cluster resources.

In this method, the CA provides you with a unique text key to store in your domain, and then tries to access your domain and read that key to verify ownership.

We will assume that you use AWS Route 53 as your DNS provider and demonstrate how to provide permissions for the certificate issuer to access it.

Wait a few minutes for cert-manager to issue your certificate, and then check the status again: Finally, your certificate is ready, and you can access your service through the host URL you provided and get routed to your Kubernetes endpoint securely.