-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scripts: easy tool to quick setup the cluster from zero #163
Conversation
May I know why use Python to organize such scripts? Since we have "tools" directory also in this repo which hosts shell scripts there. |
Tools for the cnap related shell scripts, and this is used to setup k8s quick on a Using python can brings more feature and flexiblities to it. Maybe cross platform bulabula.. Of course, if we don't need this to setup k8s, i can move it to other repo or location. :) |
Yeah, what I am thinking is just about where to put such deployment related scripts, since our current demo repo is not really open sourced in public, but for real open source project, deployment related scripts are usually in Shell/Ansible/helm(yaml), etc. |
what do yout think a directory |
Signed-off-by: Le Yao <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current directory LGTM.
Since we have involved KEDA/Kepler in this project scope in README.md, I will raise PR to include the Kepler deployment later on top of your work:)
How about KEDA then? Maybe KEDA/Kepler scripts could be placed under tools/integration?
We have keda scable job for cnap yet, and for keda installation, we deliver the document under ./docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks
This PR introduces an orchestrated procedure to setup a host machine and initialize or join a Kubernetes cluster. The script is designed to ensure host readiness, disable swap, configure kernel parameters, install necessary prerequisites like Docker and Kubernetes packages, setup Containerd, initialize or join the cluster, and optionally setup a Container Network Interface (CNI) plugin.