This message was deleted.

If you're open to a k8s native way of doing this, I am working on something for Harvester that will allow you to specify cloud-init configurations for Harvester nodes as a k8s object, which could be written in yaml and checked into a version-controlled repo. As an example:

apiVersion: <http://node.harvesterhci.io/v1beta1|node.harvesterhci.io/v1beta1>
kind: CloudInit
metadata:
  name: ssh-access
spec:
  matchSelector: {}
  filename: 99_ssh.yaml
  contents: |
    stages:
      network:
        - authorized_keys:
            rancher:
              - ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPCUNsQEnKj0nl1GS07Qr5RDCCbCim4wu06hCzQZDmTk ckuehl@suselaptop

Cool, is the CRDS already available in 1.2? Can I reconfigure nodes with this after they have been added to the harvester cluster?

Hasn't been merged into any release yet, and yes, the CRD is matched to nodes with a

matchSelector

(at least so far, this could be subject to change based on the review process)

Ah so it like manually editing the 90_custom.yaml on a node and rebooting?

Yeah, but for example in that snippet above the matchSelector is empty which matches every node, so that authorized_keys stanza would automatically propagate to all nodes in the cluster

That is very nice. That could streamline the configuration of whole new harvester clusters... if that would also work with gitops tool that would be the dream

Yeah, this is one step on the way of positioning Harvester to be more GitOps friendly