Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix batch/v1beta1 deprecated #118

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Conversation

mohamed-rafraf
Copy link
Member

Enhanced s3-syncer deployment to support both batch/v1beta1 and batch/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 version

Does this PR introduce a user-facing change?:

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 version

Signed-off-by: Mohamed Rafraf <[email protected]>
@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 20, 2024
@hc2p
Copy link
Contributor

hc2p commented Feb 20, 2024

/lgtm

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2024
@kubermatic-bot
Copy link

LGTM label has been added.

Git tree hash: de01ee8b1b74a9b67f94e50e0af40455ee0eb096

@moelsayed moelsayed added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 11, 2024
@kubermatic-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot merged commit fa165c5 into master Apr 11, 2024
5 checks passed
@kubermatic-bot kubermatic-bot deleted the mohamed-rafraf-patch-1 branch April 11, 2024 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants