Closed Automaat closed 1 month ago
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: https://github.com/kumahq/kuma/blob/fc68afc736beb477c272ac13e86b46ea3e4a76b0/pkg/core/xds/inspect/rules.go#L109-L113 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 Dataplane.Networking.Outbound[].backendRef
is set. In this case, outbound doesn't have tags and that's why we get panic.
What happened?
This happened with MeshService enabled and MeshTimeout targeting real MeshService applied