node-prox | Hookable socks5 proxy client and server in node.js | Proxy library

I found the solution: I had to set the role kms.keys.encrypterDecrypter to the service account which is used to control Kubernetes cluster in the settings of Yandex.Cloud project catalog.

I've found a solution

Add these lines:

Unfortunately, this is not an easy fix of simply changing some of your code to make it work. You appear to have a fundamental conceptual issue. At a code level, you are using wait 0.1 to stop everything happening immediately, and you don't have any command tick to advance time.

Conceptually, you need to separate the things that are there when you start and the things that happen through time. You have done this, breaking your model into the setup and go procedures as normal. But within the time progression, you need to imagine a tick as representing some specific amount of time (let's say 10 seconds). What happens within a 10s slice of time - all your evacuees move to the next node, or at least towards it or whatever.

As a first approximation:

1. replace your ask one-of type constructions with ask (that will instruct them all to do it).
2. remove the wait instruction
3. add tick as the last command in the go procedure (to advance the clock)

Then your go button will move through time every time you press it. You can edit the go button to repeatedly run the go procedure by checking the 'forever' box.

I eventually got to the bottom of this. I had not copied the same Service Account signing keys onto each master node (sa.key, sa.pub).

These keys are documented here: https://github.com/kubernetes/kubeadm/blob/master/docs/design/design_v1.7.md

a private key for signing ServiceAccount Tokens (sa.key) along with its public key (sa.pub)

And the step that I had missed is documented here: https://kubernetes.io/docs/setup/independent/high-availability/

Copy the contents of /etc/kubernetes/pki/ca.crt, /etc/kubernetes/pki/ca.key, /etc/kubernetes/pki/sa.key and /etc/kubernetes/pki/sa.pub and create these files manually on master1 and master2

Look at the ports of your app / Dockerfile:

./app1/app1.js

}).listen(8085);

and

./app1/Dockerfile

Expose 8086

they are missmatching.

The part i was missing is that jwilder/nginx-proxy is reflecting docker to look for containers that needs to be proxied.

Original post:

I guess that your problem is that reverse proxy container cannot reach each app. Therefor remove the depends_on from node-app1 and node-app2 and add in node-proxy: