-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
ingress: Add conformance test for KPR=false #27304
Merged
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
maintainer-s-little-helper
bot
added
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Aug 6, 2023
sayboras
added
area/CI
Continuous Integration testing issue or flake
release-note/ci
This PR makes changes to the CI.
labels
Aug 6, 2023
maintainer-s-little-helper
bot
removed
the
dont-merge/needs-release-note-label
The author needs to describe the release impact of these changes.
label
Aug 6, 2023
sayboras
force-pushed
the
tam/nodeport-ingress-gw-api
branch
from
August 6, 2023 11:11
af1f740
to
911a473
Compare
/ci-ingress |
sayboras
force-pushed
the
tam/nodeport-ingress-gw-api
branch
from
August 6, 2023 11:23
911a473
to
1eb9428
Compare
/ci-ingress |
This is to test the combination of kubeProxyReplacement=false, but with nodePort.enabled=true. One limitation is that the direct traffic from LB service nodeport will not be redirected to Envoy proxy. Signed-off-by: Tam Mach <tam.mach@cilium.io>
Signed-off-by: Tam Mach <tam.mach@cilium.io>
sayboras
force-pushed
the
tam/nodeport-ingress-gw-api
branch
from
August 6, 2023 15:50
1eb9428
to
9fe1597
Compare
/test |
viktor-kurchenko
approved these changes
Aug 7, 2023
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.
LGTM.
qmonnet
approved these changes
Aug 7, 2023
4 tasks
qmonnet
added
backport-done/1.12
The backport for Cilium 1.12.x for this PR is done.
and removed
backport-pending/1.12
labels
Sep 8, 2023
tklauser
added
needs-backport/1.13
needs-backport/1.14
This PR / issue needs backporting to the v1.14 branch
labels
Sep 13, 2023
tklauser
removed
needs-backport/1.13
needs-backport/1.14
This PR / issue needs backporting to the v1.14 branch
labels
Sep 13, 2023
julianwiedmann
added
backport-done/1.13
The backport for Cilium 1.13.x for this PR is done.
and removed
backport-pending/1.13
labels
Sep 14, 2023
marseel
added a commit
to marseel/cilium
that referenced
this pull request
Oct 2, 2024
Currently, we were skipping internal to NodePort test for all matrix entries. Fixes: cilium#27304 Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
marseel
added a commit
to marseel/cilium
that referenced
this pull request
Oct 2, 2024
Currently, we were skipping internal to NodePort test for all matrix entries. Fixes: cilium#27304 Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
marseel
added a commit
that referenced
this pull request
Oct 2, 2024
Currently, we were skipping internal to NodePort test for all matrix entries. Fixes: #27304 Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 4, 2024
Currently, we were skipping internal to NodePort test for all matrix entries. Fixes: #27304 Signed-off-by: Marcel Zieba <marcel.zieba@isovalent.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/CI
Continuous Integration testing issue or flake
backport-done/1.12
The backport for Cilium 1.12.x for this PR is done.
backport-done/1.13
The backport for Cilium 1.13.x for this PR is done.
release-note/ci
This PR makes changes to the CI.
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.
This is to test the combination of kubeProxyReplacement=false, but with nodePort.enabled=true.