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

NnfDataMovementManager: Add UpdateStrategy to support parallel rolling updates #261

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

bdevcich
Copy link
Contributor

The NNF DMM manages the nnf-dm-worker DaemonSet, which is reponsible for
the nnf-dm-worker pods. Adding UpdateStrategy to the
NnfDataMovementManagerSpec ensures admins can configure the update
strategy for those pods.

This allows for a non-sequential update when rolling out new worker
pods.

Signed-off-by: Blake Devcich [email protected]

…g updates

The NNF DMM manages the nnf-dm-worker DaemonSet, which is reponsible for
the nnf-dm-worker pods. Adding UpdateStrategy to the
NnfDataMovementManagerSpec ensures admins can configure the update
strategy for those pods.

This allows for a non-sequential update when rolling out new worker
pods.

Signed-off-by: Blake Devcich <[email protected]>
@@ -50,6 +51,10 @@ type NnfDataMovementManagerSpec struct {
// manages the per node data movement operations.
Template corev1.PodTemplateSpec `json:"template"`

// UpdateStrategy defines the UpdateStrategy that is used for the basis of the worker Daemon Set
// that manages the per node data movement operations.
UpdateStrategy appsv1.DaemonSetUpdateStrategy `json:"updateStrategy"`
Copy link
Contributor

Choose a reason for hiding this comment

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

Does it need to be required? Can it be omitempty?

Copy link
Contributor

Choose a reason for hiding this comment

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

Never mind, I see that sos has it covered always.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I originally had it as optional but then changed my mind to just make it a requirement. We basically never want it to use the default of 1 anyway, so I think expecting this field is the way to go.

@bdevcich bdevcich merged commit b610046 into master Feb 13, 2024
3 checks passed
@bdevcich bdevcich deleted the dmm-update-strategy branch February 13, 2024 20:21
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.

Adjust update strategy for NNF DaemonSets
3 participants