Skip to content

bug: Helm Upgrade potentially deleting namespaces (and therefore everything on that namespace) #19266

@Sharpz7

Description

@Sharpz7

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Hey Folks, I will admit I am not 100% sure coder caused this, but I had my entire coder namespace deleted, which means that all my workspaces + volumes were also deleted.

helm/helm#12287 - I think this is what occurred. I only ran helm upgrade commands, yet going through the logs a delete occurred.

I'm making this issue as a warning to others more than anything - I wonder if me being on a relatively old coder version before upgrading is part of it? I apologies for not having more information - I can go digging through the logs if that would help.

A potentially useful feature that could help from Coder here would be if the documentation instructs you to create volumes with a reclaim policy that is not "Delete", or some kind of warning. That way, even if weird things like this occur, the volumes survive.

Relevant Log Output

Expected Behavior

No response

Steps to Reproduce

helm/helm#12287

Environment

  • Host OS: Linux
  • Coder version: Upgrading from 2.2x.x to 2.25.0

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue that require triage

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions