-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.9 backports 2021-04-30 #15957
Merged
Merged
v1.9 backports 2021-04-30 #15957
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
pchaigno
added
kind/backports
This PR provides functionality previously merged into master.
backport/1.9
labels
Apr 30, 2021
pchaigno
force-pushed
the
pr/v1.9-backport-2021-04-30
branch
3 times, most recently
from
May 4, 2021 16:58
ca82e99
to
5040677
Compare
This commit also extends the Jenkinsfile to define KUBEPROXY in the same way as on 4.19. Signed-off-by: Paul Chaignon <paul@cilium.io>
[ upstream commit bfe16c2 ] This helper function will also encompass the 5.4 kernel in a subsequent commit, so we should reflect that in its name. Signed-off-by: Paul Chaignon <paul@cilium.io>
[ upstream commit a5b0ca7 ] Signed-off-by: Paul Chaignon <paul@cilium.io>
[ upstream commit 869a008 ] The bandwidth manager is the only feature we can enable on 5.4 but not on 4.19. It requires Linux v5.1. Signed-off-by: Paul Chaignon <paul@cilium.io>
[ upstream commit dfb8220 ] Since the goal of the 5.4 CI job is only to catch complexity issues, other test suites are skipped. They are not expected to help us catch new complexity issues compared to K8sVerifier and K8sDatapathConfig. Signed-off-by: Paul Chaignon <paul@cilium.io>
pchaigno
force-pushed
the
pr/v1.9-backport-2021-04-30
branch
from
May 4, 2021 18:44
5040677
to
b3da85f
Compare
test-1.17-5.4 |
test-backport-1.9 |
ti-mo
approved these changes
May 5, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, does it need more review?
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
May 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/backports
This PR provides functionality previously merged into master.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
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.
Skipped in this PR:
@
in clustermesh-apiserver helm chart #15934 -- Drop a@
in clustermesh-apiserver helm chart (@anthr76)Once this PR is merged, you can update the PR labels via: