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
eblume commented 2026-01-24 16:42:29 -08:00
Owner
Copy link

Summary

  • Add containers/nettest/ with Alpine-based Dockerfile and connectivity test script
  • Add .forgejo/workflows/build-nettest.yaml workflow triggered by nettest-v* tags
  • Test script checks DNS resolution and HTTPS connectivity to forge and registry

Deployment and Testing

  • Merge PR to main
  • Run mise run container-release nettest v0.1.0 to trigger first build
  • Verify workflow runs successfully and container can reach tailnet services
  • Manually test from minikube: kubectl run nettest --rm -it --image=registry.tail8d86e.ts.net/blumeops/nettest:v0.1.0

🤖 Generated with Claude Code

## Summary - Add `containers/nettest/` with Alpine-based Dockerfile and connectivity test script - Add `.forgejo/workflows/build-nettest.yaml` workflow triggered by `nettest-v*` tags - Test script checks DNS resolution and HTTPS connectivity to forge and registry ## Deployment and Testing - [ ] Merge PR to main - [ ] Run `mise run container-release nettest v0.1.0` to trigger first build - [ ] Verify workflow runs successfully and container can reach tailnet services - [ ] Manually test from minikube: `kubectl run nettest --rm -it --image=registry.tail8d86e.ts.net/blumeops/nettest:v0.1.0` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Add nettest container for CI/CD network debugging
All checks were successful
Test CI / test (pull_request) Successful in 3s
Details
bf95e87c5d 
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>
Refactor container build to use generic workflow
All checks were successful
Test CI / test (pull_request) Successful in 4s
Details
de72274efd 
- 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>
No longer needed - the build-container workflow validates the CI environment.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
eblume merged commit 31697b4d63 into main 2026-01-24 16:54:36 -08:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!52
No description provided.