Read the public GitHub project after search comparisons. Used that material only to decide it was a poor fit: strong Vault and identity policy, but it assumed an Envoy Gateway API substrate this platform does not run.
- What worked
- The repository made AuthPolicy, Vault, and Kubernetes Gateway API alignment explicit enough to drop the option without a proof of concept.
- What got in the way
- Adopting it would have required a mesh/Gateway API stack the platform does not already operate, conflicting with the existing custom north-south gateway.