From 49fa318dffbb9c6a0868cb471d8575f7acebca03 Mon Sep 17 00:00:00 2001 From: Guillaume-Fourrat <39527431+Guillaume-Fourrat@users.noreply.github.com> Date: Fri, 6 Sep 2019 18:02:52 +0200 Subject: [PATCH] Adjust permissions all lines from [setup-k8s-prereqs.sh] basically require elevation, and because there's no sudo prefixing each, running the script under sudo su context makes sense. But the setup-k8s-master.sh will do chmod for root instead of current user if run under sudo su (cf use of "id"). It should be run under regular user context I think ? The need for root context for [setup-volumes-agent.sh] is tied to the bond command, which is linked to another PR which I'll link later. --- .../sql-big-data-cluster/deployment/kubeadm/ubuntu/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/README.md b/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/README.md index 9c9cfd66..e9bafe0a 100644 --- a/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/README.md +++ b/samples/features/sql-big-data-cluster/deployment/kubeadm/ubuntu/README.md @@ -20,9 +20,8 @@ In this example, we will deploy Kubernetes over multiple Linux machines (physica ### Instructions -1. Start a sudo shell context -1. Execute [setup-k8s-prereqs.sh](setup-k8s-prereqs.sh/) script on each machine -1. Execute [setup-k8s-master.sh](setup-k8s-master.sh/) script on the machine designated as Kubernetes master +1. Start a sudo shell context and Execute [setup-k8s-prereqs.sh](setup-k8s-prereqs.sh/) script on each machine +1. Execute [setup-k8s-master.sh](setup-k8s-master.sh/) script on the machine designated as Kubernetes master (_not_ under sudo su as otherwise you'll setup K8S .kube/config permissions for root) 1. After successful initialization of the Kubernetes master, follow the kubeadm join commands output by the setup script on each agent machine 1. Execute [setup-volumes-agent.sh](setup-volumes-agent.sh/) script on each agent machine to create volumes for local storage 1. Execute ***kubectl apply -f local-storage-provisioner.yaml*** against the Kubernetes cluster to create the local storage provisioner.