stepan111 commented on issue #2485:
URL: https://github.com/apache/camel-k/issues/2485#issuecomment-876940651
Yes @nicolaferraro , I am using pull-secret trait for integration. Actually
I see 2 pods created when I apply integration.
And I found that there are 2 replica sets :
```
$ k get po
NAME READY STATUS RESTARTS
AGE
camel-k-operator-6f848d7b5c-9jrdn 2/2 Running 2
11h
gmail-7758f9577d-bhfz6 0/2 PodInitializing 0
13s
gmail-867d487988-sk9g9 1/2 ImagePullBackOff 0
13s
$ k get rs
NAME DESIRED CURRENT READY AGE
camel-k-operator-6f848d7b5c 1 1 1 13d
gmail-7758f9577d 0 0 0 3m46s
gmail-867d487988 1 1 1 3m46s
```
And rs that contain imagPullSecret is scaled to 0:
```
$ k get rs gmail-7758f9577d -o yaml | grep -A1 imagePullSecret
f:imagePullSecrets:
.: {}
--
imagePullSecrets:
- name: registry
$ k get rs gmail-867d487988 -o yaml | grep -A1 imagePullSecret
$
```
Seems that both replicaSets are revisions of deployment gmail made by
integration :
```
$ k rollout history deployment gmail
deployment.apps/gmail
REVISION CHANGE-CAUSE
1 <none>
2 <none>
```
And second revision doesn't contain imagePull secrets(maybe it is patched
not properly or so).
From events I see that both pods assigned to one node:
```
12m Normal Scheduled
pod/gmail-7758f9577d-bhfz6 Successfully assigned
camel-k/gmail-7758f9577d-bhfz6 to
gke-sandbox-blue-sandbox-blue-default-f0ed42c1-d6fq
12m Normal Scheduled
pod/gmail-867d487988-sk9g9 Successfully assigned
camel-k/gmail-867d487988-sk9g9 to
gke-sandbox-blue-sandbox-blue-default-f0ed42c1-d6fq
```
So I am thinking that first pod download image on node and second using this
image while node is up. And when node crashes active replicaSet can't pull
image.
Thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
