-
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
Ingress id backport 1.13 #25019
Merged
michi-covalent
merged 2 commits into
cilium:v1.13
from
jrajahalme:ingress-id-backport-1.13
Apr 25, 2023
Merged
Ingress id backport 1.13 #25019
michi-covalent
merged 2 commits into
cilium:v1.13
from
jrajahalme:ingress-id-backport-1.13
Apr 25, 2023
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
jrajahalme
added
kind/backports
This PR provides functionality previously merged into master.
backport/1.13
This PR represents a backport for Cilium 1.13.x of a PR that was merged to main.
labels
Apr 20, 2023
/test-backport-1.13 |
/test-1.18-4.19 |
/test-1.21-4.19 |
/test-1.26-net-next |
[ upstream commit f94351b ] Some Envoy API fields were renamed for clarity. Update Envoy image and API to revert Envoy TcpPorxy API change done earlier in cilium/proxy patches to support WebSocket handshake with the TcpProxy filter. This change is now replaced with a dynamic metadata method that is invisible to the Envoy API. Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
[ upstream commit 01a0367 ] Add 'useOriginalSourceAddr' parameter to ParseResources() to inform if the listener should use original source address or not. Pass this as 'true' from C/CEC watchers if OwnerReferences does not contain Kind=Ingress. That is, do not use original source addressing for Ingress listeners. This makes upstream connections from Ingress listeners to use node's allocated Ingress addresses in all cases, so that the source if Ingress traffic within the cluster is seen as 'ReservedIdentityIngress' (8). Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
jrajahalme
force-pushed
the
ingress-id-backport-1.13
branch
from
April 25, 2023 15:14
ef50ad4
to
ad8b32a
Compare
/test-backport-1.13 |
michi-covalent
approved these changes
Apr 25, 2023
/test-1.16-4.19 |
/test-1.18-4.19 |
/test-1.19-4.19 |
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
Apr 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport/1.13
This PR represents a backport for Cilium 1.13.x of a PR that was merged to main.
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.
Once this PR is merged, you can update the PR labels via:
or with