--- title: "Container" slug: "container" status: "new" updated: 2026-11-17T17:13:04Z published: 2026-11-17T17:13:04Z canonical: "help.symphonysummitai.com/container" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Container Container credentials enable Discovery to connect to supported container platforms and retrieve information about container hosts, clusters, and associated resources. The **Container Credentials** page supports the following credential types: | Credential Type | Supported Platform | Purpose | | --- | --- | --- | | Docker | Docker Engine | Connects to the Docker Engine API through a TCP endpoint or Unix socket to discover Docker resources. | | Kubernetes | Kubernetes | Connects to the Kubernetes API server through a bearer token and cluster URL to discover Kubernetes resources. | ### Docker Credentials Use a Docker credential profile to connect to the Docker Engine API through a TCP endpoint or Unix socket. You can optionally provide TLS certificate paths for a secure connection. ![Figure: Docker](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/container-image-8ngqatq0.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=m0N51EWRigaMLu%2FvWDMeUgWPxdJNVQXiFq9znCt%2BWTQ%3D) Figure: Docker #### Configure a Docker Credential Profile Create a Docker credential profile to allow Discovery to connect to the Docker Engine API through a TCP connection or Unix socket. You can configure optional TLS authentication to secure the connection. Perform the following steps to configure and test a Docker credential profile: 1. Select the **Container** credential category. 2. Select the **Docker** tab. 3. Select **New account**. 4. Select the required department from the **Department** list. 5. Enter a unique name for the credential profile in **Profile Name**. 6. Enter the hostname or IP address of the Docker host in **Docker Host/IP**. 7. Enter the port used to connect to the Docker Engine API in **Port**. 8. Select the connection type from the **Connection** list. 9. Select the authentication method from the **Authentication** list. 10. If you select a TLS-based authentication method, select the source of the TLS credentials from the **Credential source** list. 11. Provide the required TLS credentials: - Upload a .pem file or paste the certificate in **CA Certificate**. - Upload a .pem file or paste the certificate in **Client Certificate**. - Upload a .pem file or paste the private key in **Client Private Key**. - Enter the private key passphrase in Private key passphrase, if applicable. 12. Select the Discovery Worker that can connect to the Docker host from the **Discovery worker** list. 13. Select **Test Connection** to verify the connection and authentication details. 14. After a successful connection test, select **Save Profile**. Select **Cancel** to discard the entered information. #### Docker Credential Fields | Field Name | Description | | --- | --- | | Department | Select the department for which you want to create the Docker credential profile. | | Profile Name | Enter a unique and descriptive name for the credential profile. For example, Production Docker Hosts. | | Docker Host/IP | Enter the hostname or IP address of the system that hosts the Docker Engine API. For example, 192.168.50.70. | | Port | Enter the port used to connect to the Docker Engine API. For example, enter 2376 for a TLS-enabled TCP connection. | | Connection | Select the connection type used to connect to the Docker Engine API, such as **TCP**. | | Authentication | Select the authentication method used for the connection, such as **Mutual TLS (mTLS)**. The fields displayed under **TLS credentials** depend on the selected authentication method. | | Credential source | Select how the TLS credentials are provided. Select **Uploaded / stored (recommended)** to upload or paste the certificates and private key. | | CA Certificate | Upload a .pem file or paste the Certificate Authority certificate used to verify the Docker host certificate. | | Client Certificate | Upload a .pem file or paste the client certificate used to authenticate the Discovery Worker to the Docker host. | | Client Private Key | Upload a .pem file or paste the private key associated with the client certificate. | | Private key passphrase | Enter the passphrase for the client private key, if the private key is passphrase-protected. This field is optional. | | Discovery worker | Select the Discovery Worker that can connect to the Docker host. The connection test uses the selected worker to check connectivity and authentication. | **Note:** The certificate paths must be accessible from the Discovery Worker that connects to the Docker host. ### Kubernetes Credentials Use a Kubernetes credential profile to connect to the Kubernetes API server by using the cluster URL and bearer token. ![Figure: Kubernetes](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/container-image-eeeeuihr.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=aRFk5IZSLooKZX10wfnrJZgUsDoMh4%2Fm3LtPEzck%2F2M%3D) Figure: Kubernetes #### Configure a Kubernetes Credential Profile Create a Kubernetes credential profile to allow Discovery to connect to the Kubernetes API server and retrieve information about the cluster and its resources. Perform the following steps to configure and test a Kubernetes credential profile: 1. Select the **Container** credential category. 2. Select the **K8s** tab. 3. Select **New account**. 4. Select the required department from the **Department** list. 5. Enter a unique name for the credential profile in **Profile Name**. 6. Enter the complete Kubernetes API server URL in **API Server URL**. 7. Enter the token used to authenticate with the Kubernetes API server in **Bearer Token**. 8. Select **Bearer token** from the **Authentication** list. 9. Select the source of the CA certificate from the **CA certificate source** list. 10. Provide the CA certificate in one of the following ways: - Drag and drop a .crt, .pem, or .cer certificate file into **Drop CA certificate**, or select **browse** to locate the file. - Paste the certificate in **Or paste PEM (optional)**. 11. Enable **Skip TLS verify** to connect without verifying the Kubernetes API server certificate. 12. Select **Test Connection** to verify the API server URL, bearer token, certificate, and connection settings. 13. After a successful connection test, select **Save Profile**. Select **Cancel** to discard the entered information. #### Kubernetes Credential Fields | Field Name | Description | | --- | --- | | Department | Select the department for which you want to create the Kubernetes credential profile. | | Profile Name | Enter a unique and descriptive name for the credential profile. For example, Production Kubernetes Cluster. | | API Server URL | Enter the complete URL of the Kubernetes API server, including the protocol and port. For example, https://k8s-master:6443. | | Bearer Token | Enter the bearer token used to authenticate with the Kubernetes API server. | | Authentication | Select the authentication method used to connect to the Kubernetes API server. The current supported option is **Bearer token**. | | CA certificate source | Select how you want to provide the CA certificate. Select **Uploaded / stored (recommended)** to upload the certificate or paste its PEM content. | | Drop CA certificate | Drag and drop a .crt, .pem, or .cer CA certificate file, or select **browse** to locate and upload the file. The Discovery Worker uses the certificate to verify the Kubernetes API server during TLS communication. | | Or paste PEM (optional) | Paste the CA certificate in PEM format instead of uploading a certificate file. | | Skip TLS verify | Enable this option to connect without verifying the Kubernetes API server certificate. Use this option only when TLS certificate verification is not required. | > [!NOTE] > Note > > The CA certificate path must be accessible from the Discovery Worker that connects to the Kubernetes API server. Manage Container Credential Profiles The credential profile list displays the profiles configured for the selected container platform. Select the **Docker** or **K8s** tab to view and manage the corresponding credential profiles. - [List Page](/apex/docs/container#credential-profile-list) - [Activate/Deactivate credential profile](/apex/docs/container#activate-or-deactivate-a-credential-profile) - [Edit container](/apex/docs/container#edit-a-container-credential-profile) - [Change History](/apex/docs/container#change-history-fields) - [List page actions](/apex/docs/container#list-page-actions) ### Credential Profile List | Column | Description | | --- | --- | | Account Name | Displays the name assigned to the credential profile. | | Type | Displays the credential type, such as **Docker** or **Kubernetes**. | | Username | Displays the username associated with the credential profile. A hyphen (—) displays when the credential type does not use a username. | | Active Status | Indicates whether the credential profile is active. Use the toggle to activate or deactivate the profile. | | Last Updated | Displays the date and time when a user last updated the credential profile. Select the column heading to sort the profiles by the last updated date and time. | | Actions | Provides options to edit the credential profile or view its change history. | ### Activate or Deactivate a Credential Profile Use the **Active Status** toggle to control whether Discovery can use the credential profile. - Turn on the toggle to activate the credential profile. - Turn off the toggle to deactivate the credential profile. A deactivated credential profile remains available in the list, but Discovery does not use the profile for later discovery operations. ### Edit a Container Credential Profile To edit a container credential profile, perform the following steps: 1. Select the **Container** credential category. 2. Select the required container tab: - **Docker** - **K8s** 3. Locate the credential profile in the list. 4. Select the **Edit** icon under **Actions**. 5. Update the required profile details. 6. Select **Test Connection** to check the updated connection details. 7. Select **Save Profile**. ### View Credential Profile History The credential profile history provides a read-only record of changes made to the selected profile. The newest changes display first, and secret values remain masked. To view the credential profile history: 1. Select the **Container** credential category. 2. Select the required container tab. 3. Locate the credential profile in the list. 4. Select the **History** icon under **Actions**. 5. Review the available history records. #### Change History Fields | Field Name | Description | | --- | --- | | Field name | Shows the credential profile field that a user added or changed. | | Old value | Displays the field value before the change. A hyphen (—) displays when no previous value exists. Secret values remain masked. | | New value | Displays the field value after the change. Secret values remain masked. | | Date changed | Displays the date and time when the change occurred. | | Changed by | Displays the identifier of the user who made the change. | Select **Close** to exit the **Change history** page and return to the credential profile list. ### List Page Actions | Action | Description | | --- | --- | | New account | Opens the credential profile form for the selected container platform. | | Active Status | Activates or deactivates the credential profile. | | Edit | Opens the selected credential profile for modification. | | History | Displays the change history for the selected credential profile. |