...
Field Name | Required | Description | ||
---|---|---|---|---|
Endpoint Name | Yes | The name of the Endpoint. | ||
Description | No | An optional description for the Endpoint. | ||
Active | Yes | Whether or not the endpoint is active in the system. Defaults to "Yes". | ||
Connection Type | localhost | |||
Endpoint Details | ||||
Endpoint Address | localhost | The host address of this server. Fixed value of localhost. | ||
Base Directory | Yes | Subgroup | No | A working directory on the Endpoint used by FlexDeploy. ~ is not supported here. |
Group | No | An optional group identifier which can be useful when searching for Endpoints. | ||
An optional subgroup identifier which can be useful when searching for Endpoints.Working directory under /var/tmp or /tmp folder is not recommended as administrators generally have cron jobs to purge files based on age and that will cause issues when plugin files are deleted. For example, Error: Could not find or load main class flexagon.fd.core.plugin.ExternalPluginServer will be encountered when plugin lib files are deleted. | ||||
JDK Home | Yes | The JDK Home directory on the Endpoint. Not required if an endpoint is a Docker Host. | ||
Container Details | ||||
Docker Host | No | Whether or not the endpoint is capable of running Docker containers | ||
K8s clusterCluster | No | Whether or not the endpoint can run Docker containers on a K8s cluster | ||
K8s contextContext | No | Name of the configured K8s context | JDK Home||
Group | Yes | The JDK Home directory on the Endpoint. Not required if an endpoint is a Docker Host. |
...
No | An optional group identifier which can be useful when searching for Endpoints. | |
Subgroup | No | An optional subgroup identifier which can be useful when searching for Endpoints. |
Optionally, click the Test Connection button to validate that the FlexDeploy server can connect to itself properly. This will verify the Base Directory and JDK Home settings.
...