@pomerium.io ingress controller feels like abandonware :( Commit history is mostly bots, first embarrassing bug I've ran into months ago (hardcoded clusterDomain) is still not fixed, and I've got hit by a second bug today (picking up routes that belong to a different gateway class and then OOMing)
Post
Second embarrassing bug I mentioned: github.com/pomerium/ing...
github.comMutations of `HTTPRoute`s belonging to other controllers · Issue #1244 · pomerium/ingress-controllerIngress controller is unable to co-exist with any other Gateway API controller in the same cluster: it updates status of all routes regardless of their Gateway's class name. This results in two con...
Holy shit, this function just indiscriminately overwrites status for all parentRefs. I think I better stop using Pomerium, it seems to be more of a liability than a security measure.
0 reposts1 like
No replies yet.