Skip to content

Allow user to specify curated packageBundle version during cluster install #8422

@anashakt

Description

@anashakt

What would you like to be added:
Currently versioning of curated package bundle is not allowed because of by default latest curated package bundle gets activated on the cluster. I would like to have a key in the cluster spec using which one can specify a packagebundle version.

Why is this needed:
It allows controlled release of packages in production. If QA team has tested EKSA cluster lifecycle against a specific packageBundle version then production should get the same version as opposed to latest available at the time of cluster creation in Production.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions