Spinnaker使用服务帐户验证K8s。不是系统:匿名

时间:2018-01-22 09:13:09

标签: kubernetes spinnaker spinnaker-halyard

我看到使用system:anonymous用户的大三角帆来验证K8。但是我想要一个特定的用户(我已经在K8中创建)来验证K8。我在kubeconfig下面使用了用户veeru

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: RETRACTED
    server: https://xx.xx.xx.220:8443
  name: xx-xx-xx-220:8443
contexts:
- context:
    cluster: xx-xx-xx-220:8443
    namespace: default
    user: veeru/xx-xx-xx-220:8443
  name: area-51/xx-xx-xx-220:8443/veeru
current-context: area-51/xx-xx-xx-220:8443/veeru
kind: Config
preferences: {}
users:
- name: veeru/xx-xx-xx-220:8443
  user:
    client-certificate-data: RETRACTED
    client-key-data: RETRACTED

我在config(〜/ .hal / config)中指定(如hereuser,如下所示

kubernetes:
      enabled: true
      accounts:
      - name: my-k8s-account
        requiredGroupMembership: []
        providerVersion: V1
        dockerRegistries:
        - accountName: my-docker-registry2
          namespaces: []
        configureImagePullSecrets: true
        namespaces: ["area-51"]
        user: veeru
        omitNamespaces: []
        kubeconfigFile: /home/ubuntu/.kube/config
        oauthScopes: []
        oAuthScopes: []
      primaryAccount: my-k8s-account

但是大三角帆仍在使用system:anonymous

2018-01-22 08:35:13.929 ERROR 4639 --- [pool-4-thread-1] c.n.s.c.o.DefaultOrchestrationProcessor  : com.netflix.spinnaker.clouddriver.kubernetes.v1.deploy.exception.KubernetesOperationException: Get Service openshifttest-dev in area-51 for account my-k8s-account failed: User "system:anonymous" cannot get services in the namespace "area-51": User "system:anonymous" cannot get services in project "area-51"

有没有办法指定用户,大三角帆应该使用除system:anonymous

之外的已配置用户

UPDATE-1

关注:https://blog.spinnaker.io/spinnaker-kubernetes-rbac-c40f1f73c172

secret获得kubectl describe secret spinnaker-service-account-token-9sl6q并在kubeconfig中更新,如下所示

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://xx.xx.xx.xx:6443
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    namespace: webapp
    user: kubernetes-admin
  name: kubernetes-admin@kubernetes
- context:
    cluster: kubernetes
    user: spinnaker-service-account
  name: spinnaker-context
current-context: spinnaker-context
kind: Config
preferences: {}
users:
- name: kubernetes-admin
  user:
    client-certificate-data: REDACTED
    client-key-data: REDACTED
- name: spinnaker-service-account
  user:
    token: eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9....

比我跑sudo hal deploy

....
! ERROR Unable to communicate with your Kubernetes cluster: Failure
  executing: GET at: https://xx.xx.xx.xx:6443/api/v1/namespaces. Message:
  Forbidden! User spinnaker-service-account doesn't have permission. namespaces is
  forbidden: User "system:serviceaccount:default:spinnaker-service-account" cannot
  list namespaces at the cluster scope..
? Unable to authenticate with your Kubernetes cluster. Try using
  kubectl to verify your credentials.
....

我能跑

$ kubectl get namespace webapp
NAME      STATUS    AGE
webapp    Active    22m

我在webapp

中将spinnaker-service-account名称空间和用户指定为~/.hal/config

1 个答案:

答案 0 :(得分:1)

我正在使用GKE禁用基本身份验证。我让我的大三角帆使用我创建的专用K8s服务帐户。在我的~/.kube/config中,每个K8群集都有令牌。

users:
- name: gke_operation-covfefe-1_asia-east1_testing-asia-east1
  user:
    token: token1
- name: gke_operation-covfefe-1_europe-west1_testing-europe-west1
  user:
    token: token2
- name: gke_operation-covfefe-1_us-central1_testing-us-central1
  user:
    token: token3

我通过运行

获得了这些令牌
kubectl get secret spinnaker-service-account -o json \
 | jq -r .data.token \
 | base64 -d

然后手动更新我的~/.kube/config文件。

确保您的服务帐户具有所需的RBAC权限。请参阅blog post here

更新

还要确保为服务帐户提供所需的RBAC权限。请参阅上面博客文章的“角色”部分或guide here。使用kubectl测试RBAC权限时,请确保使用与Spinnaker正在使用的服务帐户相同的服务帐户。

更新2

如果您希望spinnaker作用于所有名称空间,请在RBAC中使用ClusterRole和ClusterRoleBinding。博客文章仅使用Role和RoleBinding,它将操作限制为特定的命名空间。有关Cluster *的方式,请参阅this guide。请注意PR to fix a typo here