Add Helm chart deployment

[ArieLevs]

Is this a bug fix or adding new feature? feature

What is this PR about? / Why do we need it? adding aws-fsx-csi-driver helm deployment

What testing is done? none

[k8s-ci-robot]

Welcome @ArieLevs!

It looks like this is your first PR to kubernetes-sigs/aws-fsx-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-fsx-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]

Hi @ArieLevs. 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]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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. I understand the commands that are listed here.

[ArieLevs]

I signed it

[leakingtapan]

/ok-to-test

[leakingtapan]

@ArieLevs seems CLA check is still complaining

[ArieLevs]

@jsafrane @justinsb
Can you please assist with merging this

btw, whats the next step,
i'd like to add a full example on how to install this #115 (comment)

[ArieLevs]

@leakingtapan Hi anything i can do to promote this?

[leakingtapan]

Sorry for the late reply. Please also update our e2e test to use the helm chat so that the chart is properly tested.

[ArieLevs]

@leakingtapan
How do i add helm in addition to kustomization in the e2e-test-config.yaml file?

[leakingtapan]

You will need to replace kustomization (which I think it's okay). See here for an example

[ArieLevs]

OK then, just thought it should be in addition to kustomize and not replace it.
will test the chart changes and update.

[leakingtapan]

Did you get a chance to update the e2e test?

[ArieLevs]

@leakingtapan
helm installation updated, installed and removed successfully from test log.
does the test fail related to this line? https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_aws-fsx-csi-driver/132/pull-aws-fsx-csi-driver-e2e/1238001042168221696#1:build-log.txt%3A1752

[leakingtapan]

@ArieLevs We are seeing similar issue here: kubernetes-sigs/aws-ebs-csi-driver#463 and we are still investigating the root cause. Thx for ur patience :)

[leakingtapan]

/retest

[leakingtapan]

Fixed by: #136

[leakingtapan]

/lgtm

[leakingtapan]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArieLevs, leakingtapan

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:

• OWNERS [leakingtapan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment