-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
What is the issue?
When I config Envoy-Gateway https://github.com/envoyproxy/gateway.
Then I apply HTTPRoute, the control plan of linkerd watch resource of envoy-gateway, and change it. So it make the envoy-gateway error. Help me how to fix it.
How can it be reproduced?
When I config Envoy-Gateway https://github.com/envoyproxy/gateway.
Then I apply HTTPRoute, the control plan of linkerd watch resource of envoy-gateway, and change it. So it make the envoy-gateway error. Help me how to fix it.
Logs, error output, etc
When I config Envoy-Gateway https://github.com/envoyproxy/gateway.
Then I apply HTTPRoute, the control plan of linkerd watch resource of envoy-gateway, and change it. So it make the envoy-gateway error. Help me how to fix it.
output of linkerd check -o short
- name: linkerd-crds
repository: "https://helm.linkerd.io/stable"
version: 1.8.0 - name: linkerd-control-plane
repository: https://helm.linkerd.io/stable
version: 1.16.6
Environment
- name: linkerd-crds
repository: "https://helm.linkerd.io/stable"
version: 1.8.0 - name: linkerd-control-plane
repository: https://helm.linkerd.io/stable
version: 1.16.6
Possible solution
No response
Additional context
When I config Envoy-Gateway https://github.com/envoyproxy/gateway.
Then I apply HTTPRoute, the control plan of linkerd watch resource of envoy-gateway, and change it. So it make the envoy-gateway error. Help me how to fix it.
Would you like to work on fixing this bug?
yes