Operations

Operational guides for deploying, monitoring, and maintaining the Edge Developer Platform components.

Operations Overview

This section outlines some of the operational aspects of the Edge Developer Platform (EDP). The approach emphasizes a “developer operations” mode, primarily focusing on monitoring and issue resolution rather than traditional operations.

Deployments

EDP Clusters

For details on deploying instances of EDP on OTC, see this section.

Further Infrastructural References

OTC Documentation:
- IPCEI-CIS Confluence - OTC

Edge Connect

Discontinued — under reconstruction

The edge and orca Gardener clusters described in this subsection have been discontinued. The hub, console and Gardener URLs below are no longer reachable, and cluster-level kubectl access via Gardener Account Settings is not available. The content is retained as historical reference pending the next iteration of the underlying infrastructure. See the EdgeConnect overview for current status of the surrounding tooling.

The edge and orca clouds within Edge Connect serve as deployment targets for EDP applications. These environments are Gardener Kubernetes clusters.

For general use, interaction with Edge Connect is intended via its web UI: https://hub.apps.edge.platform.mg3.mdb.osc.live

Edge Hub

Further Infrastructural References

Gardener

Cluster-level access is available for addressing operational issues. Details on obtaining access are provided in the following resources:

IPCEI-CIS Confluence - Edge Cloud
IPCEI-CIS Jira - Edge Cloud Access
Hint: To authenticate and obtain the cluster kubectl context, retrieve the kubeconfig for the platform from your Gardener Account Settings. Then, execute:
```
gardenctl target --garden mg3 --project platform --shoot edge
```

Monitoring & Observability

The observability.buildth.ing cluster within the Prod OTC tenant is designated for monitoring platform stacks, with visualization primarily through Grafana. Currently, a formal operational monitoring lifecycle with defined metrics and alerts is not fully established, reflecting the current developer-centric operational mode.

NOTE: The deployed stacks are depending on the is_observability flag setting (to include extra components for observability) in the deploy workflow within the infra-deploy repository.

EDP Grafana Dashboard

Maintenance

EDP maintenance follows an issue-driven strategy.

Updates & Upgrades

Updates are performed on-demand for individual components in stacks.

Backup & Recovery

Customer data within EDP is regularly backed up. Refer to IPCEICIS-5017 for details.