Kubernetes: kubeadm unterstützt ABAC nicht richtig

Ist dies ein FEHLERBERICHT oder eine FEATURE-ANFRAGE? :
/ freundlicher Fehler

Was ist passiert :
Ich habe versucht, einen Cluster mit dem kubeadm Tool mit aktivierter ABAC-Autorisierung zu erstellen, wobei die folgenden Konfigurationsdateien verwendet wurden.

~/config.yaml

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
networking:
  podSubnet: 10.244.0.0/16
authorizationModes:
- Node
- RBAC
- ABAC
apiServerExtraArgs:
  basic-auth-file: /etc/kubernetes/basic_auth.csv
  authorization-policy-file: /etc/kubernetes/abac_policy.json

~/basic_auth.csv

admin,admin,1,"system:masters"

~/abac_policy.json

{"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user":"*", "nonResourcePath": "*", "readonly": true}}
{"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"user":"admin", "namespace": "*", "resource": "*", "apiGroup": "*"}}
{"apiVersion": "abac.authorization.kubernetes.io/v1beta1", "kind": "Policy", "spec": {"group":"system:serviceaccounts", "namespace": "*", "resource": "*", "apiGroup": "*", "nonResourcePath": "*"}}

Der Befehl kubeadm hängt mit der folgenden Ausgabe...

[init] Using Kubernetes version: v1.9.3
[init] Using Authorization modes: [Node RBAC ABAC]
[preflight] Running pre-flight checks.
        [WARNING FileExisting-crictl]: crictl not found in system path
[preflight] Starting the kubelet service
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [####### #######]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] Generated sa key and public key.
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk: "admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf"
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests".
[init] This might take a minute or longer if the control plane images have to be pulled.

Es sieht so aus, als ob der kube-apiserver Container ständig neu gestartet wird.

Die Protokollausgabe aus dem kube-apiserver Container ergibt

I0306 12:39:33.179719       1 server.go:121] Version: v1.9.3
invalid authentication config: open /etc/kubernetes/basic_auth.csv: no such file or directory

Was Sie erwartet haben, zu passieren :
Ich habe erwartet, dass die kube-apiserver beginnen.

So reproduzieren Sie es (so minimal und genau wie möglich) :

mkdir -p /etc/kubernetes
cp ~/basic_auth.csv /etc/kubernetes
cp ~/abac_policy.json /etc/kubernetes
kubeadm init --config ~/config.yaml

Müssen wir noch etwas wissen? :

Umgebung :

• Kubernetes-Version (verwenden Sie kubectl version ): v1.9.3
• Cloud-Anbieter oder Hardware-Konfiguration: Bare Metal
• Betriebssystem (zB aus /etc/os-release): 16.04.4 LTS (Xenial Xerus)
• Kernel (zB uname -a ): Linux k8s-master 4.4.0-116-generic #140-Ubuntu SMP Mo Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• Tools installieren:
• Andere: