From a6ccab5270c8f01e68b748a2d252422c14d679c1 Mon Sep 17 00:00:00 2001
From: Itxaka <igarcia@suse.com>
Date: Tue, 17 Sep 2019 12:06:21 +0200
Subject: [PATCH] Use proper keystone path for probes

Using the direct / path for the keystone probes can lead to the
probes receiving an http 300. We want to have an http 200 so there
is no warning from the probes. Use the full v3 path so the probes
are stable

Change-Id: If8b45801bb053778bd2e1691ff8556aa73cb434d
---
 keystone/templates/deployment-api.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/keystone/templates/deployment-api.yaml b/keystone/templates/deployment-api.yaml
index 29f906a057..f1ee117913 100644
--- a/keystone/templates/deployment-api.yaml
+++ b/keystone/templates/deployment-api.yaml
@@ -76,14 +76,14 @@ spec:
           readinessProbe:
             httpGet:
               scheme: HTTP
-              path: /
+              path: /v3/
               port: {{ $portInt }}
             initialDelaySeconds: 15
             periodSeconds: 10
           livenessProbe:
             httpGet:
               scheme: HTTP
-              path: /
+              path: /v3/
               port: {{ $portInt }}
             initialDelaySeconds: 50
             periodSeconds: 20