Drop calico v3.21 support #9515
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At the upstream calico development, the v3.21 branch is not updated over 2 monthes. In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+ This drops the v3.21 support to solve the issue.
k8s-ci-robot
added
kind/cleanup
k8s-ci-robot
added
approved
|
@cristicalin has taken huge effort for this area. /cc @cristicalin |
k8s-ci-robot
added
the
do-not-merge/hold
Should we push this one forward ? as Cristian is not available lately |
I see. It is fine to go forward with us in the community. /hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, oomichi 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 |
Closed
enneitex
pushed a commit
to enneitex/kubespray
that referenced
this pull request
Jan 25, 2023
At the upstream calico development, the v3.21 branch is not updated over 2 monthes. In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+ This drops the v3.21 support to solve the issue.
HoKim98
pushed a commit
to ulagbulag/kubespray
that referenced
this pull request
Mar 8, 2023
At the upstream calico development, the v3.21 branch is not updated over 2 monthes. In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+ This drops the v3.21 support to solve the issue.
nolimitkun
pushed a commit
to nolimitkun/kubespray
that referenced
this pull request
Mar 19, 2023
At the upstream calico development, the v3.21 branch is not updated over 2 monthes. In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+ This drops the v3.21 support to solve the issue.
pedro-peter
pushed a commit
to pedro-peter/kubespray
that referenced
this pull request
May 8, 2024
At the upstream calico development, the v3.21 branch is not updated over 2 monthes. In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+ This drops the v3.21 support to solve the issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
At the upstream calico development, the v3.21 branch is not updated over 2 monthes.
In addition, unnecessary error message is output at Kubespray deployment due to different URLs for calico v3.21 or v3.22+.
This drops the v3.21 support to solve the issue.
Which issue(s) this PR fixes:
Fixes #9514
Special notes for your reviewer:
#9473 is for adding newer version support of calico.
Does this PR introduce a user-facing change?: