-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
AWS EBS CSI implementation #5549
AWS EBS CSI implementation #5549
Conversation
392bf05
to
706c963
Compare
/assign @Miouge1 |
roles/kubernetes-apps/csi_driver/aws_ebs/templates/aws-ebs-csi-controllerservice.yml.j2
Outdated
Show resolved
Hide resolved
Also nice if you can add yourself as an approver in |
Ok, but how do I do that? >_< |
You can see an example of that in #5753 |
706c963
to
60d0ad7
Compare
@Miouge1 I made the necessary changes and tested on AWS that everything was working fine and that EBS volumes were created and assigned to pods when PVCs are created, then destroyed and removed from AWS when deleted. @bl0m1 @StevenReitsma Can you please see if the code looks legit? As it touches some parts both of you wrote. |
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.
The EBS part looks good.
I have created a pr to make is easier to apply csi-drivers using a new tag. also I guess you accidentally put your name in the wrong section in the owners file
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.
Haven't really checked the EBS code but the changes to the CSI download role look good to me!
It would be great if you could add some documentation. |
Documentation added 👍 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alijahnas, LuckySB 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 |
@Miouge1 Hi, can you please lgtm this so that it is in? Thanks |
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.
Well done @alijahnas !
/lgtm
* AWS EBS CSI implementation * Fixing image repos * Add OWNERS file * Fix expressions * Add csi-driver tag * Add AWS EBS prefix to variables * Add AWS EBS CSI Driver documentation
What type of PR is this?
This is the implementation of the AWS EBS CSI driver and it's storage class deployment.
/kind feature
What this PR does / why we need it:
The k8s in-tree volume provisioners are deprecated and are going to be removed from Kubernetes. Volume provisioning should now be done through CSI drivers.
This is the implementation of the AWS EBS CSI driver.
Special notes for your reviewer:
Still needs documentation that I can do as the one for Cinder CSI driver: https://github.com/kubernetes-sigs/kubespray/blob/master/docs/cinder-csi.md
Does this PR introduce a user-facing change?:
User needs to know that the old provisioner is deprecated and needs to be changed to the CSI one.