docs: fork docs for Talos 1.4

Start new docs for v1.4.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>

Dockerfile

@@ -843,9 +843,9 @@ RUN protoc \
     /protos/time/*.proto
 
 FROM scratch AS docs
-COPY --from=docs-build /tmp/configuration.md /website/content/v1.3/reference/
-COPY --from=docs-build /tmp/cli.md /website/content/v1.3/reference/
-COPY --from=proto-docs-build /tmp/api.md /website/content/v1.3/reference/
+COPY --from=docs-build /tmp/configuration.md /website/content/v1.4/reference/
+COPY --from=docs-build /tmp/cli.md /website/content/v1.4/reference/
+COPY --from=proto-docs-build /tmp/api.md /website/content/v1.4/reference/
 
 # The talosctl-cni-bundle builds the CNI bundle for talosctl.
 

website/config.toml

@@ -135,6 +135,10 @@ offlineSearch = false
 # Enable syntax highlighting and copy buttons on code blocks with Prism
 prism_syntax_highlighting = false
 
+[[params.versions]]
+url = "/v1.4/"
+version = "v1.4 (pre-release)"
+
 [[params.versions]]
 url = "/v1.3/"
 version = "v1.3 (pre-release)"

website/content/v1.3/_index.md

@@ -4,7 +4,7 @@ no_list: true
 linkTitle: "Documentation"
 cascade:
   type: docs
-lastRelease: v1.3.0-beta.0
+lastRelease: v1.3.0-beta.2
 kubernetesRelease: "1.26.0"
 prevKubernetesRelease: "1.25.3"
 theilaRelease: "v0.2.1"

website/content/v1.4/_index.md

@@ -0,0 +1,58 @@
+---
+title: Welcome
+no_list: true
+linkTitle: "Documentation"
+cascade:
+  type: docs
+lastRelease: v1.4.0-alpha.0
+kubernetesRelease: "1.27.0"
+prevKubernetesRelease: "1.26.0"
+theilaRelease: "v0.2.1"
+nvidiaContainerToolkitRelease: "v1.10.0"
+nvidiaDriverRelease: "515.65.01"
+iscsiToolsRelease: "v0.1.1"
+preRelease: true
+---
+
+## Welcome
+
+Welcome to the Talos documentation.
+If you are just getting familiar with Talos, we recommend starting here:
+
+- [What is Talos]({{< relref "introduction/what-is-talos" >}}): a quick description of Talos
+- [Quickstart]({{< relref "introduction/quickstart" >}}): the fastest way to get a Talos cluster up and running
+- [Getting Started]({{< relref "introduction/getting-started" >}}): a long-form, guided tour of getting a full Talos cluster deployed
+
+## Open Source
+
+### Community
+
+- GitHub: [repo](https://github.com/siderolabs/talos)
+- Slack: Join our [slack channel](https://slack.dev.talos-systems.io)
+- Matrix: Join our Matrix channels:
+  - Community: [#talos:matrix.org](https://matrix.to/#/#talos:matrix.org)
+  - Support: [#talos-support:matrix.org](https://matrix.to/#/#talos-support:matrix.org)
+- Support: Questions, bugs, feature requests [GitHub Discussions](https://github.com/siderolabs/talos/discussions)
+- Forum: [community](https://groups.google.com/a/siderolabs.com/forum/#!forum/community)
+- Twitter: [@SideroLabs](https://twitter.com/talossystems)
+- Email: [info@SideroLabs.com](mailto:info@SideroLabs.com)
+
+If you're interested in this project and would like to help in engineering efforts, or have general usage questions, we are happy to have you!
+We hold a weekly meeting that all audiences are welcome to attend.
+
+We would appreciate your feedback so that we can make Talos even better!
+To do so, you can take our [survey](https://docs.google.com/forms/d/1TUna5YTYGCKot68Y9YN_CLobY6z9JzLVCq1G7DoyNjA/edit).
+
+### Office Hours
+
+- When: Mondays at 16:30 UTC.
+- Where: [Google Meet](https://meet.google.com/day-pxhv-zky).
+
+You can subscribe to this meeting by joining the community forum above.
+
+## Enterprise
+
+If you are using Talos in a production setting, and need consulting services to get started or to integrate Talos into your existing environment, we can help.
+Sidero Labs, Inc. offers support contracts with SLA (Service Level Agreement)-bound terms for mission-critical environments.
+
+[Learn More](https://www.siderolabs.com/support/)

website/content/v1.4/advanced/_index.md

@@ -0,0 +1,4 @@
+---
+title: "Advanced Guides"
+weight: 60
+---

website/content/v1.4/advanced/advanced-networking.md

@@ -0,0 +1,108 @@
+---
+title: "Advanced Networking"
+description: "How to configure advanced networking options on Talos Linux."
+aliases:
+  - ../guides/advanced-networking
+---
+
+## Static Addressing
+
+Static addressing is comprised of specifying `addresses`, `routes` ( remember to add your default gateway ), and `interface`.
+Most likely you'll also want to define the `nameservers` so you have properly functioning DNS.
+
+```yaml
+machine:
+  network:
+    hostname: talos
+    nameservers:
+      - 10.0.0.1
+    interfaces:
+      - interface: eth0
+        addresses:
+          - 10.0.0.201/8
+        mtu: 8765
+        routes:
+          - network: 0.0.0.0/0
+            gateway: 10.0.0.1
+      - interface: eth1
+        ignore: true
+  time:
+    servers:
+      - time.cloudflare.com
+```
+
+## Additional Addresses for an Interface
+
+In some environments you may need to set additional addresses on an interface.
+In the following example, we set two additional addresses on the loopback interface.
+
+```yaml
+machine:
+  network:
+    interfaces:
+      - interface: lo
+        addresses:
+          - 192.168.0.21/24
+          - 10.2.2.2/24
+```
+
+## Bonding
+
+The following example shows how to create a bonded interface.
+
+```yaml
+machine:
+  network:
+    interfaces:
+      - interface: bond0
+        dhcp: true
+        bond:
+          mode: 802.3ad
+          lacpRate: fast
+          xmitHashPolicy: layer3+4
+          miimon: 100
+          updelay: 200
+          downdelay: 200
+          interfaces:
+            - eth0
+            - eth1
+```
+
+## Setting Up a Bridge
+
+The following example shows how to set up a bridge between two interfaces with an assigned static address.
+
+```yaml
+machine:
+  network:
+    interfaces:
+      - interface: br0
+        addresses:
+          - 192.168.0.42/24
+        bridge:
+          stp:
+            enabled: true
+          interfaces:
+              - eth0
+              - eth1
+```
+
+## VLANs
+
+To setup vlans on a specific device use an array of VLANs to add.
+The master device may be configured without addressing by setting dhcp to false.
+
+```yaml
+machine:
+  network:
+    interfaces:
+      - interface: eth0
+        dhcp: false
+        vlans:
+          - vlanId: 100
+            addresses:
+              - "192.168.2.10/28"
+            routes:
+              - network: 0.0.0.0/0
+                gateway: 192.168.2.1
+```

website/content/v1.4/advanced/air-gapped.md

@@ -0,0 +1,164 @@
+---
+title: "Air-gapped Environments"
+description: "Setting up Talos Linux to work in environments with no internet access."
+aliases:
+  - ../guides/air-gapped
+---
+
+In this guide we will create a Talos cluster running in an air-gapped environment with all the required images being pulled from an internal registry.
+We will use the [QEMU]({{< relref "../talos-guides/install/local-platforms/qemu" >}}) provisioner available in `talosctl` to create a local cluster, but the same approach could be used to deploy Talos in bigger air-gapped networks.
+
+## Requirements
+
+The follow are requirements for this guide:
+
+- Docker 18.03 or greater
+- Requirements for the Talos [QEMU]({{< relref "../talos-guides/install/local-platforms/qemu" >}}) cluster
+
+## Identifying Images
+
+In air-gapped environments, access to the public Internet is restricted, so Talos can't pull images from public Docker registries (`docker.io`, `ghcr.io`, etc.)
+We need to identify the images required to install and run Talos.
+The same strategy can be used for images required by custom workloads running on the cluster.
+
+The `talosctl images` command provides a list of default images used by the Talos cluster (with default configuration
+settings).
+To print the list of images, run:
+
+```bash
+talosctl images
+```
+
+This list contains images required by a default deployment of Talos.
+There might be additional images required for the workloads running on this cluster, and those should be added to this list.
+
+## Preparing the Internal Registry
+
+As access to the public registries is restricted, we have to run an internal Docker registry.
+In this guide, we will launch the registry on the same machine using Docker:
+
+```bash
+$ docker run -d -p 6000:5000 --restart always --name registry-airgapped registry:2
+1bf09802bee1476bc463d972c686f90a64640d87dacce1ac8485585de69c91a5
+```
+
+This registry will be accepting connections on port 6000 on the host IPs.
+The registry is empty by default, so we have fill it with the images required by Talos.
+
+First, we pull all the images to our local Docker daemon:
+
+```bash
+$ for image in `talosctl images`; do docker pull $image; done
+v0.15.1: Pulling from coreos/flannel
+Digest: sha256:9a296fbb67790659adc3701e287adde3c59803b7fcefe354f1fc482840cdb3d9
+...
+```
+
+All images are now stored in the Docker daemon store:
+
+```bash
+$ docker images
+REPOSITORY                               TAG                                        IMAGE ID       CREATED         SIZE
+gcr.io/etcd-development/etcd             v3.5.3                                     604d4f022632   6 days ago      181MB
+ghcr.io/siderolabs/install-cni           v1.0.0-2-gc5d3ab0                          4729e54f794d   6 days ago      76MB
+...
+```
+
+Now we need to re-tag them so that we can push them to our local registry.
+We are going to replace the first component of the image name (before the first slash) with our registry endpoint `127.0.0.1:6000`:
+
+```bash
+$ for image in `talosctl images`; do \
+    docker tag $image `echo $image | sed -E 's#^[^/]+/#127.0.0.1:6000/#'`; \
+  done
+```
+
+As the next step, we push images to the internal registry:
+
+```bash
+$ for image in `talosctl images`; do \
+    docker push `echo $image | sed -E 's#^[^/]+/#127.0.0.1:6000/#'`; \
+  done
+```
+
+We can now verify that the images are pushed to the registry:
+
+```bash
+$ curl http://127.0.0.1:6000/v2/_catalog
+{"repositories":["coredns/coredns","coreos/flannel","etcd-development/etcd","kube-apiserver","kube-controller-manager","kube-proxy","kube-scheduler","pause","siderolabs/install-cni","siderolabs/installer","siderolabs/kubelet"]}
+```
+
+> Note: images in the registry don't have the registry endpoint prefix anymore.
+
+## Launching Talos in an Air-gapped Environment
+
+For Talos to use the internal registry, we use the registry mirror feature to redirect all image pull requests to the internal registry.
+This means that the registry endpoint (as the first component of the image reference) gets ignored, and all pull requests are sent directly to the specified endpoint.
+
+We are going to use a QEMU-based Talos cluster for this guide, but the same approach works with Docker-based clusters as well.
+As QEMU-based clusters go through the Talos install process, they can be used better to model a real air-gapped environment.
+
+Identify all registry prefixes from `talosctl images`, for example:
+
+- `docker.io`
+- `gcr.io`
+- `ghcr.io`
+- `registry.k8s.io`
+
+The `talosctl cluster create` command provides conveniences for common configuration options.
+The only required flag for this guide is `--registry-mirror <endpoint>=http://10.5.0.1:6000` which redirects every pull request to the internal registry, this flag
+needs to be repeated for each of the identified registry prefixes above.
+The endpoint being used is `10.5.0.1`, as this is the default bridge interface address which will be routable from the QEMU VMs (`127.0.0.1` IP will be pointing to the VM itself).
+
+```bash
+$ sudo --preserve-env=HOME talosctl cluster create --provisioner=qemu --install-image=ghcr.io/siderolabs/installer:{{< release >}} \
+  --registry-mirror docker.io=http://10.5.0.1:6000 \
+  --registry-mirror gcr.io=http://10.5.0.1:6000 \
+  --registry-mirror ghcr.io=http://10.5.0.1:6000 \
+  --registry-mirror registry.k8s.io=http://10.5.0.1:6000 \
+validating CIDR and reserving IPs
+generating PKI and tokens
+creating state directory in "/home/user/.talos/clusters/talos-default"
+creating network talos-default
+creating load balancer
+creating dhcpd
+creating master nodes
+creating worker nodes
+waiting for API
+...
+```
+
+> Note: `--install-image` should match the image which was copied into the internal registry in the previous step.
+
+You can be verify that the cluster is air-gapped by inspecting the registry logs: `docker logs -f registry-airgapped`.
+
+## Closing Notes
+
+Running in an air-gapped environment might require additional configuration changes, for example using custom settings for DNS and NTP servers.
+
+When scaling this guide to the bare-metal environment, following Talos config snippet could be used as an equivalent of the `--registry-mirror` flag above:
+
+```bash
+machine:
+  ...
+  registries:
+      mirrors:
+        docker.io:
+          endpoints:
+          - http://10.5.0.1:6000/
+        gcr.io:
+          endpoints:
+          - http://10.5.0.1:6000/
+        ghcr.io:
+          endpoints:
+          - http://10.5.0.1:6000/
+        registry.k8s.io:
+          endpoints:
+          - http://10.5.0.1:6000/
+...
+```
+
+Other implementations of Docker registry can be used in place of the Docker `registry` image used above to run the registry.
+If required, auth can be configured for the internal registry (and custom TLS certificates if needed).
+
+Please see [pull-through cache guide]({{< relref "../talos-guides/configuration/pull-through-cache" >}}) for an example using Harbor container registry with Talos.