At the core of the Deployments Module is the
Service Configuration commonly called
You can think of
services as an equivalent of
Pods in Kubernetes.
Space Cloud only supports running stateless services as of now.
service describes the following:
Each service requires an id. These ids need to be unique inside a project. Services can be accessed internally using the domain name Space Cloud generates from this service id.
The format for the domains goes as:
For example, if you create a service by the id
myapp inside the project
myproject, the domain generated would read as
Note: This is true for the docker driver as well.
service is composed of one or more tasks. You can see each task as an equivalent of
Containers in each
Currently, Mission Control lets you create a single task in each service. For creating multiple tasks per service, use the
There are several cases when you would need to club several tasks together into one service.
Space Cloud automatically injects an
metrics-proxy when using the Kubernetes driver.
You specify the following for each task.
Space Cloud makes you explicitly define the upstream services your service depends on. All upstream services in the project are accessible by default.
Whitelists are a way to describe service to service communication policies. As the name implies, it restricts downstream services from accessing the current service.