Skip to content

Don't delete storage bucket or db pwd secret by default when disabling mlflow plugin #8

@Adam-D-Lewis

Description

@Adam-D-Lewis

Context

I think we should do something like below. I think we should also keep the k8s secret for the postgres db by default. So if the mlflow helm chart is deleted, users can still restore mlflow to a working condition (with prior data and storage) assuming the db secret has not also been lost.

mlflow:
  enabled: false
  force_destroy_storage: true  # defaults to False
  force_destroy_db_creds: true # defaults to False

Value and/or benefit

Reduce risk of unintentional loss of data

Anything else?

No response

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