google cloud platform - Error: Status 403 trying to pull repository. kubernetes 1.5.4 specific -


i have 2 gce clusters, have identical configuration, difference kubernetes node version: 1.4.7 vs 1.5.4. deployment on first cluster starts, fails on second status 403.

here output of 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 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 secret)     secretname: default-token-s0rp8 qos class:  burstable tolerations:    <none> events:   firstseen lastseen    count                                  subobjectpath               type        reason      message   --------- --------    -----   ----                                -------------               --------    ------      -------   14m       14m     1   {default-scheduler }                                            normal      scheduled   assigned essence-elasticsearch-2766004759-lr5wf 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 pull image "gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032": error: status 403 trying pull repository en-development/essence-elasticsearch: "unable access repository: en-development/essence-elasticsearch; please verify exists , have permission access it."   14m       3m      7   {kubelet gke-nts-elastic-test-default-pool-115230a1-p17s}                       warning     failedsync  error syncing pod, skipping: failed "startcontainer" "essence-elasticsearch" errimagepull: "error: status 403 trying pull repository en-development/essence-elasticsearch: \"unable access repository: en-development/essence-elasticsearch; please verify exists , have permission 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 "startcontainer" "essence-elasticsearch" imagepullbackoff: "back-off pulling image \"gcr.io/en-development/essence-elasticsearch:f7bc95c_2e7df37_50683bc_d6e8032\"" 

are 2 clusters in same project? looks 2nd 1 can't pull gcr.io/en-development/essence-elasticsearch


Comments

Popular posts from this blog

javascript - Clear button on addentry page doesn't work -

c# - Selenium Authentication Popup preventing driver close or quit -

tensorflow when input_data MNIST_data , zlib.error: Error -3 while decompressing: invalid block type -