Skip to content
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

Rancher: k3s & rke1: Deploy Kubernetes cluster (multimachine) #12200

Merged
merged 2 commits into from
Apr 2, 2021

Conversation

pdostal
Copy link
Member

@pdostal pdostal commented Mar 29, 2021

Rancher maintains 2 Kubernetes distribution, both production grade:

  • k3s: Single binary containing containerd backend. Can be run as
    server or agent on each node of cluster. SQLite is used by default
    instead of ETCD. MySQL and Postgres also supported.
    No prerequisity. Intended for edge computing.
  • RKE: Deployed remotely over SSH on top of Docker which is the only
    required component of the underlying OS. Standard ETCD database
    in container. Each node and its roles are defined in YAML.
    Resource hungry, datacenter grade.

Each scenario needs:

  1. Support Server: As Internet gateway, DHCP and DNS server.
  2. Master node for the control node and it's database
  3. ‎4. Worker nodes joining the cluster.

TO-DO:

  • Run more tests on top of the Kubernetes cluster.
  • Implement the same for rke2 (not in production yet).

Verification runs:

Resources:

This project was inspired by the awesome SUSE @Home workshop.
This was done as HackWeek 20 project.

As the DNSSEC needs keys and those are rotating, it's better to avoid possible issues by disabling this locally.
Note that requests for foreign addresses can be still validated by our upstream DNS server where we forward those.
Copy link
Contributor

@ilausuch ilausuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, Good job!
Please, could you share a link for a test job?

@pdostal
Copy link
Member Author

pdostal commented Mar 30, 2021

Great, Good job!
Please, could you share a link for a test job?

Thank you Ivan :) Verification runs are in the description of this pull request.

@pdostal pdostal force-pushed the k3s_rke1 branch 2 times, most recently from e936c30 to 2e44acf Compare March 30, 2021 09:44
Copy link
Member

@asmorodskyi asmorodskyi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

tests/rancher/rancher_supportserver.pm Outdated Show resolved Hide resolved
Rancher maintains 2 Kubernetes distribution, both production grade:
 * k3s: Single binary containing containerd backend. Can be run as
   server or agent on each node of cluster. SQLite is used by default
   instead of ETCD. MySQL and Postgres also supported.
   No prerequisity. Intended for edge computing.
 * RKE: Deployed remotely over SSH on top of Docker which is the only
   required component of the underlying OS. Standard ETCD database
   in container. Each node and its roles are defined in YAML.
   Resource hungry, datacenter grade.

Each scenario needs:
 1) Support Server: As Internet gateway, DHCP and DNS server.
 2) Master node for the control node and it's database
 3) 4) Worker nodes joining the cluster.

TO-DO:
 * Run more tests on top of the Kubernetes cluster.
 * Implement the same for rke2 (not in production yet).

Resources:
 * [k3s webpage]: https://k3s.io/
 * [k3s github repository]: https://github.com/k3s-io/k3s
 * [rke1 github repository]: https://github.com/rancher/rke
 * [rke1 cluster.yaml]: https://rancher.com/docs/rke/latest/en/example-yamls/#minimal-cluster-yml-example
 * [rke1 deploy guide]: https://rancher.com/docs/rke/latest/en/installation/#prepare-the-nodes-for-the-kubernetes-cluster

This project was inspired by the awesome [SUSE @Home] workshop: https://github.com/SUSE/suse-at-home
This was done as [HackWeek 20] project.

https://hackweek.suse.com/20/projects/create-openqa-multimachine-tests-for-deploying-kubernetes-on-tumbleweed-using-both-k3s-and-rke1
Copy link
Contributor

@punkioudi punkioudi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work Pavel!

Copy link
Contributor

@grisu48 grisu48 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@grisu48 grisu48 merged commit a7fffbc into os-autoinst:master Apr 2, 2021
@pdostal pdostal deleted the k3s_rke1 branch December 28, 2022 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
7 participants