The Kubernetes worker has been proven to be effective on a variety of installations. But some configurations are more complex than others!
There’s three factors which affect the likelihood of success:
- Kubernetes distribution/Manged Service (eg AKS, EKS, GKE …)
- Storage provider type (i.e. the filesystem shared between worker and pods)
- The Operating System of the Kubernetes nodes
When trying to determine the best combination of these for your situation, it may be simplest to start small and iterate.
The following table defines known good configurations, though there are many other configurations which are likely to produce a valid system.
| Distribution / Managed Servicer | Storage Solution: | Approach |
|---|---|---|
| Minikube | NFS | No additional configuration required†|
| MicroK8s | NFS | No additional configuration required†|
| Kind | NFS | No additional configuration required†|
| AKS | NFS | No additional configuration required |
| Azure Files | No additional configuration required | |
| GKE | NFS | No additional configuration required |
| EKS | NFS | No additional configuration required |
| EFS | Requires Octopus Server 2024.3+ | |
| RKE2 | Longhorn | Requires pre-configured storage‡ |
| OpenShift | NFS | Requires specific configuration‡ |
†Recommended for local development or edge usage
‡ Please contact support for additional information
Any Storage class which supports being mounted in ReadWriteMany mode is likely to satisfy the Kubernetes worker’s storage requirements.
The Kubernetes worker is compatible with most Ubuntu-based nodes and also those running Amazon Linux.
The NFS Storage solution cannot be used with BottleRocket nodes as a current issue with SELinux enforcement prevents execution from the NFS share.
The Kubernetes worker is not compatible with Windows nodes, and currently unable to create script-pods based on Windows images.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Thursday, August 22, 2024