docs: Update nginx-mycelium documentation with simplified deployment and improved structure

This commit is contained in:
mik-tf
2025-11-05 22:36:21 -05:00
parent de267609d9
commit 61a911649b

View File

@@ -1,459 +1,434 @@
# 🌍 Nginx-Mycelium: Global Web Hosting with IPv6 Direct Access
# Mycelium Cloud - Nginx with IPv6 Website Hosting
A **complete and proven** example of hosting a professional website globally using Mycelium Cloud Kubernetes. This demonstrates **real-world web hosting** with custom content and confirmed global accessibility.
## 🎯 What's This About?
This example shows how to:
-**Host a professional website globally** via Mycelium IPv6 addresses
-**Use hostNetwork deployment** for direct IPv6 interface binding
-**Serve custom content** with ConfigMap-based content management
-**Demonstrate confirmed global access** with working IPv6 connectivity
A complete, production-ready example for deploying a globally accessible website on Mycelium Cloud using IPv6 networking. This demonstrates **peer-to-peer web hosting** without traditional hosting infrastructure.
## 📁 What This Contains
```
nginx-mycelium/
├── nginx-mycelium.md # This comprehensive guide with testing info
├── mycelium-website-hostnetwork.yaml # Production deployment with custom website
└── update-content.sh # Dynamic IPv6 discovery script
```
This directory contains everything you need to deploy a professional website with global IPv6 accessibility:
## 🚀 Quick Start - Global Website (3 minutes)
- **nginx-mycelium.md** - This comprehensive guide
- **mycelium-website-nodeport.yaml** - Complete deployment configuration
- **test-ipv6-website.sh** - IPv6 testing and verification script
- **update-content.sh** - Content update script (for future use)
## 🚀 Quick Start (3 minutes)
```bash
# 1. Deploy the website with hostNetwork for direct IPv6 access
kubectl apply -f mycelium-website-hostnetwork.yaml
# 1. Deploy the website
kubectl apply -f mycelium-website-nodeport.yaml
# 2. Wait for pod to be ready
# 2. Wait for deployment to be ready
kubectl wait --for=condition=ready pod -l app=mycelium-website --timeout=60s
# 3. Get the IPv6 address of the pod
NODE_NAME=$(kubectl get pod -l app=mycelium-website -o jsonpath='{.items[0].spec.nodeName}')
MYCELIUM_IP=$(kubectl get node $NODE_NAME -o jsonpath='{.status.addresses[?(@.type=="InternalIP")].address}')
# 3. Get your IPv6 address
POD_NAME=$(kubectl get pods -l app=mycelium-website -o name | head -1)
kubectl exec $POD_NAME -- ip addr show | grep "476:\|51d:\|552:" | head -1
echo "Website accessible at: http://[$MYCELIUM_IP]:80"
# 4. Test global access from ANY Mycelium IPv6 address!
curl http://[51d:3596:6cc3:81e7:ff0f:d546:3737:4c8c]:80
curl http://[476:c4f:b4cb:7205:ff0f:f56e:abea:6905]:80
curl http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80
# 4. Access your website globally
# Use the IPv6 address from step 3, replace [YOUR-IPV6] below:
curl -6 "http://[YOUR-IPV6]:8080/"
```
**🔄 Optional: Update Content with Dynamic IPv6 Discovery**
**Expected Result:** You'll see a professional website with gradient styling and IPv6 address detection.
The `update-content.sh` script can be used to regenerate content with current IPv6 addresses:
## 📋 What You'll Learn
```bash
# Run to update content with current cluster IPv6 addresses
./update-content.sh
# This will:
# 1. Discover current Mycelium IPv6 addresses
# 2. Regenerate website content with IPv6 information
# 3. Update the ConfigMap with new content
# 4. Trigger pod update with new content
```
## 🌍 Global Access URLs
Once deployed, your website is **globally accessible** at all Mycelium IPv6 addresses on port 80:
```
🌐 Master Nodes:
http://[51d:3596:6cc3:81e7:ff0f:d546:3737:4c8c]:80
http://[476:c4f:b4cb:7205:ff0f:f56e:abea:6905]:80
http://[538:964a:a1e1:4057:ff0f:63c7:960b:7c27]:80
🌐 Worker Nodes:
http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80
http://[437:9faf:1f1a:e2b1:ff0f:1fd9:7fd5:1095]:80
http://[5c3:a162:45ab:6c53:ff0f:8c55:36b0:24af]:80
```
**✅ CONFIRMED WORKING**: Direct IPv6 connectivity has been tested and verified!
**🔄 Dynamic Discovery**: IPv6 addresses are automatically discovered from your cluster using the `update-content.sh` script, ensuring the URLs always match your current infrastructure.
- ✅ IPv6-only web hosting on Mycelium Cloud
- ✅ Production nginx configuration with dual-stack support
- ✅ ConfigMap-based content management
- ✅ Global accessibility via peer-to-peer networking
- ✅ hostNetwork deployment patterns
- ✅ IPv6 troubleshooting and verification
## 🏗️ Architecture
### hostNetwork Direct Access Design
This example uses a **single-file approach** with integrated components:
```
🌍 Internet (Mycelium Clients)
🌐 Mycelium IPv6 Network (Port 80)
🖥️ hostNetwork Pod (direct IPv6 interface binding)
📊 Custom Website Content (ConfigMap-managed)
🔄 nginx Web Server (custom content, health endpoints)
```
1. **Deployment** - Pod with nginx and custom content
2. **ConfigMaps** - HTML content and nginx configuration
3. **Service** - NodePort for external accessibility
### Key Features
**Network Flow:** `Direct IPv6 → nginx:8080 → Custom HTML`
#### **Kubernetes Deployment with hostNetwork**
**Key Innovation:** Uses `hostNetwork: true` for direct access to Mycelium IPv6 interfaces.
## 🔧 Files Explanation
### mycelium-website-nodeport.yaml
```yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: mycelium-website
spec:
replicas: 1
template:
spec:
hostNetwork: true # Direct IPv6 interface binding
hostNetwork: true # Direct IPv6 access
containers:
- name: nginx
image: nginx:alpine
ports:
- containerPort: 80 # Standard web port
hostPort: 80 # Direct host binding
```
#### **Dynamic IPv6 Discovery**
The `update-content.sh` script automatically discovers Mycelium IPv6 addresses from your cluster:
```bash
# Run the script to update content with current IPv6 addresses
./update-content.sh
# The script will:
# 1. Query kubectl for cluster node IPv6 addresses
# 2. Generate HTML with dynamic address discovery
# 3. Update the ConfigMap automatically
# 4. Show website content with current cluster state
```
#### **Custom Website Content**
The deployment includes a professional website with:
- Modern HTML design with Mycelium Cloud branding
- Responsive layout with gradient backgrounds
- Interactive IPv6 address detection
- Real-time timestamp updates
- Professional web interface
#### **Content Management**
```yaml
- containerPort: 8080
hostPort: 8080
volumeMounts:
- name: html-content
mountPath: /usr/share/nginx/html
- name: nginx-config
mountPath: /etc/nginx/conf.d
volumes:
- name: html-content
configMap:
name: mycelium-website-content # Custom website content
name: mycelium-website-content
- name: nginx-config
configMap:
name: mycelium-nginx-config # nginx configuration
name: mycelium-nginx-config
```
## 🌟 Direct IPv6 Access Benefits
**What it does:**
- Creates 1 pod with nginx and custom website content
- Uses `hostNetwork: true` for direct IPv6 interface access
- Includes ConfigMaps for dynamic content management
- Dual-stack nginx (IPv4 + IPv6) configuration
### **Direct Interface Binding**
- **hostNetwork: true**: Pod directly binds to host network interface
- **IPv6 Address Access**: Gets Mycelium IPv6 address from host node
- **Simplified Architecture**: No service layer needed for IPv6 access
- **Direct Connectivity**: External clients connect directly to pod
## 🌐 Access Methods
### **Performance Advantages**
- **Zero Latency**: Direct interface binding, no service proxy overhead
- **Full IPv6 Support**: Direct access to Mycelium IPv6 addresses
- **Simple Deployment**: Single pod with hostNetwork configuration
- **Production Ready**: Standard nginx configuration with health endpoints
### Method 1: Direct IPv6 (Primary - Recommended)
### **Global Accessibility**
```bash
# Access directly via any Mycelium IPv6 address
curl http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80
# Get your pod's IPv6 address
POD_NAME=$(kubectl get pods -l app=mycelium-website -o name | head -1)
IPV6=$(kubectl exec $POD_NAME -- ip addr show | grep "476:\|51d:\|552:" | head -1 | awk '{print $2}' | cut -d'/' -f1)
# Access your website
curl -6 "http://[$IPV6]:8080/"
curl -6 "http://[$IPV6]:8080/health"
# Or in browser: http://[YOUR-IPV6]:8080/
```
## 🔧 Testing & Verification
**Why this works:**
- `hostNetwork: true` gives direct access to host IPv6 interfaces
- nginx listens on both IPv4 and IPv6
- Mycelium provides globally routable IPv6 addresses
- No port translation or proxy needed
### Method 2: Health Check Verification
### **✅ CONFIRMED: IPv6 Connectivity Test**
```bash
# ✅ VERIFIED: Direct IPv6 connectivity working!
curl -v http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80
# Test health endpoint
curl -6 "http://[YOUR-IPV6]:8080/health"
# Expected: "healthy"
# Expected output shows successful connection:
# * Connected to 552:5984:2d97:72dc:ff0f:39ef:6ec:a48c (552:5984:2d97:72dc:ff0f:39ef:6ec:a48c) port 80 (#0)
# < HTTP/1.1 200 OK (or 404 if serving default content)
# Test main page (should return 3975+ bytes)
curl -6 "http://[YOUR-IPV6]:8080/" | wc -c
# Expected: 3975 (or similar large number)
```
### **🎯 Pod Status Verification**
### Method 3: Interactive Testing
```bash
# Check pod status and location
kubectl get pods -l app=mycelium-website -o wide
# Expected output shows:
# NAME READY STATUS NODE
# mycelium-website-xxxx-xxxx 1/1 Running kc22haven612worker1
# Get the IPv6 address of the pod's node
NODE_NAME=$(kubectl get pod -l app=mycelium-website -o jsonpath='{.items[0].spec.nodeName}')
MYCELIUM_IP=$(kubectl get node $NODE_NAME -o jsonpath='{.status.addresses[?(@.type=="InternalIP")].address}')
echo "Pod running on: $NODE_NAME with IPv6: $MYCELIUM_IP"
```
### **🌐 Direct IPv6 Access Test**
```bash
# Test from multiple IPv6 addresses (all should work):
curl http://[51d:3596:6cc3:81e7:ff0f:d546:3737:4c8c]:80
curl http://[476:c4f:b4cb:7205:ff0f:f56e:abea:6905]:80
curl http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80
curl http://[437:9faf:1f1a:e2b1:ff0f:1fd9:7fd5:1095]:80
curl http://[5c3:a162:45ab:6c53:ff0f:8c55:36b0:24af]:80
curl http://[538:964a:a1e1:4057:ff0f:63c7:960b:7c27]:80
# All should return the custom Mycelium Cloud website HTML
```
### **🏥 Health Endpoint Test**
```bash
# Test the health endpoint
kubectl exec pod/mycelium-website-xxxx-xxxx -- curl -s http://localhost:8080/health
# Expected output: "healthy"
```
### **📊 Content Verification**
```bash
# Check that custom content is being served
curl -s http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80 | head -10
# Should show the custom Mycelium Cloud website HTML with:
# - <title>Mycelium Cloud - Globally Accessible Website</title>
# - Professional styling and branding
```
### **🔍 Network Interface Verification**
```bash
# Verify hostNetwork binding
kubectl exec pod/mycelium-website-xxxx-xxxx -- ip addr show | grep inet6
# Should show the Mycelium IPv6 address bound to the pod
# Example: inet6 552:5984:2d97:72dc:ff0f:39ef:6ec:a48c/64 scope global
```
### **📈 Load Testing**
```bash
# Test concurrent requests
for i in {1..5}; do
curl -s http://[552:5984:2d97:72dc:ff0f:39ef:6ec:a48c]:80 > /dev/null &
done
wait
# Monitor nginx logs
kubectl logs -l app=mycelium-website --tail=10
```
## 🌍 Global Use Cases
### **Perfect For:**
-**Static Website Hosting**: Company sites, portfolios, blogs
-**Application Frontends**: Web UIs for your applications
-**Documentation Sites**: API docs, user guides
-**Proof of Concepts**: Demonstrate global infrastructure
-**Multi-Region Access**: Users worldwide access the same site
### **Technical Benefits:**
-**Global CDN**: No centralized server, distributed across nodes
-**Low Latency**: Users connect to nearest healthy pod
-**No Bandwidth Limits**: Uses Mycelium's peer-to-peer network
-**Automatic Scaling**: Kubernetes handles pod creation/deletion
## 📋 Monitoring & Management
### **Real-Time Status**
```bash
# Check deployment status
kubectl get deployment nginx-mycelium
# View service configuration
kubectl get svc nginx-mycelium-service -o yaml
# Check external IPs are configured
kubectl get svc nginx-mycelium-service
```
### **Performance Monitoring**
```bash
# Check resource usage
kubectl top pods -l app=nginx-mycelium
# Monitor nginx access logs
kubectl logs -l app=nginx-mycelium -f
# Check pod distribution
kubectl get pods -l app=nginx-mycelium -o custom-columns=NAME:.metadata.name,NODE:.spec.nodeName,IP:.status.podIP
```
### **Scaling Operations**
```bash
# Current replica count
kubectl get deployment nginx-mycelium
# Scale up for more capacity
kubectl scale deployment nginx-mycelium --replicas=5
# Check load distribution after scaling
kubectl get pods -l app=nginx-mycelium -o wide
# Keep testing connection
watch -n 2 'curl -6 -s "http://[YOUR-IPV6]:8080/health" && echo " - $(date)"'
```
## 🔍 Troubleshooting
### **Common Issues**
### Check Deployment Status
```bash
# Check if pods are running
kubectl get pods -l app=mycelium-website
#### **Pod Won't Start**
# Check service details
kubectl get svc mycelium-website-service
# Check what's deployed
kubectl get all -l app=mycelium-website
# Verify nginx is listening on both IPv4 and IPv6
POD_NAME=$(kubectl get pods -l app=mycelium-website -o name | head -1)
kubectl exec $POD_NAME -- netstat -tuln | grep 8080
```
### Common Issues
#### IPv6 Binding Problems
```bash
# Problem: nginx only listening on IPv4
# Check current binding:
kubectl exec $POD_NAME -- netstat -tuln | grep 8080
# Should show:
# tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN
# tcp 0 0 :::8080 :::* LISTEN (IPv6)
# If missing IPv6, restart the deployment:
kubectl delete pod $POD_NAME
```
#### Pod Not Starting
```bash
# Check pod status and events
kubectl describe pod -l app=nginx-mycelium
kubectl describe pod -l app=mycelium-website
# Check node resource availability
kubectl get nodes
# Check pod logs
kubectl logs -l app=mycelium-website
# Look for scheduling issues
kubectl get events --sort-by='.lastTimestamp'
# Check nginx configuration
kubectl exec $POD_NAME -- cat /etc/nginx/conf.d/default.conf
```
#### **IPv6 Access Not Working**
#### IPv6 Not Accessible
```bash
# Verify IPv6 address exists
kubectl exec $POD_NAME -- ip addr show | grep "476:\|51d:\|552:"
# Test IPv6 connectivity
ping 51d:3596:6cc3:81e7:ff0f:d546:3737:4c8c
ping6 [YOUR-IPV6]
# Check if pods are running
kubectl get pods -l app=nginx-mycelium
# Verify service configuration
kubectl get svc nginx-mycelium-service -o wide
# Test nginx inside pod
kubectl exec $POD_NAME -- curl -s http://localhost:8080/health
```
#### **Load Balancing Issues**
#### Content Not Loading
```bash
# Check all pods are ready
kubectl get pods -l app=nginx-mycelium
# Verify ConfigMaps are mounted
kubectl exec $POD_NAME -- ls -la /usr/share/nginx/html/
# Verify endpoints are healthy
kubectl get endpoints nginx-mycelium-service
# Check actual content
kubectl exec $POD_NAME -- cat /usr/share/nginx/html/index.html | head -10
# Check pod logs for errors
kubectl logs -l app=nginx-mycelium
# Verify nginx config is loaded
kubectl exec $POD_NAME -- nginx -t
```
## 🎯 Best Practices
## 🛠️ Common Operations
### **Deployment Strategy**
1. **Start Small**: Deploy 1 replica initially
2. **Test Connectivity**: Verify IPv6 access works
3. **Scale Gradually**: Increase replicas based on traffic
4. **Monitor Performance**: Watch resource usage and response times
### **Content Management**
- **Static Files**: Update `index.html` for content changes
- **Volume Mounts**: Use ConfigMaps for dynamic content
- **Health Checks**: Implement proper liveness/readiness probes
### **Security Considerations**
- **No Authentication**: Open access for demonstration purposes
- **Rate Limiting**: Consider adding nginx rate limiting for production
- **HTTPS**: Use TF Gateway CRDs for SSL certificates
## 🚀 Advanced Features
### **Custom Content**
Replace the `index.html` with your own content:
### Updating Website Content
```bash
# Update content
kubectl create configmap nginx-content --from-file=index.html=custom.html
# Update the ConfigMap with new HTML content
kubectl create configmap mycelium-website-content \
--from-file=index.html=./new-website.html \
--dry-run=client -o yaml | kubectl apply -f -
# Rollout update
kubectl rollout restart deployment/nginx-mycelium
# Restart pod to pick up changes
POD_NAME=$(kubectl get pods -l app=mycelium-website -o name | head -1)
kubectl delete pod $POD_NAME
```
### **Additional Services**
Add more services following the same pattern:
### Scaling
```bash
# Apply additional nginx services
kubectl apply -f additional-services.yaml
# Scale to 2 replicas (each gets different IPv6)
kubectl scale deployment mycelium-website --replicas=2
# Each service gets its own LoadBalancer with IPv6
# Check distribution across nodes
kubectl get pods -o wide -l app=mycelium-website
```
### **TF Gateway Integration**
For custom domains and HTTPS:
```yaml
# Use TF Gateway CRD for public domain
apiVersion: ingress.grid.tf/v1
kind: TFGW
### Monitoring
```bash
# View nginx logs
kubectl logs -f deployment/mycelium-website
# Check resource usage
kubectl top pod -l app=mycelium-website
# Monitor IPv6 addresses
watch 'kubectl get pods -o wide -l app=mycelium-website'
```
### IPv6 Address Discovery
```bash
# Get all IPv6 addresses for the website pod
POD_NAME=$(kubectl get pods -l app=mycelium-website -o name | head -1)
kubectl exec $POD_NAME -- ip addr show | grep "inet6" | grep "scope global"
# Test multiple IPv6 addresses
for ipv6 in $(kubectl exec $POD_NAME -- ip addr show | grep "476:\|51d:\|552:" | awk '{print $2}' | cut -d'/' -f1); do
echo "Testing IPv6: $ipv6"
curl -6 -m 2 "http://[$ipv6]:8080/health" && echo " - SUCCESS" || echo " - FAILED"
done
```
## 🧹 Cleanup
When you're done testing:
```bash
# Delete the entire deployment
kubectl delete -f mycelium-website-nodeport.yaml
# Verify cleanup
kubectl get all -l app=mycelium-website
# Remove any lingering ConfigMaps (optional)
kubectl delete configmap mycelium-website-content mycelium-nginx-config
```
## 🎯 What This Demonstrates
This example shows:
- **IPv6-Only Web Hosting** - Complete website delivery via peer-to-peer networking
- **Production nginx Configuration** - Dual-stack (IPv4/IPv6) web server
- **Dynamic Content Management** - ConfigMaps for easy updates
- **Global Accessibility** - Direct IPv6 URL access worldwide
- **Kubernetes Best Practices** - Proper separation of concerns
## 🔗 Next Steps
Once you understand this example, try:
1. **SSL/HTTPS** - Add TLS termination for secure communications
2. **Custom Domains** - Integrate with Mycelium DNS services
3. **Multiple Applications** - Deploy several websites with load balancing
4. **Monitoring** - Add Prometheus/Grafana for observability
5. **CDN Integration** - Leverage Mycelium's distributed nature
## 📚 Advanced Features
### Custom nginx Configuration
```bash
# Edit nginx config
kubectl create configmap mycelium-nginx-config \
--from-file=default.conf=./custom-nginx.conf \
--dry-run=client -o yaml | kubectl apply -f -
# Restart to apply
kubectl rollout restart deployment/mycelium-website
```
### Multiple Website Support
```bash
# Deploy multiple websites (each gets unique IPv6)
kubectl apply -f - <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-website
name: mycelium-website-2
spec:
hostname: "my-website"
backends:
- "http://[51d:3596:6cc3:81e7:ff0f:d546:3737:4c8c]:80"
replicas: 1
selector:
matchLabels:
app: mycelium-website-2
template:
metadata:
labels:
app: mycelium-website-2
spec:
hostNetwork: true
containers:
- name: nginx
image: nginx:alpine
ports:
- containerPort: 8080
hostPort: 8081
EOF
```
## 📊 Performance Characteristics
## 💡 Pro Tips
### **Expected Latency**
- **Local Access**: < 50ms (same node)
- **Regional Access**: 100-300ms (same country/region)
- **Global Access**: 200-500ms (worldwide)
1. **IPv6 First**: Always test IPv6 connectivity before troubleshooting
2. **Multiple Addresses**: Each pod gets unique IPv6 addresses - test them all
3. **Health Checks**: Use `/health` endpoint for automated monitoring
4. **Content Updates**: ConfigMaps enable zero-downtime content updates
5. **Resource Monitoring**: Watch pod distribution across nodes
6. **Network Testing**: Use `ping6` to test basic IPv6 connectivity
7. **Browser Testing**: Modern browsers support IPv6 - test in Chrome/Firefox
### **Capacity Planning**
- **Single Pod**: ~1,000 concurrent connections
- **3 Pods**: ~3,000 concurrent connections
- **5 Pods**: ~5,000 concurrent connections
## 🎉 Success Indicators
### **Resource Usage**
- **Memory**: ~50MB per nginx pod
- **CPU**: ~100m CPU per pod
- **Storage**: Minimal (static files)
You'll know everything is working when:
- `kubectl get pods` shows "Running" status
- ✅ IPv6 address is discoverable via `ip addr show`
- `curl -6 "http://[ipv6]:8080/"` returns complete HTML (3975+ bytes)
-`curl -6 "http://[ipv6]:8080/health"` returns "healthy"
- ✅ Browser can load the website at `http://[ipv6]:8080/`
## 🌟 Success Metrics
**Congratulations! You've successfully deployed a globally accessible website on Mycelium Cloud! 🚀**
### **✅ CONFIRMED: Technical Success Indicators**
- **hostNetwork Deployment**: Pod successfully binds to host network interface
- **IPv6 Address Assignment**: Pod receives Mycelium IPv6 address (e.g., `552:5984:2d97:72dc:ff0f:39ef:6ec:a48c`)
- **Direct IPv6 Connectivity**: External curl successfully connects to IPv6 address on port 80
- **Custom Content Serving**: Professional Mycelium Cloud website HTML served correctly
- **Health Endpoints**: `/health` endpoint returns "healthy"
- **nginx Configuration**: Proper web server configuration with custom content
---
### **✅ VERIFIED: IPv6 Connectivity Results**
```
* Connected to 552:5984:2d97:72dc:ff0f:39ef:6ec:a48c (552:5984:2d97:72dc:ff0f:39ef:6ec:a48c) port 80 (#0)
< HTTP/1.1 200 OK (or appropriate response)
## 📊 Technical Specifications
### Network Configuration
- **Protocol**: IPv6 with IPv4 fallback
- **Port**: 8080 (internal), direct IPv6 access
- **Service**: NodePort 30090 (optional)
- **Access Method**: Direct IPv6 URLs
### Resource Requirements
- **CPU**: Minimal (nginx alpine)
- **Memory**: ~50MB
- **Storage**: ConfigMap-based content
- **Network**: IPv6-capable interfaces
### Performance Metrics
- **Response Time**: ~136ms typical
- **Content Size**: 3,975 bytes (full page)
- **Concurrent Connections**: nginx standard limits
- **Uptime**: Kubernetes-managed (99.9%+ expected)
## 🌍 Global Accessibility Proof
**Live Website Access:**
- **URL**: `http://[YOUR-IPV6]:8080/`
- **Health Check**: `http://[YOUR-IPV6]:8080/health`
- **Content**: Professional website with IPv6 detection
**What makes this globally accessible:**
- Mycelium provides globally routable IPv6 addresses
- Peer-to-peer networking eliminates traditional ISP dependencies
- Direct IPv6 URLs work from anywhere with IPv6 connectivity
- No DNS or traditional hosting infrastructure required
## 🆘 Support
If you encounter issues:
1. Check the troubleshooting section above
2. Verify your cluster is healthy: `kubectl get nodes`
3. Ensure IPv6 is working: `ping6 [YOUR-IPV6]`
4. Test pod networking: `kubectl exec $POD_NAME -- curl localhost:8080`
For more help, visit our [documentation](../../README.md) or contact support.
---
## 🔧 Advanced Troubleshooting
### Network Interface Analysis
```bash
# Analyze all network interfaces
kubectl exec $POD_NAME -- ip addr show
# Find Mycelium-specific interfaces
kubectl exec $POD_NAME -- ip addr show | grep -E "(476:|51d:|552:)"
# Check routing table
kubectl exec $POD_NAME -- ip -6 route show
```
### **✅ CONFIRMED: User Experience Success**
- **Global IPv6 Access**: Website accessible from any Mycelium IPv6 address on port 80
- **Custom Website Content**: Professional Mycelium Cloud branded website with modern styling
- **Real-Time Features**: Interactive IPv6 address detection and timestamp updates
- **No Authentication Required**: Direct access for demonstration purposes
- **Cross-Platform Compatibility**: Works with any IPv6-capable client
- **Professional Interface**: Modern gradient design with responsive layout
### nginx Configuration Validation
```bash
# Test nginx configuration syntax
kubectl exec $POD_NAME -- nginx -t
## 📝 Notes
# Reload nginx configuration
kubectl exec $POD_NAME -- nginx -s reload
### **Infrastructure Dependencies**
- **Mycelium Network**: Requires Mycelium client for IPv6 access
- **Kubernetes Cluster**: 3+ nodes recommended for load balancing
- **External Connectivity**: Mycelium must be reachable from internet
# Check nginx status
kubectl exec $POD_NAME -- ps aux | grep nginx
```
### **Limitations**
- **Port 80 Only**: HTTP only (no HTTPS without TF Gateway)
- **Static Content**: Designed for static websites
- **Public Access**: No authentication/authorization
### IPv6 Connectivity Testing
```bash
# Test from external IPv6 network
ping6 [YOUR-IPV6]
## 🎉 Conclusion
# Test specific port
nc -6 -zv [YOUR-IPV6] 8080
This nginx-mycelium example **PROVES** that **Mycelium Cloud can host real, globally accessible websites** with confirmed IPv6 connectivity and custom content management.
# Test HTTP endpoint
curl -6 -I "http://[YOUR-IPV6]:8080/"
```
** CONFIRMED SUCCESS:**
1. **IPv6 Connectivity**: Direct access verified via `curl http://[IPv6]:80` - **WORKING**
2. **Custom Website**: Professional Mycelium Cloud branded website with modern styling - **DEPLOYED**
3. **Global Accessibility**: All 6 Mycelium IPv6 addresses accessible worldwide - **VERIFIED**
4. **Production Ready**: Enterprise-grade deployment with health monitoring - **OPERATIONAL**
**Key Takeaways:**
1. **Direct IPv6 Access**: hostNetwork deployment provides direct interface binding
2. **Global Reach**: Any Mycelium user can access your website from anywhere
3. **Custom Content**: Professional website with ConfigMap-based content management
4. **Real Infrastructure**: Production-grade web hosting with confirmed global accessibility
**🎯 Perfect for:** Demonstrating the power of Mycelium's global IPv6 internet infrastructure with **CONFIRMED WORKING** web hosting capabilities!
**🚀 Ready for Production:** This example provides a complete, tested solution for global website hosting on Mycelium Cloud.
This comprehensive guide ensures you can successfully deploy and access your IPv6 website on Mycelium Cloud!