Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.2.x-openjdk11] - CLOUD-2742 - Allow kubernetes to control probe retries; avoid probes taking longer than kubernetes timeout settings #115

Merged
merged 1 commit into from Jul 16, 2019

Conversation

luck3y
Copy link
Collaborator

@luck3y luck3y commented May 29, 2019

https://issues.jboss.org/browse/CLOUD-2742
Upstream PR: #116
Signed-off-by: Ken Wills kwills@redhat.com

@luck3y luck3y changed the title [7.2.x-openjdk11] - CLOUD-2742 - Allow kubernetes to control probe retries; avoid probes taking longer than kubernetes timeout settings [7.2.x-openjdk11] - CLOUD-3264 - Allow kubernetes to control probe retries; avoid probes taking longer than kubernetes timeout settings May 29, 2019
@luck3y luck3y changed the title [7.2.x-openjdk11] - CLOUD-3264 - Allow kubernetes to control probe retries; avoid probes taking longer than kubernetes timeout settings [7.2.x-openjdk11] - CLOUD-2742 - Allow kubernetes to control probe retries; avoid probes taking longer than kubernetes timeout settings May 29, 2019
rgdoliveira
rgdoliveira previously approved these changes May 29, 2019
@luck3y
Copy link
Collaborator Author

luck3y commented May 29, 2019

@bstansberry Any thoughts on this one?

Copy link
Collaborator

@bstansberry bstansberry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be like #114.

…taking longer than kubernetes timeout settings
@luck3y
Copy link
Collaborator Author

luck3y commented Jul 16, 2019

This is g2g now.

@luck3y luck3y merged commit 63ad955 into jboss-container-images:7.2.x-openjdk11 Jul 16, 2019
if [ $# -gt 1 ] ; then
SLEEP=$2
fi
# setting the first parameter to true/false, gets you the new default behaviour of
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Things are getting complicated. Usage section will be very helpful.

I must say misusing COUNT parameter for boolean true of false (doesnt matter which) is very confusing

Why are we keeping old behaviour. For eap64 stream? Doesnt eap64 stream have own branch?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mchoma For the existing images (7.2.x on OCP 3.x) we felt that adding additional parameters for OCP 4.1 would be problematic for the user as they'd have to change depending on which version of OCP they were using. So we provided the true / false mechanism as a way to switch between these behaviours.

This is only for the 7.2.x images, the internal retry is dropped for CD 17 and later images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

4 participants