Skip to content



The Ayedo Kubernetes Engine (AKE) builds Kubernetes clusters from scratch on VMs or bare-metal machines.

It's Ansible-based and allows you to deploy Kubernetes clusters on any machine with a supported OS (Ubuntu, Debian, Centos) and architecture (x64, armhf, arm64) that you can access via SSH.

Depending on the provider of your machines (bare-metal or a supported cloud-provider), additional enhancements like CSI-integration are available.

AKE is a component of the Ayedo Cloud Stack (ACS) and uses a common directory to store output and configuration, the so called $acs_dir which defaults to ~/.acs.

ACS works with so called stacks. As such, each installation of the Ayedo Kubernetes Engine requires a $stack, just like HELM. All of AKE's output will be saved to the so called $stack_dir which defaults to $acs_dir/$stack.

Required software

Install with pip

pip3 install -r requirements.txt

Get started

We will work with a new installation that we'll call This gives us the following base-config:

  • stack_dir=~/.acs/

INFO: AKE expects your configuration and inventory to be in this directory

Create your inventory

AKE requires a valid Ansible inventory to work. In this inventory, all masters and nodes of the cluster need to be defined.

INFO: Use the Ayedo Kubernetes Infrastructure (short: AKI) to build an inventory in the cloud or with one of the supported on-premise providers

The composition of the cluster is out of scope for the AKE. AKE expects a minimum of 1 master node.

Create a directory (the $stack_dir) for your new cluster:

mkdir -p ~/.acs/

Create an inventory file for your new cluster:

edit ~/.acs/

NOTE: this must be a valid Ansible inventory; it doesn't matter if it's YAML, JSON or INI format

Setup your nodes:

# ~/.acs/

NOTE: this is pure Ansible using the defaults. Depending on your setup your inventory might look more complex or you'll need to specify additional configuration for the SSH user or a specific SSH key file to use.

Create your configuration files

In your $stack_dir, create a vars-file:

edit ~/.acs/

Setup your cluster configuration:

# ~/.acs/
  provider: longhorn

INFO: You can see the defaults here.

Use with Docker

docker run -e "STACK_DIR=/root/.acs/" -v ~/.acs/ ansible-playbook -i /root/.acs/ install.yml

Use manually

export STACK_DIR=~/.acs/
ansible-playbook install.yml -i ~/.acs/mycluster/ake/inventory.yml

Upon completion, AKE will save your Kubernetes credentials in ~/.acs/ Use this file to connect to the Kubernetes cluster.


Default configuration options can be found in defaults.yml. This file will be loaded by install.yml. Additional configuration options can be set in multiple ways:

  • creating user configuration in ~/.acs/ AKE picks up user-config automatically from there.

Configuration options

| Configuration Option | Description | Default | | -------------------- | :---------: | ------: |: | | stack_dir | Location of the stack | lookup EnvVar STACK_DIR | | | Name of the stack | - | | k3s_extra_agent_args | Additional arguments for the k3s agent | - | | k3s_extra_server_args | Additional arguments for the k3s server | --disable traefik,local-storage --disable-cloud-controller --node-taint CriticalAddonsOnly=true:NoExecute | | k3s_version | k3s version | v1.21.1+k3s1 | | k3s_token_ | k3s token for encryption of inter-node communication | mysupersecrettoken | | csi.provider | Enable/Disable CSI integration for this provider | longhorn | | hcloud.token | HETZNER Cloud API token | - |

| systemd_dir | The directory on the remote nodes where k3s service files should go to | /etc/systemd/system | | ssh_public_keys | Additional public ssh-keys to add to the nodes |- |

Issues / Troubleshooting


We use SemVer for versioning. For the versions available see the tags on this repository.


  • Fabian Peter
  • Jan Stauder

See also the list of contributors who participated in this project.


A Kubernetes Engine is Apache 2.0 licensed.


This software is maintained and commercially supported by p3r.. You can reach us here:

Last update: October 18, 2021