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

The use of KmeshWaypointPort needs to be optimized #370

Open
kwb0523 opened this issue May 27, 2024 · 0 comments
Open

The use of KmeshWaypointPort needs to be optimized #370

kwb0523 opened this issue May 27, 2024 · 0 comments

Comments

@kwb0523
Copy link
Contributor

kwb0523 commented May 27, 2024

What would you like to be added:
When storing port information, it is currently determined whether the corresponding service name contains the "waypoint" keyword. If so, the corresponding target port will be replaced with KmeshWaypointPort, so that traffic management in data plane can switch to kmesh waypoint. However, the current method of judging whether a service is a waypoint based on the "waypoint" field has a mismatch defect. Therefore, a better way to use KmeshWaypointPort or to change the waypoint port information in the environment in some way is needed, maybe we can use a cmdline tool like kmeshctl to implement it.
Why is this needed:
avoiding potential issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant