---
title: "Operations"
linkTitle: "Operations"
weight: 40
description: >
  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](/docs/edp/deployment/otc/) section.

#### Further Infrastructural References

- OTC Documentation:
  - [IPCEI-CIS Confluence - OTC](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1000105031/OTC)

### Edge Connect

The `edge` and `orca` clouds within Edge Connect serve as deployment targets for
EDP applications. These environments are [Gardener](https://gardener.cloud/)
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](edge-hub.png)

#### Further Infrastructural References

![Gardener](gardener.png)

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

- [IPCEI-CIS Confluence - Edge Cloud](https://confluence.telekom-mms.com/spaces/IPCEICIS/pages/1122869593/Edge+Cloud)
- [IPCEI-CIS Jira - Edge Cloud Access](https://jira.telekom-mms.com/browse/IPCEICIS-6222?focusedId=3411527&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3411527)
- **Hint:** To authenticate and obtain the cluster `kubectl` context, retrieve
  the `kubeconfig` for the `platform` from your Gardener Account Settings. Then,
  execute:
  ```bash
  gardenctl target --garden mg3 --project platform --shoot edge
  ```

## Monitoring & Observability

The `observability.buildth.ing` [cluster](https://observability.buildth.ing/) within the Prod OTC [tenant](https://edp.buildth.ing/DevFW/infra-deploy/src/branch/main/prod/observability) is designated
for monitoring platform stacks, with visualization primarily through
[Grafana](https://grafana.observability.buildth.ing). 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_observability` flag setting (to include extra components for observability) in the `deploy` workflow within the `infra-deploy` repository.

![EDP Grafana Dashboard](edp-grafana.png)

## Maintenance

EDP maintenance follows an issue-driven strategy.

### Updates & Upgrades

Updates are performed on-demand for individual components in
[stacks](/docs/edp/deployment/infrastructure/stacks/).

### Backup & Recovery

Customer data within EDP is regularly backed up. Refer to
[IPCEICIS-5017](https://jira.telekom-mms.com/browse/IPCEICIS-5017) for details.
