Catered for liveness and readiness probe when ingress supplied #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when deploying into a Kubernetes cluster with own ingress configured which uses specific path prefix which is not rewritten the liveness and readiness probes fail. This is because the deployment does not take into consideration the path prefix in the liveness and readiness url's even when it should. It is always your deployment.yaml
This pull request updates this section to include the path when the ingress is configured (ingress.configured=true) and the path is not being rewritten in the ingress (ingress.rewritePath=false) as per my deployment.yaml