This topic provides a summary of each container in the system, including its name, role, and the functional impact if the container is unavailable.
To give users a single reference that explains what each container does at a basic level, helping them identify components quickly when collecting logs or investigating issues.
This topic includes information only for the containers that were available at the time of publication. It does not represent a complete list of all system containers.
| Container name |
Container role |
|---|---|
| robot-ui |
This container provides the user interface. In a clustered environment, multiple instances run for resiliency. It typically starts after the core services are up, ensuring that all required processes are available before users can log in. |
| robot-dlminvmgr |
The device lifecycle manager (dlm) tracks devices as they are onboarded to Crosswork Network Controller and monitors their health through basic reach checks. |
| robot-kafka |
Kafka is an open-source messaging system used by Crosswork Network Controller services to process large volumes of streaming data. |
| nats |
The nats is a lightweight, open-source messaging system used by Crosswork Network Controller services. |
| robot-etcd |
The etcd is an open source key value database used by services on Crosswork Network Controller. |
| descheduler |
The descheduler runs on demand and is responsible for moving services to help balance container placement and optimize resource usage across the nodes. |
| robot-orch |
The orchestrator manages infrastructure services, including application lifecycle operations, backup and restore, geo HA functions, node management, and cluster management. |
| docker-registry |
This component is part of the Crosswork Network Controller application lifecycle and handles installing and uninstalling Crosswork Network Controller applications within the cluster, servicing Kubernetes requests for Docker images. |
| cw-sftp |
This component provides an SFTP server for applications that need to download device-related files during the application lifecycle. |
| cw-ftp |
This component provides an FTP server for applications that need to download device-related files during the application lifecycle. |
| cw-ipsec |
This component encrypts pod-to-pod communication across nodes. |