Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enhanced
s3-syncer
deployment to support bothbatch/v1beta1
andbatch/v1
API versions for CronJobs, ensuring compatibility with Kubernetes clusters v1.21 and above.What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
I used the community-components submodule to deploy
s3-syncer
on cluster v1.28. I found batch/v1beta is deprecated. So I went with batch/v1.We can use Helm's
Capabilities.APIVersions.Has
feature to support both apiVersions to deploy them on any kubernetes versionDoes this PR introduce a user-facing change?: