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 Kubernetes objects generated for the Workload.
Provide overrides for container commands or arguments.
Define your workload to be deployed as a
Kubernetes CronJob
through a Score extension file.
(...)
For a Workload that is deployed as a Kubernetes
Deployment, you can set properties of the
Kubernetes DeploymentSpec
on the Kubernetes Deployment object through a Score extension file for your workload.
(...)
Define environment variables for a container. There are two ways to configure them.
(...)
Add files to Containers.
(...)
Define your workload to be deployed as a
Kubernetes Job
through a Score extension file.
(...)
This example shows how to deploy multiple workloads within one deployment.
(...)
Provide overrides for container commands or arguments.
You may set additional properties for the Kubernetes
Pod objects which will be created for your workload. You can set almost any property of the Kubernetes API specification for this object. Refer to the
Pod feature
description for details on supported properties.
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.
(...)