Katia Esposito
Katia Esposito
@dhimmel please reopen if this is still an issue
@8cH9azbsFifZ please reopen if this is still an issue
My bad!
Considering the [removal of forward auth at v0.21.0](https://github.com/pomerium/pomerium/releases/tag/v0.21.0) - this seems to be an issue which will not be solved/addressed. It is a shame, as Pomerium+fwdauth hit the sweet spot...
The missing feature does not matter! Removing this feature locks you in using a Pomerium instead of any perfectly good ingress controllers, which have been battle-tested in production for decades,...
In addition, working well with other proxies can help mitigate critical CVEs.
hi Sebastiaan, sure, that sounds good. feel free to open a PR with a section added to the readme. I would appreciate if there are any other projects using this...
the api gets the csv from https://vrs-standing-data.adsb.lol/ so if that update breaks it will get outdated data. perhaps that is what you saw.
/remove-lifecycle stale
Please give the ability to not expose IPv6 InternalIPs and/or revert this change. As is, using ExternalIP as routable and InternalIP ULA addresses for the cluster, results in the ULA...