| Excerpt |
|---|
Description of the eHealth development and deployment cycle, including description of the use of eHealth environments and flow. |
...
- Telemedicine Solutions provider shall use the official eHealth docker images and helm chart for application definition and development
- After local development, the Telemedicine Solutions Providers shall upload the docker images to Docker and Helm chart repository (Harbor)
- Telemedicine Solutions Providers uses GitLab to define the deployment file or "desired state file" based on Helmsman
- A configured Jenkins deployment pipeline monitors the Helmans file in GitLab and push updates to Kubernetes
- The Jenkins deployment pipeline is configured by the eHealth Infrastructure provider.
- Kubernetes control loop watch the state of your cluster, then make or request changes where needed
The following figure illustrates the deployment pipeline.
...
Phase #4 Test and Promotion
Notice, every release must follow a strict release plan where eHealth environments are visited in the required order, that is deployed and tested on EXTTEST, before being promoted to PREPRODUCTION, and finally deployed to PRODUCTION.
...