-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 containerset retry strategy. Fixes #7290 #7377
Conversation
67efb6f
to
70b8fe3
Compare
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.
initial thoughts:
- I don't think you need limit, you already have steps in backoff.
- Do you think we want one strategy for all containers in the set? Or different ones for different containers?
Yes, it is not needed, will stick to the steps.
To keep it simpler I think we should have a general one to start of with also based upon the feedback here it seems to solve the most urgent use case. |
Sure. So we can add that in a v2. |
I mixed up it up with
|
@sarabala1979 could you take a look? |
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 there are ways to simplify the code.
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.
more changes requested I'm afraid
I have realised that the parsing from
but the generation then fails:
I guess we could recreate a new type to solve the issue but that feels a bit hacky. WDYT @alexec ? |
You can't have two types named |
b149959
to
786b376
Compare
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
b7fdb65
to
0cadccb
Compare
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
VolumeMounts []corev1.VolumeMount `json:"volumeMounts,omitempty" protobuf:"bytes,3,rep,name=volumeMounts"` | ||
Containers []ContainerNode `json:"containers" protobuf:"bytes,4,rep,name=containers"` | ||
VolumeMounts []corev1.VolumeMount `json:"volumeMounts,omitempty" protobuf:"bytes,3,rep,name=volumeMounts"` | ||
RetryStrategy *ContainerSetRetryStrategy `json:"retryStrategy,omitempty" protobuf:"bytes,5,opt,name=retryStrategy"` |
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 we could do with a comment for users here as this gets surfaced in docs. How does the retry work for example?
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.
Will update with docs.
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Signed-off-by: NikeNano <niklas.sven.hansson@gmail.com>
Thanks for all the feedback @alexec appreciate it, have a hard time to get time off from work so things take slightly longer than I wish for :) |
Fixes: #7290
Don't bother creating a PR until you've done this:
make pre-commit -B
to fix codegen, lint, and commit message problems.Create your PR as a draft.
does not need to pass.
Tips: