Load Balancing

  1. Respect "X-Forwarded-Proto" header from Cloud Flare / other frontends

    Cloud Flare correctly sets the "X-Forwarded-Proto" to "https" when using their "flexible" option (https://support.cloudflare.com/hc/en-us/articles/200170986-How-does-Cloudflare-handle-HTTP-Request-headers-) - this is the same as if we used the GCP load balancer directly to handle HTTPS and proxy via HTTP to our backends.

    I need my backend services, which listen on HTTP, to understand that the request came from a client using HTTPS - but Google Cloud load balancer is overwriting the X-Forward-Proto header to "http", even though the client is actually using HTTPS from our Cloud Flare frontend.

    This is the whole point of the "X-Forwarded-Proto" header, so I'm not sure why…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Cloud armor Security Policy Redirect

    Cloud Armor - Security Policy Rules

    It would be very useful to be able to have more informative error messages to end users in case they are inadvertently restricted by a security policy.

    Currently the only available options are to return 403, 404 or 502, with no possible extra message.

    A simple solution to remedy this case would be to add an option redirect traffic to another URL. So adding an option to return a HTTP 307 (Temporary Redirect) code with a possiblilty to define an URL would be great.

    That way end users could be served a more informative…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. BUG Error console Load Balancing

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

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    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