Added test for Fortanix secret store CSI provider

[kiran-kannur]

/kind feature
/kind test

What this PR does / why we need it:
This PR adds an e2e Bats test suite for the new Fortanix Secret Store CSI Provider integration.

The test covers:

• Installation of the Fortanix CSI provider using the upstream deployment manifest
• Validation of SecretProviderClass creation referencing Fortanix DSM
• Verification that secrets from Fortanix DSM are mounted successfully into a test pod
• Basic cleanup and teardown steps to ensure the provider, SecretProviderClass, and API key secret are deleted cleanly after test completion

These tests are modeled after existing provider test suites (e.g., AWS, Azure, Vault) and ensure compatibility of the Fortanix provider with the secrets-store-csi-driver e2e test harness.

Which issue(s) this PR fixes:
Fixes #

Is this a chart or deployment yaml update?
No, this PR only adds test files under test/bats/ to include Fortanix provider validation.

Special notes for your reviewer:

• The Fortanix provider manifest is referenced from its official GitHub repository.
• Tests require the following environment variables to be set prior to execution:
  • FORTANIX_API_KEY
  • FORTANIX_DSM_ENDPOINT
  • FORTANIX_TEST_SECRET_NAME
• Verified against Kubernetes v1.30 and secrets-store-csi-driver v1.4.1.

TODOs:

• Added new Fortanix provider e2e test
• Verified successful run on kind/minikube
• Update provider documentation with test instructions
• (optional) Integrate into CI test matrix once provider image is public

[k8s-ci-robot]

@kiran-kannur: The label(s) kind/test cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature
/kind test

What this PR does / why we need it:
This PR adds an end-to-end Bats test suite for the new Fortanix Secret Store CSI Provider integration.

The test covers:

• Installation of the Fortanix CSI provider using the upstream deployment manifest
• Validation of SecretProviderClass creation referencing Fortanix DSM
• Verification that secrets from Fortanix DSM are mounted successfully into a test pod
• Basic cleanup and teardown steps to ensure the provider, SecretProviderClass, and API key secret are deleted cleanly after test completion

These tests are modeled after existing provider test suites (e.g., AWS, Azure, Vault) and ensure compatibility of the Fortanix provider with the secrets-store-csi-driver e2e test harness.

Which issue(s) this PR fixes:
Fixes #

Is this a chart or deployment yaml update?
No — this PR only adds test files under test/bats/ to include Fortanix provider validation.

Special notes for your reviewer:

• The Fortanix provider manifest is referenced from its official GitHub repository.
• Tests require the following environment variables to be set prior to execution:
• FORTANIX_API_KEY
• FORTANIX_DSM_ENDPOINT
• FORTANIX_TEST_SECRET_NAME
• The tests are designed to be self-contained and skip gracefully if these environment variables are not defined.
• Verified against Kubernetes v1.30 and secrets-store-csi-driver v1.4.1.

TODOs:

• Added new Fortanix provider e2e test
• Verified successful run on kind/minikube
• Update provider documentation with test instructions
• (optional) Integrate into CI test matrix once provider image is public

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.

[linux-foundation-easycla]

• ❌ - login: @kiran-kannur / name: Kiran Kannur . The commit (0ab6ba7) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

This issue is currently awaiting triage.

If secrets-store-csi-driver contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

Welcome @kiran-kannur!

It looks like this is your first PR to kubernetes-sigs/secrets-store-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/secrets-store-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 @kiran-kannur. Thanks for your PR.

I'm waiting for a github.com 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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kiran-kannur
Once this PR has been reviewed and has the lgtm label, please assign ritazh 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