Track upstream v3-release tag, use loopback IP for probes

This addresses two issues that I encountered when using this chart to deploy kiam v3 on EKS: 1. kiam v3.0 was released 2018-12-06 per https://github.com/uswitch/kiam/blob/master/CHANGELOG.md, it probably doesn't make sense to track a RC tag 2. Liveness/readiness probes need to use `127.0.0.1` rather than `localhost` (see uswitch/kiam#163) because of a TLS change Signed-off-by: Steve Huff <[email protected]>
hakamadare · Jan 29, 2019 · de10d18 · de10d18
1 parent eb21fab
commit de10d18
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/stable/kiam/values.yaml b/stable/kiam/values.yaml
@@ -11,7 +11,7 @@ agent:
 
   image:
     repository: quay.io/uswitch/kiam
-    tag: v3.0-rc1
+    tag: v3-release
     pullPolicy: IfNotPresent
 
   ## Logging settings
@@ -102,7 +102,7 @@ server:
 
   image:
     repository: quay.io/uswitch/kiam
-    tag: v3.0-rc1
+    tag: v3-release
     pullPolicy: IfNotPresent
 
   ## Logging settings
@@ -164,7 +164,7 @@ server:
 
   ## Server probe configuration
   probes:
-    serverAddress: localhost
+    serverAddress: 127.0.0.1
 
   ## Base64-encoded PEM values for server's CA certificate(s), certificate and private key
   ##