Skip to content

Introduction to the Egeria Helm Charts

This set of charts has been built to assist in learning & demonstration activities, testing, and may also form a basis for production deployments.

See Helm for information on configuring Helm to be able to access these charts via a repository.

Available Charts

  • base - creates a simple Egeria environment with a single metadata server. Includes the Ecosystem UI so that metadata can be searched, browsed.
  • odpi-egeria-lab - Demo scenario for 'Coco Pharmaceuticals'. Multiple platorms, metadata repositories, cohorts. Demonstration script via Juypter notebooks. Includes both the Ecosystem UI & business UI .
  • cts - Supports testing repository connectors using our Conformance Test Suite. Can be configured to support other repositories via simple values.
  • pts - Performance test suite to aid in measuring the performance of repository connectors.

Issues & Advanced usage:

Use of 'default' namespace with OpenShift

Do not install either strimzi or egeria charts into the 'default' namespace using OpenShift. They will not work due to the way that a scc is not applied.

Red Hat recommend that the default namespace should not be used for applications.

Instead create a new project first, for example with

oc create project lab
Your context will be switched to this after creation, you can return at any time with
oc project lab
An scc will be correctly applied, and the security context of {} used by the chart as provided will allow the container to be correctly assigned a user/group within the permitted range. Storage volumes will also be assigned the correct permissions. This will not happen with 'default'.

A similar issue may apply in other kubernetes environments. Generally use of the default namespace is discouraged - though it remains common when running locally.

Strimzi: permissions and co-existance

When any of the above charts are deployed, they include the install of the Strimzi operator (for kafka). However Strimzi deploys some cluster-scoped resources which has two implications:

  • Admin level to the cluster permissions are needed - since cluster resources need to be deployed. Without these permissions the Charts will not work.
  • As the resources are cluster-level you cannot install a second chart - or additional install of the same chart as clashes will be seen on these resources. So no testing, debug in parallel or shared k8s clusters for multiple developers.

To address this, the charts all have the option to NOT install Strimzi. If this is done * You can install multiple charts (recommended 1 per namespace) for the same, or different, user. * You do not need such high permissions to install the Egeria chart.

To skip the install add the following to the install: --set strimzi.enabled=false ie:

helm install base egeria-base --set strimzi.enabled=false

You DO need Strimzi already installed by an admin:

  • See Strimzi docs for information for installing Strimzi via Helm or alternatively install another way, such as via the operator catalog.
  • Ensure the strimzi operator is configured to watch all namespaces (or at least includes the ones you want to use).