JulianTheKalamari

Same issue as everyone else. I have no idea how to fix this and am constantly in a CrashLoopBackoff

I finally figured out how to get the new .conf values to be used. Even if I modified the `parameters` section in the helm chart, they would propagate to the...

Giving my +1 to this. I have an API endpoint that returns a `Map`, and unfortunately the python code generated ends up saying `Dict[str, object]`

+1, this is still an issue, even on version 5.9.0 of the vpc module. I was hoping to play around with pulumi and converting my existing code, but the fact...

+1 to this, as I'm running into the exact same issue using helm. I'm putting the output of the redis helm chart user/pass into the datadog helm file via terraform,...

+1 to this issue as well. `GatewayClass` shows `Unknown` for the `Accepted` field. New or long-living existing AWS EKS cluster produces the same result, the `GatewayClass` is never accepted. EDIT:...

> Thanks for your issue., > > Just curious if you are having issue with GatewayClass status (same as Jullian) as well 🤔. Appreciate if you can attach sysump as...

Okay, I found the problem. The problem is that after deploying a Gateway that then creates the `Service` provisioning an external LoadBalancer, if you then restart the `cilium-envoy`, `cilium`, and...

Coming back to this, cilium 1.16.1 seems to have fixed the Gateway / Service endpoint reconciliation error, but I'd rather have someone else confirm as such.

Coming back to this, I've more or less confirmed it's a bug in Cilium. I setup an nginx pod to listen on port 80, and both http and https requests...