Skip to content

StackSimplify

GCP Google Kubernetes Engine GKE Ingress Basics

GCP Google Kubernetes Engine GKE Ingress Basics

Step-00: Pre-requisites¶

Verify if GKE Cluster is created

Verify if kubeconfig for kubectl is configured in your local terminal

# Configure kubeconfig for kubectl
gcloud container clusters get-credentials <CLUSTER-NAME> --region <REGION> --project <PROJECT>

# Replace Values CLUSTER-NAME, ZONE, PROJECT
gcloud container clusters get-credentials standard-cluster-private-1 --region us-central1 --project kdaida123

Step-01: Introduction¶

Learn Ingress Basics
Ingress Diagram Reference

Step-02: Verify HTTP Load Balancing enabled for your GKE Cluster¶

Go to Kubernetes Engine -> standard-cluster-private1 -> DETAILS tab -> Networking
Verify HTTP Load Balancing: Enabled

Step-03: Kubernetes Deployment: 01-Nginx-App3-Deployment-and-NodePortService.yaml¶

apiVersion: apps/v1
kind: Deployment
metadata:
  name: app3-nginx-deployment
  labels:
    app: app3-nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app: app3-nginx
  template:
    metadata:
      labels:
        app: app3-nginx
    spec:
      containers:
        - name: app3-nginx
          image: stacksimplify/kubenginx:1.0.0
          ports:
            - containerPort: 80

Step-04: Kubernetes NodePort Service: 01-Nginx-App3-Deployment-and-NodePortService.yaml¶

apiVersion: v1
kind: Service
metadata:
  name: app3-nginx-nodeport-service
  labels:
    app: app3-nginx
  annotations:
spec:
  type: NodePort
  selector:
    app: app3-nginx
  ports:
    - port: 80
      targetPort: 80

Step-05: 02-ingress-basic.yaml¶

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-basics
  annotations:
    # If the class annotation is not specified it defaults to "gce".
    # gce: external load balancer
    # gce-internal: internal load balancer
    kubernetes.io/ingress.class: "gce"  
spec:
  defaultBackend:
    service:
      name: app3-nginx-nodeport-service
      port:
        number: 80

Step-06: Deploy kube-manifests and Verify¶

# Deploy kube-manifests
kubectl apply -f kube-manifests/

# List Deployments
kubectl get deploy

# List Pods
kubectl get pods

# List Services
kubectl get svc

# List Ingress
kubectl get ingress
Observation:
1. Wait for ADDRESS field to populate the Public IP Address

# Describe Ingress 
kubectl describe ingress ingress-basics

# Access Application
http://<ADDRESS-FIELD-FROM-GET-INGRESS-OUTPUT>
Important Note:
1. If you get 502 error, wait for 2 to 3 mins and retry. 
2. It takes time to create load balancer on GCP.

Step-07: Verify Load Balancer¶

Go to Load Balancing -> Click on Load balancer

Load Balancer View¶

DETAILS Tab
Frontend
Host and Path Rules
Backend Services
Health Checks
MONITORING TAB
CACHING TAB

Load Balancer Components View¶

FORWARDING RULES
TARGET PROXIES
BACKEND SERVICES
BACKEND BUCKETS
CERTIFICATES
TARGET POOLS

Step-08: Clean-Up¶

# Delete Kubernetes Resources
kubectl delete -f kube-manifests

# Verify if load balancer got deleted
Go to Load Balancing -> Should not see any load balancers

GKE Ingress References¶