-
Notifications
You must be signed in to change notification settings - Fork 340
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
feat(kuma-cp): deduplicate dataplane inbounds by address and port combination #12760
Open
Automaat
wants to merge
16
commits into
kumahq:master
Choose a base branch
from
Automaat:feat/inbound-name-from-pod
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
30d0259
feat(kuma-cp): inbound name should be taken from pod instead of service
Automaat fc93dba
feat(kuma-cp): fix tests
Automaat 514fe96
feat(kuma-cp): fix tests
Automaat dfe4edb
Merge remote-tracking branch 'origin/master' into feat/inbound-name-f…
Automaat 8817d6d
fix(e2e): fix picking right interface for delegated gateway
Automaat aca4d0a
fix(e2e): fix delegated gateway behaviour
Automaat dab5391
fix(e2e): keep first inbound when deduplicating
Automaat b020271
Merge branch 'master' into feat/inbound-name-from-pod
Automaat d3a5a65
Merge branch 'master' into feat/inbound-name-from-pod
Automaat 3ad8235
feat(inbounds): fix unit tests
Automaat 653f1e6
feat(inbounds): deduplicate inbounds only for MeshService exclusive
Automaat 21f1407
feat(inbounds): add test for deduplication
Automaat bb69589
feat(inbounds): fix check
Automaat 2972853
feat(inbounds): update comments
Automaat 35f8d6d
feat(inbounds): remove unneeded log
Automaat 05ba8ae
feat(kuma-cp): add information about new rules api and dataplane kind…
Automaat File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
In one of my testing, I found when the service
port
is different than thetargetPort
, the two inbounds generated on the DP has the same name and port, but they have differentk8s.kuma.io/service-port
tags: one of them is incorrect. So in this case, we need to remove the one with incorrect tag. Could you also verify this?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.
do you mean the situation when we have service with two ports?
With this approach we don't care about tags, inbound tags will be gone after we fully switch to MeshService exclusive. I think in this situation we will just create inbound from pod port