## Summary - Create tutorials directory structure with index page - Add 5 main tutorials targeting different audiences: - **what-is-blumeops** (Reader, AI) - High-level orientation - **exploring-the-docs** (All) - Navigation guide - **ai-assistance-guide** (AI, Owner) - Context for AI-assisted operations - **contributing** (Contributor) - First contribution workflow - **replicating-blumeops** (Replicator) - Overview for building similar setup - Add 4 replication sub-tutorials: - tailscale-setup, kubernetes-bootstrap, argocd-config, observability-stack - Update README.md to mark Phase 3 complete - Add changelog fragment Each tutorial explicitly identifies its target audiences and links to reference material rather than re-explaining concepts. ## Deployment and Testing - [x] All pre-commit hooks pass (doc-links validates wiki links) - [ ] Build docs via workflow to verify rendering - [ ] Review content for accuracy 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/94
1 KiB
1 KiB
| title | tags | ||
|---|---|---|---|
| tailscale-operator |
|
Tailscale Kubernetes Operator
The Tailscale operator enables Kubernetes services to be exposed directly on the Tailscale network via Ingress resources.
Quick Reference
| Property | Value |
|---|---|
| Namespace | tailscale |
| Helm Chart | tailscale/tailscale-operator |
| ArgoCD App | tailscale-operator |
How It Works
When you create an Ingress with ingressClassName: tailscale:
- Operator provisions a Tailscale node for the service
- Service becomes accessible at
<hostname>.tail8d86e.ts.net - TLS is handled automatically via Tailscale
Limitations
Services exposed via Tailscale Ingress are not accessible from:
- Other Kubernetes pods (they're not Tailscale clients)
- Docker containers on indri
For pod-to-service communication, use routing (*.ops.eblu.me) instead.