-
Notifications
You must be signed in to change notification settings - Fork 319
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
Support multiple GatewayClass #1231
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Hi all, I think it would be great if multiple The resources allocated to it are dependent on what services are being proxied though it and are not 'automatic' as one may get via a cloud managed LB (like GKE's provided gateway api implementation mapping to GCE LB instances). If there is only ever one Having each "tenant" install a EG controller would require each tenant to have some higher level permissions to the cluster per each tenant, e.g. creating I think it would be nice to either be able to specify some sort of glob pattern for watched and/or making
a full CRD where those wanting to make Thank you all for working on this and would love to see this continue to get better! |
thanks for the feedback @wondersd !
|
@arkodg Thanks for the quick response! Any notion of how For what its worth I think having multiple I suppose one could fall back to multiple controller installs for the above, which in practice would probably be fine as the cluster administrator defining such Hope this is helpful, thanks for hearing me out! |
regarding your request for multiple thanks again for sharing your feedback ! |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
will need to prioritize this one, since there are no concrete plans in upstream to support an arbitrary infra extension point such as |
if we implemented this, this should make #1851 redundant |
cc @cnvergence curious if you're interested in looking at this since its similar to the MergeGateways feature |
@arkodg sounds good to me, I will pick it up once I will have some spare time |
awesome thanks @cnvergence |
Hey @cnvergence, kindly ping for the status of the issue, are you still working on this : ) |
hey @Xunzhuo, sorry, did not move it forward lately, but now I will be able to have more time for it, so I would like to focus on this subject :) |
Thank you @cnvergence, since it is an important feature in the next milestone, so just kindly ping you. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Description:
Today, Envoy Gateway only supports a single GatewayClass. This decision was taken to simplify logic, limit permissioning and ensure sensitive material is isolated (across tenants) before dealing with multi tenancy (each GatewayClass is a tenant).
Our proposed alternate solution is to request users to create another Envoy Gateway controller with a different name in a the same cluster in a different namespace and link the newer GatewayClass to it
Keeping this issue open to gather feedback from users.
The text was updated successfully, but these errors were encountered: