菜单
This skill should be used when the user asks about "deploy Temporal", "Temporal Helm chart", "install Temporal", "Kubernetes Temporal", "EKS Temporal", "local Temporal cluster", "temporal-server deployment", or needs guidance on deploying self-hosted Temporal clusters.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks about deploying Hugo to AWS S3, S3 static site hosting, Hugo with CloudFront, the hugo deploy command, configuring Hugo's deployment section, GitHub Actions with AWS OIDC for Hugo, S3 bucket static website configuration, CloudFront cache invalidation after Hugo deploy, or choosing between GitHub Pages and S3 for Hugo hosting. Also applies when GitHub Pages limitations (auth, custom headers, size) require an alternative deployment target.
This skill should be used when the user asks about deploying Hugo to GitHub Pages, setting up a GitHub Actions workflow for Hugo, Hugo CI/CD pipeline, content-aware path filtering for Hugo builds, caching Hugo modules in CI, Hugo PR preview deployments, Hugo build workflow, or configuring GitHub Pages deployment for a Hugo site. Also applies when troubleshooting GitHub Actions workflow failures related to Hugo builds.
This skill should be used when the user asks about Hugo's data directory, loading YAML or JSON or TOML data files in Hugo templates, using .Site.Data to access structured data, data-driven navigation or menus, rendering datasets or bibliographies or registries from data files, generating content from data, using range to iterate over data collections, Hugo resources.GetRemote for external data, or organizing data files for large projects. Also applies when the user wants to drive site content or navigation from structured data rather than hardcoding it in templates.
This skill should be used when the user asks about Hugo shortcodes, creating custom shortcodes, Hugo render hooks, custom rendering for links or images or headings or code blocks, Hugo taxonomies (tags, categories, custom), page bundles and page resources, content formatting beyond basic markdown, creating callout boxes or tabs or admonitions in Hugo, or customizing how Hugo processes markdown elements. Also applies when the user wants to add reusable content components to their Hugo site.
This skill should be used when the user asks about Hugo themes, installing a theme, customizing a theme, overriding theme layouts or partials, Hugo template lookup order, creating a Hugo theme from scratch, Hugo asset pipeline (SCSS, PostCSS), Hugo baseof.html, or theme configuration parameters. Also applies when evaluating which theme to use, switching themes, or troubleshooting theme-related rendering issues.
This skill should be used when the user asks about Hugo module mounts, mounting multiple directories into Hugo's content tree, aggregating docs from scattered directories, using hugo mod init, configuring module.mounts in hugo.toml, building a unified documentation site from a monorepo, mapping subdirectory docs/ folders into a single Hugo site, or understanding Hugo's union file system. Also applies when the user has a repository with multiple docs/ directories that need to be presented as a single site. This is the core skill for multi-directory content aggregation.
| name | cluster-deployment |
| description | This skill should be used when the user asks about "deploy Temporal", "Temporal Helm chart", "install Temporal", "Kubernetes Temporal", "EKS Temporal", "local Temporal cluster", "temporal-server deployment", or needs guidance on deploying self-hosted Temporal clusters. |
| version | 1.0.0 |
Guidance for deploying self-hosted Temporal clusters using Helm on Kubernetes.
| Environment | Method | Database | Use Case |
|---|---|---|---|
| Local Dev | docker-compose | SQLite/PostgreSQL | Development, testing |
| Local K8s | Helm | PostgreSQL | Integration testing |
| Production | Helm | PostgreSQL + Elasticsearch | Production workloads |
Quick setup for local development:
git clone https://github.com/temporalio/docker-compose.git
cd docker-compose
docker-compose up -d
Access points:
localhost:7233http://localhost:8080helm repo add temporal https://go.temporal.io/helm-charts
helm repo update
Minimal configuration for development/testing:
# values-dev.yaml
server:
replicaCount:
frontend: 1
history: 1
matching: 1
worker: 1
config:
numHistoryShards: 128
cassandra:
enabled: false
mysql:
enabled: false
postgresql:
enabled: true
elasticsearch:
enabled: false
prometheus:
enabled: false
grafana:
enabled: false
Deploy:
helm install temporal temporal/temporal \
-f values-dev.yaml \
--namespace temporal \
--create-namespace
Full production configuration with external PostgreSQL:
# values-production.yaml
server:
replicaCount:
frontend: 3
history: 3
matching: 3
worker: 1
config:
numHistoryShards: 512
persistence:
default:
driver: sql
sql:
driver: postgres
host: your-postgresql-host
port: 5432
database: temporal
user: temporal
existingSecret: temporal-db-credentials
maxConns: 20
maxIdleConns: 20
maxConnLifetime: "1h"
visibility:
driver: sql
sql:
driver: postgres
host: your-postgresql-host
port: 5432
database: temporal_visibility
user: temporal
existingSecret: temporal-db-credentials
resources:
frontend:
requests:
cpu: "500m"
memory: "1Gi"
limits:
cpu: "2"
memory: "4Gi"
history:
requests:
cpu: "1"
memory: "2Gi"
limits:
cpu: "4"
memory: "8Gi"
matching:
requests:
cpu: "500m"
memory: "1Gi"
limits:
cpu: "2"
memory: "4Gi"
worker:
requests:
cpu: "200m"
memory: "256Mi"
limits:
cpu: "1"
memory: "1Gi"
cassandra:
enabled: false
mysql:
enabled: false
postgresql:
enabled: false # Using external PostgreSQL
elasticsearch:
enabled: true
replicas: 3
minimumMasterNodes: 2
resources:
requests:
cpu: "1"
memory: "2Gi"
limits:
cpu: "2"
memory: "4Gi"
persistence:
enabled: true
size: 100Gi
web:
enabled: true
replicaCount: 2
prometheus:
enabled: true
grafana:
enabled: true
Create the database credentials secret:
kubectl create secret generic temporal-db-credentials \
--namespace temporal \
--from-literal=password='your-db-password'
helm install temporal temporal/temporal \
-f values-production.yaml \
--namespace temporal \
--create-namespace \
--wait
Initialize database schemas before first deployment:
# Run schema setup job
kubectl exec -it temporal-admintools-0 -n temporal -- \
temporal-sql-tool \
--plugin postgres \
--ep your-postgresql-host \
-p 5432 \
-u temporal \
--pw 'your-password' \
--db temporal \
setup-schema -v 0.0
# Run visibility schema
kubectl exec -it temporal-admintools-0 -n temporal -- \
temporal-sql-tool \
--plugin postgres \
--ep your-postgresql-host \
-p 5432 \
-u temporal \
--pw 'your-password' \
--db temporal_visibility \
setup-schema -v 0.0
For Amazon EKS deployments:
# values-eks.yaml
server:
config:
persistence:
default:
sql:
host: temporal.cluster-xxxxx.region.rds.amazonaws.com
# Use IAM authentication
connectAttributes:
aws_region: us-east-1
# Use ALB for ingress
web:
ingress:
enabled: true
annotations:
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/target-type: ip
hosts:
- temporal.internal.example.com
# Service account for IAM roles
serviceAccount:
create: true
annotations:
eks.amazonaws.com/role-arn: arn:aws:iam::ACCOUNT:role/temporal-role
Check deployment status:
# Check pods
kubectl get pods -n temporal
# Check services
kubectl get svc -n temporal
# Port-forward to test locally
kubectl port-forward svc/temporal-frontend 7233:7233 -n temporal
kubectl port-forward svc/temporal-web 8080:8080 -n temporal
# Verify cluster health
temporal operator cluster health
After deployment:
# Create default namespace
temporal operator namespace create --namespace default --retention 3d
Pods not starting:
kubectl describe pod <pod-name> -n temporal
kubectl logs <pod-name> -n temporal
Database connection issues:
Schema errors:
For advanced configurations, consult:
references/helm-values-reference.md - Complete Helm values documentationreferences/eks-deployment.md - EKS-specific deployment guide