## 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>
## 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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
## 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>