# Managing IP addresses of Kubernetes worker nodes

**URL:** <https://forum.scylladb.com/t/managing-ip-addresses-of-kubernetes-worker-nodes/1256>\
**Category:** Kubernetes Operator\
**Tags:** open-source\
**Created:** [January 30, 2024, 5:51pm UTC](https://forum.scylladb.com/t/managing-ip-addresses-of-kubernetes-worker-nodes/1256 "2024-01-30T17:51:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![akocic](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/akocic/32/630_2.png) [@akocic](https://forum.scylladb.com/u/akocic)\
**Post date:** [January 30, 2024, 5:51pm UTC](https://forum.scylladb.com/t/managing-ip-addresses-of-kubernetes-worker-nodes/1256/1 "2024-01-30T17:51:04Z")

</div>

Could you please explain how to manage changes in the IP addresses of Kubernetes worker nodes? The monitoring stack, connectors, and other clients rely on these IPs, but they need to be updated every time the node pool undergoes maintenance.

---

<div class="post-metadata">

**Author:** ![tnozicka](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/tnozicka/32/506_2.png) [@tnozicka](https://forum.scylladb.com/u/tnozicka)\
**Post date:** [January 30, 2024, 7:08pm UTC](https://forum.scylladb.com/t/managing-ip-addresses-of-kubernetes-worker-nodes/1256/2 "2024-01-30T19:08:16Z")

</div>

With hostNetworking and ephemeral IP addresses, you need a script when your client starts that scrapes those from the kubernetes API. I’d recommend not using hostNetworking mode though.

With Service IPs, or Pod IPs this becomes more managable to scrape, but even better is to use the IP for service `<scyllacluster_name>-client` that proxies to all nodes, and the client will discover the other nodes on its own.

---

<div class="post-metadata">

**Author:** ![akocic](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/akocic/32/630_2.png) [@akocic](https://forum.scylladb.com/u/akocic)\
**Post date:** [January 30, 2024, 10:26pm UTC](https://forum.scylladb.com/t/managing-ip-addresses-of-kubernetes-worker-nodes/1256/3 "2024-01-30T22:26:59Z")

</div>

Thanks. How is this service configured and can it be exposed as load balancer?

I found the [documentation](https://operator.docs.scylladb.com/stable/exposing.html#) about exposing ScyllaCluster, but the client service is not mentioned.