This guide walks you through inspecting a Google Kubernetes Engine (GKE) cluster. You’ll learn how to list nodes, view namespaces, deploy a sample NGINX app with Ingress, verify your kubeconfig, and prepare namespaces for GitLab CI/CD.Documentation Index
Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
Use this file to discover all available pages before exploring further.
Inspecting Cluster Nodes on GKE
Make sure you’ve authenticated with GKE and set up
kubectl (or aliased as k) using:Viewing Namespaces and the NGINX Ingress Controller
Show all namespaces:ingress-nginx namespace and inspect its resources:
- A Deployment managing the Ingress Controller pod
- A
LoadBalancerService exposing a public IP
Deploying a Sample NGINX Application
In thedefault namespace, the following resources route traffic through the Ingress Controller:
The default Ingress TLS certificate is self-signed. Browsers will warn before displaying the NGINX welcome page.

Configuring kubectl and kubeconfig for CI/CD
To automate deployments in GitLab CI, ensurekubectl is installed and authenticated via kubeconfig.
Check client and server versions:
gitlab-cluster-admin) should authenticate your GitLab CI jobs.
Creating Namespaces for Environments
Instead of separate clusters, use dedicated namespaces to isolate development and staging workloads:Kubernetes CLI Command Reference
| Command | Description |
|---|---|
kubectl get nodes | List all cluster nodes |
kubectl get namespaces | Show active namespaces |
kubectl -n ingress-nginx get all | Inspect Ingress Controller resources |
kubectl get ingress | Display all Ingress resources |
kubectl config view --minify | Show current kubeconfig context |
kubectl create namespace <name> | Create a new namespace |
Links and References
- Google Kubernetes Engine (GKE)
- Kubernetes Ingress NGINX Controller
- kubectl CLI Reference
- GitLab CI/CD Pipeline Configuration