You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a ImageListPullJob to pull images in some nodes,and set imagePullPolicy: Always to pull the latest tag whatever image exists in these nodes.
but unexpectedly,it's not working,when i build a new image and tag it harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe:latest,i push it to my harbor registry,repoDigests update to "sha256:d9d70b3d".the next day imagepulljob run again,imageid in all nodes don't update,then i clean all images in node01,it can pull the real latest iamges.
apiVersion: apps.kruise.io/v1alpha1
kind: ImageListPullJob
metadata:
name: job-with-always
spec:
images:
- 'harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe:latest'
imagePullPolicy: Always
parallelism: 2 # [optional] the maximal number of Nodes that pull this image at the same time, defaults to 1
# pullSecrets:
# - idc-harbor
selector: # [optional] the names or label selector to assign Nodes (only one of them can be set)
names:
- gz-dr-node01
- gz-dr-node02
- gz-dr-node03
- gz-dr-node04
- gz-dr-node05
- gz-dr-node06
- gz-dr-node07
- gz-dr-node08
# matchLabels:
# env: prod
completionPolicy:
type: Never # [optional] defaults to Always
#activeDeadlineSeconds: 1200 # [optional] no default, only work for Always type
#ttlSecondsAfterFinished: 300 # [optional] no default, only work for Always type
pullPolicy: # [optional] defaults to backoffLimit=3, timeoutSeconds=600
backoffLimit: 3
timeoutSeconds: 300
pullSecrets:
- idc-harbor
@zmberg Maybe we should talk here and leave every comment, because some other developer may have the same issue which they can search this resolved issue then.
what's wrong
I created a ImageListPullJob to pull images in some nodes,and set imagePullPolicy: Always to pull the latest tag whatever image exists in these nodes.
but unexpectedly,it's not working,when i build a new image and tag it harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe:latest,i push it to my harbor registry,repoDigests update to "sha256:d9d70b3d".the next day imagepulljob run again,imageid in all nodes don't update,then i clean all images in node01,it can pull the real latest iamges.
image inspect in node04
"status": {
"id": "sha256:d5b08854cde36b2531131773a36b6920ee650b3575dbe91982451a39760dca5e",
"repoTags": [
"harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe:latest"
],
"repoDigests": [
"harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe@sha256:41f571b072b5f0a5ee85b1393dbd95de6bc3cc13a5bc826a412f9a0f066e6c6e"
],
"size": "30127273",
"uid": null,
"username": "",
"spec": null,
"pinned": false
}
image inspect in node01
"status": {
"id": "sha256:91849a5248a24bf524879ddb34192ddd291dc547c229abc6364d3d25c0db7788",
"repoTags": [
"harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe:latest"
],
"repoDigests": [
"harbor.jusda.int/juslink-ms/juslink-4pl-spm-fe@sha256:d9d70b3d97587d027ce12d773cca1ed66e6d16dd8a563a5b9c7c216d84d7dbda"
],
"size": "30127842",
"uid": null,
"username": "",
"spec": null,
"pinned": false
}
version
k8s:v1.26.15
containerd://1.7.13
kruise:v1.7.2
ImageListPullJob:
ImagePullJob:
nodeimage:gz-dr-node01
nodeimage:gz-dr-node04
logs:
gz-dr-node04
gz-dr-node01
The text was updated successfully, but these errors were encountered: