-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The tagged - e.g. v4.0.1, v4.0.2 - versions manifests install pods from shifting images #1170
Comments
/cc @oshoval Thanks for bringing this to my attention Or. |
Since multus doesnt pin image correctly, pin it before deploying multus. See k8snetworkplumbingwg/multus-cni#1170 Signed-off-by: Or Shoval <oshoval@redhat.com>
Nope |
Since multus doesnt pin image correctly, pin it before deploying multus. See k8snetworkplumbingwg/multus-cni#1170 Signed-off-by: Or Shoval <oshoval@redhat.com>
I think two parts...
|
This problem is getting more problematic with time. I was going crazy because as I restarted nodes calico would stop working because multus couldn't find |
Unfortunately, the image in the daemonset for v4.0.2 uses a snapshot that is effectively latest. This change pins to `v4.0.2-thick` to match the deployment being used. See k8snetworkplumbingwg/multus-cni#1170 for more details.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
What happend:
When we use the manifest from a tagged version - e.g. v4.0.2 - the version of multus we are installing is not pinned, since this "snapshot" tag keeps getting overwritten everytime a PR is merged.
In essence, the
snapshot
andlatest
tags are essentially the same. Same thing happens with theirthick
counterparts.What you expected to happen:
A manifest present on a "tagged" commit should point to a pinned image, not to one that varies over time.
How to reproduce it (as minimally and precisely as possible):
Install a versioned manifest.
Anything else we need to know?:
Environment:
image path and image ID (from 'docker images')
kubectl version
):kubectl get net-attach-def -o yaml
)kubectl get pod <podname> -o yaml
)The text was updated successfully, but these errors were encountered: