This allows to filter out addresses reported by Talos machines to
SideroMetal and which appear under `Machine.status.addresses`.
Fixes#1368
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Correct minor typo found in the "Expose Sidero Services" documentation.
Signed-off-by: Luke Carrier <luke@carrier.im>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
The website currently redirects to 0.5 instead of 0.6
Signed-off-by: Oscar Utbult <oscar.utbult@gmail.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
`sudo` begins a new command, so the preceding line must not end in `\`.
Signed-off-by: Daniel Höxtermann <daniel@hxtm.dev>
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Drop the pivoting step.
Drop the upgrades step (as it promotes in-place upgrades which don't
quite match the CAPI flow, and require additional handling).
Update for DHCP proxy.
Makes v0.6 the default documentation.
Signed-off-by: Andrey Smirnov <andrey.smirnov@siderolabs.com>
Users who are getting started will expect the code snippets to work as
is. Adding "sudo" in the documentation to improve user experience.
Signed-off-by: Sander Flobbe <s@nder.flob.be>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
These Sidero versions are outdated, using extremely old CAPI contract,
and they don't support recent versions of Talos.
Fixes#1075
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Explain how to set --auto-bmc-setup=false
using SIDERO_CONTROLLER_MANAGER_AUTO_BMC_SETUP.
Signed-off-by: Michael Vorburger <mike@vorburger.ch>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
The docs currently suggest placing the ipxe configuration file in /etc/dhcp/ - while this seems sane, when you update the firmware of an EdgeOS Device, which this is geared towards (or any other vyatta-based device), the entire filesystem is wiped, other than the /config directory.
This becomes especially problematic, because the config itself will still reference this file, and the dhcp server will refuse to start. From /var/log/messsages:
```
Oct 29 00:17:03 ubnt systemd[1]: vyatta-dhcpd.service: Control process exited, code=exited status=1
Oct 29 00:17:03 ubnt systemd[1]: Failed to start EdgeOS DHCP Server.
Oct 29 00:17:03 ubnt systemd[1]: vyatta-dhcpd.service: Unit entered failed state.
Oct 29 00:17:03 ubnt systemd[1]: vyatta-dhcpd.service: Failed with result 'exit-code'.
Oct 29 00:17:05 ubnt dhcpd3: Can't open /etc/dhcp/ipxe-metal.conf: No such file or directory
Oct 29 00:17:05 ubnt dhcpd3:
Oct 29 00:17:05 ubnt dhcpd3: If you did not get this software from ftp.isc.org, please
Oct 29 00:17:05 ubnt dhcpd3: get the latest from ftp.isc.org and install that before
Oct 29 00:17:05 ubnt dhcpd3: requesting help.
Oct 29 00:17:05 ubnt dhcpd3:
Oct 29 00:17:05 ubnt dhcpd3: If you did get this software from ftp.isc.org and have not
Oct 29 00:17:05 ubnt dhcpd3: yet read the README, please read it before requesting help.
Oct 29 00:17:05 ubnt dhcpd3: If you intend to request help from the dhcp-bugs at isc.org
Oct 29 00:17:05 ubnt dhcpd3: mailing list, please read the section on the README about
Oct 29 00:17:05 ubnt dhcpd3: submitting bug reports and requests for help.
Oct 29 00:17:05 ubnt dhcpd3:
Oct 29 00:17:05 ubnt dhcpd3: Please do not under any circumstances send requests for
Oct 29 00:17:05 ubnt dhcpd3: help directly to the authors of this software - please
Oct 29 00:17:05 ubnt dhcpd3: send them to the appropriate mailing list as described in
Oct 29 00:17:05 ubnt dhcpd3: the README file.
Oct 29 00:17:05 ubnt dhcpd3:
Oct 29 00:17:05 ubnt dhcpd3: exiting.
```
To fix this, any files which are referenced in the EdgeOS config need to be stored in the /config directory. Updating the docs to fix this reference, so others don't get bitten by this.
Signed-off-by: Russell Troxel <russell@troxel.io>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This PR is a copy of two PRs from talos:
https://github.com/siderolabs/talos/pull/5389/fileshttps://github.com/siderolabs/talos/pull/5391/files
It ensures that the banner is shown if the user isn't viewing the latest
sidero docs. This actually already was working but the banner html was in an incorrect spot, so moved that to match what's seen in Talos repo. Also adds the canonical links for search engines to update their
indexes.
Signed-off-by: Spencer Smith <spencer.smith@talos-systems.com>
This is final part of #735, previous part in #823.
This imports all remaining changes with some fixups minus the webhook
changes.
This change adds detailed hardware information to the Server CRD.
Hardware info is extracted by the agent from SMBIOS.
The ServerClass CRD is also updated so more precise qualifiers can be used.
Co-authored-by: Gerard de Leeuw <gdeleeuw@leeuwit.nl>
Signed-off-by: Gerard de Leeuw <gdeleeuw@leeuwit.nl>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This PR has two major changes:
* retire the code which supported seamless migration from
pre-ServerBinding era to ServerBindings: creating `ServerBinding` on the
fly from the `MetalMachine` and `Server`; as there's no migration path
from pre-ServerBinding Sidero to the new version, it's time to drop it
* instead of creating workload cluster Kubernetes client each time, use
CAPI standard class to cache the client; the problem with "leaking"
clients is that HTTP/2 clients are almost never gc'ed, so they stay in
memory keeping an open connection with keepalives going both ways, so
caching lowers the load both on the controller and the control plane
endpoint
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
While attempting to follow the v0.5 install instructions currently put up on the Sidero website, I encountered the target namespace error, and had to search further to find the solution in https://github.com/siderolabs/cluster-api-bootstrap-provider-talos/blob/master/README.md#installing
This PR adds the info to the Sidero v0.5 install docs, which to my knowledge the files in the repo is directly rendered by the https://sidero.dev website.
Signed-off-by: Spencer Smith <spencer.smith@talos-systems.com>
Upgrading Sidero on a single-node cluster with host networking enabled fails because the used ports can only be bound once. By setting the deployment strategy to `Recreate` in these cases upgrades can succeed (but with a small amount of downtime).
Signed-off-by: Gerard de Leeuw <gdeleeuw@leeuwit.nl>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This PR fixes a turbo-nit where the configs for the DHCP settings
weren't getting processed as code blocks
Signed-off-by: Spencer Smith <spencer.smith@talos-systems.com>
Includes bumps to the pkgs/tools for Go 1.17.7 and new kernel version.
Added clusterctl move label to the `siderolink` root secret.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
PRs: #719#720
Co-authored-by: Steve Francis <steve.francis@siderolabs.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Signed-off-by: Steve Francis <steve.francis@siderolabs.com>
From PRs #706#707#708#709
Co-authored-by: Steve Francis <steve.francis@siderolabs.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Signed-off-by: Steve Francis <steve.francis@siderolabs.com>
Fixes#527
Talos logs (see https://github.com/talos-systems/talos/pull/4600) are
delivered to Sidero over the SideroLink tunnel.
Logs can be seen with:
```
$ kubectl logs -n sidero-system deployment/sidero-controller-manager -c serverlogs -f
{"clock":67194673,"cluster":"management-cluster","facility":"user","machine":"default/management-cluster-cp-4j8f4","metal_machine":"default/management-cluster-cp-hbq57","msg":"[talos] phase bootloader (19/19): done, 176.795226ms\n","priority":"warning","seq":768,"server_uuid":"5b72932a-c482-4aa5-b00e-4b8773d3ac48","talos-level":"warn","talos-time":"2021-11-26T19:34:42.444342392Z"}
```
Logs are annotated on the fly with the information about `Server`,
`MetalMachine`, `Machine` and `Cluster`.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
