Hercules

joined 2 years ago
[–] Hercules@lemmy.world 3 points 2 days ago (1 children)

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

Thank you for your help!

[–] Hercules@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (4 children)

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.

 

Hello,

Im planning on running a postgresql server on my k3s cluster using the bitnami/postgresql helmchart & container image. I already set it up for testing and it works really well.

But since newer versions of immich are moving to VectorChord I would like to install this extention so i can move my immich database to this postgresql server.

I already tried to search how i should/could install an extention in the bitnami/postgresql image but I haven't found something usefull to me. Im not a postgresql expert so maybe i missed some stuff :).

Does someone have experience with this or know in which direction i should like i would greatly appreciate it.

Thanks for your time and have a wonderfull day!

EDIT: Could someone explain me why im getting downvotes for this post? Is the way i wrote it not good? Is it a bad question? Is the software i mentioned unpopular?

[–] Hercules@lemmy.world 1 points 1 week ago (1 children)

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?

[–] Hercules@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (3 children)

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 :)

[–] Hercules@lemmy.world 1 points 1 week ago

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

[–] Hercules@lemmy.world 2 points 1 week ago

Oh alright, thanks for explaining!

[–] Hercules@lemmy.world 2 points 1 week ago (2 children)

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

[–] Hercules@lemmy.world 1 points 1 week ago

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

[–] Hercules@lemmy.world 2 points 1 week ago

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

[–] Hercules@lemmy.world 1 points 1 week ago* (last edited 1 week ago) (3 children)

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?

6
submitted 1 week ago* (last edited 1 week ago) by Hercules@lemmy.world to c/selfhosted@lemmy.world
 

Hello,

I have a little homelab that contains a 3 node k3s cluster which im pretty happy about but i got some questions regarding ingress.

Right now i use nginx as ingress controller and i have the IP of one of the nodes defined under externalIPs. All the nodes are behind the router my ISP gave me so this is nothing special, in this router i configured it to forward port 443 to port 443 of that ip. This all works as excpected im able to access the ingress resources that i want.

But i wanna make some improvements to this setup and im honestly not really sure how i could implement this.

  1. Highly available ingress. When the node which contains the IP of the ingress controller goes down im unable to reach my clusters ingress since my router cant forward the traffic. Whats the best way to configure all 3 nodes to be able to receive ingress traffic? (If needed im able to put it behind something like openwrt or opnsense but not sure if this is needed)
  2. Some ingres resources i only want to expose on my local network. I read online that i can use nginx.ingress.kubernetes.io/whitelist-source-range: 192.168.0.0/24 but this doesn't work i think because since the ingress doesn't receive the clients actual ip rather it receives an internal k3s ip. Or is their another way to only allow certain ips to access an ingress resource?

Could someone point my in the right direction for these improvements i wanna make? If you need more information you can always ask!

Thanks for your time and have a great day!

 

Hello, Im trying to host a backup solution on my k8s cluster for my linux and windows clients. I would like it to use https so its easy to manage ingress. Does someone have any recommendations? thanks

EDIT: a requirement i forgot is that it is meant for multiple users but idk if thats possible