Skip to content
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

deploy: Add resizer and snapshotter images to kustomization #1080

Conversation

maxbrunet
Copy link
Contributor

Is this a bug fix or adding new feature?

Feature

What is this PR about? / Why do we need it?

  • Set csi-snapshotter and csi-resizer images in kustomization.yaml like the others
  • Add their Public ECR counterparts in ECR overlay

What testing is done?

Deployed images from Public ECR on EKS

@k8s-ci-robot
Copy link
Contributor

Welcome @maxbrunet!

It looks like this is your first PR to kubernetes-sigs/aws-ebs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-ebs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 6, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @maxbrunet. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 6, 2021
@wongma7
Copy link
Contributor

wongma7 commented Oct 6, 2021

/ok-to-test
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 6, 2021
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 6, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maxbrunet, wongma7

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2021
@k8s-ci-robot k8s-ci-robot merged commit d90b8ea into kubernetes-sigs:master Oct 6, 2021
@andymset
Copy link

andymset commented Oct 8, 2021

This PR references an image which doesn't appear to exist:

  - name: k8s.gcr.io/sig-storage/csi-resizer
    newName: public.ecr.aws/eks-distro/kubernetes-csi/external-resizer
    newTag: v1.0.1-eks-1-18-3
docker pull public.ecr.aws/eks-distro/kubernetes-csi/external-resizer:v1.0.1-eks-1-18-3
Error response from daemon: manifest for public.ecr.aws/eks-distro/kubernetes-csi/external-resizer:v1.0.1-eks-1-18-3 not found: manifest unknown: Requested image not found

Images with tags v1.0.1-eks-1-18-1 and v1.1.0-eks-1-18-3 do exist.

https://gallery.ecr.aws/eks-distro/kubernetes-csi/external-resizer

@maxbrunet
Copy link
Contributor Author

Oops, I had a last minute change of mind about the tag, and I thought I tested it, I will submit another PR to fix that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants