Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/en/docs/next/install/kubernetes/talos-bootstrap.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,10 @@ talos-bootstrap --help
- 10.96.0.0/16
```

{{% alert title="Do not change op: on these entries" color="warning" %}}
Talos rejects `op: create` for any file outside `/var`, returning the error `create operation not allowed outside of /var` — the only exception is the special-cased `/etc/cri/conf.d/20-customization.part`. Because `/etc/lvm/lvm.conf` already exists on the node, it must use `op: overwrite`. Changing the op (or pointing `create` at another `/etc` path) fails the `WriteUserFiles` boot step: the node pauses and enters a reboot loop, and `talosctl bootstrap` reports only `bootstrap is not available yet` with no obvious cause.
{{% /alert %}}

1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:

```yaml
Expand Down
4 changes: 4 additions & 0 deletions content/en/docs/next/install/kubernetes/talosctl.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,10 @@ Discovered open port 50000/tcp on 192.168.123.13
- 10.96.0.0/16
```

{{% alert title="Do not change op: on these entries" color="warning" %}}
Talos rejects `op: create` for any file outside `/var`, returning the error `create operation not allowed outside of /var` — the only exception is the special-cased `/etc/cri/conf.d/20-customization.part`. Because `/etc/lvm/lvm.conf` already exists on the node, it must use `op: overwrite`. Changing the op (or pointing `create` at another `/etc` path) fails the `WriteUserFiles` boot step: the node pauses and enters a reboot loop, and `talosctl bootstrap` reports only `bootstrap is not available yet` with no obvious cause.
{{% /alert %}}

1. Make another configuration patch file `patch-controlplane.yaml` with settings exclusive to control plane nodes:

Note that VIP address is used for `machine.network.interfaces[0].vip.ip`:
Expand Down