How to manage pods in SynetoOS 5

Written By Christian Castagna (Administrator)

Updated at April 3rd, 2025

→ Applies to: SynetoOS 5.x

All commands in this article are intended to be executed via SynetoOS CLI.

 

Pods: Roles and Responsibilities

  • Minerva - Hypervisor Integration

Minerva is responsible for managing the integration between SynetoOS and hypervisors, enabling seamless VM lifecycle management. It handles:

  • Provisioning of virtual machines.
  • Power management of VMs.
  • Hardware management for virtualized environments.
  • VM migration across different hosts.

 

Marte - Task Execution

Marte is responsible for executing all tasks on the platform, ensuring efficient automation and system operations.

 

Mercurio - Cloud Connection

Mercurio enables seamless communication between on-premise Syneto HYPER appliances and Syneto Central cloud services, facilitating remote management and integration.

 

Chronos - Time Manager

Chronos is responsible for task scheduling and automation within the SynetoOS environment. It handles:

  • Task scheduling to optimize system operations.
  • SLA policy management, including protection tasks and data retention.
  • Recovery point scheduling to ensure regular and reliable backups.

 

Aurora - Monitoring & Metrics

Aurora manages the monitoring and performance metrics of Syneto appliances. Its key functions include:

  • Collecting performance metrics for system optimization.
  • Log collection to provide insights into system health.
  • Alerting and notifications for proactive issue resolution.
  • Integration with Serenity or third-party platforms for comprehensive monitoring.

 

List pods and statuses

kubectl get pods -A

EXAMPLE of output

To be operational, the Ready column status of each pod must be 1/1.
If a different status is found, it means that the pods have not been started correctly.

 

Restart a pod

kubectl delete pod <pods_name>

EXAMPLE

kubectl delete pod mercurio-54cf975dfd-vv2bp

The correct pod name must be taken from the Name column in the pod list.

 

Access pod logs

kubectl logs -f <pods_name>

EXAMPLE

kubectl logs -f mercurio-54cf975dfd-vv2bp

The correct pod name must be taken from the Name column in the pod list.