Skip to content

Possible mess when upgradeBeforeDeployment: true on an install with multiple chartreuses #5

Description

@desaintmartin

during the upgrade we do control the order (helm hooks order)

2 chartreuses = 2 jobs on install (first time), the first one (may be the least important one, may finish first and start-pods while the import chartreuse is still running) => error logs

maybe upgradeBeforeDeployment: true on install should run as upgradeBeforeDeployment: false

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions