cockroach-operator VS ansible-role-rke2

On the topic of Postgres, you should look into an operator or Helm chart that can setup common things (like replication and auto-failover), such as Crunchy's Postgres operator, or consider using a "cloud-native" distributed database like CockroachDB (disclaimer: I am a Cockroach Labs employee) which has its own operator as well. Another word of warning, running stateful services, particularly mission critical databases, can require a lot of maintenance work (it's my full-time job), so unless this is for a hobby project, I would highly recommend you look into using a managed database offerring. Every major cloud provider and most database companies have one.

We've been looking into CockroachDB because it has been solid for one of our customers. https://github.com/cockroachdb/cockroach-operator

I've implemented Kubernetes in my company during the last year. It's a great technology. I love it. By now I have 10Nodes, 3 masters and ~35 Namespaces for different applications. I use RKE2 as my kubernetes engine. I've setup the whole cluster via ansible and this module: GitHub - lablabs/ansible-role-rke2: Ansible Role to install RKE2 Kubernetes. My Servers get deployed via terraform. I host everything on hetzner.

I deployed Kubernetes using ansible + lablabs.rke2 role, and used Kube-vip as the virtual IP provider. Now I have a Kubernetes cluster and can create a service with type=LoadBalancer without any problem. However, the IP range that I assigned for load balancing is quite limited, so I want to use ingress instead. But when creating an ingress object, their addresses are the addresses of my 2 worker nodes. Is it possible to assign a virtual IP to distribute traffic to my worker nodes instead? I heard that DNS round-robin isn't very reliable.

Hello, I guess you can use an Ansible RKE2 role to provision your cluster. https://github.com/lablabs/ansible-role-rke2