7.4

Table 2‑20. Health Configuration Modes (Continued)
Mode Description
TCP connection If you select TCP connection, you must only enter a port for
the container. The health check attempts to establish a TCP
connection with the container on the provided port. You can
also specify a timeout value for the operation and set healthy
or unhealthy thresholds as with HTTP.
Command If you select Command, you must enter a command to be
executed on the container. The success of the health check is
determined by the exit status of the command.
Ignore health check on provision Uncheck this option to force health check on provision. By
forcing it, a container is not considered provisioned until one
successful health check passes.
Autodeploy Automatic redeployment of containers when they are in
ERROR state.
7 Click Save.
Configure Links in Containers
Links and exposed services address communication across container services and load balancing across
hosts. You can configure link settings for your containers in Containers.
You can use links to enable communication between multiple services in your application. Links in
Containers are similar to Docker links, but connect containers across hosts. A link consists of two parts: a
service name and an alias. The service name is the name of the service or template being called. The
alias is the host name that you use to communicate with that service.
For example, if you have an application that contains a Web and database service and you define a link in
the Web service to the database service by using an alias of my-db, the Web service application opens a
TCP connection to my-db:{PORT_OF_DB}. The PORT_OF_DB is the port that the database listens to,
regardless of the public port that is assigned to the host by the container settings. If MySQL is checking
for updates on its default port of 3306, and the published port for the container host is 32799, the Web
application accesses the database at my-db:3306.
Note It is recommended that you use networks instead of links. Links are now a legacy Docker feature
with significant limitations when linking container clusters, including:
n
Docker does not support multiple links with the same alias. It is recommended that you allow
Containers for vRealize Automation to generate link aliases for you.
n
You cannot update the links of a container runtime. When scaling up or down a linked cluster, the
dependent container’s links will not be updated.
Prerequisites
n
Verify that Containers for vRealize Automation is enabled in your supported vRealize Automation
deployment.
n
Verify that you have container administrator or container architect role privileges.
Configuring vRealize Automation
VMware, Inc. 326