Skip to content

StatefulRollout #1635

@james-callahan

Description

@james-callahan

Summary

I'd like to use a blue/green deployment strategy with a stateful application.

Use Cases

e.g. I have a stateful application and I want to keep the old version up until the new version has proven itself.

Suggested by @jessesuen in #132 (comment)

Aside from the Deployment resource, the only other native k8s resources that might need similar advanced deploy strategies are: StatefulSet and DaemonSet. But both of these resources have very different behaviors that would warrant an entirely new resource kind and controller. I don't think a generic approach could handle all three types because the manner in which these resources manage their pods are wildly different.
So while it's conceivable that we would introduce something like a StatefulRollout or DaemonRollout in the future, in all likelihood, these other kinds would need very specific/different implementations to mirror their k8s native counterparts.


Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions