-
Notifications
You must be signed in to change notification settings - Fork 361
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
Run Envoy Gateway locally on host #1393
Comments
Relates to envoyproxy#1393 Signed-off-by: Arko Dasgupta <[email protected]>
* Add API for Custom provider Relates to #1393 Signed-off-by: Arko Dasgupta <[email protected]> * lint Signed-off-by: Arko Dasgupta <[email protected]> --------- Signed-off-by: Arko Dasgupta <[email protected]> Co-authored-by: Xunzhuo <[email protected]>
* Add API for Custom provider Relates to envoyproxy#1393 Signed-off-by: Arko Dasgupta <[email protected]> * lint Signed-off-by: Arko Dasgupta <[email protected]> --------- Signed-off-by: Arko Dasgupta <[email protected]> Co-authored-by: Xunzhuo <[email protected]>
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
the API is in, implementation is remaining, unassigned myself since I won't be able to pick up the implementation anytime soon due to other higher priority issues in the project, if anyone in the community is interested in picking this one up, please go for it |
Testing Envoy Gateway v1.0.0-rc.1 as a replacement for Cilium Gateway implementation. There are plenty of options (great!) but I can't understand how to use Envoy Gateway on the edge cluster where VIP is assigned to the distinct node. Can I configure the Envoy Gateway to run as DaemonSet? |
I would love to see this kicks in after GA, wanna give it a try, so assign myself. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
moving this to v1.2.0 to track docs work |
Description:
[optional Relevant Links:]
Relates to Relates to #1001 & #1035
The text was updated successfully, but these errors were encountered: