Update Kong ingress controller to version 1.4. It fixes the occasional 404 error.

[it/dep.git] / ric-aux / helm / infrastructure / subcharts / kong / ci / loadbalancer-values.yaml

diff --git a/ric-aux/helm/infrastructure/subcharts/kong/ci/loadbalancer-values.yaml b/ric-aux/helm/infrastructure/subcharts/kong/ci/loadbalancer-values.yaml
deleted file mode 100755 (executable)
index 7a24b87..0000000
--- a/ric-aux/helm/infrastructure/subcharts/kong/ci/loadbalancer-values.yaml
+++ /dev/null
@@ -1,50 +0,0 @@
-# CI test for LoadBalancer admin/proxy types
-
-admin:
-  useTLS: true
-  type: LoadBalancer
-  loadBalancerSourceRanges:
-    - 192.168.1.1/32
-    - 10.10.10.10/32
-
-proxy:
-  useTLS: true
-  type: LoadBalancer
-  loadBalancerSourceRanges:
-    - 192.168.1.1/32
-    - 10.10.10.10/32
-
-updateStrategy:
-  type: "RollingUpdate"
-  rollingUpdate:
-    maxSurge: 1
-    maxUnavailable: 0
-
-readinessProbe:
-  httpGet:
-    path: "/status"
-    port: admin
-    scheme: HTTPS
-  initialDelaySeconds: 30
-  timeoutSeconds: 1
-  periodSeconds: 10
-  successThreshold: 1
-  failureThreshold: 5
-
-livenessProbe:
-  httpGet:
-    path: "/status"
-    port: admin
-    scheme: HTTPS
-  initialDelaySeconds: 30
-  timeoutSeconds: 5
-  periodSeconds: 30
-  successThreshold: 1
-  failureThreshold: 5
-
-postgresql:
-  enabled: true
-  postgresUser: kong
-  postgresDatabase: kong
-  service:
-    port: 5432