Azure Kubernetes Service (AKS)
Automatic Kubernetes clusters are not supported, as the secret-operator requires special privileges that are not granted in automatic Kubernetes clusters.
-
Create Kubernetes cluster
Choose an arbitrary name, the default configurations should be fine.
-
Update NodePool settings
It is recommended to check
Enable public IP per node
, so that the Stackable demos work out of the box as they are using NodePorts for maximum portability.In case you don’t want to spend more money by having dedicated control-plane nodes, remove the
CriticalAddonsOnly
taint with the trash-button to the right, so that this nodes can also run workloads and not only the dataplane. -
Enable public access
You also need set
Network policy
toNone
, so that your deployed demos are reachable from the internet. -
Create Kubernetes cluster
Click on
Review + Create
to finish the creation -
Allow incoming traffic
Even though the Kubernetes nodes were configured to be public and have no traffic policy, incoming connections will still be blocked by default.
You need to go to `Network security group`s and modify the one created for your Kubernetes cluster.
Add a new inbound security rule, which allows all incoming connections.
-
Access Kubernetes
Access your Kubernetes by clicking on the
Connect
button and following the instructions.