Fix paths to dynamic_provisioning_s3 manifests

[nathanweeks]

Is this a bug fix or adding new feature?
Bug fix

What is this PR about? / Why do we need it?
In the dynamic_provisioning_s3 example, the code block that creates the StorageClass, PVC, and Pod uses pathnames for the dynamic_provisioning manifests, rather than the dynamic_provisioning_s3 example.

What testing is done?
Executed the updated commands while deploying/testing the AWS CSI FSx for Lustre driver in my EKS cluster.

[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: login-issues@jira.linuxfoundation.org

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.

[k8s-ci-robot]

Welcome @nathanweeks!

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 @nathanweeks. 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.

[leakingtapan]

/ok-to-test

[leakingtapan]

Should be

Suggested change

	>> kubectl apply -f examples/kubernetes/dynamic_provisioning/specs_s3/claim.yaml
	>> kubectl apply -f examples/kubernetes/dynamic_provisioning_s3/specs/claim.yaml

[leakingtapan]

Could you fix the path here to be kubectl apply -f examples/kubernetes/dynamic_provisioning_s3/specs/claim.yaml ? then the PR is good to merge.

[leakingtapan]

Same as above

[leakingtapan]

@nathanweeks thx for the fix. You will need to sign CLA for the PR to be merged 😃

[nathanweeks]

@leakingtapan I need to check with administration to verify that this can be considered an individual contribution. I should hopefully find out soon.

[leakingtapan]

@nathanweeks just checkin, got any luck to check with administration and address the comment?

[nathanweeks]

@leakingtapan : yes, and thanks for the reminder! I signed an individual CLA, updated the email associated with the commit, and force pushed to the dynamic-provisioning-s3 branch.

[leakingtapan]

Seems CLA check is still failed. Could you also address the comment? thx :)

[nathanweeks]

@leakingtapan : I finally figured it out. Sorry it took so long!

[leakingtapan]

Could you address my comment for your change? After that this PR is good to merge :)

[nathanweeks]

Done. Apologies for making a hassle the simplest of PRs!

[leakingtapan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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