The following is a list of the default container images used as part of the Kubernetes agent & worker.
Note
The Helm values paths are based on the v2 version of the Helm chart.
octopusdeploy/kubernetes-agent-tentacle
Default registry
Source code
Helm values path
.agent.image
Purpose
The main application container. Provides registration and communication with Octopus Server and manages the script pods.
octopusdeploy/nfs-server
Default registry
Source code
Helm values path
.persistence.nfs.image
Purpose
A small Alpine-based NFS server. Runs in a separate pod when a custom storage class is not provided.
octopusdeploy/kubernetes-agent-nfs-watchdog
Default registry
Source code
Helm values path
.persistence.nfs.watchdog.image
Purpose
A small application that monitors the health of the NFS mount. Terminates the Tentacle or running script pod if the NFS mount is deemed to be unhealthy. Only runs when the NFS pod is running.
octopusdeploy/kubernetes-agent-tools-base
Default registry
Source code
Helm values path
.scriptPods.deploymentTarget.image
Purpose
The default image used for deployments when running as a deployment target. If no values are specified, uses the tag that matches the cluster version.
octopusdeploy/worker-tools
Default registry
Source code
Helm values path
.scriptPods.worker.image
Purpose
The default image used for workloads when running as a worker.
For ARM workloads use octopuslabs/k8s-workertools or your own custom docker image.
octopuslabs/k8s-workertools
Default registry
Source code
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Tuesday, September 24, 2024