mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-12 03:56:53 +03:00

Files

T

Magnus HedemarkandGitHub c7c4d3b74f Port 11 methodology skills from hermes-profiles (#69 )

Engineering: backend-engineering, frontend-engineering, data-engineering,
ml-engineering, platform-engineering, qa-methodology

Executive: go-to-market, legal-strategy, operational-design, org-design,
product-strategy

ml-engineering: added missing training-infrastructure.md reference
qa-methodology: added test-data-management, performance-testing,
security-testing references

All frontmatter converted to agent-skills convention.
Source: https://github.com/magnus919/hermes-profiles

2026-07-21 00:58:26 -04:00

2.7 KiB

Raw Blame History

Container Orchestration — Reference

Kubernetes and k3s

Core objects: Pod, Service, Deployment, StatefulSet, DaemonSet, Ingress, ConfigMap, Secret, PersistentVolume/PVC, Namespace, RBAC (Role/ClusterRole/RoleBinding/ClusterRoleBinding), NetworkPolicy
Lifecycle: Rolling updates, recreate, canary via flags, blue-green via Services; readiness/liveness/startup probes, preStop hooks, pod disruption budgets
Scheduling: nodeSelector, node affinity/anti-affinity, pod affinity/anti-affinity, taints and tolerations, topology spread constraints, resource limits/requests, QoS classes (Guaranteed/Burstable/BestEffort)
k3s specifics: Lightweight Kubernetes (single binary), embedded etcd (or SQLite), Traefik as default ingress, servicelb, HelmController, local-path-provisioner, useful for edge/IoT/development

Helm

Chart structure: Chart.yaml, values.yaml, templates/, charts/ (dependencies), crds/, templates/NOTES.txt, templates/tests/
Conventions: helper templates (helpers.tpl), named templates, required values with required, global values for cross-chart values, conditionally-enabled subcharts
Lifecycle: helm create, helm lint, helm template, helm install --values, helm upgrade --install, helm rollback, helm uninstall, helm dependency update
Repos: ChartMuseum, OCI registries (GHCR, ECR, ACR), helm repo add/update
Best practices: Pin dependency versions, set resource limits, use release namespace, separate env values files, enable/disable subcharts via tags or condition

Kustomize

Core model: Base + overlays — base sets common config, overlays apply env-specific patches
Key directives: resources, patchesStrategicMerge, patchesJson6902, configMapGenerator, secretGenerator, namePrefix, namespace, commonLabels, images, replicas, vars
Patterns: Multi-environment (dev/staging/prod), multi-cluster, component-based composition, in-line vs file-sourced patches
Integration: kustomize build as input to kubectl or ArgoCD, kustomize edit for interactive modification

Docker Compose (Production Patterns)

Production concerns: Health checks (healthcheck:), restart policies (unless-stopped/always), resource limits (deploy.resources.limits), logging drivers, network isolation (custom networks), volume management (named volumes, bind mounts, tmpfs)
Multi-service patterns: Depends-on with health check wait, init containers, sidecar containers (nginx reverse proxy, log shipper), environment file separation (.env, multiple --env-file)
Orchestration compatibility: Compose file can be used directly (single host), converted to K8s via kompose, or used as a local dev environment matching production topology

2.7 KiB Raw Blame History

Container Orchestration — Reference

Kubernetes and k3s

Helm

Kustomize

Docker Compose (Production Patterns)

2.7 KiB

Raw Blame History