Skip to content

Release 3.5 (February 2022)

Known Issues
Use chromium-based browser for UIs

It is recommended to use a chromium-based browser such as Google Chrome, Microsoft Edge or Apple Safari for the Egeria Ecosystem UI. Some parts of the UI experience such as Dino currently experience problems with Firefox. See odpi/egeria-react-ui#96 .

This applies to version 3.4.0 as used by our helm charts.

Config documents cannot be displayed in Dino

Config documents cannot be displayed in the Egeria Ecosystem UI (Dino). See egeria-ract-ui#264 .

This applies to version 3.4.0 as used by our helm charts.

Functional changes

None

Type changes: added, modified, deprecated

None.

Container Deployment
Container Images support arm64

The Egeria container image is now multi-architecture, supporting both arm64 & x86_64 architectures. This now allows execution on Apple Silicon based macs, and Raspberry pi running 64 bit OS in addition to Intel based environments.

See https://quay.io/odpi/egeria and https://docker.io/odpi/egeria

Helm Charts updated & support arm64
  • Helm Charts have been updated to release 3.5.0 to include this release of Egeria 3.5.
  • Ecosystem UI remains at 3.4.0
  • General UI remains at 3.2.0
  • Lab, Base charts now additionally support arm64 including for use on Apple Silcon based macs and Raspberry pi running a 64 bit OS and use Strimzi 0.27.1 for Kafka.
  • Lab, Base charts now use Strimzi 0.27.1 for Kafka

In this release of the charts, default security context should be sufficient for deployment in OpenShift, fixing an earlier issue.

docker-compose support removed

Support for a docker-compose based deployment of Egeria was deprecated in 3.1, and has now been removed. For a orchestrated setup of our labs or a simple environment, use our Helm Charts on Kubernetes.

You can continue to use container images directly & use these in your own docker-compose configurations.

Deprecations

None.

Bug fixes and other updates
Implementation status

Egeria implementation status