Versions Compared

Old Version 13

changes.mady.by.user John Schneider

Saved on

compared with

New Version 14

changes.mady.by.user John Schneider

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor


Excerpt

Description of the eHealth development and deployment cycle, including description of the use of eHealth environments and flow. 

...

  1. Telemedicine Solutions provider shall use the official eHealth docker images and helm chart for application definition and development
  2. After local development, the Telemedicine Solutions Providers shall upload the docker images to Docker and Helm chart repository (Harbor)
  3. Telemedicine Solutions Providers uses GitLab to define the deployment file or "desired state file" based on Helmsman
  4. A configured Jenkins deployment pipeline monitors the Helmans file in GitLab and push updates to Kubernetes 
    1. The Jenkins deployment pipeline is configured by the eHealth Infrastructure provider.
  5. 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.

...