-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Fix: Support GCE in ingress path #9427
base: master
Are you sure you want to change the base?
Fix: Support GCE in ingress path #9427
Conversation
Compatbility with GKE / GCE, where GCE requires a path that contains /* to function and here we can't use the /* and it messes up the ingress. NB: let the user choose his own path, if he wants more complicated paths then he will do it on his own after consulting the documentation Signed-off-by: El Mehdi Bouamama <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ElMehdiBouamama-Infomineo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @ElMehdiBouamama-Infomineo! |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Compatbility with GKE / GCE, where GCE requires a path that contains /* to function properly.
With the current path setup we can't use the /* and it messes up the ingress.
NB: let the user choose his own path, if he wants more complicated paths then he will do it on his own after consulting the documentation. DO NOT FORCE PATHS ON USERS