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
Kubernetes is introducing API-gateway to improve gateway concern natively inside Kubernetes.
Looking at services-mesh, it seems to be highly related and the migration to support natively Kubernetes API-gateway is a must-have for future generation of services-mesh tools.
I'm asking: do you plan the Gateway API to become the default API for all Consul traffic management in the future ?
If, yes:
Will this change create a breaking changes in Consul ?
The text was updated successfully, but these errors were encountered:
Feature Description
Kubernetes is introducing API-gateway to improve gateway concern natively inside Kubernetes.
Looking at services-mesh, it seems to be highly related and the migration to support natively Kubernetes API-gateway is a must-have for future generation of services-mesh tools.
I'm asking: do you plan the Gateway API to become the default API for all Consul traffic management in the future ?
If, yes:
Will this change create a breaking changes in Consul ?
The text was updated successfully, but these errors were encountered: