When hosting a Telemedicine Solution including a potential BFF on the eHealth platform, you will be given access to the following tools.
These tools will for most cases follow a naming scheme based on:
{Vendor Short Name}-{Application Short Name}/*
Deployment specified as code
The deployment and configuration is defined in a dedicated git repository for each solution.
The git repository is hosted on the eHealth infrastructure, and is named:
{Vendor Short Name}-{Application Short Name}/helmsman
This repository contains a values.yaml file for each environment that the solution can be deployed to, containing the specific values for this environment, if any.
A deployment pipeline is connected to this repository, following the outline described in Development and deployment cycle .
Docker Image hosting
Each solution is given a docker repository hosted on the eHealth Platform. It is only possible and allowed to deploy images to the different environments from this docker repository.
This docker repository is not meant for all development builds, but only for images that the vendor has tested and validated internally, and that the vendor believes are ready for testing and QA.
All images in the docker repository is scanned for known security problems. And when any new security problems are found it is the responsibility of the Vendor to build a new image, push it, test it, and make sure it is deployed.
See Docker Base Images for requirements for the image and security risk mitigation.
Docker repository is named:
{Vendor Short Name}-{Application Short Name}/bff
Helm Chart repository
The vendor is given access to the helm chart repository hosted by the eHealth Platform.
This repository contains the only helm chart that the vendor is allowed to use to deploy their applications on the platform. The chart should be complete enough to run the application, with different configuration for values, health endpoints, resource usage etc.
See Helm Charts for more info about the chart.
Kubernetes namespace
All applications on the platform is hosted on Kubernetes. To enforce separation between applications and to harden the security on the platform each application will have it’s own Kubernetes namespace.
From this namespace only communication to other specified namespaces is allowed.
This is at the moment only the
ehealth-publicnamespace.
Likewise only communication to whitelisted services outside the eHealth Platform is allowed.
Please contact FUT-S Contact Information if new white-listings are needed
Namespace is named:
{Vendor Short Name}-{Application Short Name}
Splunk Central Logging
The vendor is given access to a central log collection where the vendor can query and access logs, audits and metrics collected from the application.
The vendor do not have access to logs for the rest of the platform services, or from other applications.
When moving up through the different environments, the access will be less and less to protect against unwanted data disclosure.
Indexes available is:
{environment}_k8s_{Vendor Short Name}-{Application Short Name}_application
{environment}_k8s_{Vendor Short Name}-{Application Short Name}_audit
{environment}_k8s_{Vendor Short Name}-{Application Short Name}_metrics
See also Logging model for logging requirements.
See also Using Splunk for short introduction on how to use Splunk.
Jaeger tracing
In the test environment the vendor is given access to a common tracing system where a call and the response times of each involved service can be found. This is possible when all involved services has implemented the header propagation as described in Call Tracing
In production the access to tracedata will be limited.
A GUI presenting the collected data for i.e. EXTTEST car be accessed here https://jaeger.admin.exttest.ehealth.sundhed.dk/search