Search…
Troubleshooting Guide

Error: couldn't find 'ingress-nginx-controller'

1
Checking if NGINX ingress is installed
2
---------------------------------------------
3
Could not finish setting up Vamp: couldn't find 'ingress-nginx-controller'
4
5
Sending failure status to Vamp Cloud
6
---------------------------------------------
Copied!
This error occurs when the application is configured to use NGINX but the installer cannot find a Deployment called ingress-nginx-controller anywhere in the cluster.
Check you have the NGINX Ingress controller deployed in the cluster
If your NGINX Ingress controller has a different name, then follow these instructions

Error: couldn't find 'httpproxies.projectcontour.io' CRD

1
Checking if CONTOUR ingress is installed
2
---------------------------------------------
3
4
Could not finish setting up Vamp: couldn't find 'httpproxies.projectcontour.io' CRD
5
6
Sending failure status to Vamp Cloud
7
---------------------------------------------
Copied!
This error occurs when the application is configured to use Contour but the installer cannot find Contour's HTTPProxy Custom Resource Definition (CRD) on the cluster.
The Vamp Release Agent works with Contour v1.6.0 and newer.
Check you have the Contour Ingress controller deployed in the cluster

Error: couldn't find 'url' key in secret 'prometheus-connection' in namespace 'xyz'

1
Checking if 'production' namespace exists
2
---------------------------------------------
3
Found namespace 'production'
4
Error from server (NotFound): secrets "prometheus-connection" not found
5
Could not finish setting up Vamp: couldn't find 'url' key in secret 'prometheus-connection' in namespace 'production'
6
7
Sending failure status to Vamp Cloud
8
---------------------------------------------
9
Copied!
This error message indicates that the installer found the specified Namespace, but was unable to locate a Prometheus server using data from prometheus-secret.
Check that the prometheus-connection Secret exists.
Check that the prometheus-connection Secret contains a url key.
Check that the value of the url key is a valid URL and that the Prometheus server is accessible from the cluster.

Error: couldn't connect to http://prometheus.projectcontour-monitoring:9090

1
Checking if 'production' namespace exists
2
---------------------------------------------
3
Could not find namespace 'production'
4
namespace/production created
5
Created namespace 'production'
6
Could not finish setting up Vamp: couldn't connect to http://prometheus.projectcontour-monitoring:9090
7
8
Sending failure status to Vamp Cloud
9
---------------------------------------------
Copied!
This error occurs when the application is configured to use Contour but the installer did not find a Prometheus server in the expected location. By default, the installer tries to connect to a Service named prometheus in the projectcontour-monitoring Namespace.
If Prometheus server is installed in a different location then follow these instructions to configure a custom Prometheus location.

Error: couldn't read config from Vault

1
+-------------------------------------------+
2
| |
3
| Starting setup... |
4
| |
5
+-------------------------------------------+
6
Could not connect to Vault
7
Could not finish setting up Vamp: couldn't read config from Vault
8
command terminated with exit code 1
Copied!
This error message indicates that the installer could not connect to Vamp Cloud to fetch the configuration data needed to complete the installation.

Expired Token

This error normally occurs when your try to run the installer with an expired token.
The installer token is only valid for 30 minutes and can only be used once.
Generate a new install command in the Vamp Cloud UI and run the installer again.

Restricted Network Access

Another common cause of this error is that network traffic to Vamp Cloud is blocked.
The installer runs as a Pod in your Kubernetes cluster. If your cluster restricts traffic to destinations outside you cluster, the installer will fail.
The Vamp Release Agent needs frequent access tovault.vamp.cloudand nats.vamp.cloud.