Load Balancing

  1. HTTP Load Balancer with client certificate verification

    Currently the load balancer supports only server side certificates. It will be big step to have client certificate verification.

    141 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. HTTPS Load Balancing: Support multiple certificates for a single target proxy.

    A single target proxy can be attached to a URL map containing multiple host rules, thereby allowing it to support multiple hostnames. However, a target HTTPS proxy currently only supports a single certificate. Therefore, supporting multiple hostnames using a single HTTPS global forwarding rule requires that each hostname be specified as a separate SAN within the certificate.

    This is not ideal for a number of reasons: for example, some certificate authorities charge more for a single SAN than for a single-hostname certificate. A certificate with multiple SANs is also larger than necessary, potentially leading to a slower TLS handshake.

    It…

    56 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. We need load balancer log....

    If the detail access log from load balancer can be read, will better!

    52 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 →
  4. 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 →
  5. 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 →
  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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. Ingress filter for HTTP(S) Load Balancing

    It would be great if we could filter what kind of traffic is allowed to the Load Balancer.
    Ie. To be able to allow/deny incoming requests by their Host and Path.
    I see too much of these "hacking attempts" in our request logs, requests that just connect with the IP address and try to access paths suchs as /phpmyadmin, /wp-admin, etc.
    It would be much more beneficial to be able to filter these kind of requests in the LB layer than in the application layer.

    5 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 →
  9. Allow RSA and ECC certs per frontend

    It would be great if the load balancer supported both RSA and ECC certs for the same frontend.

    In our experience supporting ECC improves both connection startup time for the client and CPU usage on the server.

    4 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 →
  10. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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 →
2 Next →
  • Don't see your idea?

Load Balancing

Categories

Feedback and Knowledge Base