Feature Proposal: 3rd Party API Gateway(Traefik Proxy) Validation Support #63
Labels
kind/new-capability
Proposal for a new capability
logic-processing
Related to parsing and processing K8s manifests.
skill/kong
skill/nodejs
skill/traefik
skill/typescript
Scope
We want to make usage of 3rd party API Gateways easier and safer. Kubevious is already equipped with a Gateway View where Ingresses, Services, and Applications are correlated and presented in a Domain -> URL -> Ingress -> Service -> Service Port -> Container Port -> Application path. We want to extend Gateway support capability and add support to popular API Gateways such as Traefik, Kong, Istio, Ambassador, Skipper, etc.
Kubevious already validates Service selectors in Ingresses, and Pod and Port selectors in Services. We also want to validate 3rd party API Gateways to detect errors early and aid with troubleshooting. That could require the correlation of 3rd party CRDs and other runtime sources to build a more clear understanding of what's going on in the cluster, application, and the API Gateway.
Requirements
Validation Logic
Validator documentation: https://kubevious.io/docs/built-in-validators/traefik-proxy/
DRI
@rubenhak
Current State
Traefik Proxy native support is already available in version 1.0.7.
Progress
Appendixes
Kubevious Gateway View
A glimpse of what Kubevious does for K8s Ingresses. We want to do the same (and more) for 3rd party API Gateways.
Legend
✅ - Complete
👉 - Current / active stage
The text was updated successfully, but these errors were encountered: