eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Add nettest container for CI/CD network debugging #52

Merged
eblume merged 3 commits from feature/network-test-container into main 2026-01-24 16:54:36 -08:00
Conversation 0 Commits 3 Files changed 6 +239 -78

3 commits

Author SHA1 Message Date
Erich Blume
13d231687d Remove test workflow 
No longer needed - the build-container workflow validates the CI environment.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-24 16:54:21 -08:00
Erich Blume
de72274efd Refactor container build to use generic workflow
All checks were successful
Test CI / test (pull_request) Successful in 4s
Details 
- Replace per-container build-<name>.yaml with single build-container.yaml
- Workflow triggers on *-v* tags, parses container name from tag prefix
- Checks containers/<name>/Dockerfile exists, skips gracefully if not
- Rename container-release to container-tag-and-release for clarity
- Update container-list to scan containers/ directory

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-24 16:52:44 -08:00
Erich Blume
bf95e87c5d Add nettest container for CI/CD network debugging
All checks were successful
Test CI / test (pull_request) Successful in 3s
Details 
Add a simple Alpine-based container that tests connectivity to tailnet
services (forge.tail8d86e.ts.net and registry.tail8d86e.ts.net). This
helps diagnose networking issues when building containers from:
- Docker on indri (during CI builds)
- Minikube pods (manual testing)

The workflow triggers on nettest-v* tags and also runs the container
after building to verify Docker network access.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
 2026-01-24 16:41:07 -08:00