How to Create an Internal Developer Platform in GKE
Kuberise.io makes it straightforward to set up an internal developer platform on Google Kubernetes Engine (GKE). Here are the key integration points.
GKE Integration Highlights
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 managed through Cloudflare or any other DNS provider.
Traffic Management
Two Nginx Ingress Controllers handle traffic separation: an internal controller for secure microservice communication within the cluster, and an external controller for public-facing services.
Service Account for DNS
A Google Cloud service account with DNS permissions is attached to a Kubernetes service account, allowing ExternalDNS to manage DNS records without injecting cloud credentials into pods.
GitOps Integration
All cluster configurations and deployments are stored and version-controlled in your Git repository, following the GitOps model for reliable and auditable infrastructure management.
For detailed instructions, check out the GKE Deployment Documentation.
Traffic Management with Two Ingress Controllers
How to route internal and external traffic separately using two Nginx Ingress Controllers in Kubernetes.
Kuberise.io: Key Advantages and Core Capabilities
An overview of what makes Kuberise.io a powerful open-source internal developer platform for Kubernetes.