Question

我有两个GCE集群，它们具有相同的配置，唯一的区别是kubernetes节点版本：1.4.7对1.5.4。第一个集群上的部署成功启动，但在第二个集群上的状态为403时失败。

以下是describe 1.5.4 pod的输出：

Name:       essence-elasticsearch-2766004759-lr5wf
Namespace:  default
Node:       gke-nts-elastic-test-default-pool-115230a1-p17s/10.128.0.2
Start Time: Tue, 28 Mar 2017 16:25:00 +0300
Labels:     app=essence-elasticsearch-app
        pod-template-hash=2766004759
Status:     Pending
IP:     10.104.0.9
Controllers:    ReplicaSet/essence-elasticsearch-2766004759
Containers:
  essence-elasticsearch:
    Container ID:   
    Image:      gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032
    Image ID:       
    Port:       9200/TCP
    Requests:
      cpu:      100m
    State:      Waiting
      Reason:       ImagePullBackOff
    Ready:      False
    Restart Count:  0
    Volume Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-s0rp8 (ro)
    Environment Variables:  <none>
Conditions:
  Type      Status
  Initialized   True 
  Ready     False 
  PodScheduled  True 
Volumes:
  default-token-s0rp8:
    Type:   Secret (a volume populated by a Secret)
    SecretName: default-token-s0rp8
QoS Class:  Burstable
Tolerations:    <none>
Events:
  FirstSeen LastSeen    Count   From                                SubObjectPath               Type        Reason      Message
  --------- --------    -----   ----                                -------------               --------    ------      -------
  14m       14m     1   {default-scheduler }                                            Normal      Scheduled   Successfully assigned essence-elasticsearch-2766004759-lr5wf to gke-nts-elastic-test-default-pool-115230a1-p17s
  14m       3m      7   {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}   spec.containers{essence-elasticsearch}  Normal      Pulling     pulling image "gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032"
  14m       3m      7   {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}   spec.containers{essence-elasticsearch}  Warning     Failed      Failed to pull image "gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032": Error: Status 403 trying to pull repository en-development/essence-elasticsearch: "Unable to access the repository: en-development/essence-elasticsearch; please verify that it exists and you have permission to access it."
  14m       3m      7   {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}                       Warning     FailedSync  Error syncing pod, skipping: failed to "StartContainer" for "essence-elasticsearch" with ErrImagePull: "Error: Status 403 trying to pull repository en-development/essence-elasticsearch: \"Unable to access the repository: en-development/essence-elasticsearch; please verify that it exists and you have permission to access it.\""

  14m   8s  59  {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}   spec.containers{essence-elasticsearch}  Normal  BackOff     Back-off pulling image "gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032"
  14m   8s  59  {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}                       Warning FailedSync  Error syncing pod, skipping: failed to "StartContainer" for "essence-elasticsearch" with ImagePullBackOff: "Back-off pulling image \"gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032\""

Answer 1

两个集群是否在同一个项目中？看起来第二个人不能拉gcr.io/en-development/essence-elasticsearch

错误：状态403尝试拉出存储库。 kubernetes 1.5.4具体

1 个答案: