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.
## 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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
snail007/goproxyhttp://example.com/andhttp://example.com/robots.txtseparatelyVerification
/returned200,/robots.txtreturned404git diff --check: PASSThe Kubernetes cluster was not changed; rollout remains Flux-controlled after merge.