<p>I am trying to modify a kubernetes keycloak deployment to respond on <code>/auth</code> in place of <code>/</code>. I see in the documentation that this should be possible by setting <code>--http-relative-path</code> to <code>/auth</code>. I have attempted this and it causes all the services to receive <code>Connection refused</code> from the keycloak service. Is this possibly an issue with keycloak or could there be another config required?</p>

Seth Faulkner
<p>The issue was that the networking solution was not routing to the service because the health checks had not been updated with the correct routes.</p>
<pre><code>        readinessProbe:
          httpGet:
            path: /health/ready
            port: 8080
          initialDelaySeconds: 30
          periodSeconds: 10
          timeoutSeconds: 1
          failureThreshold: 20
        startupProbe:
          httpGet:
            path: /health/ready
            port: 8080
          initialDelaySeconds: 30
          periodSeconds: 10
          timeoutSeconds: 1
          failureThreshold: 20
        livenessProbe:
          httpGet:
            path: /health/ready
            port: 8080
          initialDelaySeconds: 30
          periodSeconds: 10
          timeoutSeconds: 1
          failureThreshold: 20
</code></pre>
<p>Changing these to <code>/auth/health/ready</code> fixed the ready checks.</p>
