-
Notifications
You must be signed in to change notification settings - Fork 333
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
Panic when calling /meshes/default/dataplanes/mycurlpod.kuma-demo/rules
endpoint
#11194
Comments
I wasn't able to reproduce it at this time. I installed the counter demo app and created the following policies, when I try the URL endpoint, it succeeded without any issues. apiVersion: kuma.io/v1alpha1
kind: Mesh
metadata:
labels:
kuma.io/env: kubernetes
kuma.io/origin: zone
kuma.io/zone: default
name: default
spec:
meshServices:
enabled: Everywhere apiVersion: kuma.io/v1alpha1
kind: MeshTimeout
metadata:
labels:
k8s.kuma.io/namespace: kuma-demo
kuma.io/env: kubernetes
kuma.io/mesh: default
kuma.io/origin: zone
kuma.io/policy-role: consumer
kuma.io/zone: default
name: timeout-on-demo-app
namespace: kuma-demo
spec:
targetRef:
kind: Mesh
to:
- default:
connectionTimeout: 10s
http:
requestTimeout: 5s
streamIdleTimeout: 1h0m0s
targetRef:
kind: MeshService
name: demo-app
namespace: kuma-demo |
Let's look at the code and see what was the reason. |
It was this: kuma/pkg/core/xds/inspect/rules.go Lines 109 to 113 in fc68afc
Is is still the case? Is it true for MeshService? I was unable to reproduce the panic locally |
I managed to reproduce this on Universal when |
What happened?
This happened with MeshService enabled and MeshTimeout targeting real MeshService applied
The text was updated successfully, but these errors were encountered: