This option adds an additional hostname or IP as a Subject Alternative Name in the TLS cert, and it can be specified multiple times if you would like to access via both the IP and the hostname. To avoid certificate errors in such a configuration, you should install the server with the -tls-san YOUR_IP_OR_HOSTNAME_HERE option. So you can, for example, modify your kubeconfig file to point to it instead of a specific node. This endpoint can also be used for accessing the Kubernetes API. This endpoint can be set up using any number approaches, such as: Therefore, you should have a stable endpoint in front of the server nodes that will not change over time. For example, if you are running your cluster in a cloud that supports scaling groups, you may scale the server node group up and down over time, causing nodes to be created and destroyed and thus having different IPs from the initial set of server nodes. This can be the IP or hostname of any of the server nodes, but in many cases those may change over time. Configure the Fixed Registration Address Īgent nodes need a URL to register against. You should see your server nodes in the Ready state. Once you've launched the k3s server process on all server nodes, ensure that the cluster has come up properly with k3s kubectl get nodes. The node-taint parameter will allow you to configure nodes with taints, for example -node-taint CriticalAddonsOnly=true:NoExecute. If you wish to have a dedicated control plane where no user workloads will run, you can use taints. For more details, see the Configuration Options documentation.īy default, server nodes will be schedulable and thus your workloads can get launched on them. The same installation options available to single-server installs are also available for high-availability installs. When empty, this token will be generated automatically for further use.įor example, a command like the following could be used to install the K3s server with a MySQL database as the external datastore and set a token: The token parameter can also be used to set a deterministic token when adding nodes. When running the k3s server command on these nodes, you must set the datastore-endpoint parameter so that K3s knows how to connect to the external datastore. See the Requirements guide for minimum machine requirements. K3s requires two or more server nodes for this HA configuration. See the Cluster Datastore Options documentation for more details. You will first need to create an external datastore for the cluster. Setting up an HA cluster requires the following steps: 1. This is a websocket connection initiated by the k3s agent process, it is maintained by a client-side load balancer running as part of the agent process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |