Azure ACS AzureFile动态持久卷声明

我正在尝试使用我用azure file类型定义的storageclass动态调配存储。我已尝试在storageclass中为storageAccount和skuName设置两个参数。下面是我使用storageAccount set的示例

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: azuretestfilestorage
  namespace: kube-system
provisioner: kubernetes.io/azure-file
parameters:
  storageAccount: <storage_account_name>

以下是我的persistentvolumeclaim的代码

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: logging-persistent-volume-claim-test
  namespace: kube-system
spec:
  accessModes:
    - ReadWriteMany  
  resources:
    requests:
      storage: 5Gi
  storageClassName: azuretestfilestorage

我的storageaccount肯定与我的acs群集位于同一资源组和数据中心位置。我的理解是，应该自动生成一个秘密的、持久的卷和文件共享。相反，我只是被困在一个挂起状态，上面有错误

这是我的kubectl版本命令的输出

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T12:22:21Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

---

如有任何意见，将不胜感激。谢谢

我向microsoft azure支持部门发送了电子邮件，并收到了回复

如果主节点VM的“/etc/kubernetes/manifests/kube controller manager.yaml”中的--cluster name值大于16个字符，则acs kubernetes版本1.7.7中存在一个错误，不允许动态持久卷声明工作。非常难懂的虫子。修复方法是升级集群或使用其他名称重新部署

以下是错误报告：

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T12:22:21Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}