Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Commit

Permalink
Restructured documentation and landing page
Browse files Browse the repository at this point in the history
  • Loading branch information
afritzler committed Oct 29, 2018
1 parent d810fb6 commit 183103d
Show file tree
Hide file tree
Showing 15 changed files with 520 additions and 495 deletions.
506 changes: 15 additions & 491 deletions README.md

Large diffs are not rendered by default.

501 changes: 501 additions & 0 deletions docs/README.md

Large diffs are not rendered by default.

File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes.
File renamed without changes.
8 changes: 4 additions & 4 deletions doc/troubleshoot.md → docs/troubleshoot.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ If `k8s/bin/{master X/worker X}` isn't working, make sure the following:

# Fix Control plane by using the Bootstrap Controlplane

In case the `kube-{apiserver,controller-manager,scheduler}` isn't working, you can use the bootstrap control plane on `master-0` to recover the Kubernetes control plane. To do that you need to copy the `bootstrap-sercrets` into the `/etc` folder
In case the `kube-{apiserver,controller-manager,scheduler}` isn't working, you can use the bootstrap control plane on `master-0` to recover the Kubernetes control plane. To do that you need to copy the `bootstrap-sercrets` into the `/etc` folder

```
k8s/bin/master
Expand All @@ -33,7 +33,7 @@ Once the Bootstrap components have reconciled the broken Kubernetes control plan

```
sudo rm /etc/kubernetes/manifests/bootstrap-apiserver.yaml
sudo rm /etc/kubernetes/manifests/bootstrap-controller-manager.yaml
sudo rm /etc/kubernetes/manifests/bootstrap-controller-manager.yaml
sudo rm /etc/kubernetes/manifests/bootstrap-scheduler.yaml
```
The Boostrap secrets are also not needed anymore and can be removed.
Expand All @@ -46,7 +46,7 @@ sudo rm -rf /etc/kubernetes/bootstrap-secrets
## Startup ETCD client pod
Spin up an Pod which has the ETCD certificates mounted
```
k8s/bin/ks apply -f https://raw.githubusercontent.com/gardener/kubify/master/doc/manifests/etcdctl.yaml
k8s/bin/ks apply -f https://raw.githubusercontent.com/gardener/kubify/master/docs/manifests/etcdctl.yaml
k8s/bin/ks exec -it etcdctl sh
```
## Show current memory consumption
Expand Down Expand Up @@ -99,7 +99,7 @@ __IMPORTANT__: Remove/comment out the `recovery_cluster` and the `etcd_backup_fi

## Post Restore Check

After the cluster is restored, you need to make sure that the worker nodes have successfully joined the cluster. A restart of the worker nodes might be necessary
After the cluster is restored, you need to make sure that the worker nodes have successfully joined the cluster. A restart of the worker nodes might be necessary

```
k8s/bin/worker {0,1,2,...}
Expand Down

0 comments on commit 183103d

Please sign in to comment.