Service
In Hyper, a Service
is an abstraction which defines a logical set of containers in a single (private) network and a policy by which to access them. The set of containers targeted by a Service is determined by labels.
As an example, consider an image-processing backend which is running with 3 replicas. Those replicas are fungible - frontends do not care which backend they use. While the actual containers that compose the backend set may change, the frontend clients should not need to be aware of that or keep track of the list of backends themselves. The Service abstraction enables this decoupling.
Every service will receive an internal IP address which can only be accessed within the network where the service resides. For public access, a floating IP address needs to be attached by attach-fip
command.
Currently, service supports four different protocols:
tcp
tcp traffic ---> service ---tcp---> containershttp
http traffic ---> service ---http---> containershttps
https traffic ---> service ---https---> containershttpsTerm
https traffic ---> service ---http---> containers
Examples
Create a HTTP service:
Create a HTTPS termination service:
First gets a https certificate from certificate:
Then create a service with protocol httpsTerm
:
List service:
Attach an allocated floating IP to a service:
Scale the service to more replicas:
Rolling update the service to new image:
Last updated