【发布时间】:2018-08-08 04:41:41
【问题描述】:
我在 gce 中有一个 mongo 数据库。 (配置见下文)
当我将它部署到 1.7.12-gke.1 时,一切正常。这意味着 sidecar 会解析 pod 和链接
现在,当我将相同的配置部署到 1.8.7-gke.1 时,会导致缺少列出 pod 的权限,请参见下文。
我不明白发生了什么变化。我假设我需要为用户帐户分配特定权限,对吗?
我错过了什么?
错误日志
message: 'pods is forbidden: User "system:serviceaccount:default:default" cannot list pods at the cluster scope: Unknown user "system:serviceaccount:default:default"',
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | status: 'Failure',
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | metadata: {},
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | apiVersion: 'v1',
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | { kind: 'Status',
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | message:
mongo-sidecar | Feb 28, 2018, 11:04:19 AM | Error in workloop { [Error: [object Object]]
mongo-sidecar | Feb 28, 2018, 11:04:14 AM | statusCode: 403 }
mongo-sidecar | Feb 28, 2018, 11:04:14 AM | code: 403 },
mongo-sidecar | Feb 28, 2018, 11:04:14 AM | details: { kind: 'pods' },
mongo-sidecar | Feb 28, 2018, 11:04:14 AM | reason: 'Forbidden',
配置:
---
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: fast
provisioner: kubernetes.io/gce-pd
parameters:
type: pd-ssd
---
apiVersion: v1
kind: Service
metadata:
name: mongo
labels:
name: mongo
spec:
ports:
- port: 27017
targetPort: 27017
clusterIP: None
selector:
role: mongo
---
apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
name: mongo
spec:
serviceName: "mongo"
replicas: 3
template:
metadata:
labels:
role: mongo
environment: test
spec:
terminationGracePeriodSeconds: 10
containers:
- name: mongo
image: mongo:3.4.9
command:
- mongod
- "--replSet"
- rs0
- "--smallfiles"
- "--noprealloc"
ports:
- containerPort: 27017
volumeMounts:
- name: mongo-persistent-storage
mountPath: /data/db
- name: mongo-sidecar
image: cvallance/mongo-k8s-sidecar
env:
- name: MONGO_SIDECAR_POD_LABELS
value: "role=mongo,environment=test"
volumeClaimTemplates:
- metadata:
name: mongo-persistent-storage
annotations:
volume.beta.kubernetes.io/storage-class: "fast"
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 5Gi
【问题讨论】:
-
> 未知用户 "system:serviceaccount:default:default"' 默认服务帐户应该存在。您可以执行“kubectl get serviceAccounts”并查看您有一个名为“default”的帐户吗?
-
同时运行“kubectl get ns”来查看是否有默认命名空间(理想情况下应该有默认服务帐户)
-
使用 RBAC 是 1.8 的默认设置。
-
正确的 RBAC 是触发器。在 1.7 中,旧版身份验证选项默认启用,而在 1.8 中则不启用。 @JonahBenton 如果您发布带有屏幕截图作为解决方案的帖子,我会将其标记为解决方案。当我将遗留身份验证选项设置为启用时,这是有效的。还值得注意的是,将 1.7 集群升级到 1.8 会启用旧版身份验证,这就是另一个 1.8 集群正常工作的原因
-
也许您可以将此信息添加到问题中或提交答案以帮助将来可能遇到此问题的其他人?
标签: kubernetes google-kubernetes-engine kubernetes-security kubernetes-mongodb-sidecar