Troubleshooting
Common issues and how to resolve them when using the KloudMate Agent.
Reporting Issues
Before creating an issue, please:
- Check existing issues
- Provide detailed reproduction steps
- Include environment information (K8s version, VM host info, OS, etc.)
Getting Help
- Email: support@kloudmate.com
- Issues β Bug reports and feature requests
- Documentation
Community Resources
Common Issues
Agent Not Starting
- Verify the
KM_API_KEYis correctly set. - Ensure the
KM_COLLECTOR_ENDPOINTis reachable from the host. - Check system logs for error messages.
Kubernetes Pods Not Scheduling
If agent DaemonSet pods are not scheduling on tainted nodes, ensure you have configured the appropriate tolerations during Helm installation. See the Installation guide for details.
eBPF Features Not Working
- Ensure your Linux kernel version is at least 5.8 (recommended). Some features work on 4.18+.
- Verify the agent has
CAP_SYS_ADMINandCAP_BPFcapabilities. - In Kubernetes, confirm RBAC permissions for Node, Pod, Service, and ReplicaSet viewers.
Configuration Changes Not Taking Effect
Manually updating ConfigMaps is not recommended. Use the KloudMate Agent Config Editor to ensure configurations are synchronized and persisted correctly.