Back to list
doanchienthangdev

orchestrating-with-kubernetes

by doanchienthangdev

Omega Vibecode Kit

2🍴 1📅 Jan 21, 2026

SKILL.md


name: Orchestrating with Kubernetes description: The agent implements Kubernetes container orchestration with deployments, services, Helm charts, and production patterns. Use when deploying containerized applications, configuring autoscaling, managing secrets, or setting up ingress routing.

Orchestrating with Kubernetes

Quick Start

# deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: api-server
spec:
  replicas: 3
  selector:
    matchLabels:
      app: api-server
  template:
    metadata:
      labels:
        app: api-server
    spec:
      containers:
        - name: api
          image: ghcr.io/org/api:v1.0.0
          ports:
            - containerPort: 3000
          resources:
            requests: { cpu: "100m", memory: "256Mi" }
            limits: { cpu: "500m", memory: "512Mi" }
kubectl apply -f deployment.yaml

Features

FeatureDescriptionGuide
DeploymentsDeclarative pod management with rollbacksDefine replicas, update strategy, pod template
ServicesInternal/external load balancingClusterIP for internal, LoadBalancer for external
ConfigMaps/SecretsConfiguration and sensitive dataMount as volumes or environment variables
IngressHTTP routing with TLS terminationUse nginx-ingress or cloud provider ingress
HPAHorizontal Pod AutoscalerScale based on CPU, memory, or custom metrics
HelmPackage manager for K8s applicationsTemplate and version deployments

Common Patterns

Production Deployment with Probes

spec:
  containers:
    - name: api
      image: ghcr.io/org/api:v1.0.0
      livenessProbe:
        httpGet: { path: /health/live, port: 3000 }
        initialDelaySeconds: 15
        periodSeconds: 20
      readinessProbe:
        httpGet: { path: /health/ready, port: 3000 }
        initialDelaySeconds: 5
        periodSeconds: 10
      env:
        - name: DATABASE_URL
          valueFrom:
            secretKeyRef: { name: app-secrets, key: database-url }

Horizontal Pod Autoscaler

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: api-server
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: api-server
  minReplicas: 3
  maxReplicas: 20
  metrics:
    - type: Resource
      resource: { name: cpu, target: { type: Utilization, averageUtilization: 70 } }

Ingress with TLS

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: api-ingress
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  tls:
    - hosts: [api.example.com]
      secretName: api-tls
  rules:
    - host: api.example.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service: { name: api-server, port: { number: 80 } }

Best Practices

DoAvoid
Set resource requests and limitsRunning containers as root
Implement liveness and readiness probesUsing latest tag in production
Use namespaces for environment isolationHardcoding config in container images
Configure Pod Disruption BudgetsSkipping network policies
Use Secrets for sensitive dataExposing unnecessary ports
Implement pod anti-affinity rulesUsing NodePort in production
Set up HPA for autoscalingIgnoring pod security standards

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon