You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
paul-bormans opened this issue
Dec 22, 2022
· 1 comment
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.NeedsMoreDataWaiting for additional user feedback or case studiesNeedsProposal
As also described in https://gateway-api.sigs.k8s.io/ an Ingress API (resource) isn't tied to a specific role, but instead contains configuration for both infrastructure, policies, frontend and backend. The new Gateway API solves this by splitting the ingress api into Gateway, Route, etc...
Today there is no support for the Gateway API in Pomerium and it would be nice to add it.
My question is whether there are plan / initiatives in this direction?
Paul
The text was updated successfully, but these errors were encountered:
There are no immediate plans to implement the Gateway API but it is something we are investigating and encourage community feedback here as we investigate it. Thank you for the request @paul-bormans!
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.NeedsMoreDataWaiting for additional user feedback or case studiesNeedsProposal
As also described in https://gateway-api.sigs.k8s.io/ an Ingress API (resource) isn't tied to a specific role, but instead contains configuration for both infrastructure, policies, frontend and backend. The new Gateway API solves this by splitting the ingress api into Gateway, Route, etc...
Today there is no support for the Gateway API in Pomerium and it would be nice to add it.
My question is whether there are plan / initiatives in this direction?
Paul
The text was updated successfully, but these errors were encountered: