我试图直接访问Kubernetes API而不运行 kubectl -proxy
. 但是当我使用serviceaccount默认的令牌时,我得到403.即使在为此serviceaccount创建ClusterRole和ClusterRoleBinding之后,该请求也被403拒绝 .
我应用的配置如下所示:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: pod-reader
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "watch", "list"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: pod-reader
subjects:
- kind: ServiceAccount
name: default
namespace: default
roleRef:
kind: ClusterRole
name: pod-reader
apiGroup: rbac.authorization.k8s.io
(它几乎是关于kubernetes io的文档中的一个,只是将ServiceAccount用作Subject并将资源更改为pods)
然后我应用了配置并尝试通过curl访问pod:
$ kubectl apply -f secrets.yaml
clusterrole "pod-reader" created
clusterrolebinding "pod-reader" created
$ curl https://192.168.1.31:6443/v1/api/namespaces/default/pods --header "Authorization: Bearer $TOKEN" --insecure
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message": "forbidden: User \"system:serviceaccount:default:default\" cannot get path \"/v1/api/namespaces/default/pods\"",
"reason": "Forbidden",
"details": {
},
"code": 403
}
我想错误消息显示认证部分没问题,因为看起来请求被正确识别为来自serviceaccount default:default . 但是,如何授权此(或其他服务帐户)访问有关pod或节点的信息,我该怎么办?
从Pod外部调用curl时我看到了这个错误,但是如果我 - 例如 - 使用kubernetes java客户端使用安装在/ var / run / secrets下的秘密从Pod中访问API .
我是K8的新手,所以如果这是一个愚蠢的问题,请原谅我 .
关于配置:我在Raspberry Pis集群上运行K8s 1.8,其中包含一个Master和两个Worker Nodes . 我没有传递给kubeadm init,所以我猜它应该有默认配置 . FWIW kubectl describe为apiserver显示此命令:
kube-apiserver
--requestheader-group-headers=X-Remote-Group
--service-account-key-file=/etc/kubernetes/pki/sa.pub
--admission-control=Initializers,NamespaceLifecycle,LimitRanger,ServiceAccount,PersistentVolumeLabel,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,ResourceQuota
--secure-port=6443
--requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
--proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt
--proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key
--advertise-address=192.168.1.31
--service-cluster-ip-range=10.96.0.0/12
--tls-cert-file=/etc/kubernetes/pki/apiserver.crt
--tls-private-key-file=/etc/kubernetes/pki/apiserver.key
--kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt
--kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key
--enable-bootstrap-token-auth=true
--requestheader-username-headers=X-Remote-User
--allow-privileged=true
--kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
--requestheader-extra-headers-prefix=X-Remote-Extra-
--requestheader-allowed-names=front-proxy-client
--client-ca-file=/etc/kubernetes/pki/ca.crt
--insecure-port=0
--authorization-mode=Node,RBAC
--etcd-servers=http://127.0.0.1:2379
1 回答
我认为你的卷曲路径有一点问题,它应该是
/api/v1/namespaces/...
而不是/v1/api/namespaces/...
. 参见例如https://kubernetes.io/docs/api-reference/v1.8/#list-62