Skip to content

The K3s installation docs should mention that the auto deploy directory is applied on every boot #24

@DavidZidar

Description

@DavidZidar

The K3s docs instruct you to put the yaml files in an auto deploy directory before installation of K3s which makes it seem this directory is only used during setup. The link to the K3s documentation is also wrong, so it's harder to read up on what the directory actually does.

In reality the contents of the directory are applied during every boot of the server which caused me some headaches before I realized what was going on as kube-vip kept gettiing reverted to my initial configuration after I rebooted my initial K3s server.

Please correct the link to this one and maybe update the instructions to make it more clear what that directory does and why it's important to put the files there before installation, if it even is important?

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