nging | beautiful Go language general-purpose background management | FTP library

Don't know which tutorial you are following and not sure how you created the pod but if it worked for them and it doesn't work for you then the issue is probably in that you are running newer version of kubernetes.

Using kubectl run ... used to create pod as well as replication controller. Nowadays (since 1.18) it only creates a single pod. You need either replication controller (deprecated), or relicaset or deployment in order to scale it. You can't scale a single pod (pod resource doesn't have a concept of replicas that you might scale - increase/decrease).

You can replace the old run command with

you can add the command to remove the default nginx index page just before copying

Your docker-compose configuration is fine, there is no reason it wouldn't work.

There might be an issue with permissions or something similar, depending on the platform you use. If you start from scratch (git clone, docker-compose up), it should work.

Solution was to create one ingress for the api that require url-rewrite, and one for the front that does not. From the question above, I replaced the one ingress with these two:

While you can override the warning about ERR_CERT_AUTHORITY_INVALID it will only override the warning for exactly this certificate at exactly this hostname and not automatically trust this certificate for any other hosts.

Just imagine that this would be otherwise: in this case some man in the middle attacker could use a certificate to intercept the connection to some unimportant host where many would just override the warning because there are no sensitive data. Once this is done the attacker could use the same certificate (now trusted by the browser) to intercept connections to important hosts. That's why any certificate exemption is only for the specific hostname where the certificate was explicitly exempted for.