Path to SSH private key used to authenticate to the node (defaults to ~/.ssh/id_rsa)Īdvanced Configurations: RKE has many configuration options for customizing the install to suit your specific environment. The private DNS or IP address for internal cluster traffic List of Kubernetes roles assigned to the node 42.73 user: ubuntu role: services: etcd: snapshot: true creation: 6h retention: 24h # Required for external TLS termination with # ingress-nginx v0.22+ ingress: provider: nginx options: use-forwarded-headers: "true" Common RKE Nodes Options Option If your private key for a certain node is in a different location than the default, you will also need to configure the ssh_key_path option for that node. RKE will need to connect to each node over SSH, and it will look for a private key in the default location of ~/.ssh/id_rsa. Some services like AWS EC2 require setting the internal_address: if you want to use self-referencing security groups or firewalls. If your node has public and internal addresses, it is recommended to set the internal_address: so Kubernetes will use it for intra-cluster communication. Replace the IP addresses in the nodes list with the IP address or DNS names of the 3 nodes you created. Using the sample below as a guide, create the rancher-cluster.yml file. In a later step, when you set up the cluster with an RKE command, it will use this file to install Kubernetes on your nodes. In this section, you will create a Kubernetes cluster configuration file called rancher-cluster.yml. Install kubectl, a Kubernetes command-line tool.Īlso install RKE, the Rancher Kubernetes Engine, a Kubernetes distribution and command-line tool. In both single-node setups, Rancher can be installed with Helm on the Kubernetes cluster in the same way that it would be installed on any other cluster. The single node should have all three roles: etcd, controlplane, and worker. To set up a single-node RKE cluster, configure only one node in the cluster.yml. However, installing Rancher on a single-node cluster can be useful if you want to save resources by using a single node in the short term, while preserving a high-availability migration path. In a single-node Kubernetes cluster, the Rancher server does not have high availability, which is important for running Rancher in production. The below instructions represent only one possible way to install Kubernetes.įor systems without direct internet access, refer to Air Gap: Kubernetes install.
This cluster should be dedicated to run only the Rancher server.Īs of Rancher v2.5, Rancher can run on any Kubernetes cluster, included hosted Kubernetes solutions such as Amazon EKS.
RUNNING KAFKA ON NUTANI HOW TO
This section describes how to install a Kubernetes cluster.