[patch-1] Include AKS in the oddity list

Signed-off-by: Martyn Ranyard <m@rtyn.berlin>
This commit is contained in:
Martyn Ranyard authored and Martyn Ranyard committed 2019-06-07 15:56:38 +02:00
1 parent fb22976750
commit 397904ee14
1 file changed
+7
+7
View File
@@ -12,6 +12,7 @@ This is the case for Kubernetes deployments on:
* [OpenShift](https://www.openshift.com/)
* [Rancher](http://rancher.com/)
* [Google Kubernetes Engine (GKE)](https://cloud.google.com/kubernetes-engine/)
* [Azure AKS](https://docs.microsoft.com/en-us/azure/aks/)
Especially in these environments, the kubelet needs to be told to use a different FlexVolume plugin directory that is accessible and read/write (`rw`).
These steps need to be carried out on **all nodes** in your cluster.
@@ -81,6 +82,12 @@ The kubelet on GKE is already configured to use that directory.
Continue with [configuring the FlexVolume path](#configuring-the-flexvolume-path) to configure Rook to use the FlexVolume path.
### Azure AKS
AKS uses a non-standard FlexVolume plugin directory: `/etc/kubernetes/volumeplugins`
The kubelet on AKS is already configured to use that directory.
Continue with [configuring the FlexVolume path](#configuring-the-flexvolume-path) to configure Rook to use the FlexVolume path.
### Tectonic
Follow [these instructions](tectonic.md) to configure the Flexvolume plugin for Rook on Tectonic during ContainerLinux node ignition file provisioning.
If you want to use Rook with an already provisioned Tectonic cluster, please refer to the [ContainerLinux](#containerlinux) section.