Setting cluster-domain has no effect about bottlerocket HOT 2 CLOSED

Thank you for the report.

I tried this on one of my running eks worker nodes. It is running the bottlerocket-aws-k8s-1.29-x86_64-v1.20.2-536d69d0 image. When I used apiclient in the control container to set settings.kubernetes.cluster-domain, I did see the new cluster domain in /etc/resolv.conf on a busybox container (and I did see the new domain in the kubelet configuration file, as well).

Applying the change as I did only affects the EC2 instance where I ran apiclient, but at least I can demonstrate that the setting works as expected inside one instance, so the problem is not with the API server and how the setting populates our kubelet configuration template.

Could you describe how you applied the configuration change? It seems likely that the failure is somewhere along the chain of tools between your configuration input and the worker node.

from bottlerocket.

Thanks for checking larvacea.
We use karpenter for provisioning nodes. I tried setting the cluster domain using the apiclient as you have done and it does change the setting as expected. Might be an issue with Karpenter.

from bottlerocket.