helm-chart-packaging
暂无简介
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 13
- Forks
- 2
03 SKILL.md 正文
/helm-chart-packaging
When to Use
- Package yamtam agent deployment as a reusable, versioned Helm chart
- Parameterize deployments: different tiers, replicas, resource limits via values.yaml
- Chart hooks: run database migration Job before deployment, cleanup Job after delete
- Dependency management: yamtam chart depends on Redis, PostgreSQL subcharts
Do NOT use for
- Single-environment one-off deployments (kubectl apply is simpler)
- GitOps sync (combine with [[argocd-gitops]] for full GitOps pipeline)
Chart directory structure
yamtam-agent/
├── Chart.yaml ← chart metadata
├── values.yaml ← default values (override at deploy time)
├── templates/
│ ├── _helpers.tpl ← named template functions
│ ├── deployment.yaml
│ ├── service.yaml
│ ├── configmap.yaml
│ ├── hpa.yaml ← HorizontalPodAutoscaler
│ └── NOTES.txt ← post-install instructions
└── charts/ ← subchart dependencies
Chart.yaml
apiVersion: v2
name: yamtam-agent
description: Yamtam agent deployment chart
type: application
version: 1.3.52 # chart version (SemVer)
appVersion: "1.3.52" # app version (informational)
dependencies:
- name: redis
version: "^17.0.0"
repository: https://charts.bitnami.com/bitnami
condition: redis.enabled
values.yaml
replicaCount: 2
image:
repository: ghcr.io/yamtam/agent
pullPolicy: IfNotPresent
tag: "" # defaults to Chart.appVersion
agent:
tier: power
skills: [ecc-key-management, jwt-jws-jwe-patterns]
resources:
requests: { memory: "256Mi", cpu: "100m" }
limits: { memory: "512Mi", cpu: "500m" }
autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 10
targetCPUUtilizationPercentage: 70
redis:
enabled: true
auth:
enabled: false
templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "yamtam-agent.fullname" . }}
labels: {{ include "yamtam-agent.labels" . | nindent 4 }}
spec:
replicas: {{ .Values.replicaCount }}
selector:
matchLabels: {{ include "yamtam-agent.selectorLabels" . | nindent 6 }}
template:
metadata:
labels: {{ include "yamtam-agent.selectorLabels" . | nindent 8 }}
spec:
containers:
- name: agent
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
env:
- name: YAMTAM_TIER
value: {{ .Values.agent.tier | quote }}
- name: YAMTAM_SKILLS
value: {{ .Values.agent.skills | join "," | quote }}
resources: {{ toYaml .Values.resources | nindent 12 }}
Deploy / upgrade / rollback
# Install
helm install yamtam-prod ./yamtam-agent \
--namespace yamtam --create-namespace \
--set agent.tier=power \
--set replicaCount=4
# Upgrade (rolling update)
helm upgrade yamtam-prod ./yamtam-agent \
--namespace yamtam \
--set image.tag=1.3.53 \
--atomic # rollback automatically if upgrade fails
# Rollback to previous release
helm rollback yamtam-prod 0 # 0 = previous revision
# Dry-run (render templates without applying)
helm install --dry-run --debug yamtam-test ./yamtam-agent
Anti-Fake-Pass Checklist
❌ image.tag: "latest" → Kubernetes caches latest; new image not pulled without imagePullPolicy: Always
❌ No --atomic on upgrade → failed upgrade leaves chart in broken state with no automatic rollback
❌ Hard-coded secrets in values.yaml → secrets in git history; use Sealed Secrets or External Secrets
❌ Missing _helpers.tpl fullname truncation to 63 chars → label values exceed K8s limit
❌ Subchart not updated (helm dependency update) → old subchart version installed silently
❌ templates/ directory empty → helm install succeeds but deploys nothing
04 同仓库更多 Skills
openai--sentry--sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
ito-basket-compare
Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.
implementing-network-traffic-baselining
Build network traffic baselines from NetFlow/IPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly/daily traffic pattern profiling
detecting-evasion-techniques-in-endpoint-logs
Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.
implementing-microsegmentation-with-guardicore
Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.
ramdisk-tmpfs-patterns
暂无简介