-
Notifications
You must be signed in to change notification settings - Fork 748
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
imagePullPolicy management doesn't supported by cluster-addon json schema #3059
Comments
Is there any work around while using terraform to change this? The fix here - https://github.com/aws/amazon-vpc-cni-k8s/pull/3010/files seems like we want to respect the imagepullpolicy, which is a reasonable request. I am not sure how terraform automation will play part. This is not configuration schema value of aws-cni. It is helm chart configuration for image pull. |
I wasn't sure how critical of a change it is for you. The value of That said; we can enhance the Managed Addon Schema to suppor this override. This will come in an internal change to the VPC-CNI addon and will support an extra schema field like this.
And will be similar how to some other addons like pod-identity-agent provides.
|
@orsenthil hi! thanks for your input here. we're highly appreciate your involvement into this.
I would say, that we as the engineering team which using EKS would like to manage ImagePullPolicy by ourself, so for us it's a bit critical just from point to have the options for choose. We want to decide by ourselves what value for ImagePullPolicy we want to use, so having options to overwrite would make our work easier rather we have now. We're understand that CNI shouldn't restart a lot, we have our own technical reasons why we need this options
That's brilliant and exactly what we looking for! If we can have the same options in cluster-addon-schema, but for vpc-cni, we would highly appreciate for implementing that |
@zemliany - Thanks for this feedback. We will implement this in the next version of VPC CNI 1.18.6 scheduled to be released by end of october. |
@orsenthil thanks for update. we'll be wait for this implementation! highly appreciate for your support on this |
any updates/progress about that? |
This is fixed with the latest addon v1.18.6. Please verify this when it is available in your region. The deployment is in progress.
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
@orsenthil sir, sorry for bother, just one minor question: how much time should pass for deployment? we've not received new versionn
Would you mind to guide us, how much time required for deployment of the new VPC CNI version? |
addon-name should be vp-cni
|
@orsenthil my apologies, sir, for such inattentive from my side, it's embarrassing. Thanks for your understanding and valuable support. Much appreciated. All works as expected, we have checked cluster-addon-schema and now we're able to overwrite pullPolicy natively. Thanks! |
What happened:
Hi team! With recent changes that started from release 1.18.4 https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.18.4 we're noticed that there was a change introduced to respect ImagePullPolicy for daemonset
initContainer
andNodeAgent
that strictly pointed toAlways
#3010 and seems there is no possibility to overwrite/manage this value by any automation, because currently such settings is not supported by cluster-addon json schemaaws eks describe-addon-configuration --addon-name vpc-cni --addon-version v1.18.5-eksbuild.1 | jq -r '.configurationSchema' | python -m json.tool
Attach logs
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):v1.30.3-eks-a18cd3a
v1.18.5-eksbuild.1
cat /etc/os-release
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: