loud-helmet-97067
02/15/2023, 12:01 PMcat /etc/rancher/k3s/config.yaml.d/50-rancher.yaml
{
"agent-token": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"disable-apiserver": false,
"disable-cloud-controller": false,
"disable-controller-manager": false,
"disable-etcd": false,
"disable-kube-proxy": false,
"disable-network-policy": false,
"disable-scheduler": false,
"docker": false,
"etcd-expose-metrics": false,
"etcd-snapshot-retention": 5,
"etcd-snapshot-schedule-cron": "0 */5 * * *",
"kube-controller-manager-arg": [
"cert-dir=/var/lib/rancher/k3s/server/tls/kube-controller-manager",
"secure-port=10257"
],
"kube-scheduler-arg": [
"cert-dir=/var/lib/rancher/k3s/server/tls/kube-scheduler",
"secure-port=10259"
],
"node-label": [
"<http://cattle.io/os=linux|cattle.io/os=linux>",
"<http://rke.cattle.io/machine=b89290bb-5f82-47e7-96bc-9cc16f126a5c|rke.cattle.io/machine=b89290bb-5f82-47e7-96bc-9cc16f126a5c>"
],
"node-taint": [
"<http://node-role.kubernetes.io/control-plane:NoSchedule|node-role.kubernetes.io/control-plane:NoSchedule>",
"<http://node-role.kubernetes.io/etcd:NoExecute|node-role.kubernetes.io/etcd:NoExecute>"
],
"private-registry": "/etc/rancher/k3s/registries.yaml",
"protect-kernel-defaults": false,
"secrets-encryption": false,
"selinux": false,
"server": "<https://x.x.x.1:6443>",
"token": "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
Master Node 1 [Sample ip: x.x.x.1]:
cat /etc/rancher/k3s/config.yaml.d/50-rancher.yaml
{
"agent-token": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"cluster-init": true,
"disable-apiserver": false,
"disable-cloud-controller": false,
"disable-controller-manager": false,
"disable-etcd": false,
"disable-kube-proxy": false,
"disable-network-policy": false,
"disable-scheduler": false,
"docker": false,
"etcd-expose-metrics": false,
"etcd-snapshot-retention": 5,
"etcd-snapshot-schedule-cron": "0 */5 * * *",
"kube-controller-manager-arg": [
"cert-dir=/var/lib/rancher/k3s/server/tls/kube-controller-manager",
"secure-port=10257"
],
"kube-scheduler-arg": [
"cert-dir=/var/lib/rancher/k3s/server/tls/kube-scheduler",
"secure-port=10259"
],
"node-label": [
"<http://cattle.io/os=linux|cattle.io/os=linux>",
"<http://rke.cattle.io/machine=77f5f3c6-a380-48b0-8b74-c7c3da330ff6|rke.cattle.io/machine=77f5f3c6-a380-48b0-8b74-c7c3da330ff6>"
],
"node-taint": [
"<http://node-role.kubernetes.io/control-plane:NoSchedule|node-role.kubernetes.io/control-plane:NoSchedule>",
"<http://node-role.kubernetes.io/etcd:NoExecute|node-role.kubernetes.io/etcd:NoExecute>"
],
"private-registry": "/etc/rancher/k3s/registries.yaml",
"protect-kernel-defaults": false,
"secrets-encryption": false,
"selinux": false,
"token": "YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY"
}
On testing the issue when Master Node1 goes down. When Master Node0 goes down, sometimes kubectl works (not 100%). We assume kube-api-server and related pods are distributed among both Master nodes alng with etcd datastore sync when w provision from Rancher UI
Any insights/feedback on how to correctly achieve HA for Rancher UI provisioned k3s when one of master node goes down is highly appreciated.rich-cartoon-70161
02/15/2023, 1:29 PMTo run K3s in this mode, you must have an odd number of server nodes. We recommend starting with three nodes.
loud-helmet-97067
02/15/2023, 2:20 PMrich-cartoon-70161
02/15/2023, 5:26 PMloud-helmet-97067
02/16/2023, 1:17 AMhandsome-jewelry-34280
03/18/2023, 3:46 AM