8000 [ambient] Disable L7 istio configs for services that are in Ambient but doesn't have a waypoint proxy · Issue #7900 · kiali/kiali · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[ambient] Disable L7 istio configs for services that are in Ambient but doesn't have a waypoint proxy #7900

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.

Sign up for GitHub

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

Jump to bottom
Open
Tracked by #8250
, #7826
...
josunect opened this issue Nov 6, 2024 · 2 comments
Open
Tracked by #8250
, #7826
...

[ambient] Disable L7 istio configs for services that are in Ambient but doesn't have a waypoint proxy #7900

josunect opened this issue Nov 6, 2024 · 2 comments
Labels
ambient Related to Istio Ambient Mesh enhancement This is the preferred way to describe new end-to-end features. refinement Still being full defined before taking any action sub-task Ties an issue to an epic

Comments

@josunect
Copy link
Contributor
josunect commented Nov 6, 2024 •
edited
Loading

What do you want to improve?

If a service is in Ambient but just with L4 processing, it shouldn't let the user create L7 traffic policies, as they don't be applicable:
image
t might confuse the user if Kiali let them create the istio config but then it is not taking effect.

What is the current behavior?

If a service is in Ambient with just L4 processing, Kiali enables L7 istio configs.

What is the new behavior?

If the service is in an Ambient Mesh, but it doesn't have a waypoint, should disable L7 istio configs not applicable. I think just the TCP Traffic shifting should be enabled:

image

Ref. #7826

https://istio.io/latest/docs/ambient/usage/l4-policy/
@josunect josunect added enhancement This is the preferred way to describe new end-to-end features. sub-task Ties an issue to an epic ambient Related to Istio Ambient Mesh labels Nov 6, 2024
@josunect josunect mentioned this issue Nov 6, 2024
Closed
19 tasks
@jshaughn
Copy link
Collaborator

Instead of blocking config creation, I wonder if we should treat this more as a troubleshooting issue, and report validation errors whenever there is L7 config for a component that is not captured by a waypoint? Because it could be that it was captured at create-time, but later the waypoint was removed. Also, I suppose a user may want to create L7 config prior to defining the waypoint.

@jshaughn jshaughn added the refinement Still being full defined before taking any action label Feb 24, 2025
@josunect
Copy link
Contributor Author

Instead of blocking config creation, I wonder if we should treat this more as a troubleshooting issue, and report validation errors whenever there is L7 config for a component that is not captured by a waypoint? Because it could be that it was captured at create-time, but later the waypoint was removed. Also, I suppose a user may want to create L7 config prior to defining the waypoint.

I think that would be helpful

@josunect josunect mentioned this issue Mar 18, 2025
Open
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ambient Related to Istio Ambient Mesh enhancement This is the preferred way to describe new end-to-end features. refinement Still being full defined before taking any action sub-task Ties an issue to an epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jshaughn @josunect
0