Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't fail when there is no .kube dir #2

Merged
merged 3 commits into from
Nov 18, 2020
Merged

Conversation

schnatterer
Copy link
Member

@schnatterer schnatterer commented Nov 17, 2020

Following #1, I tried this on a plain ubuntu (I used multipass) and it actually failed when there was no kubeconfig:
./scripts/init-cluster.sh: line 97: /home/ubuntu/.kube/config2: No such file or directory

multipass launch --name gitops 20.04
multipass shell gitops
sudo apt update && sudo apt install -y docker.io
sudo usermod -aG docker ubuntu
exit
multipass shell gitops
git clone https://github.com/cloudogu/k8s-gitops-playground
cd k8s-gitops-playground

git switch feature/init-without-kubectl

yes | scripts/init-cluster.sh

This should fix it.
It also checks our only prerequisite left: docker binary present and fails otherwise.

@schnatterer schnatterer force-pushed the feature/init-without-kubectl branch 2 times, most recently from 212755e to d1be54c Compare November 17, 2020 16:25
Also update prerequisites in README.
Not strictly necessary. k3s runs as root. Containers/pods are accessible via kubectl. Everything else is just convenience.
@marekzan marekzan merged commit 6d71825 into main Nov 18, 2020
@marekzan marekzan self-requested a review November 18, 2020 09:21
@schnatterer schnatterer deleted the feature/init-without-kubectl branch November 20, 2020 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants