Michal Schott

Think I've got something. This is how it looks thanos: ``` [root@admin]# find .bottlerocket/rootfs/ -iname 'thanos' | grep bin 2>/dev/null .bottlerocket/rootfs/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/362/fs/bin/thanos [root@admin]# readelf -h .bottlerocket/rootfs/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/362/fs/bin/thanos ELF Header: Magic: 7f 45...

@mchaker any luck reproducing this issue? Or maybe an idea about corrupted entrypoints? Maybe it is worth to ping friends fron containerd project?

Think the issue might be too low disk attached to bottlerocket, since I've extended it this never happened 🤦

Worth to mention we're looking for only NetworkPolicies feature and IPAM is still handled by aws-vpc-cni.

Something to add: ``` ➜ k -n prometheus get pod,svc,endpoints -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES pod/prometheus-prometheus-prometheus-0 3/3 Running 0 38m 10.200.60.11 ip-10-200-60-245.eu-west-1.compute.internal...

So to me it looks more like a bug with chart itself. Pointing remote thanos reader to `service/prometheus-prometheus` (doesn't matter if ingress is being used) means each request will flip-flop...

@yorinasub17 I have been using below snippet (slightly modified from what I have originally pasted above) and it runs flawlessly so far: ``` func TestMain(m *testing.M) { t := &testing.T{}...

BUMP I'm also hit with that problem (2.11.4) ``` ~ kubectl -n linkerd-jaeger get saz/collector -o yaml apiVersion: policy.linkerd.io/v1beta1 kind: ServerAuthorization metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"policy.linkerd.io/v1beta1","kind":"ServerAuthorization","metadata":{"annotations":{"linkerd.io/created-by":"linkerd/helm stable-2.11.4"},"labels":{"app.kubernetes.io/instance":"linkerd-jaeger","component":"collector","linkerd.io/extension":"jaeger"},"name":"collector","namespace":"linkerd-jaeger"},"spec":{"client":{"unauthenticated":true},"server":{"selector":{"matchLabels":{"component":"collector","linkerd.io/extension":"jaeger"}}}}} linkerd.io/created-by: linkerd/helm stable-2.11.4...

@adleong somehow denied client ip was from `169.X.X.X` range, i suspect this is because I have `config.linkerd.io/skip-inbound-ports: 80,443` annotation on my ingress ?

Hey @nyrahul indeed it eventually recovers, thanks for an update. Looking forward for 0.6 release!