PLATFORM MODULES

The right tools for each operational task.

E-platform connects deployment, operations, monitoring and continuity in one interface. Explore what each module does and how it supports your team’s daily work.

Zero Installation — Provisioning

Deploy servers from a common foundation.

Avoid installing Ubuntu, RKE2 and the platform manually on each server. Prepare the first server and deployment plan, then create boot media for subsequent servers.

Plan / Image / Flash
Server tracking and the failed-server path

Deployment details

High Availability

Understand the impact of losing a node.

Review node readiness, control-plane and etcd quorum, replica distribution and single points of failure. What-if analysis helps identify what the environment needs for high availability.

What-if node failure analysis
Readiness tied to cluster topology

Continuity readiness

Auto Scaling

Match application replicas to demand.

Scale workload replicas with actual demand, within limits that account for allocatable capacity, quotas and the headroom needed after a node loss.

Policies based on load and limits
Capacity headroom for an N−1 scenario

Smart Maintenance

Prepare maintenance before acting.

Run preflight checks and a dry run, then cordon a node, drain its workloads and return it to service through authorized, confirmed and audited actions.

Preflight checks and dry runs
Cordon / Drain / Return to service

Backup & DR

Connect backups to a recovery plan.

Organize backups for Kubernetes resources, volumes and databases, with schedules, retention, destinations, encryption, recovery plans and isolated restore tests.

RPO / RTO objectives in recovery plans
Restore tests in an isolated environment

Backup and recovery

Disaster

Coordinate continuity across two sites.

Coordinate starting protected services at a prepared standby site when the primary site cannot continue. Pairing, synchronization, production ownership and operation logs keep the transition organized.

Status / Pairing / Sync / Requests
Balance / Logs / Settings

Coordination between sites

Hardware Health

Connect server health with its components.

Follow CPU, memory, RAID, fans, temperatures, power supplies and network interfaces to identify the component that needs attention.

Hardware indicators in the server context
Health, temperature and power visibility

Network Monitoring

See what is happening on network links.

Review link state, speed, errors and bonds to distinguish connectivity problems from resource pressure or application issues.

Link state, speed and errors
Network interface and bond visibility

OBSERVABILITY WITH OPERATIONAL CONTEXT

From component health to service impact.

Observability tools add context to readings and alerts, helping the team identify what needs investigation or action.

Service Availability

Is the service reachable from the site?

Run HTTP, HTTPS and TCP checks from inside the site, with availability and SLO indicators calculated from actual samples.

Unified Alerts

Which alerts need action?

Group and deduplicate Alertmanager alerts, with Arabic and English runbooks and audited maintenance silences.

Power & UPS

How does power affect the nodes?

Read UPS state, remaining runtime, power-supply redundancy and affected nodes through NUT and Redfish integrations.

Available modules and integrations depend on the project licence, hardware and services connected to the environment.

E-platform overview showing nodes, workloads, resource requests and a cluster map — Start with the overview, then open the relevant module.
Enterprise Overview puts cluster state and resources in context before teams move to specialized details and actions.