Skip to content

feat: increase lieveness probe failureThreshold for apl-operator#3012

Open
j-zimnowoda wants to merge 3 commits intomainfrom
APL-1586-1
Open

feat: increase lieveness probe failureThreshold for apl-operator#3012
j-zimnowoda wants to merge 3 commits intomainfrom
APL-1586-1

Conversation

@j-zimnowoda
Copy link
Contributor

@j-zimnowoda j-zimnowoda commented Mar 5, 2026

📌 Summary

The failure threshold is a bit too low to decide if a pod should be killed.

🔍 Reviewer Notes

🧹 Checklist

  • Code is readable, maintainable, and robust.
  • Unit tests added/updated

@svcAPLBot
Copy link
Contributor

Comparison of Helm chart templating output:

@@ spec.template.spec.containers.apl-operator.livenessProbe.failureThreshold @@
! ± value change
- 1
+ 3


Copy link
Contributor

@Ani1357 Ani1357 left a comment

Choose a reason for hiding this comment

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

With this change, in case the operator gets stuck, the earlier restart would happen after 18min(15min + 3 X 60s X failureThreshold).
How about lowering the test to check so it tests after 10 min (600s) and keep the failureThreshold at 3, so it takes 13min in the best case. I think after 13min is still reasonable to consider the operator stuck.

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.

5 participants