service-discovery | Simple service discovery implementation using Nx | Microservice library

I have an error message as so when trying to convert an existing app to use react-router v6:

Error: A is only ever to be used as the child of element, never rendered directly. Please wrap your in a .

here is my App component (BrowserRouter wraps the app, custom Router component is a child):

Summary:
I want to make NGINX (not NGINX Plus) re-resolve the IP address from the DNS name by using a variable in proxy_pass (as suggested in this official Nginx article in the section "Setting the Domain Name in a Variable"). But when I do that it won't set/forward the correct Content-Type header, but always use text/html, for .css, .js etc. files.

My setup:
I have a frontend and a backend service running in separate Docker containers (to be deployed to OpenShift in production). There's also a third container that runs nginx:latest (v1.19.9 as of today) and acts as a reverse proxy, forwarding calls made to /my-app to the frontend and /my-app/api to the backend container. The NGINX reverse proxy has set them up as upstream servers using their DNS names. All three containers run within the same custom Docker network, so resolving in itself works fine - but only, when NGINX is (re-)started.

The problem:
When the frontend or backend container gets restarted it may get a new IP address. Since NGINX caches IP addresses I'm getting a 502 when I make calls to them. I want NGINX to re-resolve the IP address more frequently, like NGINX Plus does. This is how the problem with the Content-Type came up, when I tried to have NGINX re-resolve DNS names.

The configuration:
Here's my NGINX configuration (simplified to the relevant stuff only):

We use CDK and we are starting using service discovery within our ECS services (hence, server to server not client to server). This means that we don't need ALB (for the moment at least, maybe we can revisit this choice later).

Unfortunately the CDK pattern that exists for building ECS services (ecs_patterns.ApplicationLoadBalancedFargateService) also creates an ALB, so we cannot use it as it is and we need to create those CDK steps ourselves.

The idea is basically to "port" this tutorial from AWS from using AWS CLI to use CDK.

Question is: has anyone done that already and wants to share it or knows the reason why CDK Patterns doesn't have that option?

(If nobody is going to share it, we will do it and then share it of course; I think this option should be present in CDK straight away and it's just a matter of not wasting time with "just" a configuration issue – unless there is something we are not seeing here...).

I am trying to use a variable from with_item to create a fact whose name changes:

I'm reverse proxying an AWS API Gateway stage using nginx. This is pretty straightforward:

My goal is this:

• A single public DNS record for my entire cluster
• A single ingress for my entire cluster
• I don't want to have to update the ingress for new deployments/services- it has a way of automatically routing to them

I'm using gke: https://cloud.google.com/kubernetes-engine/docs/concepts/service-discovery

So by default a service gets an internal DNS record like my-svc.my-namespace.svc.my-zone

What I want is to be able to hit that service like this: http://myapps.com/my-svc.my-namespace.svc.my-zone/someEndpoint

Is this possible? It would mean I could deploy new deployments and services and they would be immediately be accessible to consumers outside the cluster.

Do you have to associate an ingress with a backend service? I don't want to do that because it means I'll need to update it to add every new deployment/service and I want to make it dynamic. Can you have an ingress use internal DNS for routing to services?

I have a microservice arhitecture and each microservice has it's own mysql database. The application works fine in an IDE but i have problems deploying it because I can't bind my mysql db to game microservice. I'm getting Communication link failure. Stack trace is below.

docker-compose.yml

Below is the build.gradle file:

I have 2 applications, both written using spring boot. Both are running in different docker containers. I also have consul running in a different docker container. I have exposed port 8500 for consul using docker-compose.yml file. So, how do I specify to my spring boot applications where to register themselves, i.e, where is consul running. Do I give the address of the mapped port (port mapped to my local machine), or some other change?

The example I'm using right now: https://github.com/Java-Techie-jt/cloud-consul-service-discovery

Edit:

docker-compose.yml: