Oh alright, thanks a lot for your explanation. I learned a lot, im going with the operator route!

Thank you for your help!

Thanks for your response, could you explain what the advantages of an operator are in this example?

And what is the matter with the licensing? I never heard this issue before.

The link that you attached looks like it is for the pgvecto.rs extention instead of vectorchord.

Ceph is really cool, i also wanna use it in the future but i need way more disks for that :). Are those 25 worker nodes virtual machines? How did you attatch the disks to the ceph nodes?

Im not using any hypervisor (yet), but in the feature im probably going to look at proxmox.

Never heard of cloudstack before but what i just read and what you described sounds really intresting!

27 nodes in 12 minutes sounds insane :)

Other people also recommanded this to me, i will take a look at it! Thanks!!!

Oh alright, thanks for explaining!

And does this work for ingress? I searched a little bit around but as far as i understand metallb is for k8s services?

Thanks for your reply, i havent look into metallb before but i will try it out!

Currently I only will need to use it for k8s so kube-vip will do the job for now.

Thanks for your response!

I haven’t used keepalived or haproxy before, but i quickly took a look at it. Do you mean i should setup 2 new vms which run keepalived an ha proxy?

While looking at keepalived i remembered reading about kube-vip https://kube-vip.io/. Couldnt this also help me with the issue? Since this also uses a vip and 1 node gets elected and its able to inform the network which node this is?