Rancher: k3s & rke1: Deploy Kubernetes cluster (multimachine) #12200
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
pdostal
requested review from
Vogtinator,
asmorodskyi,
ge0r,
grisu48,
ilausuch,
jlausuch,
mloviska and
punkioudi
asmorodskyi
reviewed
Mar 29, 2021
asmorodskyi
reviewed
Mar 29, 2021
asmorodskyi
reviewed
Mar 29, 2021
asmorodskyi
reviewed
Mar 29, 2021
ilausuch
reviewed
Mar 29, 2021
ilausuch
reviewed
Mar 29, 2021
Contributor
ilausuch
left a comment
ilausuch
left a comment
There was a problem hiding this comment.
Great, Good job!
Please, could you share a link for a test job?
Member
Author
Thank you Ivan :) Verification runs are in the description of this pull request. |
asmorodskyi
reviewed
Mar 30, 2021
pdostal
force-pushed
the
k3s_rke1
branch
2 times, most recently
from
e936c30 to
2e44acf
Compare
ilausuch
approved these changes
Mar 31, 2021
ge0r
approved these changes
Mar 31, 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). 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rancher maintains 2 Kubernetes distribution, both production grade:
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.
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:
TO-DO:
Verification runs:
Resources:
This project was inspired by the awesome SUSE @Home workshop.
This was done as HackWeek 20 project.