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

Implement the Service API #279

Open
shaneutt opened this issue Sep 5, 2024 · 0 comments
Open

Implement the Service API #279

shaneutt opened this issue Sep 5, 2024 · 0 comments
Labels
area/controlplane area/dataplane kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@shaneutt
Copy link
Member

shaneutt commented Sep 5, 2024

Blixt started with intentions to implement just Gateway API but it kinda toes the line of being a Service implementation. In fact, the prototype for Blixt abused Service for faux IPAM as a hack to get things working.

The purpose of this issue is to discuss and consider whether we would implement the Service API using Blixt, but ideally we do this with as limited scope as possible. I am particularly interested to see if we can build off of KEP 4770 so that we can be an alternative, while deployed compatibly alongside existing default cluster implementations.

@shaneutt shaneutt added area/dataplane area/controlplane kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it. labels Sep 5, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/controlplane area/dataplane kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Status: Triage
Development

No branches or pull requests

1 participant