The examples below illustrate how to use Score files for your workload specification.
Each example may contain a Score file (score.yaml) and/or a Humanitec-specific Score extension file (usually named humanitec.score.yaml).
Note that in practice, a Score file is always required even when only an extension file is shown. When only a Score file is shown, no extension file is required.
Define Annotations that are added to Pods generated for the Workload.
Provide overrides for container commands or arguments.
Define environment variables for a container. There are two ways to configure them.
(...)
Add files to Containers.
(...)
Provide overrides for container commands or arguments.
Define liveness and readiness probes for your Workload.
(...)
Specify the resources required for a container.
A
route resource defines how to route traffic to the Workload. See Routes and Ingress for details.
Define how a service for the Workload is configured.
(...)
Define the Kubernetes Service Account that Pods in the Workload should run as. It does not manage the creation of that Service Account.
(...)
Define tolerations rules that are added to Pods generated for the Workload.
Define volumes and volume mounts for a Workload.
(...)