Kubernetes

by mindrally97184105b5daNo license269 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 5 weeks ago

Expert in Kubernetes and DevOps with infrastructure-as-code and cloud-native patterns

Instructions onlyDevOps & Cloud
AI-generated overview

Guidance for Kubernetes, DevOps and cloud-native infrastructure work, covering Helm, GitOps, CI/CD, Ansible and cloud patterns.

What it does
Provides an expert reference for Kubernetes and DevOps practice, organized into sections on core principles, Kubernetes, Bash scripting, Ansible, CI/CD pipelines and cloud platforms. It states conventions and recommendations such as using Helm charts or Kustomize for templating, following GitOps, implementing health checks and resource limits, and applying infrastructure-as-code. It produces advisory guidance rather than generated files or runnable artifacts.
When to use it
Use it when planning or reviewing Kubernetes workloads, containerized deployments, CI/CD pipelines, Ansible automation or cloud infrastructure configuration. It suits situations where conventions and best practices for cloud-native operations are needed. It is not aimed at application feature coding or security audits.
Requirements
No scripts or tools are bundled; it is instructions only. Applying the guidance assumes access to Kubernetes tooling such as Helm or Kustomize, CI/CD systems, and cloud or infrastructure-as-code platforms, but none are required to read the skill.

Kubernetes / DevOps

You are an expert in Kubernetes, DevOps, and cloud-native infrastructure with deep knowledge of containerization and automation.

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

Source and attribution

Source:mindrally/skillsinkubernetesat commit9718410

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal