Step 4: Expose Your Service
To expose your service outside the Kubernetes cluster, you need to tell Vamp the domain name and path you want to use for the application.
The next step is to expose your service outside of the Kubernetes cluster, using a publicly accessible URL.

Expose Your Application

Choose whether to expose your application.
Vamp Cloud currently requires applications to be exposed through a Kubernetes Ingress.
Private cloud customers have the option to not expose an application outside of the cluster.
Choose Yes if your application has a mix of services, some or all of which need to be exposed.
Only choose No if none of the services in the application should be exposed.
The No option is available only if No Ingress was selected in Step 1.
This is the fully qualified domain name that you want to use for your application. For example,
Applications can be exposed as either a primary domain, such as,or a subdomain, such as
Exposing multiple applications on the same primary domain or subdomain is not supported.
For example, and is not supported.


Choose whether to use TLS to secure all external network traffic to your application.
If you choose Terminate at the Edge, the URL of your application will start with https:// instead of http://.

Secret Name

If you enable TLS, you need to provide the name of a Kubernetes Secret for the TLS certificates.
If you are using cert-manager or a similar project to dynamically provision TLS certificates, use the name of the application as the certificate name, for example, my-application-tls.
If you already have a TLS certificate for your domain, enter the name of the Kubernetes Secret that contains the certificate chain.


To expose a service, you need to give it a URL path.
The default is to expose each of your services, using the path name /<service-name>. If you want to expose your service on a different path, for example /, you can edit the path.
If you do not want to expose a service, you can delete the route.
If choose not to expose a service, you will be unable to use release policies that include traffic-based SLOs with that service.