From d22ea6aba39646712d654136f579c39e0a54ce3d Mon Sep 17 00:00:00 2001 From: "metal-robot[bot]" <68018895+metal-robot[bot]@users.noreply.github.com> Date: Thu, 15 Jul 2021 09:16:23 +0200 Subject: [PATCH] Bump releases to version v0.7.2 (#69) * Bump releases to version v0.7.2 * Auto generate Co-authored-by: metal-stack Co-authored-by: Gerrit91 --- Makefile | 2 +- docs/src/external/mini-lab/README.md | 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/Makefile b/Makefile index e9a82d14d5..8d84e657ab 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ .DEFAULT_GOAL := build -RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.7.1") +RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.7.2") ifeq ($(CI),true) DOCKER_TTY_ARG= diff --git a/docs/src/external/mini-lab/README.md b/docs/src/external/mini-lab/README.md index efe2d9175b..5133d39580 100644 --- a/docs/src/external/mini-lab/README.md +++ b/docs/src/external/mini-lab/README.md @@ -168,9 +168,8 @@ consolepassword: ... If you want to access the firewall with SSH or have internet connectivity from the firewall and machine, you'll need to have a static route configured that points to the vagrant boxes of the leaf switches: ```bash -make route # shows you the route needed to access the network internet-vagrant-lab -add this route to communicate with the virtual internet network 100.255.254.0/24 over leaf01 and leaf02 -sudo ip r a 100.255.254.0/24 nexthop via 192.168.121.120 dev virbr0 nexthop via 192.168.121.132 dev virbr0 +# Add the route to the network internet-vagrant-lab 100.255.254.0/24 via leaf01 and leaf02, whose IPs are dynamically allocated. Make sure there's no old route before execution. +make route # Connect to the firewall ssh metal@100.255.254.1