2.6.0

Probes configuration (livenessProbe and startupProbe)

This change resolves issue #7, where some applications failed to start due to overly restrictive probe configurations. The problem was addressed by moving the startupProbe and livenessProbe sections directly into the HelmRelease files of specific applications. The Helm chart now imports this configuration to create the deployment objects.

Example

startupProbe:
  httpGet:
    path: /
    port: 666
  failureThreshold: 30
  periodSeconds: 10
livenessProbe:
  tcpSocket:
    port: 666
  initialDelaySeconds: 10
  periodSeconds: 2

More info on: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

Pre hook: initWebsiteDir

In some situations hook returned non 0 status code, so applications deployment was distrupted. This was fixed by checking if application directory exists.