-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add support for deploying k3s #682
Conversation
AFAICT those remaining lint failures aren't actually in code I touched in this PR. |
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.
sesdev create k3s --deploy-ses
failed for me with:
master: ++ curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
master: In order to verify checksum, openssl must first be installed.
master: Please install openssl or set VERIFY_CHECKSUM=false in your environment.
master: Failed to install helm
After I added export VERIFY_CHECKSUM=false
into seslib/templates/k3s/provision.sh.j2
the deploy succeeded and the cluster is working.
Great job! Thanks!
Just a note. It might be useful to have the toolbox pod installed during deploy or have a hint message at the end of the deployment :
|
even though they must be fixed |
@tserong btw, the deployment test is still failing how about to fix the repo issues or/and switch to the newer ses version in self test. |
@trociny I've updated this to explicitly install @kshtsk I've cherry picked your commits from #683 here to hopefully get a clean jenkins and tox run, but I'm happy to rebase this if you want to merge your PR before merging this one. |
@tserong I gonna try this PR pretty soon |
Looks interesting, could you please rebase and merge. |
This adds `sesdev create k3s`, which by default will deploy a master with four workers on openSUSE Tumbleweed. It will also deploy on SLE 15 SP3 if you specify `--os=sles-15-sp3`. k3s is installed by running `curl https://get.k3s.io`. Helm is also installed on the master, again using `curl`. If you don't want the latest stable k3s, you can install a specific version with the `--k3s-version` option. If you want more or less workers, use `--roles='[master],[worker],[...]`. Signed-off-by: Tim Serong <tserong@suse.com>
This adds the `--deploy-ses` option to `sesdev create k3s`, which will pull registry.suse.com/ses/7.1/charts/rook-ceph, then deploy Rook, which in turn will deploy Ceph, and have it eat all the disks on all the workers. Signed-off-by: Tim Serong <tserong@suse.com>
Signed-off-by: Tim Serong <tserong@suse.com>
When deploying on SLE 15, openssl is already installed as it's a dependency of ca-certificates. This is not true on Tumblweed though, so let's just always install it. Signed-off-by: Tim Serong <tserong@suse.com>
Signed-off-by: Tim Serong <tserong@suse.com>
Rebased |
|
Just wonder why it wasn't failing before rebase, and btw, it is not reproducible on master now. |
This avoids causing confusion by overloading the caasp_deploy_ses setting. Signed-off-by: Tim Serong <tserong@suse.com>
so, gonna merge this? |
Yep :-) |
This does a couple of things:
sesdev
to deploy k3s, just for the sake of having an easy way to create little VM clusters running k3s (think: arbitrary k3s dev/test playground)