How to Create an Internal Developer Platform in GKE Using Kuberise.io

GKE

🌐 How to Create an Internal Developer Platform in GKE 🌐

I’ve added a new example to the Kuberise.io open-source project to help you quickly and easily set up an internal developer platform on Google Kubernetes Engine (GKE).

Some Integration Points with GKE

1️⃣ Internal and External Domains:

Internal services communicate using a private domain like kuberise.internal, configured automatically in Google Cloud DNS via ExternalDNS.
External services are exposed using a public domain, such as gke.kuberise.dev, managed automatically in Cloudflare via ExternalDNS. (It can be done with any other DNS provider.)

2️⃣ Ingress Controllers for Traffic Management with NGINX and Right Annotations:

The internal ingress controller ensures secure communication between microservices within the cluster using an internal load balancer.
The external ingress controller handles traffic from outside the cluster, leveraging an external load balancer for exposure.

3️⃣ Service Account for DNS Management:

A Google Cloud service account with DNS permissions is created and attached to a Kubernetes service account. This setup allows ExternalDNS to manage the internal domain in Cloud DNS without needing to add Google Cloud credentials directly to Kubernetes or the ExternalDNS pod.

4️⃣ GitOps Integration:

Kuberise.io follows the GitOps model, ensuring your cluster configurations and deployments are stored and version-controlled in your repository.

🚀 Why Choose Kuberise.io?

Kuberise.io is a self-service open-source developer platform built with platform engineering best practices. It simplifies Kubernetes for developers by offering an easy-to-manage GitOps-based platform with pre-configured open-source tools like Ingress-Nginx, Prometheus, Grafana, ExternalDNS, and more.

For detailed instructions, check out Kuberise.io GKE Deployment Documentation