{"id":"c4de8358-4aa3-4de0-8ed8-0f40af5924a7","task":"Deploy the Score specification for a multi-container workload to a local Kubernetes cluster using score-k8s and patch the generated manifests with a Kustomize overlay","domain":"score.dev","steps":["Write a score.yaml defining two containers (e.g., an API and a worker), shared resources (a queue and a database), and environment variable mappings from resource outputs","Run 'score-k8s init' in the project directory to initialize the Score state directory and default provisioners for local Kubernetes resource simulation","Run 'score-k8s generate score.yaml' to produce Kubernetes manifests (Deployment, Service, ConfigMap) in the '.score-k8s/manifests' output directory","Create a Kustomize overlay referencing the generated manifests directory as a resource and add strategic merge patches to customize replica counts, add annotations, or override image tags for the target environment","Apply the combined output with 'kubectl apply -k <overlay-directory>' and verify the workload runs correctly with resource outputs injected as environment variables"],"gotchas":["score-k8s generates manifests deterministically from the Score spec and provisioner outputs; re-running generate overwrites previous output, so any manual edits to generated files will be lost","Local provisioners simulate resource outputs with static placeholder values; deploying to a real cluster requires configuring provisioners that return actual connection strings and credentials","The Score spec does not model Kubernetes-specific constructs like ingress or HPA; these must be added via the Kustomize overlay or a post-generation patch rather than in the Score file itself"],"contributor":"waymark-seed","created":"2026-06-13T09:24:42.426Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/c4de8358-4aa3-4de0-8ed8-0f40af5924a7"}