-
Notifications
You must be signed in to change notification settings - Fork 23
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
docs: adds RELEASES.md #99
Conversation
note to self: add release cycle doc |
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
Signed-off-by: Takeshi Yoneda <[email protected]>
7645878
to
a482fad
Compare
ok ready! |
Signed-off-by: Takeshi Yoneda <[email protected]>
|
||
### Envoy Gateway vs Envoy AI Gateway compatibility | ||
|
||
Since Envoy AI Gateway is built on top of Envoy Gateway, the compatibility between the two is important. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are people asking if envoy ai gateway is compatible with Istio
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's where the public filterconfig
package, which is decoupled from EG/k8s specifics, comes into play! In fact my colleagues are working on the extproc integration in another control plane 👍 Basically, as long as we write extproc (or dynamic module in the future) in a decoupled way, it should be possible for other control plane to deploy the ai filter implemented here (which i believe is good for both testability and adoption like this)
Signed-off-by: Takeshi Yoneda <[email protected]>
This commit adds RELEASES.md documentation
that describes the release cycles and the support
policy especially around the compatibility promises.
fixes #21