ECCoSP on Kubernetes¶
Four standalone Helm charts. One starting point for installing, configuring and securely operating the Energy Communication Platform.
Get started with Helm Explore the charts
One repository for documentation and charts¶
Helm repository: https://luth2.github.io/helm-charts/
helm repo add eccosp https://luth2.github.io/helm-charts/
helm repo update
helm search repo eccosp --versions
The website explains operations. At the same address, Helm reads the repository index and downloads versioned chart packages. No source code checkout is required.
-
Component Directory
Central trust and registration authority for the ECP network.
-
ECP Broker
Message routing between network participants.
-
Internal Artemis broker
Internal message transport for connected components.
-
ECP Endpoint
Connect business applications to the ECP network.
From package to operation¶
- Choose a version: Check published packages in the chart catalog.
- Prepare values: Retrieve the complete defaults for the selected version.
- Meet the prerequisites: Provision the namespace, images, storage, external Secrets and partner services.
- Render and install: Treat each chart as a separate, versioned Helm release.
- Perform acceptance testing: Verify registration, TLS, the database and message flow.
Do not deploy with unchanged defaults
The charts do not create private Secrets. Each enabled instance needs complete external configuration. Successful Helm rendering replaces neither registration nor functional testing. Do not blindly upgrade existing releases: Migration and PVC preservation.
Further reading¶
- Operations guide: Secrets, HA, storage and updates
- Gateway API and TLS
- Components and official ENTSO-E documentation
- GitHub Releases
The legacy umbrella chart ecco-sp remains in the repository for existing users. For new installations, use only the four standalone charts. These charts do not install EDX Toolbox, Service Catalogue or databases.