Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
a
abundant-hair-58573
01/19/2023, 3:13 PMI enabled the aws cloud provider in my rke1 cluster, but it doesn't appear to be happy with my host names. Our host names follow the format of ip-xxx-xxx-xxx-xxx, apparently the k8s cloud-provider is looking for the format ip-xxx-xxx-xxx-xxx.region.compute.internal. This left the cluster in a weird state with new control plane and etcd nodes in rancher that don't resolve. Has anyone run into this before?
I was able to recover this by removing the cloud provider section of the cluster.yml, rebooting one of the control planes, and then deleting the "new" etcd and control plane nodes from Rancher. There were duplicates, one of ip-xxx-xxx-xxx and one of ip-xxx-xxx-xxx-xxx.region.compute.internal, I deleted the latter. After about 10 minutes the control plane and etcd nodes cleared up.
I would still like to get the cloud provider working, it seems like my only option is to change the host names of all the of the nodes to the correct format? Is that possible to do in a running cluster?