Sync with upstream

[LiyangW]

No description provided.

[cert-manager-prow]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• 9420237 feat: initial implementation of ibm cis webhook
• 9e0ffef feat: misc security improvements
• d498adc fix(makefile): build native arch instead of always trying to build
• b1c7b93 fix: findLongestMatchingZone now works as intended
• 1ca1754 feat(helm chart): add poddisruptionbudget
• 2e95f8d fix(helm-chart): add a network policy allowing egress to ibm cis
• 207faee style(helm-chart): add well-known annotations and labels
• 05457e1 chore(helm chart): release 2.0.0
• 9b3fc52 chore: add CODEOWNERS
• c4997c5 Create .whitesource
• e8e2bdf Add Contrast SAST Scan workflow
• 8f1d8ef Update Contrast SAST Scan workflow
• 7e6ac90 Delete Contrast SAST Scan workflow file
• ac7f1e5 Add Contrast SAST Scan workflow child
• 8363c73 chore: sync CODEOWNERS
• dd03153 ci(dependencies): add workflow
• 8ea34a3 ci(dependencies): remove workflow
• ee47577 fix(deps): update module github.com/ibm-cloud/bluemix-go to v0.0.0-20240423071914-9e96525baef4 (Improvments #24)
• a80d6d5 fix(deps): update module github.com/cert-manager/cert-manager to v1.15.1 (Change apiVersion of cert-manager in APIService to the up to date one #17)
• ee75db2 fix(deps): update kubernetes packages to v0.30.2 (Add test for getting config from yaml file #16)
• 8177a4b fix(deps): update kubernetes packages to v0.30.3 (failed with: OpenAPI spec does not exist #27)
• 2a54aa2 fix(deps): update github.com/ibm-cloud/bluemix-go digest to 078fcb3 (Circleci project setup #28)
• 5c6056c chore(deps): bump (Update golang modules #31)
• 9e2758e fix(deps): update module github.com/cert-manager/cert-manager to v1.15.2 (integration test example does not work with certmanager v1.5.0 #32)
• e892d20 chore(deps): update dependency go to v1.22.6 (Use challenge namespace if issuers empty #25)
• 07b7b81 chore(deps): update dependency go to v1.23.0 (update cert-manager version and kubebuilder #34)
• 13fbc8c fix(deps): update module github.com/cert-manager/cert-manager to v1.15.3 (update cert-manager version and kubebuilder #36)
• d397e35 build(modules): upgrade to fix vul
• 83d3694 build(apiserver): upgrade to ffix vul
• c8ded16 Revert "build(apiserver): upgrade to ffix vul"
• db7b968 chore(deps): update dependency go to v1.23.1 (Add logging example #37)
• 8301b73 fix(deps): update kubernetes packages to v0.31.1 (update cert-manager version and kubebuilder #35)
• 9cd533c build(test.yaml): workflow dispatch
• 14cc75c sync deps

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

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign irbekrm for approval. For more information see the Kubernetes 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

[cert-manager-prow]

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.

[cert-manager-prow]

Hi @LiyangW. Thanks for your PR.

I'm waiting for a cert-manager 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.