You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workload captured waypoint requires some brain power atm to ensure the use-waypoint label on the pod is pointing to a waypoint that can capture workload, which isn't default and requires specific configuration when deploying a waypoint.
Would be nice to improve this - by giving some warnings when inconsistency detected via analyzer? Or use a different gatewayclass for workload waypoint?
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[x ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
The text was updated successfully, but these errors were encountered:
Describe the feature request
Workload captured waypoint requires some brain power atm to ensure the use-waypoint label on the pod is pointing to a waypoint that can capture workload, which isn't default and requires specific configuration when deploying a waypoint.
Would be nice to improve this - by giving some warnings when inconsistency detected via analyzer? Or use a different gatewayclass for workload waypoint?
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[x ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
The text was updated successfully, but these errors were encountered: