Remove HealthCheckPolicy's (#976)

* feat: remove HealthCheckPolicy's * chore: remove the corresponding values
nmshd · Dec 12, 2024 · 35687c4 · 35687c4
1 parent 8c0a607
commit 35687c4
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 70 deletions.
diff --git a/helm/templates/consumerapi/healthcheckpolicy.yaml b/helm/templates/consumerapi/healthcheckpolicy.yaml
diff --git a/helm/templates/sseserver/healthcheckpolicy.yaml b/helm/templates/sseserver/healthcheckpolicy.yaml
diff --git a/helm/values.yaml b/helm/values.yaml
@@ -210,19 +210,6 @@ consumerapi:
       # unhealthyThreshold - the number of consecutive failed checks required to mark a backend as unhealthy
       unhealthyThreshold: 2
 
-  # healthCheckPolicy - only applicable if .Values.global.provider is set to "Azure"; see https://learn.microsoft.com/en-us/azure/application-gateway/for-containers/custom-health-probe for a description of `HealthCheckPolicy`s
-  healthCheckPolicy:
-    # hostOverride - the host name that should be used for the health check; if empty, the toplevel `hostname` property is used
-    hostOverride: ""
-    # interval - the interval in seconds between health checks
-    interval: 15
-    # timeout - the timeout in seconds for each health check
-    timeout: 15
-    # healthyThreshold - the number of consecutive successful health checks required to mark a backend as healthy
-    healthyThreshold: 1
-    # unhealthyThreshold - the number of consecutive failed health checks required to mark a backend as unhealthy
-    unhealthyThreshold: 2
-
 #=========================== Database Migrator ===========================
 
 databasemigrator:
@@ -540,19 +527,6 @@ sseserver:
       # unhealthyThreshold - the number of consecutive failed checks required to mark a backend as unhealthy
       unhealthyThreshold: 2
 
-  # healthCheckPolicy - only applicable if .Values.global.provider is set to "Azure"; see https://learn.microsoft.com/en-us/azure/application-gateway/for-containers/custom-health-probe for a description of `HealthCheckPolicy`s
-  healthCheckPolicy:
-    # hostOverride - the host name that should be used for the health check; if empty, the toplevel `hostname` property is used
-    hostOverride: ""
-    # interval - the interval in seconds between health checks
-    interval: 15
-    # timeout - the timeout in seconds for each health check
-    timeout: 15
-    # healthyThreshold - the number of consecutive successful health checks required to mark a backend as healthy
-    healthyThreshold: 1
-    # unhealthyThreshold - the number of consecutive failed health checks required to mark a backend as unhealthy
-    unhealthyThreshold: 2
-
 global:
   # defaultHostname - the default hostname the services should be reachable under (this can be overriden in the individual service configurations)
   defaultHostname: ""