Skip to content

bug: cached vcluster recreation doesn't allow new vclusters of same name with updated configurations #13

@waveywaves

Description

@waveywaves

when deleting and creating a new vcluster with the same name and updated configuration, the newly created vcluster takes on the old configuration instead of the newly provided configuration. There might be some issue here with helm charts getting cached and not getting updated by the helm controller.

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