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:
Edge Connect
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
Further Infrastructural References
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
kubectlcontext, retrieve thekubeconfigfor theplatformfrom 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.
Login credentials can be found in the grafana-admin-credentials secret within the cluster.
NOTE: The deployed stacks are depending on the
is_observabilityflag setting (to include extra components for observability) in thedeployworkflow within theinfra-deployrepository.
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.