How iam-veeramalla/kubernetes-zero-to-hero works
Main Components
a. User Environment:
• The user’s machine (which could be an EC2 instance or a personal laptop) where all commands are run.
• Key tools installed locally such as Python3, AWS CLI, kubectl, and KOPS.
b. AWS Infrastructure:
• EC2 instances: The nodes (masters and workers) that will form the Kubernetes cluster.
• S3 Bucket: Used to store the state and configuration objects for the Kubernetes cluster (as created with the “aws s3api create-bucket” command).
• IAM: AWS Identity and Access Management that enforces security permissions (e.g., AmazonEC2FullAccess, S3, IAM, and VPC permissions).
c. Kubernetes Cluster:
• The cluster objects and settings managed by KOPS.
• Internal components (masters and nodes) communicating as per Kubernetes design.
d. Security Guidelines:
• The “Security/Manage_Security_Like_Pro.md” file implies there are recommendations for configuring the system securely. These could involve best practices around key management, permissions, and hardening the environment.
Relationships and Interactions
• The user starts by setting up their local environment by installing necessary dependencies.
• KOPS is the orchestration tool communicating with AWS (through the AWS CLI and IAM) to create and configure the Kubernetes control plane and worker nodes.
• After deployment, kubectl is used to interact with the Kubernetes Cluster.
• The security guidelines influence configuration choices (for example, specifying IAM user policies or hardening access to the S3 bucket).
Architectural Patterns/Principles
• Service orchestration through KOPS, which automates cluster setup.
• Separation of responsibilities: development (tool installation and command execution) is separated from the underlying AWS infrastructure provisioning.
• Security best practices integrated, as evidenced by the inclusion of a dedicated Security directory.
Technologies and Tools
• Python3, AWS CLI, kubectl, and KOPS.
• AWS services: EC2 for instances, S3 for storage, and IAM for security.
• Kubernetes itself as the orchestrator for containerized workloads.