Collection of production-ready DevOps templates, configurations, and best practices for Kubernetes, Docker, AWS, and CI/CD pipelines.
.
├── KUBERNETES/ # K8s manifests and configurations
├── DOCKER/ # Docker examples and compose files
├── CLOUD_FORMATION/ # AWS CloudFormation templates
├── AWS_CODE_PIPELINE/ # AWS CodePipeline examples
├── ARCHITECTURE/ # Architecture diagrams
├── BEST_PRACTICES/ # Security and operations checklists
└── CICD_PINELINE/ # CI/CD pipeline configurations
Comprehensive collection of Kubernetes manifests covering common use cases.
- Deployments with health checks
- Services (ClusterIP, NodePort, LoadBalancer)
- ConfigMaps and Secrets
- Persistent Volumes
- StatefulSets (Cassandra example)
- DaemonSets
- Pod affinity and anti-affinity
- Tolerations and taints
- Pod security policies
- Ingress controllers (nginx)
- AWS ALB Ingress
- External DNS configuration
- Service mesh (Istio)
- Network policies
- Persistent volumes
- StatefulSets with storage
- WordPress with volumes
- Horizontal Pod Autoscaler (HPA)
- Metrics server setup
- Database service examples
- Internal DNS configuration
- RBAC configurations
- Pod security policies
- Secrets management
- Non-root containers
- Mutating webhooks
- Pod lifecycle hooks
- Pod presets
- Resource quotas
- Postgres operator examples
- Chart templates
- Jenkins deployment
- S3 helm repository setup
- Gateway configuration
- Traffic routing
- Canary deployments
- JWT authentication
- TLS configuration
- RBAC policies
- EKS-specific configurations
- Amazon Linux containers
- Kubeless functions (Node.js, Python)
- Event-driven examples
- Skaffold configuration
- Flux GitOps
Basic Docker setup with Python Flask application.
Files:
Dockerfile- Multi-stage build exampledocker-compose.yml- Service orchestrationapp.py- Sample Flask applicationrequirements.txt- Python dependencies
Infrastructure as Code templates for AWS services.
Templates:
ecs.json- ECS cluster and servicesalb_ecs.json- Application Load Balancer with ECS
CI/CD pipeline examples for AWS.
Examples:
- EKS deployment with GitHub Actions and CodeBuild
- Automated container builds
Visual references for common patterns:
- Kubernetes architecture
- AWS CodePipeline flow
- 3-tier application design
- Multi-region AWS setup
- Ingress architecture
- OAuth 2.0 flow
- RBAC with IAM integration
- Control plane security
- Pod security policies
- Network security with CNI plugins
- Secrets management
- Vulnerability scanning
- Audit logging
- Monitoring and alerting
- Least privilege principle
- Access control guidelines
- Role management
- Policy optimization
- Container security
- Network isolation
- Encryption at rest
- Secrets management
- Image scanning
- High availability patterns
# Basic deployment
kubectl apply -f KUBERNETES/deployment/helloworld.yml
# With ConfigMap
kubectl apply -f KUBERNETES/configmap/nginx.yml
# Ingress setup
kubectl apply -f KUBERNETES/ingress/nginx-ingress-controller.yml
kubectl apply -f KUBERNETES/ingress/ingress.yml
# Autoscaling
kubectl apply -f KUBERNETES/autoscaling/hpa-example.ymlcd DOCKER
docker-compose up -daws cloudformation create-stack \
--stack-name my-ecs-stack \
--template-body file://CLOUD_FORMATION/ecs.json \
--capabilities CAPABILITY_IAMUse service selectors to switch traffic between versions.
Istio configuration in KUBERNETES/istio/helloworld-v2-canary.yaml
Liveness and readiness probes in deployment examples.
- Kubernetes Secrets with volume mounts
- AWS Secrets Manager integration
- Environment variable injection
- Resource requests and limits
- Resource quotas per namespace
- Pod priority classes
- kubectl (for Kubernetes)
- docker and docker-compose
- AWS CLI (for CloudFormation)
- helm (for Helm charts)
- istioctl (for Istio examples)
- All examples use declarative YAML configurations
- Manifests are production-ready but should be customized for your environment
- Security policies should be reviewed and adjusted per requirements
- Resource limits should be tuned based on workload needs
- Start with basic examples in
KUBERNETES/first-app/ - Review security checklist before production deployment
- Use namespaces to isolate environments
- Implement monitoring and logging from day one
- Always define resource limits
- Enable security features (RBAC, PSP, network policies)
- Regular vulnerability scanning for images
- Backup state (etcd, persistent volumes)
Architecture diagrams in ARCHITECTURE/ provide visual context for complex deployments.
Best practice checklists in BEST_PRACTICES/ cover security and operational guidelines.