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
If feels that every backend allows for different options to be passed, and in different ways. For example options available for frontends/backends in traefik.yml are different than ones in docker, and also different than in kubernetes backend.. Would it be willing to standardise/adapt on API format, just like tyk or api umbrella did?
Ideally I'd be able to put such definition inside docker labels / kubernetes matadata, even as JSON.
Does it sound reasonable? Do you know any other definitions other than tyk or api umbrella?
The text was updated successfully, but these errors were encountered:
If feels that every backend allows for different options to be passed, and in different ways. For example options available for frontends/backends in traefik.yml are different than ones in docker, and also different than in kubernetes backend.. Would it be willing to standardise/adapt on API format, just like tyk or api umbrella did?
Ideally I'd be able to put such definition inside docker labels / kubernetes matadata, even as JSON.
Does it sound reasonable? Do you know any other definitions other than tyk or api umbrella?
The text was updated successfully, but these errors were encountered: