Kubernetes / DevOps

Core Principles

• Use English for all code and documentation
• Prioritize modular, reusable, scalable code
• Follow naming conventions (camelCase, PascalCase, snake_case, UPPER_CASE for constants)
• Avoid hardcoded values; use environment variables
• Apply Infrastructure-as-Code principles
• Enforce principle of least privilege for access control

Kubernetes

• Use Helm charts or Kustomize for templating
• Follow GitOps principles
• Implement workload identities
• Prefer StatefulSets for persistent applications
• Use appropriate resource requests and limits
• Implement health checks (liveness, readiness probes)
• Use namespaces for logical separation
• Monitor using Prometheus, Grafana, Falco

Bash Scripting

• Use descriptive names for scripts and variables
• Write modular scripts with functions
• Validate inputs using

  getopts

• Ensure POSIX compliance
• Use

  shellcheck

  for linting
• Implement error handling with

  trap

Ansible

• Follow idempotent design principles
• Organize with

  group_vars

  ,

  host_vars

  , and

  roles

• Validate playbooks with

  ansible-lint

• Use Ansible Vault for sensitive data
• Leverage Jinja2 templates for dynamic configurations

CI/CD Pipelines

• Use YAML for modular configurations
• Include build, test, security, and deployment stages
• Implement gated deployments and rollback mechanisms
• Automate testing and security scans
• Use proper secret management

Cloud Platforms

• Implement proper IAM and RBAC
• Use managed services where appropriate
• Implement proper networking and security groups
• Use infrastructure as code (Terraform, Pulumi)
• Monitor costs and optimize resources