Closed Avaar0032 closed 3 years ago
Is there is another thing what must be done except described in manual or ccm does not support k8s 19.3?
@Avaar0032 the node name is expected to match the Linode label: https://github.com/linode/linode-cloud-controller-manager/blob/6e3f585f6e7d5dd4b3e33f2f03792e41a978c77c/cloud/linode/instances.go#L191-L203
Do they match?
li1403-18, li1483-253, and li1800-66 in this case.
if you add LINODE_DEBUG=1
to the environment of the CCM pods, or the command-line argument --linodego-debug=true
you should see the API call including the label filter parameter and any messages received by the Linode API service.
Hello,
Internally we only test up to the current LKE version, which is at 1.18. It would not surprise me that we are behind on updating something. We will work on updating CCM in the near future.
Thanks for the report!
Thanks for reply! We currently testing some database on cluster, when finish i will redeploy ccm with debug argument and test it again.
General:
and coredns stuck in pending state. Is there is another thing what must be done except described in manual or ccm does not support k8s 19.3? kubelet kubectl kubead v 19.3
Bug Reporting
Expected Behavior
ccm pods starting properly & Linode NodeBalancer created on creating service with type LoadBalancer
Actual Behavior
ccm pods started with state Running and errors in log, k8s coredns pods stuck in pending state
Steps to Reproduce the Problem
Environment Specifications
VMs with centos7
Screenshots, Code Blocks, and Logs
Additional Notes
For general help or discussion, join the Kubernetes Slack team channel
#linode
. To sign up, use the Kubernetes Slack inviter.The Linode Community is a great place to get additional support.