-
Notifications
You must be signed in to change notification settings - Fork 303
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
Duplicate rules created in load balancer #821
Comments
@gijo-varghese Nothing about your Ingress spec stands out, it looks pretty normal... Can you dump the contents of the url map k8s-um-default-basic-ingress--6dca0e07f... via the gcloud command line tool? I want to see if the output JSON also has duplicate rules. This would rule out some sort of UI issue. |
@rramkumar1 here is the dump of a similar load balancer:
|
@rramkumar1 the reason for the duplicate rule I think is because the first rule is created for 'defaultService' and the second one for 'pathRules/paths' any way to specify backend for a domain without adding 'paths'? |
@gijo-varghese Yea appears that is the case, although I remember the UI rendering it differently...
I believe if you leave "paths" empty, we fill in "/*" for you but I don't see how that would change the UI. It seems like your UrlMap is structurally correct so I don't think this is any sort of bug. Perhaps they changed the UI a bit which is why this looks a little weird. Given that, can we close this? |
@rramkumar1 ok. My concern is about the price. Since there are duplicate rules in the UI (4 rules), will I be charged for 4 rules or 2 rules? |
@gijo-varghese Please correct me if I am wrong, but you are never charged for individual rules in a UrlMap. You are only charged for ForwardingRules themselves (which are a completely different API resource). |
Here are the Load balancing and forwarding rules pricing: https://cloud.google.com/compute/all-pricing#lb |
You will not be charged anything. These are rules in a UrlMap resource and a UrlMap resource does not incur any charges. What you are charged for is a ForwardingRule. If you look under the "Frontend" heading, you will see two entries (HTTP and HTTPS). These correspond to ForwardingRules. You are charged for those. |
haha! Thanks a lot 😄 I was thinking about some weird solutions like this! https://stackoverflow.com/questions/57456652/how-to-use-gke-ingress-along-with-nginx-ingress/ |
/close |
@rramkumar1: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Every time I add a new rule to the ingress, it creates multiple rules in the load balancer. The rules are basically the same, pointing to the same backend
Here is my ingress file:
Here are the duplicate rules created in the load balancer:
The text was updated successfully, but these errors were encountered: