Closed epDHowwD closed 7 months ago
From the provider-aws perspective, configuring the kubelet to use a credential helper is not hard. The question would be how to get https://github.com/kubernetes/cloud-provider-aws/blob/ca6c03d852a0a2823281add3c302d57bc3e293d6/cmd/ecr-credential-provider/main.go safely into the node.
/cc @oliver-goetz
/assign
Hi @kon-angelo,
I see https://github.com/gardener/gardener-extension-provider-aws/pull/854 is merged. Was this the only required change?
Thanks Gordon
@epDHowwD Yes, just this change. Just a note that is requires the gardener node agent to be enabled on the gardenlet.
How to categorize this issue?
/area control-plane os security /kind enhancement
What would you like to be added: We would like to request to have the binary
ecr-credential-provider
added to each node and configured to be used in kubelet in AWS.Background is CHANGELOG-1.27.md:
Why is this needed: When clusters use AWS kubelet credential provider to authenticate towards ECR on Gardener, an update to Kubernetes 1.27 is currently not possible without transferring the entire setup to a dockersecret based authentication model where a cron job resets the image pull secret token on daily basis. We would like to continue the account based authentication and authorization to ECR that is much more easy to handle.