Skip to content

Automatically detect the Helm version to use #20

@jfrancoa

Description

@jfrancoa

One of the problems with weaviate-local-k8s, mostly for old versions is that you need to know the Helm branch which corresponds to the Weaviate version, otherwise the deployment might fail (mostly when big changes happened between versions, like it's the case of pre-RAFT to RAFT).
To avoid that the user needs to remember this or know when to retreieve the version, local-k8s could use the following yaml, which is the one used to build the Weaviate Helm's site and will get updated with every new version being released. This way we don't need to keep a harcoded map of Weaviate version to Helm version.

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