Bump releases to version v0.19.0

Makefile

@@ -1,5 +1,5 @@
 .DEFAULT_GOAL := build
-RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.18.18")
+RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.19.0")
 
 ifeq ($(CI),true)
 DOCKER_TTY_ARG=

docs/src/external/metalctl/docs/metalctl_firewall_create.md

@@ -11,6 +11,7 @@ metalctl firewall create [flags]
 ```
       --bulk-output                  when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
   -d, --description string           Description of the firewall to create. [optional]
+      --dnsservers strings           dns servers to add to the machine or firewall. [optional]
   -f, --file string                  filename of the create or update request in yaml format, or - for stdin.
 
                                      Example:
@@ -85,6 +86,7 @@ metalctl firewall create [flags]
                                      MODE can be omitted or one of:
                                      	auto	IP address is automatically acquired from the given network
                                      	noauto	No automatic IP address acquisition
+      --ntpservers strings           ntp servers to add to the machine or firewall. [optional]
   -S, --partition string             partition/datacenter where the firewall is created. [required, except for reserved machines]
   -P, --project string               Project where the firewall should belong to. [required]
   -s, --size string                  Size of the firewall. [required, except for reserved machines]

docs/src/external/metalctl/docs/metalctl_machine_create.md

@@ -51,6 +51,7 @@ Once created the machine installation can not be modified anymore.
 ```
       --bulk-output               when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
   -d, --description string        Description of the machine to create. [optional]
+      --dnsservers strings        dns servers to add to the machine or firewall. [optional]
   -f, --file string               filename of the create or update request in yaml format, or - for stdin.
 
                                   Example:
@@ -77,6 +78,7 @@ Once created the machine installation can not be modified anymore.
                                   MODE cane be omitted or one of:
                                   	auto	IP address is automatically acquired from the given network
                                   	noauto	IP address for the given network must be provided via --ips
+      --ntpservers strings        ntp servers to add to the machine or firewall. [optional]
   -S, --partition string          partition/datacenter where the machine is created. [required, except for reserved machines]
   -P, --project string            Project where the machine should belong to. [required]
   -s, --size string               Size of the machine. [required, except for reserved machines]

docs/src/external/metalctl/docs/metalctl_partition_capacity.md

@@ -9,10 +9,11 @@ metalctl partition capacity [flags]
 ## Options
 
 ```
-  -h, --help              help for capacity
-      --id string         filter on partition id. [optional]
-      --size string       filter on size id. [optional]
-      --sort-by strings   order by (comma separated) column(s), sort direction can be changed by appending :asc or :desc behind the column identifier. possible values: description|id|name
+  -h, --help                help for capacity
+      --id string           filter on partition id. [optional]
+      --project-id string   consider project-specific counts, e.g. size reservations. [optional]
+      --size string         filter on size id. [optional]
+      --sort-by strings     order by (comma separated) column(s), sort direction can be changed by appending :asc or :desc behind the column identifier. possible values: description|id|name
 ```
 
 ## Options inherited from parent commands

docs/src/external/metalctl/docs/metalctl_partition_create.md

@@ -12,6 +12,7 @@ metalctl partition create [flags]
       --bulk-output             when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
       --cmdline string          kernel commandline for the metal-hammer in the partition. [required]
   -d, --description string      Description of the partition. [required]
+      --dnsservers string       dns servers for the machines and firewalls in the partition. [optional]
   -f, --file string             filename of the create or update request in yaml format, or - for stdin.
 
                                 Example:
@@ -30,6 +31,7 @@ metalctl partition create [flags]
       --kernelurl string        kernel url for the metal-hammer in the partition. [required]
       --mgmtserver string       management server address in the partition. [required]
   -n, --name string             Name of the partition. [optional]
+      --ntpservers string       ntp servers for the machines and firewalls in the partition. [optional]
       --skip-security-prompts   skips security prompt for bulk operations
       --timestamps              when used with --file (bulk operation): prints timestamps in-between the operations
 ```

docs/src/external/metalctl/docs/metalctl_switch.md

@@ -50,6 +50,7 @@ switch are the leaf switches in the data center that are controlled by metal-sta
 * [metalctl switch detail](metalctl_switch_detail.md)	 - switch details
 * [metalctl switch edit](metalctl_switch_edit.md)	 - edit the switch through an editor and update
 * [metalctl switch list](metalctl_switch_list.md)	 - list all switches
+* [metalctl switch migrate](metalctl_switch_migrate.md)	 - migrate machine connections and other configuration from one switch to another
 * [metalctl switch port](metalctl_switch_port.md)	 - sets the given switch port state up or down
 * [metalctl switch replace](metalctl_switch_replace.md)	 - put a leaf switch into replace mode in preparation for physical replacement. For a description of the steps involved see the long help.
 * [metalctl switch ssh](metalctl_switch_ssh.md)	 - connect to the switch via ssh

docs/src/external/metalctl/docs/metalctl_switch_migrate.md

@@ -0,0 +1,46 @@
+# metalctl switch migrate
+
+migrate machine connections and other configuration from one switch to another
+
+```
+metalctl switch migrate <oldSwitchID> <newSwitchID> [flags]
+```
+
+## Options
+
+```
+  -h, --help   help for migrate
+```
+
+## Options inherited from parent commands
+
+```
+      --api-token string       api token to authenticate. Can be specified with METALCTL_API_TOKEN environment variable.
+      --api-url string         api server address. Can be specified with METALCTL_API_URL environment variable.
+  -c, --config string          alternative config file path, (default is ~/.metalctl/config.yaml).
+                               Example config.yaml:
+
+                               ---
+                               apitoken: "alongtoken"
+                               ...
+
+
+      --debug                  debug output
+      --force-color            force colored output even without tty
+      --kubeconfig string      Path to the kube-config to use for authentication and authorization. Is updated by login. Uses default path if not specified.
+      --no-headers             do not print headers of table output format (default print headers)
+  -o, --output-format string   output format (table|wide|markdown|json|yaml|template), wide is a table with more columns. (default "table")
+      --template string        output template for template output-format, go template format.
+                               For property names inspect the output of -o json or -o yaml for reference.
+                               Example for machines:
+
+                               metalctl machine list -o template --template "{{ .id }}:{{ .size.id  }}"
+
+
+      --yes-i-really-mean-it   skips security prompts (which can be dangerous to set blindly because actions can lead to data loss or additional costs)
+```
+
+## SEE ALSO
+
+* [metalctl switch](metalctl_switch.md)	 - manage switch entities
+

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

@@ -193,16 +193,15 @@ docker compose run --rm metalctl machine rm e0ab02d2-27cd-5a5e-8efc-080ba80cf258
 
 ## Flavors
 
-There's few versions of mini-lab environment that you can run. We call them flavors. There's 2 flavors at the moment:
+There are two versions, or flavors, of the mini-lab environment which differ in regards to the NOS running on the leaves:
 
-- `default` -- runs 2 machines.
-- `cluster-api` -- runs 3 machines. Useful for testing Control plane and worker node deployment with [Cluster API provider](https://github.com/metal-stack/cluster-api-provider-metalstack).
-- `sonic` -- use SONiC as network operating system for the leaves
+- `cumulus` -- runs 2 Cumulus switches.
+- `sonic` -- runs 2 SONiC switches
 
 In order to start specific flavor, you can define the flavor as follows:
 
 ```bash
-export MINI_LAB_FLAVOR=cluster-api
+export MINI_LAB_FLAVOR=sonic
 make
 ```