-
Notifications
You must be signed in to change notification settings - Fork 84
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
adding config option for ALB & NLB healthy threshold count #453
adding config option for ALB & NLB healthy threshold count #453
Conversation
@szuecs please review, thanks |
@universam1 nice addition - thanks for adding 👍 |
Good idea, I like that addition, too. 👍 |
2be8ffb
to
c0f1020
Compare
@szuecs Not sure what to do about the coverage decrease. Tested this change in our clusters, works as expected |
@universam1 it's no an issue if coverage drops <1%. It's more a hint we should make it better in the future. |
c0f1020
to
540b232
Compare
4808a5d
to
7cb98cf
Compare
controller.go
Outdated
kingpin.Flag("alb-healthy-threshold-count", "The number of consecutive successful health checks required before considering an unhealthy target healthy. The range is 2–10. The default is 5. (ALB only)"). | ||
Default(strconv.FormatUint(aws.DefaultAlbHealthyThresholdCount, 10)).UintVar(&albHealthyThresholdCount) | ||
kingpin.Flag("alb-unhealthy-threshold-count", "The number of consecutive failed health checks required before considering a target unhealthy. The range is 2–10. The default is 2. (ALB only)"). | ||
Default(strconv.FormatUint(aws.DefaultAlbUnhealthyThresholdCount, 10)).UintVar(&albUnhealthyThresholdCount) | ||
kingpin.Flag("nlb-healthy-threshold-count", "The number of consecutive successful or failed health checks required before considering an target healthy or unhealthy. The range is 2 to 10. The default is 3. (NLB only)"). | ||
Default(strconv.FormatUint(aws.DefaultNlbHealthyThresholdCount, 10)).UintVar(&nlbHealthyThresholdCount) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the default value is rendered in the help message:
--alb-healthy-threshold-count=5
The number of consecutive successful health
checks required before considering an unhealthy
target healthy. The range is 2–10. The default
is 5. (ALB only)
--alb-unhealthy-threshold-count=2
The number of consecutive failed health checks
required before considering a target unhealthy.
The range is 2–10. The default is 2. (ALB only)
--nlb-healthy-threshold-count=3
The number of consecutive successful or failed
health checks required before considering an
target healthy or unhealthy. The range is 2 to
10. The default is 3. (NLB only)
so lets remove The default is ...
.
For --nlb-healthy-threshold-count
it should be considering _a_ target
and I think we should use the same format for the range as for ALB: The range is 2–10
for consistency (I get that it is different in the AWS docs).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, thanks for the review
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. _an_ target
is still there though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, sorry
7cb98cf
to
a00ec35
Compare
Healthy threshold: The number of consecutive health checks successes required before considering an unhealthy target healthy This configuration is required since the default of "5" time the interval which is minimum of sum of 30s that is too long delay in our configurations Signed-off-by: Samuel Lang <[email protected]>
a00ec35
to
bc74868
Compare
👍 |
1 similar comment
👍 |
Healthy threshold: The number of consecutive health checks successes required before considering an unhealthy target healthy
This configuration is required since the default of "5" time the interval, which is minimum of 6s, sums up to 30s that is too long delay in our configurations.
Signed-off-by: Samuel Lang [email protected]