#FREEPLANE CHANGE NODE ORDER UPGRADE#

You have the ability to add an arbitrary map of labels for each node. The default is /var/run/docker.sock Labels If the Docker socket is different than the default, you can set the docker_socket. ssh_cert, to be used to connect to the node. Instead of setting the path to the signed SSH certificate, you can alternatively specify the actual certificate, i.e. ssh_cert_path, for the signed SSH certificate to be used when connecting to this node. SSH Certificate Pathįor each node, you can specify the path, i.e. ssh_key, to be used to connect to the node. Instead of setting the path to the SSH key, you can alternatively specify the actual key, i.e. The SSH key path set in each node will always take precedence. Note: If you have a private key that can be used across all nodes, you can set the SSH key path at the cluster level. The default key path for each node is ~/.ssh/id_rsa. ssh_key_path, for the SSH private key to be used when connecting to this node. SSH Key Pathįor each node, you specify the path, i.e. This user must be a member of the Docker group or allowed to write to the node’s Docker socket. SSH Usersįor each node, you specify the user to be used when connecting to this node. In each node, you specify which port to be used when connecting to this node.

There is an exception for the AWS cloud provider, where the hostname_override field will be explicitly ignored. Note: When cloud providers are configured, you may need to override the hostname in order to use the cloud provider correctly. If the hostname_override isn’t set, then the address directive is used when registering the node in Kubernetes.

This hostname doesn’t need to be a routable address, but it must be a valid Kubernetes resource name. The hostname_override is used to be able to provide a friendly name for RKE to use when registering the node in Kubernetes. To change the interface used for the vxlan traffic of the Canal or Flannel network plug-ins please refer to the Network Plug-ins Documentation. The internal_address directive will set the address used for inter-host communication of the Kubernetes components, e.g. If the internal_address is not set, the address is used for inter-host communication. The internal_address provides the ability to have nodes with multiple addresses set a specific address to use for inter-host communication on a private network. RKE must be able to connect to this address. The address directive will be used to set the hostname or IP address of the node. Within each node, there are multiple directives that can be used. With this role, any workloads or pods that are deployed will land on these nodes. Taint set on nodes with the controlplane role is shown below: Taint Key These components are used to run the API server, scheduler, and controllers. With this role, the stateless components that are used to deploy Kubernetes will run on these nodes. Taint set on nodes with the etcd role is shown below: Taint Key Etcd is a distributed reliable key-value store which stores all Kubernetes state. Although you can run etcd on just one node, it typically takes 3, 5 or more nodes to create an HA configuration. Etcd keeps the state of your cluster and is the most important component in your cluster, single source of truth of your cluster. With this role, the etcd container will be run on these nodes. Note: Before v0.1.8, workloads/pods might have run on any nodes with worker or controlplane roles, but as of v0.1.8, they will only be deployed to any worker nodes.

#FREEPLANE CHANGE NODE ORDER UPGRADE#

It’s also possible to change a node’s role using the upgrade process. It’s possible to assign any combination of roles to any node. Three roles are supported: controlplane, etcd and worker. You can specify the list of roles that you want the node to be as part of the Kubernetes cluster. 1.6 labels: app: ingress Kubernetes Roles taints: # Available as of v0.3.0 - key: test-key value: test-value effect: NoSchedule - address: user: ubuntu role: - worker hostname_override: node3 internal_address: 192.168. 4.4 user: ubuntu role: - worker ssh_key_path: /home/user/.ssh/id_rsa ssh_cert: | AAAAHHNza. address: 3.3.3.3 user: ubuntu role: - worker ssh_key_path: /home/user/.ssh/id_rsa ssh_cert_path: /home/user/.ssh/id_rsa-cert.pub - address: 4.4. BEGIN RSA PRIVATE KEY-END RSA PRIVATE KEY. 2.2 user: ubuntu role: - worker ssh_key: |. 1.1 user: ubuntu role: - controlplane - etcd ssh_key_path: /home/user/.ssh/id_rsa port: 2222 - address: 2.2.

Freeplane change node order