Cluster initialization and/or importation

[alexarnoldy]

Again, I'm still in the beginning stages of working with K3AI so some of this might only be valuable as a view into one person's rookie-mistakes.

It seems like there are four different paths a user could take when it comes to the underlying K8s cluster:

• A cluster that needs to be installed on the same (aka local) system as the K3AI tool is installed.
• A cluster that needs to be installed on one or more hosts (aka remote) that are different from the one where the K3AI tool is installed.
• • This could also encapsulate a cluster where K3AI is installed on one of the cluster nodes.
• An existing cluster that just needs to be referenced via its KUBECONFIG file.
• A cluster that will be deployed via a cloud provider API.

It seems that this could be described with the k3ai init options of:

• --local (no passwordless SSH and/or sudo required)
• --remote (requires passwordless SSH and/or sudo)
• • The config file would require things like node IP's, LB IP, SSH key location and/or contents, etc.
• --import (very minimal config file to contain the KUBECONFIG file location and/or contents)
• --cloud (I haven't touched this yet)

[k3aibot]

I've opened an Issue What will happen now?

So here it is what our super duper bot will do for you 👇

1. Our Super Duper @k3aibot will add some label to your issue to your issue to better track it
2. Second @k3aibot will move the issue into our funnel here (General Funnel Board)[https://github.com/orgs/kf5i/projects/3]
3. One of the K3ai members will be assigned to review your issue and start the real job on it
   Oh one last thing if you like to speed up the entire process let us know what kind of issue is this adding one of these labels (only one per comment)
   👇 👇 👇

• /ena this is needed if your issue require a new feature
• /bug in case you forgot to use the bug template we will take care of it
• /question if it is a Question for us
• /docs if this require us to update/refresh our docs