traefik | The Cloud Native Application Proxy | Continuous Deployment library

I am getting list of videos from youtube API. I want to also get views and comment count in response from youtube apis.

I am trying the following.

We have a 2 node K3S cluster with one master and one worker node and would like "reasonable availability" in that, if one or the other nodes goes down the cluster still works i.e. ingress reaches the services and pods which we have replicated across both nodes. We have an external load balancer (F5) which does active health checks on each node and only sends traffic to up nodes.

Unfortunately, if the master goes down the worker will not serve any traffic (ingress).

This is strange because all the service pods (which ingress feeds) on the worker node are running.

We suspect the reason is that key services such as the traefik ingress controller and coredns are only running on the master.

Indeed when we simulated a master failure, restoring it from a backup, none of the pods on the worker could do any DNS resolution. Only a reboot of the worker solved this.

We've tried to increase the number of replicas of the traefik and coredns deployment which helps a bit BUT:

• This gets lost on the next reboot
• The worker still functions when the master is down but every 2nd ingress request fails
  • It seems the worker still blindly (round-robin) sends traffic to a non-existant master

We would appreciate some advice and explanation:

• Should not key services such as traefik and coredns be DaemonSets by default?
• How can we change the service description (e.g. replica count) in a persistent way that does not get lost
• How can we get intelligent traffic routing with ingress to only "up" nodes
• Would it make sense to make this a 2-master cluster?

UPDATE: Ingress Description:

I'm trying to get React to change content of the site when it's file is being saved.

I'm using VS code which doesn't have safe write. I'm using docker-compose on Windows via Docker Desktop.

Dockerfile:

I'm trying to set a server-side event correctly with Traefik to no avail. I have a Django server that has a URL that sends sse, I can proxy easily with nginx with this simple conf:

We are using Linkerd 2.11.1 on Azure AKS Kubernetes. Amongst others there is a Deployment using using an Alpine Linux image containing Apache/mod_php/PHP8 serving an API. HTTPS is resolved by Traefik v2 with cert-manager, so that in coming traffic to the APIs is on port 80. The Linkerd proxy container is injected as a Sidecar.

Recently I saw that the API containers return 504 errors during a short period of time when doing a Rolling deployment. In the Sidecars log, I found the following :

I am creating a FastAPI server with simple CRUD functionalities with Postgresql as database. Everything works well in my local environment. However, when I tried to make it run in containers using docker-compose up, it failed. I was getting this error:

I had the previous version (from last yr) of minio running well behind traefik and on portainer with no issues. I attempted an upgrade 4 days ago to the new version and it's been downhill since then. I get the login page but it won't accept credentials; Error: {"code":500,"detailedMessage":"Post \"https://storage.example.com/\": dial tcp :443: i/o timeout","message":"invalid Login"} I suspect it has something to do with the TLS certificate.

Below is my compose file, I've generated the certs as required; any assistance is is welcomed:

I would like to serve custom error pages for common HTTP error codes. I was following this tutorial. For this purpose, I created the following docker-compose.yml file to test the functionality. It consists of:

1. errorPageHandler which is a nginx server which is able to return static HTML pages (404.html and 502.html).

2. whoami1 which routes the request to port 80 of traefik/whoami image

3. whoami2 which routes the request to non-existent port 81 of traefik/whoami image which results in 502 - Bad Gateway

I am trying to setup a certificate for a locally running react app on a virtual host local.example.com. This has to just work locally on docker setup. After going through some articles, I came up with this docker-compose.yml: