Development and deployment happens in four steps.

1. Local development

All suppliers start development of their components in their own local environment.

This could be a complete clone of the official test environments running on the ehealth-platform. But this is not a strict requirement.

2. Publish build to the ehealth-platform

When the supplier believes that the application / service / microservice is ready for testing it is published to the ehealth-platform.

This means that the docker image is pushed to the central docker image registry used and hosted by the ehealth-platform.

3. Deploy to test environment

To actually deploy the docker image as a container on the first test environment, the image needs to be added to the helmsman specification file for the given environment.

All applications running on an environment is specified as code in the desired state specification for the given environment.

For each application this includes:

• The docker image to run
  • Docker repository
  • Image tag
• The helm chart
  • Helm chart repository
  • Helm chart version
• Configuration
  • Ports
  • Replicas
  • Memory usage
  • Environment variables
  • Database and queue secrets
  • DNS bindings
  • ect..

When the desired state specification is updated the applications and configuration is automatically rolled on to the environment.

4. Test and Promotion

IntTest and ExtTest

Tests should be carried out on the inttest environment.

When the application has passed QA, it can be promoted to the next environment. This happens by a promotion of a specific desired state specification in Jenkins, by users with the right privileges.

PreProd and Prod

Going onwards to preproduction happens by making a pull-request to the "prod" branch from the "master" branch.

When the pull-request is approved all updates in the desired state specification  for preprod is rolled on the preprod environment.

Deployment to production happens by a promotion of a specific desired state specification in Jenkins, by users with the right privileges.

4.1. Hot-fixing

If serious bugs or security errors is found in production code, or containers a hotfix can be handled in the following way.

4.2. Rollback

Rollback is handled somewhat semi-automatic, if the problem is visible through the pod probe services liveness and readiness. In other rollback situation manual intervention is necessary.

In the first situation, where either liveness and readiness is responding negative, the new pod instance will never be part of the serving cluster. The cluster will automatically keep sending traffic to the old instances of the service and skip the new pod. What should happen next has to be decided by the one who started the deployment. It could be a configuration fix or a rollback to the old software version.

In the second situation, where both liveness and readiness respond positive, the new pod will receive trafik. The one who started the deployment will look at cluster readout and decide a rollback. That person has to commit a new cluster configuration. This could be a reverse commit to the desired state file.
Note: if we are using canary deployment, the negative impact of a software problem can be held at a minimum.