-
Notifications
You must be signed in to change notification settings - Fork 808
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
Add a1compat image to publish-ecr github action #1897
Add a1compat image to publish-ecr github action #1897
Conversation
Code Coverage DiffThis PR does not change the code coverage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
1 similar comment
/retest |
/test pull-aws-ebs-csi-driver-test-e2e-external-eks-windows |
Hi, how can I enable this in my EKS cluster? Should I deploy another daemon set with this image? |
Is this a bug fix or adding new feature?
CI
What is this PR about? / Why do we need it?
#1805 provided a workaround for the aws-ebs-csi-driver's minimal AL23 base image not working on
a1
instance family by building and maintaininga1compat
images (that are based off of an AL2 minimal base image) for use ona1
nodes.This PR automates the copying of this a1-compatible manifest to our public ECR repository.
Note: This step was placed before "Copy manifest list to ECR Public" so that the latest non-workaround manifest list shows up by default on our ECR repository.