Restarting Agents

How to restart Connectware agents running in Docker or Kubernetes environments.

Connectware agents run as containerized workloads, which are managed by your chosen deployment method (Docker or Kubernetes). Agent restarts are performed outside of Connectware using standard platform tools.

Restarting an agent can be necessary if the agent becomes unresponsive, loses connectivity, or needs to reload its configuration.

Kubernetes

Restarting Agents on Kubernetes

Restarting a Single Agent

Use this if you want to restart a single agent.

kubectl rollout restart statefulset ${STATEFULSET_NAME} -n ${NAMESPACE}

Replace ${STATEFULSET_NAME} with your agent StatefulSet name and ${NAMESPACE} with your namespace.

Restarting All Agents from a connectware-agent Installation

Use this if you want to restart all agents managed by one connectware-agent installation.

kubectl rollout restart statefulset -l app.kubernetes.io/instance=${INSTALLATION_NAME} -n ${NAMESPACE}

Replace ${INSTALLATION_NAME} with your Helm release name and ${NAMESPACE} with your namespace.

Result

After restarting, your agent will automatically reconnect to Connectware once the pod is running again. Restarting an agent does not affect other agents or the Connectware core system.

Troubleshooting

If your agent does not reconnect after a restart, check the pod/container logs for errors and ensure network connectivity to Connectware.

Docker

Additional Resources

For platform-specific details, see the official documentation:

• Docker: https://docs.docker.com/

• Kubernetes: https://kubernetes.io/docs/