- kubectl configured to access your cluster
- Linode API token
- Target region identified
- Generate the manifest:
./deploy/generate-manifest.sh $LINODE_API_TOKEN $REGION
- Review the generated manifest:
The script creates
ccm-linode.yaml
containing:
- ServiceAccount
- ClusterRole and ClusterRoleBinding
- Secret with API token
- DaemonSet for the CCM
- Apply the manifest:
kubectl apply -f ccm-linode.yaml
You can modify the DaemonSet to include custom environment variables:
env:
- name: LINODE_INSTANCE_CACHE_TTL
value: "15"
- name: LINODE_ROUTES_CACHE_TTL_SECONDS
value: "60"
Adjust compute resources as needed:
resources:
requests:
cpu: 100m
memory: 128Mi
limits:
cpu: 200m
memory: 256Mi
To remove the CCM:
kubectl delete -f ccm-linode.yaml