load-balancing | Implementing several load balancing scheduling algorithms

I have two services running Cloud Run such as api1 and api2.

I set up a global external HTTP(S) load balancer (classic) in GCP to route the path to both services.

such as

When I send a request mydomain/api1/aaa/ccc/, api1 get the request url as mydomain/api1/aaa/ccc/

When I send a request mydomain/api2/ddd/eee/, api2 get the request url as mydomain/api2/ddd/eee/

Is there a way to rewrite the incoming request for api1, so that api1 will see the request as mydomain/aaa/ccc/?

This also apply to api2, so api2 will see the request as mydomain/ddd/eee/

From the Rewrite documentation,

The load balancer provides the following mutually exclusive primary actions:

• Reads the incoming URL in the request.
• Replaces the host, the path, or both the host and the path, transforming the URL before directing traffic to the backend service or backend bucket.

I think there is a way, but I don't manage to make it work.

Any advice?

I'd like to extract just a one value from below output and to be exactly, the host line.

Like:

I am trying to setup simple cluster of 2 ActiveMQ Artemis brokers within Docker Swarm environment.

Stack configuration

tail -n 10000 access_log | awk '{print $1}'| sor t| uniq -c| sort -nr| head -n 10

From Google

The IP address of the Google Front End (GFE) that connected to the backend. These IP addresses are in the 130.211.0.0/22 and 35.191.0.0/16 ranges.

This particular web server will go down once in a while and I've been trying to pinpoint the issue but to no avail. I noticed the over 1000+ connection from 130.211.x.x. I've another web server which is also using a load balancer but they receive connections from 35.191.x.x range only. There is no reference of 130.211.x.x

Are these connections consider normal?

I'm trying to redistribute an array (mesh-like) over a set of processes for load-balancing needs. My special requirement is that array elements should only be moved to the spatially adjacent processes as only the elements near the front between elements can be moved easily.

In the above example setup, all first three processes should donate elements to the last one:

I am trying to understand the usage of the ip addresses from my vpc in the eks with fargate environment. I can see that each pod has its own private ip address, which seems to be the same ip address for fargate node as well. It seems that the ENI allocates a single primary address for a EC2 node and many ip address as secondary based on the size, but I cannot find the same information on fargate. Does that mean it does not have any secondary ip addresses allocated ?

Extending on the question, it seems that a network load balancer requires a minimum of 8 free ip addressses to be created, Does that mean it blocks all the 8 ?

I'm trying to protect my Firebase Cloud Functions with Cloud Armor so I'm trying to setup Load Balancer. I created a Backend and added a Serverless Network Endpoint Group. In this panel, I can select only one cloud function but I have more than one cloud function so I have to use other option which is URL masking.

I'm following this guide: https://cloud.google.com/load-balancing/docs/https/setting-up-https-serverless#using-url-mask

Problem is:

When I try URL masking like this:

We recently updated the deployment of a dropwizard service deployed using Docker and Kubernetes.

It was working correctly before, the readiness probe was yielding a healthcheck ping to internal cluster IP getting 200s. Since we updated the healthcheck pings are resulting in a 301 and the service is considered down.

I've noticed that the healthcheck is now Default kubernetes L7 Loadbalancing health check for NEG. (port is set to 80) where it was previously Default kubernetes L7 Loadbalancing health check. where the port was configurable.

The kube file is deployed via CircleCI but the readiness probe is:

I am creating nginx ingress controller of type nlb with static ips, but for static ips I am getting this error AllocationIdNotFound. Although this allocation id is valid and eip with this id is present in the same region. Here are the annotations that I am using with nginx ingress controller service