system-upgrade-controller
| system-upgrade-controller | cluster-version-operator | |
|---|---|---|
| 5 | 3 | |
| 644 | 78 | |
| 2.0% | - | |
| 6.6 | 8.6 | |
| 19 days ago | 8 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
system-upgrade-controller
- Updating k3s cluster
-
Is it possible to upgrade a node's kubelet using an operator?
Rancher can do this with https://github.com/rancher/system-upgrade-controller
-
My self-hosting infrastructure, fully automated from empty disk to operating services.
In theory I should use https://github.com/rancher/system-upgrade-controller, but because my homelab is still in active development and I keep nuking it, I never had a chance to upgrade lol
-
My self-hosting infrastructure, fully automated
I'm currently bumping the versions manually, but I plan to automate that with system upgrade controller [1] and Dependabot [2] (or similar)
[1]: https://github.com/rancher/system-upgrade-controller
[2]: https://github.com/dependabot
-
k3s vs microk8s vs k0s and thoughts about their future
Updating k3s is much easier using their system upgrade controller. I've been using it for a year and no hiccups. Runs in cluster, updates automatically depending on what release channel you want to use.
cluster-version-operator
-
New TSE in search of advice!
Try searching Bugzilla "confusing error" site:bugzilla.redhat.com and Github? Some of the information on each of the git repos are super informative. Examples: https://github.com/openshift/ https://github.com/openshift/cluster-version-operator/tree/master/docs/user https://github.com/openshift/enhancements/blob/master/dev-guide/cluster-version-operator/user/update-workflow.md
-
Is it possible to upgrade a node's kubelet using an operator?
Openshift uses https://github.com/openshift/cluster-version-operator
-
Just wrote about the differences between OpenShift and Kubernetes. Tell me what you think?
A really big point that you missed is that OpenShift uses Operators to manage the lifecycle of the cluster. The Operators manage adding and removing nodes, upgrades and updates, and generally keeping things running: https://docs.okd.io/latest/operators/understanding/olm-what-operators-are.html https://cloud.redhat.com/blog/helm-and-operators-on-openshift-part-2 https://docs.okd.io/latest/operators/operator-reference.html https://github.com/openshift/cluster-version-operator
What are some alternatives?
sidero - Sidero Metal is a bare metal provisioning system with support for Kubernetes Cluster API.
cluster-api-provider-azure - Cluster API implementation for Microsoft Azure
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
homelab - Fully automated homelab from empty disk to running services with a single command.
ansible-role-k3s - Ansible role for installing k3s as either a standalone server or HA cluster.
Mayastor - Dynamically provision Stateful Persistent Replicated Cluster-wide Fabric Volumes & Filesystems for Kubernetes that is provisioned from an optimized NVME SPDK backend data storage stack.
traefik - The Cloud Native Application Proxy
Ansible-NAS - Build a full-featured home server or NAS replacement with an Ubuntu box and this playbook.
k3s - Lightweight Kubernetes
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
nas - configuration for my NAS