CI: Remove Debian 10 support & macvlan test move to Debian 11 #11347
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
k8s-ci-robot
added
release-note
k8s-ci-robot
added
the
size/M
|
/ok-to-test |
k8s-ci-robot
added
the
ok-to-test
tico88612
force-pushed
the
remove/debian-10-support
branch
from
880c7a0 to
1bfcab1
Compare
ant31
reviewed
Jul 2, 2024
ant31
reviewed
Jul 2, 2024
tico88612
force-pushed
the
remove/debian-10-support
branch
from
1bfcab1 to
fb7fcb0
Compare
tico88612
changed the title
|
/retest-failed |
|
/approve |
k8s-ci-robot
added
the
approved
tico88612
force-pushed
the
remove/debian-10-support
branch
from
fb7fcb0 to
e46b5ed
Compare
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
tico88612
force-pushed
the
remove/debian-10-support
branch
from
e46b5ed to
0ca6e4f
Compare
Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
tico88612
force-pushed
the
remove/debian-10-support
branch
from
0ca6e4f to
aeeec26
Compare
|
Macvlan test will fail at Debian 12. I changed it to Debian 11. https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/7255832762 |
|
/approve Can you create an issue for macvlan ? Anyidea why it failes with 12 but not 11? |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ant31, tico88612 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 |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
tico88612
changed the title
|
/cherrypick release-2.25 |
|
@tico88612: new pull request created: #11429 In response to this:
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. |
kpoxo6op
pushed a commit
to kpoxo6op/kubespray
that referenced
this pull request
Dec 27, 2024
…etes-sigs#11347) * CI: macvlan test switch to debian 11 & default job Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com> * CI: cilium-svc-proxy test switch to debian 12 Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com> * CI: remove debian 10 test Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com> * Docs: remove debian 10 support Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com> --------- Signed-off-by: tico88612 <17496418+tico88612@users.noreply.github.com>
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:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
This PR cleans all Debian 10 related files. If I have missed any, please correct me in the review.
Does this PR introduce a user-facing change?: