-
Notifications
You must be signed in to change notification settings - Fork 3.4k
l7lb: fix registration of flag loadbalancer-l7 #35623
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
Merged
sayboras
merged 1 commit into
cilium:main
from
mhofstetter:pr/mhofstetter/l7lb-fix-flag
Oct 30, 2024
Merged
l7lb: fix registration of flag loadbalancer-l7 #35623
sayboras
merged 1 commit into
cilium:main
from
mhofstetter:pr/mhofstetter/l7lb-fix-flag
Oct 30, 2024
Conversation
This file contains hidden or 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
Currently, the flag `loadbalancer-l7` isn't properly registered. Even though it's working fine when reading the config property from the Cilium Configmap, it's not working when trying to use the flag as Go flag. ``` 2024-10-29T16:24:26Z debug layer=debugger Adding target 23 "/usr/bin/cilium-operator-generic-bin --config-dir=/tmp/cilium/config-map --debug=true --loadbalancer-l7=envoy" Error: unknown flag: --loadbalancer-l7 ``` Therefore, this commit is moving the config property into the respective Hive Cell where it gets properly registered. Reported-by: André Martins <andre@cilium.io> Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
/test |
pippolo84
approved these changes
Oct 29, 2024
aanm
approved these changes
Oct 29, 2024
sayboras
approved these changes
Oct 30, 2024
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.
Good findings both ✔️
This was referenced Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/servicemesh
GH issues or PRs regarding servicemesh
backport-done/1.15
The backport for Cilium 1.15.x for this PR is done.
backport-done/1.16
The backport for Cilium 1.16.x for this PR is done.
kind/bug
This is a bug in the Cilium logic.
release-note/bug
This PR fixes an issue in a previous release of Cilium.
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.
Currently, the flag
loadbalancer-l7
isn't properly registered.Even though it's working fine when reading the config property from the Cilium Configmap, it's not working when trying to use the flag as Go flag.
Therefore, this commit is moving the config property into the respective Hive Cell where it gets properly registered.
Reported-by: André Martins andre@cilium.io
Note: The initial PR that moved this logic and flags into a Hive Cell probably skipped moving the config flag
loadbalancer-l7
as there might be multiple cells that implement L7 loadbalancing functionality in the future. While this might be true, IMO it's ok to move if for the time being and deal with this later.