Troubleshooting Guide

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

Checking if NGINX ingress is installed
---------------------------------------------
Could not finish setting up Vamp: couldn't find 'ingress-nginx-controller'
Sending failure status to Vamp Cloud
---------------------------------------------

This 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 that 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

Checking if CONTOUR ingress is installed
---------------------------------------------
Could not finish setting up Vamp: couldn't find 'httpproxies.projectcontour.io' CRD
Sending failure status to Vamp Cloud
---------------------------------------------

This occurs when the application is configured to use Contour but the installer cannot find Contour's HTTPProxy Custom Resource Definition (CRD) is not installed on the cluster.

The Vamp Release Agent works with Contour v1.6.0 and newer

Check that you have the Contour Ingress controller deployed in the cluster

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

Checking if 'production' namespace exists
---------------------------------------------
Found namespace 'production'
Error from server (NotFound): secrets "prometheus-connection" not found
Could not finish setting up Vamp: couldn't find 'url' key in secret 'prometheus-connection' in namespace 'production'
Sending failure status to Vamp Cloud
---------------------------------------------

This message indicates that the installer found that Namespace in the application config already exist but was not able to find a Prometheus using the data contained in the 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 Prometheus server is accessible from the cluster.

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

Checking if 'production' namespace exists
---------------------------------------------
Could not find namespace 'production'
namespace/production created
Created namespace 'production'
Could not finish setting up Vamp: couldn't connect to http://prometheus.projectcontour-monitoring:9090
Sending failure status to Vamp Cloud
---------------------------------------------

This 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

+-------------------------------------------+
| |
| Starting setup... |
| |
+-------------------------------------------+
Could not connect to Vault
Could not finish setting up Vamp: couldn't read config from Vault
command terminated with exit code 1

This message indicates that the installer could not connect to Vamp Cloud to fetch 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 you Kubernetes cluster. If your cluster restricts traffic to destinations outside you cluster then installer will fail.

The Vamp Release Agent needs frequent access tovault.vamp.cloudand nats.vamp.cloud