我需要从启用RBAC的集群中同一命名空间中的另一个Pod调用Kubernetes作业。使用C#Kubernetes client library创建作业。此任务在未启用RBAC的测试环境中可以正常工作。
遵循Kubernetes documentation创建服务帐户后,我具有以下YAML。
apiVersion: v1
kind: ServiceAccount
metadata:
name: x20-jobs-sp
namespace: prod
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
namespace: prod
name: x20-jobs-sp-role
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["batch", "extensions"]
resources: ["jobs"]
verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: x20-jobs-sp-rolebinding
namespace: prod
subjects:
- kind: ServiceAccount
# Reference to ServiceAccount kind's `metadata.name`
name: x20-jobs-sp
# Reference to ServiceAccount kind's `metadata.namespace`
namespace: prod
roleRef:
kind: ClusterRole
name: x20-jobs-sp-role
apiGroup: rbac.authorization.k8s.io
这是调用作业的代码。
var job = await client.CreateNamespacedJobAsync(new k8s.Models.V1Job
{
Metadata = new k8s.Models.V1ObjectMeta
{
Name = safeName
},
Spec = new k8s.Models.V1JobSpec
{
Template = new k8s.Models.V1PodTemplateSpec
{
Spec = new k8s.Models.V1PodSpec
{
Containers = new List<k8s.Models.V1Container>()
{
new k8s.Models.V1Container
{
Image = $"{_containerRegistry}/{jobName}:{_imageTag}",
Args = args.Select(x => x.ToString()).ToList(),
Env = GetDefaultEnvironment(),
Name = safeName,
ImagePullPolicy = "Always"
}
},
ImagePullSecrets = new List<k8s.Models.V1LocalObjectReference>
{
new k8s.Models.V1LocalObjectReference
{
Name = _containerRegistry
}
},
RestartPolicy = "OnFailure",
ServiceAccountName = "x20-jobs-sp" // jobs service principal
}
},
TtlSecondsAfterFinished = _ttlSecondsAfterFinished
}
}, _namespace);
此正确创建的是ServiceAccount,ClusterRole和ClusterRoleBinding,但是尝试调用任务仍然会导致Forbidden
结果。
我已经为ClusterRole尝试了许多不同的选项,包括使用内置的cluster-admin
角色,但都没有成功。已经使用kubectl auth can-i
命令对此进行了测试。
我想念什么?
答案 0 :(得分:2)
因此,原来的原因是试图调用作业的pod的默认服务帐户没有必要的角色绑定。
我通过将cluster-admin
RoleBinding添加到命名空间中的默认服务帐户并调用该作业来进行了测试。
kubectl create clusterrolebinding --user system:serviceaccount:prod:default prod-cluster-admin --clusterrole cluster-admin