# K3S in production

**URL:** https://forums.suse.com/t/k3s-in-production/39055
**Category:** k3s, k3OS, and k3d
**Created:** [September 25, 2022, 3:02pm UTC](https://forums.suse.com/t/k3s-in-production/39055 "2022-09-25T15:02:21Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![notech](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/notech/32/9463_2.png) [@notech](https://forums.suse.com/u/notech)
#### Post date: [September 25, 2022, 3:02pm UTC](https://forums.suse.com/t/k3s-in-production/39055/1 "2022-09-25T15:02:21Z")

</div>

Hello,

I’d like to deploy k3s for a production use on managed bare metal servers. But I trying to understand how the LB works in k3s.

kube-vip is assingning the default public ip of server when I run k3s in a standalone server. How it works with 3 worker nodes ? The ingress shoud take one public ip to route all traffic to cluster-ip services, but which IP will be used ?

I plan to use ovh for this setup. Is it possible to use a failover ip to assign this ip to ingress ?

Thanks for your help …