kubernetes-sigs
Add `metadata.namespace` to chart templates
This MR aligns with practices followed by the aws-ebs-csi-driver chart.
This also improves compatibility with ArgoCD, which otherwise will complain when it detects no namespace field for namespaced k8s resources. See screenshot below
The committers listed above are authorized under a signed CLA.
- :white_check_mark: login: Kellen275 (1852b04a40931a7283b5ec395a3e9ccac65d37be)
![linux-foundation-easycla[bot] avatar](https://avatars.githubusercontent.com/in/17893?v=4 "Published by a pub.dev verified publisher"){kind=small}
Welcome @Kellen275!
It looks like this is your first PR to kubernetes-sigs/aws-efs-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-efs-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. :smiley:
Hi @Kellen275. 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-sigs/prow repository.
Not quite sure why the EasyCLA is marked as "Not Covered" still. Received a confirmation email and all looks good?
@Kellen275 the commits show From: Kellen Sappington <[email protected]> as your email, if you match that with the email id you used for CLA that would make it work. You can also try associating this email with your github as an additional email as an alternative.
PS: https://github.com/kubernetes-sigs/aws-efs-csi-driver/commit/fa33fad37ffd42b009b3e33a3e0bb4c9a2c9b357.patch
@dims: GitHub didn't allow me to assign the following users: arnavgup1.
Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/ok-to-test
/assign @mskanth972 @arnavgup1
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-sigs/prow repository.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Kellen275, mskanth972
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [mskanth972]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment