Cluster Configuration

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:

  1. Kubernetes distribution/Manged Service (eg AKS, EKS, GKE …)
  2. Storage provider type (i.e. the filesystem shared between worker and pods)
  3. 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 ServicerStorage Solution:Approach
MinikubeNFSNo additional configuration required†
MicroK8sNFSNo additional configuration required†
KindNFSNo additional configuration required†
AKSNFSNo additional configuration required
Azure FilesNo additional configuration required
GKENFSNo additional configuration required
EKSNFSNo additional configuration required
EFSRequires Octopus Server 2024.3+
RKE2LonghornRequires pre-configured storage‡
OpenShiftNFSRequires 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.

Send feedback

Page updated on Thursday, August 22, 2024