fharper
commented
3 months ago Thanks for feature request @aemadrid
Just to be sure I understand correctly, cause it seems to be conflicting messaging here.
I'd like to be able to onboard a running (bare) k3s cluster that is running locally or hosted.
Right now, there is no way to use existing Kubernetes cluster for any clouds. I doubt it will be a feature we will add caused kubefirst install multiples things that could conflict with any existing configurations, and it's too risky. What we suggest folks to do in that situation, is to create a new cluster with kubefirst, and once everything is up and running, deploy or transfer what's needed from the previous running one.
I want to try KubeFirst on my own k3s machines. They are beefier than my local machine, and I have several of them available.
This is the part I'm not sure I understood well. Unless you are using managed K3s services, which I don't know exist, creating a K3s cluster is done on any vms you create yourself, so there is no limits on the resources you want to assign to them. Our K3s implementation will only install K3s, and deploy the kubefirst platform. With any other clouds we support, you can choose the type of cluster you want to create; with K3s, you create the VM you want K3s to use.
Does that make sense for the not beef enough problem?
What is your feature idea?
I'd like to be able to onboard a running (bare) k3s cluster that is running locally or hosted. The UI would be nice, but CLI is only fine.
Why is it needed?
I want to try KubeFirst on my own k3s machines. They are beefier than my local machine, and I have several of them available.
Is this missing feature preventing you from using kubefirst?
Code of Conduct