Excerpt |
---|
This page describes the third-party tools (e.g. Jeager, Docker Repository, Splunk) used for e.g. log analysis and tracing. |
...
Code Block | ||
---|---|---|
| ||
{Vendor Short Name}-{Application Short Name}/* |
Deployment specified as code
The deployment and configuration are defined in a dedicated git repository for each solution.
...
This repository contains a valuesvalue.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.
...
All images in the docker repository is are 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.
...
Code Block |
---|
{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.
...
See Helm Charts for more info about the chart.
Kubernetes namespace
All applications on the platform is are hosted on Kubernetes. To enforce separation between applications and to harden the security on the platform each application will have its own Kubernetes namespace.
...
Code Block |
---|
{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.
...
See also Using Splunk for a short introduction on how to use Splunk.
Jaeger tracing
In the test environments, 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 have implemented the header propagation as described in Call Tracing
...