将 AWS IAM 角色分配给 AWS EKS Jenkins 代理 Pod

Question

我正在使用不同的代理配置基于 AWS EKS 的 Jenkins 主站。 Jenkins 可以很好地启动新的 pod。 问题是当我尝试通过服务帐户将 IAM 角色分配给该 Pod 时。 它只是不捡起来。 两天前它起作用了，但我不得不删除 jenkins_home 目录，所以我又从头开始了。

服务帐户是这样的：

$ kubectl get serviceaccount -n jenkins jenkins-agents -o yaml 
apiVersion: v1
automountServiceAccountToken: false
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::1111111111111:role/clz_deployer_role
  creationTimestamp: "2020-09-22T15:19:55Z"
  name: jenkins-agents
  namespace: jenkins
  resourceVersion: "145998"
  selfLink: /api/v1/namespaces/jenkins/serviceaccounts/jenkins-agents
  uid: 8d55df19-140d-4703-bc61-886a25a20eac
secrets:
- name: jenkins-agents-token-mmxb8

我将服务帐户的名称传递给 Pod 配置：

metadata:
  labels:
    jenkins/label: jenkins-slave-aws-cli
  name: awsclislave
  # annotations:
  #   eks.amazonaws.com/role-arn: arn:aws:iam::1111111111111:role/clz_deployer_role
spec:
  containers:
    - image: pquery/jnlp-slave-docker:latest
      imagePullPolicy: IfNotPresent
      name: awsclislave
      command:
        - cat
      resources:
        limits:
          memory: 512Mi
          cpu: 512m
        requests:
          memory: 512Mi
          cpu: 512m
      tty: true
      volumeMounts:
        - mountPath: /home/jenkins
          name: workspace-volume
          readOnly: false
      workingDir: /home/jenkins
  hostNetwork: false
  nodeSelector:
    kubernetes.io/os: linux
  restartPolicy: Never
  serviceAccount: jenkins-agents
  volumes:
    - emptyDir:
        medium: ""
      name: workspace-volume

我尝试使用注释（评论）但它也不起作用。 错误消息始终相同：

com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: User: arn:aws:sts::1111111111111:assumed-role/shared_services20200922074522597500000008/i-0c1c41c96e96e82df is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::2222222222222:role/clz_aws_cicd_access (Service: AWSSecurityTokenService; Status Code: 403; Error Code: AccessDenied; Request ID: bfe43133-13c1-4cdb-b4b9-626cf11def58; Proxy: null)

它尝试使用实例角色而不是附加到服务帐户的角色来执行操作。 有谁知道问题是什么？

Answer 1

问题出在 clz_deployer_role IAM 角色信任关系上，其中命名空间错误。 更具体地说，内部条件：

"条件": { "StringEquals": { "oidc.eks.eu-west-1.amazonaws.com/id/C1B7F80BE15AC5C89956D55EF7E3FFC5:sub": "system:serviceaccount:jenkins:jenkins-agents" } }

“system:serviceaccount:jenkins:jenkins-agents”字符串是“system:serviceaccount::<service_account_name>”并且命名空间指向“default”，当它在“jenkins”中时它现在工作得很好