How saikiranpi/mastering-kubernetes works
Project’s Main Focus and Components
• Each “Day” directory highlights a specific Kubernetes concept: cluster deployment (kubeadm, kOPS), orchestration (deployments, pods), networking (services, ingress, network policies), storage (PV/PVC, storage class), security (RBAC, secrets, configmaps), and more advanced integrations (Istio service mesh, Prometheus/Grafana, AWS EKS/Jenkins integration, MetricsServer, etc.).
• In addition, the “Rancher K3S” folder indicates additional guidance on lightweight Kubernetes clusters via Rancher’s distribution.
Break Down the Architecture into Clear Components
a. Core Cluster Components:
– Control Plane: Include the Kubernetes API Server, Scheduler, Controller Manager, etc.
– Worker Nodes: Represent the nodes which run PODs and include Resource Quotas, Sidecar containers, etc.
b. Deployment & Management:
– Deployment configurations (YAML files in many directories) indicating the desired state.
– Tools for cluster provisioning (kops, kubeadm, Rancher K3S).
– Advanced Scheduling modules demonstrating node selectors, affinity/anti-affinity, and taints.
c. Networking and Access:
– Service configurations, Ingress configurations, Network Policies.
– Istio Service Mesh components (Ingress Gateway, Virtual Services, auxiliary tools like Kiali and Jaeger).
d. Storage and Persistence:
– Persistent Volume (PV), Persistent Volume Claims (PVC) setups, dynamic provisioning and storage classes.
e. Monitoring, Logging, and Metrics:
– Integration of Prometheus, Grafana, and the EFK stack (Elasticsearch, Fluentd, Kibana).
– Metrics Server and autoscaling concepts (VPA, HPA, and Karpenter support).
f. CI/CD and Integration:
– AWS EKS-Jenkins configuration files along with kustomize overlays, demonstrating a continuous integration pipeline.
g. Security & Config Management:
– RBAC, Secrets, and ConfigMaps configurations.
Relationships and Data Flows
– Show how deployment YAML files define pods that communicate with services, which in turn interact with ingress controllers.
– Represent the control flow within the Kubernetes control plane from API Server → Scheduler → Worker Nodes.
– Indicate CI/CD pipelines (Jenkins) triggering deployments and updates across the cluster.
– Demonstrate monitoring data flows from cluster components (pods/nodes) to Prometheus and then dashboards like Grafana.
Architectural Patterns and Design Principles
• Clearly demarcate the separation of concerns: operational concerns (deployment, networking, storage, security) are modularized by “Day” folders.
• Common Kubernetes patterns such as declarative configuration via YAML, desired state management, and microservices architecture when combined with service meshes.
• Stress extensibility points (e.g., how additional configurations for RBAC or network policies can be added).
Final Assembly
• Every module from cluster provisioning (Day 00, Day 01, Day 17, Rancher K3S) to advanced topics (Service Mesh, Monitoring, Metrics, CI/CD) is represented.