Implement the Service API #279
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.
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.The text was updated successfully, but these errors were encountered: