Fix readiness probe. #885
Merged
Fix readiness probe. #885
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes a problem in the readiness probe. The previous code set the probe to "/weblogic" which will result in the server returning a 302 redirect. In cases where the cluster is behind a load balancer and WebLogic has been configured with a frontend host/port so that external clients can use applications deployed in the cluster, the 302 will redirect to the load balancer address, and kubelet will not be able to hit this address successfully. The readiness probe will show as failed (503), because the endpoints have not been added to the cluster service (and therefore the ingress) yet, because the pod is not yet considered ready. So you get a chicken and egg problem.
This change fixes the readiness probe to use "/weblogic/" (with the trailing slash). This will not result in a 302, it will return the 200, and then kubelet will consider the pod as ready and add it into the cluster service, ingress, etc., and everything will work as expected.
Credit to BRIAN DUECK for initial identification of this problem.