make liveness and readiness probes optional and further configurable

This commit is contained in:
jessebot
2025-01-18 20:20:33 +01:00
parent c64cf91e69
commit 295aa694d7
4 changed files with 29 additions and 18 deletions
+2
View File
@@ -6,9 +6,11 @@ A helm chart to setup [Pixelfed](https://pixelfed.org/). Uses matt's docker [ima
## Features ## Features
- includes bitnami subcharts for [valkey](https://github.com/bitnami/charts/blob/main/bitnami/valkey/README.md#parameters) (redis) and [postgresql](https://github.com/bitnami/charts/blob/main/bitnami/postgresql/README.md#parameters) (database) - includes bitnami subcharts for [valkey](https://github.com/bitnami/charts/blob/main/bitnami/valkey/README.md#parameters) (redis) and [postgresql](https://github.com/bitnami/charts/blob/main/bitnami/postgresql/README.md#parameters) (database)
- but you can also bring your own valkey, redis, or postgresql database
- helm parameter docs autogenerated via helm-docs - helm parameter docs autogenerated via helm-docs
- use existing Secrets for valkey, postgresql, and smtp - use existing Secrets for valkey, postgresql, and smtp
- RenovateBot keeps the subcharts and docker image up to date - RenovateBot keeps the subcharts and docker image up to date
- configurable liveness and readiness probes
## TLDR ## TLDR
+1 -1
View File
@@ -15,7 +15,7 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes # This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version. # to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/) # Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.4.2 version: 0.5.0
# This is the version number of the application being deployed. # This is the version number of the application being deployed.
# renovate:image=ghcr.io/mattlqx/docker-pixelfed # renovate:image=ghcr.io/mattlqx/docker-pixelfed
+6 -2
View File
@@ -335,10 +335,14 @@ spec:
- name: DB_APPLY_NEW_MIGRATIONS_AUTOMATICALLY - name: DB_APPLY_NEW_MIGRATIONS_AUTOMATICALLY
value: "{{ .Values.pixelfed.db_apply_new_migrations_automatically }}" value: "{{ .Values.pixelfed.db_apply_new_migrations_automatically }}"
{{- with .Values.livenessProbe }}
livenessProbe: livenessProbe:
{{- toYaml .Values.livenessProbe | nindent 12 }} {{- toYaml . | nindent 12 }}
{{- end }}
{{- with .Values.readinessProbe }}
readinessProbe: readinessProbe:
{{- toYaml .Values.readinessProbe | nindent 12 }} {{- toYaml . | nindent 12 }}
{{- end }}
resources: resources:
{{- toYaml .Values.resources | nindent 12 }} {{- toYaml .Values.resources | nindent 12 }}
{{- with .Values.volumeMounts }} {{- with .Values.volumeMounts }}
+20 -15
View File
@@ -59,10 +59,14 @@ service:
# -- Port to attach to on the pods. Also sets what port nginx listens on inside the container. # -- Port to attach to on the pods. Also sets what port nginx listens on inside the container.
targetPort: 80 targetPort: 80
# This block is for setting up the ingress for more information can be found here: https://kubernetes.io/docs/concepts/services-networking/ingress/ # This block is for setting up the ingress for more information can be found here:
# https://kubernetes.io/docs/concepts/services-networking/ingress/
ingress: ingress:
# -- enable deploy an Ingress resource - network traffic from outside the cluster
enabled: false enabled: false
# -- ingress class name, e.g. nginx
className: "" className: ""
# annotations to apply to the Ingress resource
annotations: {} annotations: {}
hosts: hosts:
- host: chart-example.local - host: chart-example.local
@@ -74,11 +78,8 @@ ingress:
# hosts: # hosts:
# - chart-example.local # - chart-example.local
# -- set resource limits and requests for cpu, memory, and ephemeral storage
resources: {} resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits: # limits:
# cpu: 100m # cpu: 100m
# memory: 128Mi # memory: 128Mi
@@ -86,18 +87,22 @@ resources: {}
# cpu: 100m # cpu: 100m
# memory: 128Mi # memory: 128Mi
# This is to setup the liveness and readiness probes more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ # -- This is to setup the liveness probe
livenessProbe: # more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
httpGet: livenessProbe: {}
path: /api/service/health-check # httpGet:
port: http # path: /api/service/health-check
# port: http
readinessProbe: # -- This is to setup the readiness probe
httpGet: # more information can be found here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
path: /api/service/health-check readinessProbe: {}
port: http # httpGet:
# path: /api/service/health-check
# port: http
# This section is for setting up autoscaling more information can be found here: https://kubernetes.io/docs/concepts/workloads/autoscaling/ # This section is for setting up autoscaling
# more information can be found here: https://kubernetes.io/docs/concepts/workloads/autoscaling/
autoscaling: autoscaling:
enabled: false enabled: false
minReplicas: 1 minReplicas: 1