Isolated Clusters (#178)

Author: majst01

.github/workflows/deploy.yaml

@@ -17,7 +17,7 @@ jobs:
           lfs: true
       - uses: julia-actions/setup-julia@latest
         with:
-          version: 1.9.3
+          version: 1.9.4
       - name: Install dependencies
         run: julia --color=yes --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd()))'
       - name: Build and deploy

.github/workflows/release.yaml

@@ -16,7 +16,7 @@ jobs:
           lfs: true
       - uses: julia-actions/setup-julia@latest
         with:
-          version: 1.9.3
+          version: 1.9.4
       - name: Install dependencies
         run: julia --color=yes --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd()))'
       - name: Build and deploy

Dockerfile

@@ -1,4 +1,4 @@
-FROM julia:1.9.3
+FROM julia:1.9.4
 WORKDIR /workdir
 COPY Project.toml Project.toml
 COPY docs/Project.toml docs/Project.toml

README.md

@@ -1,7 +1,7 @@
 # Docs
 
-[![](https://img.shields.io/badge/docs-stable-blue.svg)](https://docs.metal-stack.io/)
-[![](https://img.shields.io/badge/docs-dev-blue.svg)](https://docs.metal-stack.io/dev/)
+[![Stable Docs](https://img.shields.io/badge/docs-stable-blue.svg)](https://docs.metal-stack.io/)
+[![Devel Docs](https://img.shields.io/badge/docs-dev-blue.svg)](https://docs.metal-stack.io/dev/)
 
 This repository contains the documentation of metal-stack at [docs.metal-stack.io](https://docs.metal-stack.io/).
 
@@ -11,15 +11,15 @@ It is being generated using [Julia Documenter](https://github.com/JuliaDocs/Docu
 
 To generate the documentation you can use the following command (only Docker is required):
 
-```
+```bash
 make
 ```
 
 The result is being written to `docs/build` and is fully static. You can simply view it in your browser by opening `docs/build/index.html`.
 
 To update the docs that is included from external repositories (e.g. metalctl, mini-lab, ...), you can run the following target:
 
-```
+```make
 RELEASE_VERSION=master make update
 ```
 

docs/Manifest.toml

@@ -1,8 +1,8 @@
 # This file is machine-generated - editing it directly is not advised
 
-julia_version = "1.9.3"
+julia_version = "1.9.4"
 manifest_format = "2.0"
-project_hash = "6c066df5b0d713de03a4d110004792392e9245d3"
+project_hash = "b3a3eb60d80c5437b5b46fccc7820a2fe79e60c7"
 
 [[deps.ANSIColoredPrinters]]
 git-tree-sha1 = "574baf8110975760d391c710b6341da1afa48d8c"

docs/Project.toml

@@ -3,4 +3,4 @@ Docs = "e1c13cdf-5c0d-472c-a597-c85aecc67ad6"
 Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
 
 [compat]
-Documenter = "0.27.23"
+Documenter = "0.27.25"

docs/make.jl

@@ -16,7 +16,7 @@ makedocs(
     linkcheck_ignore = [
         r"^(?!http)",
     ],
-    # strict = false, # TODO: Should be enabled soon, links from repos to CONTRIBUTING have to be updated though...
+    strict = false, # TODO: Should be enabled soon, links from repos to CONTRIBUTING have to be updated though...
     clean = true,
     pages = [
         "Introduction" => "index.md",
@@ -26,6 +26,7 @@ makedocs(
             "Hardware Support" => "overview/hardware.md",
             "Operating Systems" => "overview/os.md",
             "Kubernetes Integration" => "overview/kubernetes.md",
+            "Isolated Kubernetes" => "overview/isolated-kubernetes.md",
             "Storage" => "overview/storage.md",
             "Comparison" => "overview/comparison.md",
         ],

docs/src/development/proposals/MEP9/README.md

@@ -111,9 +111,9 @@ TODO
 ## References
 
 1. [WireGuard: Next Generation Secure Network Tunnel](https://www.youtube.com/watch?v=88GyLoZbDNw)
-2. [How Tailscale works](https://tailscale.com/blog/how-tailscale-works/)
-3. [Tailscale is officially SOC 2 compliant](https://tailscale.com/blog/soc2/)
-4. [Why not Wireguard](https://blog.ipfire.org/post/why-not-wireguard)
+2. [How Tailscale works](https://tailscale.com/blog/how-tailscale-works)
+3. [Tailscale is officially SOC 2 compliant](https://tailscale.com/blog/soc2)
+4. [Why not Wireguard](https://www.ipfire.org/blog/why-not-wireguard)
 5. [Wireguard: Known Limitations](https://www.wireguard.com/known-limitations/)
 6. [Wireguard: Things That Might Be Accomplished](https://www.wireguard.com/todo/)
 7. [Headscale: Tailscale control protocol v2](https://github.com/juanfont/headscale/issues/526)

docs/src/external/mini-lab/README.md

@@ -11,8 +11,8 @@ The mini-lab is a small, virtual setup to locally run the metal-stack. It deploy
 - [Requirements](#requirements)
 - [Known Limitations](#known-limitations)
 - [Try it out](#try-it-out)
-    - [Reinstall machine](#reinstall-machine)
-    - [Free machine](#free-machine)
+  - [Reinstall machine](#reinstall-machine)
+  - [Free machine](#free-machine)
 - [Flavors](#flavors)
 
 <!-- /TOC -->
@@ -23,7 +23,7 @@ The mini-lab is a small, virtual setup to locally run the metal-stack. It deploy
 - kvm as hypervisor for the VMs (you can check through the `kvm-ok` command)
 - [docker](https://www.docker.com/) >= 20.10.13 (for using kind and our deployment base image)
 - [kind](https://github.com/kubernetes-sigs/kind/releases) == v0.20.0 (for hosting the metal control plane)
-- [containerlab](https://containerlab.srlinux.dev/install/) >= v0.47.1
+- [containerlab](https://containerlab.dev/install/) >= v0.47.1
 - the lab creates a docker network on your host machine (`172.17.0.1`), this hopefully does not overlap with other networks you have
 - (recommended) haveged to have enough random entropy (only needed if the PXE process does not work)
 

docs/src/overview/architecture.md

@@ -108,7 +108,7 @@ Some notes on this picture:
 - By design, a partition only has very few ports open for incoming-connections from the internet. This contributes to a smaller attack surface and higher security of your infrastructure.
 - With the help of NSQ, it is not required to have connections from the metal control plane to the metal-core. The metal-core instances register at the message bus and can then consume partition-specfic topics, e.g. when a machine deletion gets issued by a user.
 
-# Machine Provisioning Sequence
+## Machine Provisioning Sequence
 
 The following sequence diagram illustrates some of the main principles of the machine provisioning lifecycle.