Skip to content

How to migrate standalone k3s to existing External datastore backed K3s Cluster (multi-node) #4648

Closed

Description

@prnvkv

Is your feature request related to a problem? Please describe.
This is not a feature request but just a question. If we have a k3s single node cluster running on a local datastore (default), how can we migrate to existing k3s multi-node cluster running with external datastore (e.g. MariaDB) without affecting the running workloads.

Describe the solution you'd like
When a k3s standalone node joins the existing cluster, the existing workloads should not be affected.

Describe alternatives you've considered
No alternative.

Activity

  1. brandond commented on Dec 7, 2021

    @brandond
    Member

    We don't currently support migrating from one Kine sql backend to another, say from sqlite to mysql. We do support migrating from sqlite to etcd; all you need to do is start an existing standalone node with --cluster-init.

  2. locked and limited conversation to collaborators on Dec 7, 2021
  3. converted this issue into a discussion #4650 on Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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