To edit an service click Details button next to the services in the list.
This is the name that will be displayed wherever your service is used, including external notifications like Slack.
This should be a short and meaningful description that will provide additional context to the service.
Vamp Cloud supports two types of service: API-based services and message-based services.
Vamp Cloud currently only supports API-based services
Message-based services are supported for private cloud customers
API-based services are services that expose a REST-based API or a GraphQL-based API and that can be progressively released using traffic shaping.
Also known as canary releasing, this requires that each new version of a service is deployed in parallel with the existing, live version of the service. For this reason, API-based services deployed using Kubernetes Deployments.
Message-based services are services that either do not expose an API or expose an API using a messaging system like NATS. This type of service cannot be progressively released.
This is the network port on which your container exposes the API. Vamp uses this port to Kubernetes Service to expose the API.
Vamp Cloud currently only supports one network port per service
Your container can expose multiple network ports but Vamp will only create a Kubernetes Service for the chosen port
Vamp Cloud supports two types of Kubernetes workload: Deployments and StatefulSets.
Vamp Cloud currently only supports Kubernetes Deployments. This is because progressive releasing requires the different versions to be deployed in parallel.
StatefulSets and Deployments using rolling updates are supported for private cloud customers
Vampdiscovers new versions of your service using Kubernetes labels.
Each Kubernetes workload that Vamp releases needs to have an app label set, this label is used to locate all the instances of your service for an application.
The default name for the app label is "app". The value must be unique and is normally the name of the service.
The name of the label which will contain the semantic version number for each instance of your service. The default name of this label is "version".
Vamp uses this label to distinguish between versions of your service.
This label is also used to decide which release policy to apply when releasing a new version of your service.
Updating the Service
Click the Update service button to update the service and you will see a message indicating that the service has been updated.