docs: add some missing flags and info on host.k3d.internal

docs/faq/faq.md

@@ -8,6 +8,7 @@
 ## Issues with ZFS
 
 - k3s currently has [no support for ZFS](ttps://github.com/rancher/k3s/issues/66) and thus, creating multi-server setups (e.g. `k3d cluster create multiserver --servers 3`) fails, because the initializing server node (server flag `--cluster-init`) errors out with the following log:
+
   ```bash
   starting kubernetes: preparing server: start cluster and https: raft_init(): io: create I/O capabilities probe file: posix_allocate: operation not supported on socket
   ```
@@ -18,12 +19,12 @@
 ## Pods evicted due to lack of disk space
 
 - Pods go to evicted state after doing X
-    - Related issues: [#133 - Pods evicted due to `NodeHasDiskPressure`](https://github.com/rancher/k3d/issues/133) (collection of #119 and #130)
-    - Background: somehow docker runs out of space for the k3d node containers, which triggers a hard eviction in the kubelet
-    - Possible [fix/workaround by @zer0def](https://github.com/rancher/k3d/issues/133#issuecomment-549065666):
-        - use a docker storage driver which cleans up properly (e.g. overlay2)
-        - clean up or expand docker root filesystem
-        - change the kubelet's eviction thresholds upon cluster creation: `k3d cluster create --k3s-agent-arg '--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%' --k3s-agent-arg '--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%'`
+  - Related issues: [#133 - Pods evicted due to `NodeHasDiskPressure`](https://github.com/rancher/k3d/issues/133) (collection of #119 and #130)
+  - Background: somehow docker runs out of space for the k3d node containers, which triggers a hard eviction in the kubelet
+  - Possible [fix/workaround by @zer0def](https://github.com/rancher/k3d/issues/133#issuecomment-549065666):
+    - use a docker storage driver which cleans up properly (e.g. overlay2)
+    - clean up or expand docker root filesystem
+    - change the kubelet's eviction thresholds upon cluster creation: `k3d cluster create --k3s-agent-arg '--kubelet-arg=eviction-hard=imagefs.available<1%,nodefs.available<1%' --k3s-agent-arg '--kubelet-arg=eviction-minimum-reclaim=imagefs.available=1%,nodefs.available=1%'`
 
 ## Restarting a multi-server cluster or the initializing server node fails
 
@@ -38,9 +39,13 @@
 - The Problem: Passing a feature flag to the Kubernetes API Server running inside k3s.
 - Example: you want to enable the EphemeralContainers feature flag in Kubernetes
 - Solution: `#!bash k3d cluster create --k3s-server-arg '--kube-apiserver-arg=feature-gates=EphemeralContainers=true'`
-    - Note: Be aware of where the flags require dashes (`--`) and where not.
-        - the k3s flag (`--kube-apiserver-arg`) has the dashes
-        - the kube-apiserver flag `feature-gates` doesn't have them (k3s adds them internally)
+  - Note: Be aware of where the flags require dashes (`--`) and where not.
+    - the k3s flag (`--kube-apiserver-arg`) has the dashes
+    - the kube-apiserver flag `feature-gates` doesn't have them (k3s adds them internally)
 
 - Second example: `#!bash k3d cluster create k3d-one --k3s-server-arg --cluster-cidr="10.118.0.0/17" --k3s-server-arg --service-cidr="10.118.128.0/17" --k3s-server-arg --disable=servicelb --k3s-server-arg --disable=traefik --verbose`
-    - Note: There are many ways to use the `"` and `'` quotes, just be aware, that sometimes shells also try to interpret/interpolate parts of the commands
+  - Note: There are many ways to use the `"` and `'` quotes, just be aware, that sometimes shells also try to interpret/interpolate parts of the commands
+
+## How to access services (like a database) running on my Docker Host Machine
+
+- As of version v3.1.0, we're injecting the `host.k3d.internal` entry into the k3d containers (k3s nodes) and into the CoreDNS ConfigMap, enabling you to access your host system by referring to it as `host.k3d.internal`

docs/usage/commands.md

@@ -16,7 +16,10 @@ k3d
       --k3s-server-arg  # add additional arguments to the k3s server (see https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/#k3s-server-cli-help)
       -s, --servers  # specify how many server nodes you want to create
       --network  # specify a network you want to connect to
+      --no-hostip # disable the automatic injection of the Host IP as 'host.k3d.internal' into the containers and CoreDN
       --no-image-volume  # disable the creation of a volume for storing images (used for the 'k3d load image' command)
+      --no-lb # disable the creation of a LoadBalancer in front of the server nodes
+      --no-rollback # disable the automatic rollback actions, if anything goes wrong
       -p, --port  # add some more port mappings
       --token  # specify a cluster token (default: auto-generated)
       --timeout  # specify a timeout, after which the cluster creation will be interrupted and changes rolled back

tests/extra_test_k3s_versions.sh

@@ -12,7 +12,7 @@ source "$CURR_DIR/common.sh"
 for version in "${K3S_VERSIONS[@]}"; do
 
   info "Creating a cluster with k3s version $version ..."
-  $EXE cluster create c1 --wait --timeout 60s --api-port 6443 --image "rancher/k3s:$version" || failed "could not create cluster with k3s version $version"
+  $EXE cluster create c1 --wait --timeout 60s --image "rancher/k3s:$version" || failed "could not create cluster with k3s version $version"
 
   info "Checking we have access to the cluster ..."
   check_clusters "c1" || failed "error checking cluster with k3s version $version"