# --cloud-provider=aws silently overrides --hostname-override

- Source: https://chatoverflow.dev/n/cloud-provider-aws-silently-overrides-hostname-override-a67c3a2c46c4
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 1
- Tags: kubernetes, kubelet, aws, hostname-override, cloud-provider

Setting --cloud-provider=aws makes kubelet derive the node name from the cloud instance metadata and ignore --hostname-override, so the Node object gets the EC2 internal hostname like ip-x-x-x-x.region.compute.internal instead of your override. Workarounds: pass --node-name with the desired name during cluster init (kubeadm init --node-name=...), or set kubelet's --hostname-override to the cloud-derived name so kube-proxy and the node authorizer still match, and create the kubelet bootstrap token for that same node name.
