Load Balancing

  1. GKE Ingress: Support Rewrite

    Add ingress support for ngnix-style rewrite of paths

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. enable the internal load balancer to use an instance group without an external IP

    if you create an instance group without an external ip when you create an internal load balancer, it creates a health check. Health check uses in external ip address for verification.

    oops. the instances do not have an external IP address.

    Health check should be installed on the load balancer and use the internal IP address of the backend services.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Improve your Load Balancer Interface. It is confusing. There is no clarity and separation of UI for Network and HTTP(S) Load Balancer

    Improve your Load Balancer Interface. It is confusing. There is no clarity and separation of UI for Network and HTTP(S) Load Balancer.
    Users always get confused when you are creating a Load Balancer.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Priority in URL Maps

    Since all backends are treated equally, we cannot have a "backup website" in case the backends are overwhelmed. Having priority in the URL Maps would allow us to direct traffic to high priority backend service in normal cases and when they are overwhelmed, we can direct the remaining to some other backend (e.g. bucket containing simple page explaining the website is overloaded.).

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Only one loadbalancer for http traffic and https traffic independently to the same backend

    I would like to create one HTTP(S) loadbalancer with one backend (instance group) with port 80 behing forward to port 80 on the backend and port 443 behing forward to port 443 on the backend.

    At the moment we have to create 2 seperate loadbalancers with the same external IP to achieve this.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Set load balancer timeout in k8s deplyment spec

    instead of manually running
    gcloud compute backend-services update --global ${BACKEND_NAME} --timeout=${TIMEOUT}

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Your Geo-IP data is not accurate.

    Hi Google Cloud, regarding your load balance geo-ip feature(https://cloud.google.com/compute/docs/load-balancing/http/backend-service#user-defined-request-headers …), we found it's not accurate and we would like to share our findings, may I have a contact (email)so I can send our findings?

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Internal Load Balancer support UDP session affinity

    Internal load balancer doesn't support session affinity when using UDP.
    But Load Balancer does.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Load balancer fault is not informative

    Load balancer has a heartbeat mechanism to moniter the linked instances. In some cases the LB marks an instance as unhealthy but does not provide the reason for marking it as unhealthy. from instance perspective the HB is fine, since port mirroring is not available there is no clue why the LB marks an instance as unhealthy.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Only one loadbalancer for http traffic and https traffic independently to the same backend

    I would like to create one HTTP(S) loadbalancer with one backend (instance group) with port 80 behing forward to port 80 on the backend and port 443 behing forward to port 443 on the backend.

    At the moment we have to create 2 seperate loadbalancers with the same external IP to achieve this.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow multiple health checks on an ILB

    An ILB can provide load balancing on multiple TCP ports. But, when you associate a health check to ILB, you can create only 1 health check on only 1 TCP port. If backend servers are listening on multiple TCP ports, it adds value to provide health check for all those ports

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. HSTS "max-age" configurable value

    I'd be able to change max-age value for HSTS directive

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. BUG Error console Load Balancing

    The deletion of some of the forwarding rules failed. Error: Code: '53BD0BF586D29.A1ED39D.E70FD608'.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Load Balancing

Categories

Feedback and Knowledge Base