![]() ![]() In my configuration, the master nodes only have etcd and controlplane roles. # `node_selector` controls ingress placement and is optional # To disable ingress controller, set `provider: none` # Currently only nginx ingress provider is supported. # Use `mode: none` to disable authorization # This is useful if you want to use a load balancer for the # You can optionally create additional SANs (hostnames or IPs) to # Currently, only authentication strategy supported is x509. # Specify DNS provider (coredns or kube-dns) # After you launch the cluster, you cannot change your network provider. # KE provides the following network plug-ins that are deployed as add-ons: flannel, calico, weave, and canal # Set max pods to 150 instead of default 110 # IP address for the DNS service endpoint # This must match the service_cluster_ip_range in kube-api ![]() # CIDR pool used to assign IP addresses to pods in the cluster # Expose a different port range for NodePort services # This must match the service_cluster_ip_range in kube-controller # IP range for any services created on Kubernetes Sysctl: sudo tee -a /etc/sysctl.d/nf rke config -list-version -all name: Set authorized key taken from file name: Create rke user with passwordless sudo For this reason, we’ll create a user account called rke for deployment purpose. If using Red Hat Enterprise Linux, Oracle Enterprise Linux or CentOS, you cannot use the root user as SSH user due to Bugzilla 1527565. & sudo reboot -f Step 2: Create rke user Sudo apt update & sudo apt -y full-upgrade The first step is to update your Linux machines which will be used to build the cluster.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |