container-orchestration_skill

This skill helps you implement container orchestration best practices for Docker and Kubernetes via patterns, health checks, and efficient deployments.
  • Shell

8

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 0xdarkmatter/claude-mods --skill container-orchestration

  • SKILL.md4.7 KB

Overview

This skill provides concise Docker and Kubernetes patterns to build, run, and operate containerized applications. It bundles verified Dockerfile best practices, docker-compose examples, Kubernetes manifests (Deployment, Service, Ingress), and common kubectl commands. It’s designed to speed up reliable container builds, local compose workflows, and production-ready Kubernetes deployments.

How this skill works

The skill inspects Dockerfiles, docker-compose files, Kubernetes manifests, Helm templates, and related container artifacts to suggest best practices and fixes. It highlights concrete improvements: pinned base images, multi-stage builds, non-root users, health checks, resource requests/limits, and probe configurations. It also maps common kubectl commands and compose service patterns to actionable steps for local development and cluster rollout.

When to use it

  • Creating or reviewing Dockerfiles for production images
  • Assembling or troubleshooting docker-compose local stacks
  • Authoring Kubernetes manifests (Deployment, Service, Ingress) for clusters
  • Validating health checks, liveness/readiness probes, and resource settings
  • Preparing images and manifests for CI/CD and cluster rollout

Best practices

  • Pin explicit base image versions instead of :latest
  • Use multi-stage builds and .dockerignore to keep images small
  • Run containers as a non-root user and avoid baking secrets into images
  • Order Dockerfile layers by change frequency to improve cache efficiency
  • Define healthchecks and Kubernetes liveness/readiness probes for graceful recovery
  • Set resource requests and limits to protect cluster stability

Example use cases

  • Convert a development Dockerfile into a production-ready multi-stage image
  • Compose a local dev stack with database healthchecks and named volumes
  • Create a Deployment with probes, resource quotas, and secret-backed env vars
  • Expose services with an Ingress using nginx annotations for path rewrite
  • Use kubectl commands to debug pods, stream logs, or port-forward services

FAQ

Avoid :latest for reproducible builds. Pin a specific image version or digest to ensure consistent deployments.

Where should secrets live?

Keep secrets out of images. Use Kubernetes Secrets, environment variables populated by your CI, or external secret managers.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
container-orchestration skill by 0xdarkmatter/claude-mods | VeilStrat