Prepare for release by pinning to v0.11.0 release and updating images. (#119)

Author: Gerrit91

.github/workflows/master.yaml

@@ -15,10 +15,10 @@ jobs:
         [ -d "${GITHUB_WORKSPACE}" ] && sudo chown -R $USER:$USER ${GITHUB_WORKSPACE}
 
     - name: Checkout
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
 
     - name: Docker Login
-      uses: docker/login-action@v1
+      uses: docker/login-action@v2
       with:
         registry: ${{ secrets.DOCKER_REGISTRY }}
         username: ${{ secrets.DOCKER_REGISTRY_USER }}

.github/workflows/pr.yaml

@@ -15,10 +15,10 @@ jobs:
         [ -d "${GITHUB_WORKSPACE}" ] && sudo chown -R $USER:$USER ${GITHUB_WORKSPACE}
 
     - name: Checkout
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
 
     - name: Docker Login
-      uses: docker/login-action@v1
+      uses: docker/login-action@v2
       with:
         registry: ${{ secrets.DOCKER_REGISTRY }}
         username: ${{ secrets.DOCKER_REGISTRY_USER }}

README.md

@@ -22,8 +22,8 @@ The mini-lab is a small, virtual setup to locally run the metal-stack. It deploy
 - Linux machine with hardware virtualization support
 - kvm as hypervisor for the VMs (you can check through the `kvm-ok` command)
 - [docker](https://www.docker.com/) >= 18.09 (for using kind and our deployment base image)
-- [docker-compose](https://docs.docker.com/compose/) >= 1.25.4 (for ease of use and for parallelizing control plane and partition deployment)
-- [kind](https://github.com/kubernetes-sigs/kind/releases) == v0.12.0 (for hosting the metal control plane on a kubernetes cluster v1.23.4)
+- [docker-compose](https://docs.docker.com/compose/) >= 2.0 (for ease of use and for parallelizing control plane and partition deployment)
+- [kind](https://github.com/kubernetes-sigs/kind/releases) == v0.15.0 (for hosting the metal control plane on a kubernetes cluster v1.25)
 - [containerlab](https://containerlab.srlinux.dev/install/) == v0.25.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)

inventories/group_vars/all/images.yaml

@@ -1,5 +1,5 @@
 ---
-metal_stack_release_version: develop
+metal_stack_release_version: v0.11.0
 
 ##
 ## for development purposes, you can override releases from our image vector here

inventories/group_vars/control-plane/metal.yml

@@ -12,16 +12,16 @@ metal_api_admin_key: metal-admin
 metal_api_nsq_tcp_address: nsqd:4150
 
 metal_api_images:
-- id: firewall-ubuntu-2.0.20220531
-  name: Firewall 2 Ubuntu 20220531
-  description: Firewall 2 Ubuntu 20220531
-  url: http://images.metal-stack.io/metal-os/firewall/2.0-ubuntu/20220531/img.tar.lz4
+- id: firewall-ubuntu-2.0.20220830
+  name: Firewall 2 Ubuntu 20220830
+  description: Firewall 2 Ubuntu 20220830
+  url: http://images.metal-stack.io/metal-os/firewall/2.0-ubuntu/20220830/img.tar.lz4
   features:
     - firewall
-- id: ubuntu-20.04.20220531
-  name: Ubuntu 20.04 20220531
-  description: Ubuntu 20.04 20220531
-  url: http://images.metal-stack.io/metal-os/ubuntu/20.04/20220531/img.tar.lz4
+- id: ubuntu-20.04.20220830
+  name: Ubuntu 20.04 20220830
+  description: Ubuntu 20.04 20220830
+  url: http://images.metal-stack.io/metal-os/ubuntu/20.04/20220830/img.tar.lz4
   features:
     - machine