-
Hello, I have tried to replicate RADAR-Kubernetes with the documentation you provide but I get this error whenever I run it, I am using minikube to deploy it with 8cpu-32gb-220g: Upgrading release=nginx-ingress, chart=radar/ingress-nginx hook[postsync] logs | Application nginx-ingress (default) is ready, installation successful. UPDATED RELEASES: FAILED RELEASES: PATH: ARGS: ERROR: EXIT STATUS STDERR: COMBINED OUTPUT: - I can't understand what the problem is and when I open the log of the gninx controller pod I see the following: NGINX Ingress controller W0518 01:12:01.144917 7 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I'm doing all this locally. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Looks to me like the newly created service account (nginx-ingress-ingress-nginx) has not got the right permissions on "services" and "configmaps".
|
Beta Was this translation helpful? Give feedback.
-
Is it possible to test the installation with
|
Beta Was this translation helpful? Give feedback.
-
The 400 error is strange, I haven't seen it happening before. Please post more information about your installation.
|
Beta Was this translation helpful? Give feedback.
It was resolved, apparently there were problems because there is a gninx that provides ssl. Quite the ssl redirect. And I can enter without problems.