SOLVED! Public Networking With Couchbase Autonomous Operator Using Kubernetes External DNS
When deploying apps on Kubernetes, you usually use Kubernetes resources like Service and Ingress to expose apps outside the Kubernetes cluster at your desired domain. This involves a lot of manual configuration of both Kubernetes resources and the DNS records at your provider, which can be a time-consuming and error-prone process. To address this, the Kubernetes sig-network team created the External DNS solution to manage external DNS records in an autonomous way from within a Kubernetes cluster.
In this session, we’ll do a deep dive to learn how the Couchbase cluster can be publicly addressable using Couchbase Autonomous Operator with Kubernetes External DNS solution. We’ll show how the External DNS solution helps to dynamically manage the external DNS records from within a Kubernetes cluster.