• 2 Posts
  • 104 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle












  • Apparently this is a new driver which uses the open source headers and Linux kernel modules from nVidia’s proprietary drivers, and it doesn’t borrow very much from nouveau driver because that one has different names for things in their headers due to the clean room reverse engineering aspect of nouveau. Although I am not an expert on this so I could be wrong.




  • Single node k3s is possible and can do what you’re asking but has some overhead (hence your acknowledgment of overkill). One thing i think it gets right and would help here is the reverse proxy service. It’s essentially a single entity with configuration of all of your endpoints in it. It’s managed programmatically so additions or changes are not needed to he done by hand. It sounds like you need a reverse proxy to terminate the TLS then ingress objects defined to route to individual containers/pods. If you try for multiple reverse proxies you will have a bad time managing all of that overhead. I strongly recommend going for a single reverse proxy setup unless you can automate the multiple proxies setup.


  • notfromhere@lemmy.onetoSelfhosted@lemmy.worldCosmos 0.12 major update
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 year ago

    And here I am running a bare metal k3s cluster fully managed by custom ansible playbooks with my templatized custom manifests. I definitely learned a lot going that way. This project looks like it has just about everything covered except high availability or redundancy, but maybe I missed it in the readme. Good work but definitely not for me.