docs: add getting started

Author: Lukas Gentele

Diff for: .gitattributes

@@ -1,2 +1,3 @@
 * linguist-vendored
 *.go linguist-vendored=false
+*.mp4 filter=lfs diff=lfs merge=lfs -text

Diff for: docs/package.json

@@ -9,8 +9,8 @@
     "deploy": "docusaurus deploy"
   },
   "dependencies": {
-    "@docusaurus/core": "^2.0.0-alpha.55",
-    "@docusaurus/preset-classic": "^2.0.0-alpha.55",
+    "@docusaurus/core": "^2.0.0-alpha.56",
+    "@docusaurus/preset-classic": "^2.0.0-alpha.56",
     "classnames": "^2.2.6",
     "mdx-link-checker": "^0.0.7",
     "react": "^16.8.4",

Diff for: docs/pages/administration/uninstall.mdx

@@ -2,3 +2,22 @@
 title: Uninstall loft
 sidebar_label: Uninstall loft
 ---
+
+## Delete Helm Release
+```bash
+helm delete -n loft loft
+```
+
+## Delete Namespace (optional)
+```bash
+kubectl delete ns loft
+```
+
+## Delete CRDs (optional)
+```bash
+kubectl api-resources --api-group='storage.loft.sh' -o name | xargs kubectl delete crd
+```
+
+:::warning Data Loss
+Deleting the loft CRDs will also remove all loft objects inside your cluster, e.g. `Cluster`, `Team`, `User`. This **cannot** be undone.
+:::

Diff for: docs/pages/administration/upgrade.mdx

@@ -3,6 +3,11 @@ title: Upgrade loft
 sidebar_label: Upgrade loft
 ---
 
+Make sure you are in the kube-context of your loft management cluster and run the following command using helm v3:
 ```bash
-helm upgrade -n loft loft loft --repo https://charts.devspace.sh --reuse-values --version v0.0.1-beta.26
-```
+helm upgrade -n loft loft loft --repo https://charts.devspace.sh --reuse-values --version 0.0.1
+```
+
+:::important Version Numbers
+Make sure to use version numbers without the `v` prefix.
+:::

Diff for: docs/pages/fragments/change-default-limits.mdx

@@ -0,0 +1,11 @@
+
+**Option A:** To automatically create a kube-config using [loft CLI](#TODO), run the following command:
+```bash
+loft generate admin-kube-config
+```
+**Note:** Make sure you are in the right cluster/context before executing the command shown above.
+
+**Option B:** To manually create a kube-config, you need to:
+1. Create a ServiceAccount
+2. Create a ClusterRoleBinding to bind the ServiceAccount to the ClusterRole `cluster-admin`
+3. Create a kube-config for the cluster using the token of the ServiceAccount created above

Diff for: docs/pages/fragments/change-user-limits.mdx

@@ -0,0 +1,5 @@
+Enter a name for your cluster. This name must be a Kubernetes-compatible object name, i.e. only lowercase characters and dashes are allowed.
+
+:::note Naming
+Cluster names should tell engineers what the cluster is used for and where it is located, e.g. `gke-prod`, `gke-dev-tpu-us-1`, `eks-dev-us-west-1`
+:::

Diff for: docs/pages/fragments/connect-cluster.mdx

@@ -1,9 +1,13 @@
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+
 <Tabs
   groupId="platform"
-  defaultValue="npm"
+  defaultValue="mac"
   values={[
-    { label: 'npm', value: 'npm', },
-    { label: 'yarn', value: 'yarn', },
+  //  { label: 'npm', value: 'npm', },
+  //  { label: 'yarn', value: 'yarn', },
     { label: 'Mac Terminal', value: 'mac', },
     { label: 'Linux Bash', value: 'linux', },
     { label: 'Windows Powershell', value: 'windows', },

Diff for: docs/pages/fragments/connect-cluster/kube-config.mdx

@@ -2,12 +2,19 @@ After deploying loft, `helm install` will show an output similar to this one:
 
 ```bash
 ########## Set Admin Password ##########
-https://invite?token=[RESET_PASSWORD_TOKEN]
+https://loft.my-domain.tld/invite?token=[RESET_PASSWORD_TOKEN]
 ########################################
 ```
 
 Copy the link from the terminal output and open it in the browser to configure your admin account.
 
+<figure class="frame">
+  <video controls loop autoplay="true" muted>
+    <source src="/img/ui/auth/create-admin-user.mp4" type="video/mp4" />
+  </video>
+  <figcaption>loft UI - Create Admin User</figcaption>
+</figure>
+
 :::note
 If you lost the output of the `helm install` command, run the following command to view it again:
 ```bash