Still changes for k3d testing setup
Some checks failed
Test / Static Analysis (push) Successful in 33s
Test / Unit Tests — Docker Stack (push) Successful in 35s
Test / Unit Tests — K8s Stack (push) Successful in 37s
Test / Integration Test — K8s (k3d) (push) Failing after 49s

This commit is contained in:
2026-03-14 17:11:44 +01:00
parent f54fa6efbd
commit 8de67a1f93
2 changed files with 12 additions and 10 deletions

View File

@@ -107,12 +107,13 @@ jobs:
--agents 1 \ --agents 1 \
--k3s-arg "--disable=traefik@server:0" \ --k3s-arg "--disable=traefik@server:0" \
--wait --wait
# Gitea runners execute inside a Docker container (DinD). The host # Gitea runners run inside a Docker container. k3d creates its own
# loopback (127.0.0.1) is unreachable from inside the runner container, # bridge network (k3d-tofu-test); the runner isn't on it, so we
# so we patch the kubeconfig to use the k3d server container's # join the runner container to that network, then patch the kubeconfig
# Docker-network IP and connect directly on port 6443. # to use the server container's IP on that network directly (port 6443).
docker network connect k3d-tofu-test "$(hostname)"
SERVER_IP=$(docker inspect k3d-tofu-test-server-0 \ SERVER_IP=$(docker inspect k3d-tofu-test-server-0 \
--format '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}') --format '{{(index .NetworkSettings.Networks "k3d-tofu-test").IPAddress}}')
k3d kubeconfig get tofu-test \ k3d kubeconfig get tofu-test \
| sed "s|https://0\.0\.0\.0:[0-9]*|https://${SERVER_IP}:6443|g" \ | sed "s|https://0\.0\.0\.0:[0-9]*|https://${SERVER_IP}:6443|g" \
| sed "s|https://127\.0\.0\.1:[0-9]*|https://${SERVER_IP}:6443|g" \ | sed "s|https://127\.0\.0\.1:[0-9]*|https://${SERVER_IP}:6443|g" \

View File

@@ -91,12 +91,13 @@ integration-k8s:
--agents 1 \ --agents 1 \
--k3s-arg "--disable=traefik@server:0" \ --k3s-arg "--disable=traefik@server:0" \
--wait --wait
# GitLab CI runners execute inside a Docker container (DinD). The host # GitLab CI runners run inside a Docker container. k3d creates its own
# loopback (127.0.0.1) is unreachable from inside the runner container, # bridge network (k3d-tofu-test); the runner isn't on it, so we
# so patch the kubeconfig to use the k3d server container's # join the runner container to that network, then patch the kubeconfig
# Docker-network IP and connect directly on port 6443. # to use the server container's IP on that network directly (port 6443).
docker network connect k3d-tofu-test "$(hostname)"
SERVER_IP=$(docker inspect k3d-tofu-test-server-0 \ SERVER_IP=$(docker inspect k3d-tofu-test-server-0 \
--format '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}') --format '{{(index .NetworkSettings.Networks "k3d-tofu-test").IPAddress}}')
k3d kubeconfig get tofu-test \ k3d kubeconfig get tofu-test \
| sed "s|https://0\.0\.0\.0:[0-9]*|https://${SERVER_IP}:6443|g" \ | sed "s|https://0\.0\.0\.0:[0-9]*|https://${SERVER_IP}:6443|g" \
| sed "s|https://127\.0\.0\.1:[0-9]*|https://${SERVER_IP}:6443|g" \ | sed "s|https://127\.0\.0\.1:[0-9]*|https://${SERVER_IP}:6443|g" \