Add podLabels parameter

[bueti]

Is this a bug fix or adding new feature?
This PR is adding a new feature - enabling users to specify custom pod labels for the FSx CSI driver controller and node components.

What is this PR about? / Why do we need it?
This PR enhances the AWS FSx CSI driver Helm chart by parameterizing pod labels for both the controller deployment and node daemonset. This allows users to add custom labels to the pods, which can be useful for:

• Better pod identification and filtering in large clusters
• Integration with monitoring, security, or compliance tools that rely on pod labels
• Enabling organization-specific labeling standards

The implementation adds new configuration options (controller.podLabels and node.podLabels) to the values.yaml file, which are then applied to the respective pod template specs.

What testing is done?
The changes have been tested by:

• Verifying that the chart installs successfully with default values
• Testing the chart with custom pod labels specified for both controller and node components

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: bueti / name: Benjamin Bütikofer (0ab1708, 9e98beb)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bueti
Once this PR has been reviewed and has the lgtm label, please assign torredil for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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]

Welcome @bueti!

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

[kuba-wolf]

Should this be an if instead of with?

[bueti]

not sure it makes a big difference, but i changed it anyways :)

[kuba-wolf]

Yup basically no difference, we just try to stay consistent with other csi drivers when they already have things set

[kuba-wolf]

Hi @bueti, thanks for the PR. I think you might want to use if instead of with just looking at some other csi drivers. Once you've done the EasyCLA authorization we can move forward with the PR

[bueti]

Hi @bueti, thanks for the PR. I think you might want to use if instead of with just looking at some other csi drivers. Once you've done the EasyCLA authorization we can move forward with the PR

hey @kuba-wolf , thanks for your review. since this is the first contribution to a cncf repo for my company getting cla done might take a few days, but i am working on it!

[kuba-wolf]

@bueti Can you squash your commits into a single one? Otherwise this looks good to me

[bueti]

@bueti Can you squash your commits into a single one? Otherwise this looks good to me

finally got the CLA sorted. Squashed commits and merged master.

[bueti]

@kuba-wolf if you could have another look and give the ok for the tests?

[k8s-ci-robot]

PR needs rebase.

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.