Skip to content
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

☔ Add XDS config tab to outbound and inbound view #3181

Closed
1 of 5 tasks
lahabana opened this issue Nov 13, 2024 · 1 comment · Fixed by #3186
Closed
1 of 5 tasks

☔ Add XDS config tab to outbound and inbound view #3181

lahabana opened this issue Nov 13, 2024 · 1 comment · Fixed by #3186
Assignees
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone

Comments

@lahabana
Copy link
Contributor

lahabana commented Nov 13, 2024

Description

For outbound it should work only with MeshService.

Now that we have predictable names for Clusters we should be able to show the XDS config for a specific outbound.

We would have a new tab next to config/stats/clusters and show just the data we are interested in. This make it a lot easier for folks to understand what the XDS config for an outbound is and to understand what could be happening.

For only do DPPs (no gateway proxies).

@lahabana lahabana added triage/accepted The issue was reviewed and is complete enough to start working on it kind/feature New feature labels Nov 13, 2024
@lahabana lahabana added this to the 2.10.x milestone Nov 13, 2024
@lahabana
Copy link
Contributor Author

Here's some XDS config for demo-app and redis:
demo-app-xds.json
redis-xds.json

@lahabana lahabana changed the title Add XDS config tab to outbound and inbound view ☔ Add XDS config tab to outbound and inbound view Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants