-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
feat: add local variable pod.retryAttempt. Fixes #2808, Fixes #2898. #2911
Conversation
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.
Great start! Some comments to fix
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.
Looking better!
This LGTM as is, but I want to confirm with the rest of the team that |
Great. Thanks Simon. Naming is half the battle. |
Hey @seddonm1, sorry for the delay. We decided to name this flag Can you update the naming and resolve the conflicts please? |
this code is now up to date and has the variable named |
@seddonm1 Seems like there was a Git issue when you rebased/merged with master. You can see that this PR now changes 150+ files, which is not desired. Can you solve this and make sure that it only contains your desired changes? |
- add pod.retryAttempt which only executes on nodes with retryStrategy defined and starts at 0.
376bbaf
to
e0de88d
Compare
This comment was marked as resolved.
This comment was marked as resolved.
@simster7 Sorry. not sure what happened with my client. fixed. |
pod.retryAttempt
that reports the retry attempt number starting at 0 for first attempt and increasing by 1 each attempt.retryStrategy
defined.examples/retry-with-steps.yaml
to demonstrate usage.docs/variables.md
to describe variable.Fixes #2808 and Fixes #2898 for enhancement request.
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.