Skip to content

Fix no inplace update way #6530

@liubog2008

Description

@liubog2008

We expected no inplace update can act like deployment. However, a new instance will be created immediately after the outdated one is marked as deleting.

The expected behavior is waiting until the outdated one is fully deleted.

Now there are at most two extra instances created which is more than maxSurge(1).

Metadata

Metadata

Assignees

No one assigned

    Labels

    v2for operator v2

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions