Lars Bing Bong.
Lars Bing Bong.
Any news on this I see the same issue on Cilium v1.15.3 and cilium-cli v0.16.3. Cilium is running on a K3s v1.28.7+k3s1 cluster. Thank you.
Why is tls auth. required for the liveness and readiness probes anyway? I don't get it? We have this issue as well. We can't bump to v1.19.0 or 1.19.1 because...
Allow me to add some more context here. I'm a colleague of @Havnevej and we worked together on our `token based auth. as a service` for our internal `Kubernetes` based...
We found another way of completing what we needed. And a way that does not have the current limitation on the ingress side of controlling the Envoy Listener for certain...
Why isn't anything happening here? It would really be nice if this was merged so that we can bump and patch these sec. issues.
Lucas yes there is. We do so in our prod. and test setup. Keycloak being the JWK broker and enovy the entrance gateway to authenticate through. I'm not at the...
Very cool @col ..... why not give back to this project with the fixes you did?
> Observing same issue, but for us it's not just annoyance since decrypted file is parsed by ytt which requires "---" to be present to separate set of instructions. Current...
@dberardo-com - `strict-local` signals that the Longhorn volumes replica should be on the same node as your Pod. If not the volume cannot be attached and your Pod will never...
@abaguas that would be so wonderfully awesome. As we've already transitioned many of our workloads being exposed outside X Kubernetes cluster to be using the Gateway API.