We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reported by Brent Yarger. Apparently when applied this policy
apiVersion: kuma.io/v1alpha1 kind: MeshRetry metadata: name: retry-all namespace: kong-mesh-system labels: kuma.io/mesh: default spec: targetRef: kind: Mesh to: - targetRef: kind: Mesh default: http: numRetries: 1 backOff: baseInterval: 5s maxInterval: 1m retryOn: - "5xx"
and
apiVersion: kuma.io/v1alpha1 kind: MeshRetry metadata: name: retry-echo-to-mockserver namespace: kong-mesh-system labels: kuma.io/mesh: default # optional, defaults to `default` if unset spec: targetRef: kind: MeshService name: echo-service_default_svc_8080 to: - targetRef: kind: MeshService name: mockserver_mockserver_svc_1080 default: http: numRetries: 5 backOff: baseInterval: 10s retryOn: - "5xx"
results in the other upstreams in the echo service sidecar get retry config removed.
The text was updated successfully, but these errors were encountered:
I confirm the issue
Sorry, something went wrong.
jakubdyszkiewicz
Successfully merging a pull request may close this issue.
What happened?
Reported by Brent Yarger. Apparently when applied this policy
and
results in the other upstreams in the echo service sidecar get retry config removed.
The text was updated successfully, but these errors were encountered: