Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support K8S Gateway API #463

Open
paul-bormans opened this issue Dec 22, 2022 · 1 comment
Open

Support K8S Gateway API #463

paul-bormans opened this issue Dec 22, 2022 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies NeedsProposal

Comments

@paul-bormans
Copy link

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

@desimone desimone added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies NeedsProposal labels Dec 28, 2022
@desimone
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. NeedsMoreData Waiting for additional user feedback or case studies NeedsProposal
Projects
None yet
Development

No branches or pull requests

2 participants