27 Commits
Author SHA1 Message Date
hermes e381f46b4d fix(k3s): support GoProxy on armv7 nodes (#19)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m24s
## Problem
The GoProxy egress-check init container only handled `x86_64` and `aarch64`. On the `xu4` node, `uname -m` is `armv7l`, so the init container exited with `unsupported architecture: armv7l` and the Deployment stayed in CrashLoopBackOff.

## Fix
- select the upstream GoProxy v15.3 `proxy-linux-arm-v7.tar.gz` asset for `armv7l`;
- verify it with its pinned SHA-256 checksum;
- document ARMv7 support.

This PR is limited to the GoProxy workload and does not change the registry-DNS or connectivity-tester PRs.

Validation: `git diff --check`, architecture-to-asset mapping for `x86_64`, `aarch64`, and `armv7l`, and SHA-256 verification of the downloaded upstream ARMv7 release asset.
Reviewed-on: #19
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-21 18:59:20 +01:00
hermes 1cdfe25d32 feat(k3s): add GoProxy egress check POC (#17)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m27s
## Summary

- add a Kubernetes GoProxy egress-check POC using `snail007/goproxy`
- keep the existing Squid egress-check workload
- check `http://example.com/` and `http://example.com/robots.txt` separately
- route the client HTTP traffic through the GoProxy sidecar

## Verification

- PyYAML manifest parsing and structural assertions: PASS
- local upstream integration through GoProxy: `/` returned `200`, `/robots.txt` returned `404`
- `git diff --check`: PASS

The Kubernetes cluster was not changed; rollout remains Flux-controlled after merge.

Reviewed-on: #17
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-18 23:58:48 +01:00
hermes 1389a3b84c fix(k3s): route checker requests through squid (#16)
Build K3s Connectivity Image / build-and-push (push) Failing after 2m35s
Route the checker HTTP requests through the local Squid forward listener while retaining transparent interception.

Reviewed-on: #16
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 16:37:37 +01:00
hermes 664db3a784 fix(k3s): put squid forward port first (#15)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m11s
Place the regular forward-proxy port before the intercepted port so Squid getMyPort() resolves a valid non-interception listener during startup.

Reviewed-on: #15
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 15:59:20 +01:00
hermes 20d43598c9 fix(k3s): add squid forward proxy port (#14)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m21s
Keep the transparent interception listener on 3128 and add a regular forward-proxy listener on 3129 so Squid internal URLs have a valid port.

Reviewed-on: #14
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 15:18:49 +01:00
hermes aa00e66346 fix(k3s): clear squid init pid before startup (#13)
Build K3s Connectivity Image / build-and-push (push) Failing after 2m35s
Run squid -z in foreground mode and remove its PID file before starting the long-running Squid process.

Reviewed-on: #13
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 11:27:53 +01:00
hermes 88045795b3 fix(k3s): initialize squid swap directories (#12)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m8s
The Squid startup log explicitly requires squid -z before normal startup when using the UFS cache store. Initialize swap directories after creating the top-level cache path.

Reviewed-on: #12
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 09:04:52 +01:00
hermes f39d32ad89 fix(k3s): create squid cache directory before startup (#11)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m2s
Squid documentation requires the cache_dir top-level directory to exist and be writable; Squid only creates its L1/L2 subdirectories. Create /tmp/squid in the container command before starting Squid with the UFS store.

Reviewed-on: #11
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 08:08:04 +01:00
hermes 3d7351b4a7 fix(k3s): use writable squid cache path (#10)
Build K3s Connectivity Image / build-and-push (push) Successful in 2m56s
The mounted emptyDir cache path remains unusable for the Squid UFS initializer even with permissive modes. Use /tmp/squid, which is writable in the container, and remove the unnecessary cache volume/initContainer.

Reviewed-on: #10
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-16 00:31:08 +01:00
hermes b215d5bbfb fix(k3s): allow squid cache directory writes (#9)
Build K3s Connectivity Image / build-and-push (push) Successful in 2m45s
The init container now completes, but Squid still cannot create nested UFS swap directories with mode 0770. Use mode 0777 on this disposable emptyDir cache volume so the runtime user can initialize its cache store.

Reviewed-on: #9
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 22:09:14 +01:00
hermes 39604d4c65 fix(k3s): allow squid cache directory initialization (#8)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m0s
The init container cannot chown the emptyDir volume: chown returns Operation not permitted. Keep fsGroup 13 and only create the UFS directory plus chmod 0770 so Squid uid 13 can initialize its swap directories.

Reviewed-on: #8
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 21:46:02 +01:00
hermes 5ac4fe6ea6 fix(k3s): initialize squid cache directories (#7)
Build K3s Connectivity Image / build-and-push (push) Failing after 2m10s
Initialize the UFS cache directory as root before starting Squid, then hand ownership to uid/gid 13. Squid requires a supported cache_dir store and the runtime image cannot create its swap directories under the non-root user.

Reviewed-on: #7
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 20:24:34 +01:00
hermes c5580de386 fix(k3s): use null squid cache store (#6)
Build K3s Connectivity Image / build-and-push (push) Successful in 2m54s
Follow-up to #5. Squid still exits while initializing the ufs store because the runtime image cannot create the swap directories. Use the null cache store; caching is already disabled with cache deny all, and the writable mount remains for the configured path.

Reviewed-on: #6
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 14:00:20 +01:00
hermes 73a1473929 fix(k3s): configure squid cache store (#5)
Build K3s Connectivity Image / build-and-push (push) Successful in 2m53s
Follow-up to #4.

The writable /run fix is deployed, but Squid exits because the custom configuration has no cache_dir stores configured. Add a minimal writable ufs store backed by an emptyDir at /var/spool/squid; caching remains disabled with cache deny all.

Reviewed-on: #5
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 13:45:21 +01:00
hermes 01e838cce3 fix(k3s): make egress checker runtime healthy (#4)
Build K3s Connectivity Image / build-and-push (push) Successful in 2m50s
Fix the live egress-check deployment failure.

- provide writable /run for Squid pid creation with fsGroup 13
- remove HTTP probes from the client, which does not run an HTTP server

Observed production failures: Squid exited with permission denied for /run/squid.pid; client was killed by /healthz and /status probes.

Reviewed-on: #4
Reviewed-by: admin <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-15 13:10:19 +01:00
hermesandhermes 12d13f6a7c feat(k3s): add transparent HTTP egress checker (#3)
Build K3s Connectivity Image / build-and-push (push) Successful in 3m54s
## Summary
Add a small Kubernetes client that checks two configurable HTTP URLs on the same domain with different paths.

## Changes
- add the `egress-check` namespace, Service, Deployment, client ConfigMap, and Squid ConfigMap
- redirect client HTTP egress to the Squid sidecar with iptables in the shared pod network namespace
- reject direct non-DNS TCP/UDP egress from the pod
- expose `/status` and `/healthz`
- document the HTTP-only boundary; HTTPS transparent proxying requires TLS interception and a trusted CA

## Verification
- `python3 -m py_compile k3s/app.py`
- `git diff --check`
- reviewed the Kustomize resource list and manifest

---------

Co-authored-by: hermes <hermes@rudolf.keenetic.link>
Reviewed-on: #3
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-11-14 22:29:27 +01:00
admin 9286552737 x
Build K3s Connectivity Image / build-and-push (push) Successful in 11m34s
2026-10-16 23:13:36 +02:00
admin 29b036965c x
Build K3s Connectivity Image / build-and-push (push) Successful in 2m46s
2026-10-16 19:11:06 +02:00
admin d62b12c67d x 2026-10-16 19:10:10 +02:00
admin e51e40b9e5 x
Build K3s Connectivity Image / build-and-push (pull_request) Successful in 1m51s
2026-10-16 19:03:10 +02:00
admin 31e460843f x
Build K3s Connectivity Image / build-and-push (push) Successful in 10m54s
Build K3s Connectivity Image / build-and-push (pull_request) Successful in 2m39s
2026-10-16 18:43:36 +02:00
admin 7fbaf5c94a k3s
Build K3s Connectivity Image / build (push) Successful in 33s
Build K3s Connectivity Image / build (pull_request) Successful in 14s
2026-10-16 18:28:59 +02:00
admin b728807c5f Update .gitea/workflows/release.yml
release / build (push) Successful in 1m17s
2026-10-10 12:15:16 +02:00
admin 28af782b39 Update .gitea/workflows/release.yml 2026-10-10 12:14:14 +02:00
admin c76b25fd9e Merge pull request 'feat: add swarm connectivity tester' (#1) from hermes/swarm_connectivity_tester:main into main
Reviewed-on: Org1/swarm_connectivity_tester#1
2026-10-10 11:47:01 +02:00
admin 3dbd0db8b6 x 2026-10-10 11:43:00 +02:00
admin dddf94a719 Add empty.txy 2026-10-08 22:13:38 +02:00