Edge Services

A Secure Edge service is a representation of an application running on an Edge iNode. A service contains application containers and shared networking and storage resources.

A service has an IP address that can be allocated dynamically by an iNode or specified manually as a static IP address. The service IP address is part of the same IP subnet as the iNode local network. All containers in the service share this IP address. They also share network ports.

A service can have storage volumes shared by all containers in the service. A volume is a directory, possibly with data in it. Volumes are used to retain data across container restarts. This is important because on-disk files in a container are lost when the container ceases to exist. Note that when the service ceases to exist, the storage volumes in the service also go away and the data in the volumes will be deleted.

A service can also have secrets, which are secure objects that store sensitive data needed by application containers. Examples of this kind of data are passwords, application license keys, Secure Shell (SSH) keys, container image pull credentials, etc.

If you are using one of the predefined services in Secure Edge Portal and need to use an external Domain Name System (DNS) server instead of the default, which is the iNode’s DNS server configuration, you can configure up to three nameservers for an edge service through Secure Edge Portal.

The status of a service is derived from the status of the containers in the service. The status of a container can be:

• WAITING – Container is being created, or is starting, or is paused
• RUNNING – Container is running
• TERMINATED – Container has exited; could be due to success or failure
• UNKNOWN – Container status is not available because the iNode is not ALIVE

The status of a service can be:

• PENDING – All containers in the service are in WAITING status
• HEALTHY – All containers in the service are in RUNNING status
• UNHEALTHY – Containers in the service are in disparate status
• TERMINATED – All containers in the service are in TERMINATED status
• UNKNOWN – Service status is not available since the iNode is not ALIVE