homemade-external-load-balancer | External Load Balancer for kubernetes | Load Balancing library

I know that the spark-cassandra connector comes with its own default loadbalancing policy implementation(DefaultLoadBalancingPolicy). How can I go about implementing my own custom LoadBalancing class? I want to have the application use the WhiteListRoundRobin policy. What steps would I need to take? I'm still a newbie in working with spark and Cassandra and I would appreciate any guidance in this. Thanks

I have an app launched on AWS ELB at the moment. AWS automatically enables an application load balancer which is a significant cost driver to my application. I only have 20 users at the moment, so the load on my application is quite low. When is a good time to enable load balancing?

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 are using load balancer as default on our aws server. But we want to host our subdomain on another host. Is it possible using Route 53 or Load Balancer to redirect or pointed the subdomain to another host?

Is there any way to limit the access to Kubernetes Service of type LoadBalancer from outside the cluster?

I would like to expose my database's pod to the Internet using the LoadBalancer service that would be accessible only for my external IP address.

My Kubernetes cluster runs on GKE.

I have 3 containers deployed on ecs and traffic is distributed by an application load balancer, swagger on this individual containers can be accessed via e.g 52.XX.XXX.XXX/swagger.

I need the services to be accessed via for e.g:

I have the following basic architecture:

For reasons I don't want to get into, I want to allow the client to fetch data from either server if they so choose. If they don't care then the load balancer will decide for them.

Is there a best practice for designing the API request?

I've come up with a few options:

• Add an optional query string parameter:

I am working on a project in Laravel 8 which I am now testing the deployment on production servers. I have set up 2 Digital Ocean Droplets that are behind a load balancer with Sticky Sessions enabled. I am attempting to login via a SPA app with a separate Laravel API so the middleware is configured for the api routes to be stateful API and perform CSRF validation. This works perfectly fine when I just hit a single droplet and bypass the load balancer but as soon as the load balancer is in use, I always receive a 419 CSRF Token mismatch.

Everything I found on Google says that the session needs to be shared between servers, but I don't believe this is the case in this scenario. I have turned on sticky session with a cookie called DO-LB in the load balancer so all requests from the same session go to the same server, and I am tailing the Apache access log on both servers, and I can see all requests such as the get-csrf and the auth route (using Sanctum) both hit the same server so would I would still be getting a token mismatch.

I am also using the cookie session driver.

UPDATE

I've found something a little strange, if I point my DNS to a singled droplet I see the X-XSRF-TOKEN is sent as a request header, but if I change DNS to point to the load balancer then X-xSRF-TOKEN is not sent as a request header. I am using Axios to send the request but I can't see how a load balancer can affect Axios

UPDATE 2

It looks like when I run it locally XSRF-TOKEN is not an HttpOnly cookie but when running it on production the XSRF-TOKEN is flagged as HttpOnly which from what I've read means its inaccessible from Javascript hence why Axios isn't sending it. I seem to have confirmed this by doing Cookies.get("XSRF-TOKEN") and printing the result, locally it prints the token to the console, but in production its undefined.

UPDATE 3

I updated my Apache configuration to override the headers as a test to remove the HttpOnly flag which seems to have done the trick, and I can now see when I log in, Chrome sends an X-XSRF-TOKEN in the request even though I still get a CSRF Token Mismatch.

I've compared the string in the chrome cookie store with what is being sent in the X-XSRF-TOKEN and they both match so I don't understand why Laravel keeps returning me a mismatch and I am at a complete loss.

I'm trying to deploy an Application Load Balancer to AWS using Terraform's kubernetes_ingress resource:

I'm using aws-load-balancer-controller which I've installed using helm_release resource to my cluster.

Now I'm trying to deploy a deployment with a service and ingress.

This is how my service looks like: