x-proxy | honeypot proxy | Proxy library

The try_files directive needs to be set in the Angular apps Nginx Docker component. The first Nginx instance does not have access to the Angular containers' filesystem, which it needs to check whether a file exists or not.

Create a Nginx configuration file, admin/nginx-config.conf:

You can try to configure the temporary cache directory

Running kubectl get ingressclass returned 'No resources found'.

That's the main reason of your issue.

Why?

When you are specifying ingressClassName: nginx in your Grafana values.yaml file you are setting your Ingress resource to use nginx Ingress class which does not exist.

I replicated your issue using minikube, MetalLB and NGINX Ingress installed via modified deploy.yaml file with commented IngressClass resource + set NGINX Ingress controller name to nginx as in your example. The result was exactly the same - ingressClassName: nginx didn't work (no address), but annotation kubernetes.io/ingress.class: nginx worked.

(For the below solution I'm using controller pod name ingress-nginx-controller-86c865f5c4-qwl2b, but in your case it will be different - check it using kubectl get pods -n ingress-nginx command. Also keep in mind it's kind of a workaround - usually ingressClass resource should be installed automatically with a whole installation of NGINX Ingress. I'm presenting this solution to understand why it's not worked for you before, and why it works with NGINX Ingress installed using helm)

In the logs of the Ingress NGINX controller I found (kubectl logs ingress-nginx-controller-86c865f5c4-qwl2b -n ingress-nginx):

The issue seemed to be the number of times I had requested a certificate for those specific domains. I tried the deploy multiple times to figure out how to do it properly for the deployment server and also to write a proper version of the script, that I requested many times a certificate for two specific domains.

The issue was resolved after I tried a different domain and subdomain.

I make a bit of research, and it led me to this github issue: https://github.com/Azure/aks-engine/issues/1494

SMB mount options(including dir permission) could not be changed, it's by SMB proto design, while for disk(ext4, xfs) dir permission could be changed after mount close this issue, let me know if you have any question.

From what I see, there are no options chown after mounting it.

BUT

I also find a workaround that might apply to your issue: https://docs.openshift.com/container-platform/3.11/install_config/persistent_storage/persistent_storage_azure_file.html

It's Workaround for using MySQL with Azure File for Openshift, but I think it could work with your case.

This is up to your architecture.

• If your NGINX proxy is the public endpoint, it must have SSL certificate.
• If your Load Balancer is the public endpoint, it must have SSL certificate.

At this case, your Load Balancer is internal config which only allows internal VPC access so HTTP traffic (over port 80) is enough. But for best practices, you can enhance security at any layers and make them HTTPS which is encouraged.

For security reasons, for the public endpoint, we usually configure to redirect traffic from port 80 to port 443.

Reference: https://linuxize.com/post/redirect-http-to-https-in-nginx/

Fortunately increasing timeoutSeconds for both livenessProbe & readinessProbe from 1 to 60 fixes the issue.

In the on("data") callback you receive chunks of data, so it only makes sense to juse JSON.parse after all the chunks have been assembled. So you should do something like this:

It looks like you're trying to replace the application code in the image with different code using Docker bind mounts. Docker's general model is that a container runs a self-contained image; you shouldn't need to separately install the application code on the host.

In particular, these two volumes: blocks cause the error you're seeing, and can safely be removed: