From 397904ee141583bc6e036d9ec4db235ecf5918ae Mon Sep 17 00:00:00 2001 From: Martyn Ranyard Date: Fri, 7 Jun 2019 15:51:57 +0200 Subject: [PATCH] [patch-1] Include AKS in the oddity list Signed-off-by: Martyn Ranyard --- Documentation/flexvolume.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/flexvolume.md b/Documentation/flexvolume.md index 228b56f66..6b6155fcd 100644 --- a/Documentation/flexvolume.md +++ b/Documentation/flexvolume.md @@ -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.