- Deleted vip-setup.yml playbook (Keepalived no longer needed)
- Updated MIKROTIK-VIP-SETUP-CUSTOM.md with corrected MikroTik syntax:
* Fixed path notation: use spaces not slashes (/ip firewall nat not /ip/firewall/nat/)
* Fixed action parameter: use dst-nat not dstnat
* Added web interface alternative for NAT rule configuration
* Added important syntax notes section
- Removed Keepalived documentation from README.md
- Kept MIKROTIK-VIP-SETUP.md as general reference guide
- Updated DNS and external access section to reference MikroTik VIP only
This simplifies the project by removing software-based VIP complexity since
the hardware-based MikroTik VIP provides better performance with no node overhead.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Create vip-setup.yml Ansible playbook for Keepalived-based VIP configuration
- Automatic failover between cluster nodes using VRRP protocol
- Health checks for API server availability
- Single IP address can be used in DNS instead of multiple A records
- Master node holds VIP by default, workers act as backups
Update README.md with comprehensive VIP documentation:
- Add three DNS options (single record, multiple records, VIP)
- Detailed VIP installation and verification steps
- Monitoring and failover testing procedures
- Troubleshooting guide for common VIP issues
- Instructions for disabling VIP if needed
Benefits:
- Single DNS A record pointing to VIP (192.168.30.100)
- Automatic failover with no manual intervention
- Load balancing capability across all nodes
- Transparent to applications
Fix markdown linting issues:
- Add proper blank lines around lists and code blocks
- Use consistent ordered list numbering (all 1.)
- Remove duplicate/extra blank lines
- Ensure proper spacing around headings
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Update nginx-test ingress to include test.zlor.fi domain
- Add comprehensive DNS configuration section to README with:
- DNS A record setup (single and multi-record options)
- Ansible playbook for automated DNS resolver configuration
- Manual DNS configuration instructions
- Ingress verification steps
- Testing procedures and troubleshooting guide
- Instructions for adding additional domains
- Fix markdown linting issues (blank lines, language identifiers, list prefixes)
DNS configuration now supports:
- External domain resolution (test.zlor.fi)
- systemd-resolved integration
- Load balancing across cluster nodes
- Multiple domain support
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Remove 'when: not k3s_binary.stat.exists' condition from k3s-server and
k3s-agent installation tasks to allow in-place upgrades of K3s versions
- Update task names to reflect both install and upgrade functionality
- Add change detection using stdout inspection for better Ansible reporting
Add InfluxDB v2 native dashboard alongside Grafana dashboard:
- Create influxdb/rpi-cluster-dashboard-v2.json for InfluxDB 2.8 compatibility
- Update Grafana dashboard datasource UID from 'influx' to 'influxdb'
- Remove unused disk usage and network traffic panels per user request
Update worker node discovery in compute-blade-agent verification script:
- Fix pattern matching to work with cm4-* node naming convention
- Add support for pi-worker and cb-0* patterns as fallbacks
- Now correctly parses [worker] section from inventory
Update inventory version documentation:
- Add comment explaining how to use 'latest' for auto-updates
- Set version to v1.35.0+k3s1 (updated from v1.34.2+k3s1)
- Add guidance on version format for users
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
michi