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

adding config option for ALB & NLB healthy threshold count #453

Merged
merged 1 commit into from
Nov 19, 2021

Conversation

universam1
Copy link
Contributor

@universam1 universam1 commented Nov 18, 2021

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]

@universam1
Copy link
Contributor Author

@szuecs please review, thanks

@dhohengassner
Copy link

@universam1 nice addition - thanks for adding 👍

@w-reichert
Copy link

Good idea, I like that addition, too. 👍

@universam1 universam1 force-pushed the healthyThreshold branch 3 times, most recently from 2be8ffb to c0f1020 Compare November 18, 2021 15:15
@universam1
Copy link
Contributor Author

@szuecs Not sure what to do about the coverage decrease.

Tested this change in our clusters, works as expected

@szuecs
Copy link
Member

szuecs commented Nov 18, 2021

@universam1 it's no an issue if coverage drops <1%. It's more a hint we should make it better in the future.
PR as always great, thanks!

controller.go Outdated Show resolved Hide resolved
@universam1 universam1 changed the title adding config option for Healthy threshold adding config option for ALB healthy threshold count Nov 18, 2021
@universam1 universam1 force-pushed the healthyThreshold branch 2 times, most recently from 4808a5d to 7cb98cf Compare November 19, 2021 08:55
controller.go Outdated
Comment on lines 227 to 232
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)
Copy link
Member

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).

Copy link
Contributor Author

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

Copy link
Member

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks, sorry

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]>
@szuecs
Copy link
Member

szuecs commented Nov 19, 2021

👍

1 similar comment
@AlexanderYastrebov
Copy link
Member

👍

@universam1 universam1 changed the title adding config option for ALB healthy threshold count adding config option for ALB & NLB healthy threshold count Nov 19, 2021
@AlexanderYastrebov AlexanderYastrebov merged commit 0928e13 into zalando-incubator:master Nov 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants