kubectl get pods -n kube-system -l app=ccm-linode
kubectl describe pod -n kube-system -l app=ccm-linode
Common causes:
- Invalid API token
- Missing RBAC permissions
- Resource constraints
Check the logs:
kubectl logs -n kube-system -l app=ccm-linode
Common causes:
- API rate limiting
- Network connectivity issues
- Configuration errors
kubectl describe service <service-name>
Check for:
- API token permissions
- NodeBalancer quota limits
- Network configuration
Verify:
- Backend pod health
- Service port configuration
- Health check path configuration
kubectl get nodes --show-labels
Verify:
- CCM node controller logs
- Node annotations
- API permissions
Check:
- Private IP configuration
- VPC/VLAN setup
- Firewall rules
# Get CCM version
kubectl get pods -n kube-system -l app=ccm-linode -o jsonpath='{.items[0].spec.containers[0].image}'
# Check events
kubectl get events -n kube-system
# Get CCM logs with timestamps
kubectl logs -n kube-system -l app=ccm-linode --timestamps
Set the following environment variable in the CCM deployment:
env:
- name: LINODE_DEBUG
value: "1"
If issues persist:
- Join #linode on Kubernetes Slack
- Check GitHub Issues
- Submit a new issue with:
- CCM version
- Kubernetes version
- Relevant logs
- Steps to reproduce