Install with Edgectl

We recommend edgectl for installing Ambassador Edge Stack. Edgectl is very helpful and quite robust, but there are certain situations where it is unable to successfully complete the installation. In those cases, edgectl directs you to the following appropriate “more help” detailed instructions pages. (If you’re not using edgectl install, these pages won’t be that relevant, but they are here for you to read if you want.)

• Ambassador Edge Stack failed to respond to the ACME challenge
• Could not find a Kubernetes cluster
• Email request interrupted
• Failed to create a Host resource in your cluster
• Failed to download AES manifests
• Failed to download CRD manifests
• Failed to download Helm chart
• Failed to log in to the cluster
• Failed to parse AES manifests
• Failed to register DNS name for the current installation
• Failed to retrieve the Host resource from your cluster
• Found existing AES CRD but no Ambassador Edge Stack installation
• Found existing Ambassador Edge Stack installation
• Found incompatible AES CRD versions
• kubectl not found in $PATH
• Timeout while waiting for AES manifests to be deployed
• Timeout while waiting for CRD manifests to be deployed
• Unable to acquire a DNS name for the custer's load balancer
• Unable to acquire a TLS certificate from Let's Encrypt
• Unable to apply AES manifests
• Unable to apply CRD manifests
• Unable to create a new client for the given configuration
• Unable to get client configuration or namespace
• Unable to get versions via kubectl
• Unable to provision a load balancer or retrieve the IP address
• Unable to resolve your new DNS name on this machine
• Unable to talk to the AES pod