MEmerb·Feb 5, 2020
it would be cool if https://github.com/coreos/container-linux-update-operator would also be part of flatcar.
In End-of-Life Announcement for CoreOS Container Linuxcoreos
container-linux-update-operator
Go2017–2020
coreos / container-linux-update-operator · Archived
container-linux-update-operator
A Kubernetes operator to manage updates of Container Linux by CoreOS
2Distinct people
4Mentions
0Explicit recommenders
207GitHub stars
What to know before exploring
What it is
A Kubernetes operator to manage updates of Container Linux by CoreOS
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month4 dated mentions
Observed mentions: 2017-11-09 20:50:48 UTC to 2020-02-05 21:50:33 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2017 | 2017-11-01 00:00:00 UTC | 2017-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2017 | 2017-12-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2018 | 2018-01-01 00:00:00 UTC | 2018-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2018 | 2018-02-01 00:00:00 UTC | 2018-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2018 | 2018-03-01 00:00:00 UTC | 2018-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2018 | 2018-04-01 00:00:00 UTC | 2018-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2018 | 2018-05-01 00:00:00 UTC | 2018-06-01 00:00:00 UTC | 1 | 0 | 1 |
| Jun 2018 | 2018-06-01 00:00:00 UTC | 2018-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2018 | 2018-07-01 00:00:00 UTC | 2018-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2018 | 2018-08-01 00:00:00 UTC | 2018-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2018 | 2018-09-01 00:00:00 UTC | 2018-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2018 | 2018-10-01 00:00:00 UTC | 2018-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2018 | 2018-11-01 00:00:00 UTC | 2018-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2018 | 2018-12-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2019 | 2019-01-01 00:00:00 UTC | 2019-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2019 | 2019-02-01 00:00:00 UTC | 2019-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2019 | 2019-03-01 00:00:00 UTC | 2019-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2019 | 2019-04-01 00:00:00 UTC | 2019-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2019 | 2019-05-01 00:00:00 UTC | 2019-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2019 | 2019-06-01 00:00:00 UTC | 2019-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2019 | 2019-07-01 00:00:00 UTC | 2019-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2019 | 2019-08-01 00:00:00 UTC | 2019-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2019 | 2019-09-01 00:00:00 UTC | 2019-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2019 | 2019-10-01 00:00:00 UTC | 2019-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2019 | 2019-11-01 00:00:00 UTC | 2019-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2019 | 2019-12-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2020 | 2020-01-01 00:00:00 UTC | 2020-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2020 | 2020-02-01 00:00:00 UTC | 2020-03-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourceswell you actually should be a little bit more familiar with all the concepts of the system to do the stuff.
what do you use to scale your databases:
databases can be scaled with statefulsets there is a good library that helps with that: github.com/zalando/spilo
it is actually way easier than scaling over vms (especially on bare metal) since 1.10 you can even use block storage with local storage, so no need for a storage system.
so basically k8s is just a good layer to scale such things, before we used patroni without k8s and it is way harder to actually do service discovery (more on that later)
what do you use for master election:
master election can be done with configmap or endpoints (actually github.com/zalando/spilo uses github.com/zalando/patroni for running postgresql and does master election over endpoints or configmap annotations)
Read the rest
actually etcd also exists when you use k8s (actually it's the hardest thing to install when you deploy k8s)
what do you use to deploy your stuff:
well deployment/apps are extremly easy to use and do zero downtime deployments when you just change your image version
what do you use on the tcp level for HA (keepalived?):
some folks at google created metallb: https://metallb.universe.tf/ it's actually a load balancer on top of k8s that is so simple to use (just run https://metallb.universe.tf/tutorial/layer2/ and it will work)
what do you use to keep your system up to date:
well that's more tricky however ContainerLinux (formerly CoreOS) (not related to k8s) works very well for keeping the os up to date. you can even use https://github.com/coreos/container-linux-update-operator to only update one node at the time in a k8s env. however it also works without k8s, but you still need to run mostly container software on ContainerLinux.
If you are new to k8s and want to know more about "easy" to use on bare-metal stuff you should look into ContainerLinux ignition and kubeadm, it's really simple to get up and running from scratch, it's mostly just creating a nice cloud-config and run kubeadm once on the nodes you wanna install.
is there an alternative to locksmith? the "automatic" update (https://coreos.com/os/docs/latest/update-strategies.html) and/or https://github.com/coreos/container-linux-update-operator?
basically on coreos I don't need to run "rpm-ostree" to have an updated system. it is actually updated automatically.
In Red Hat to Acquire CoreOSI recently learned about a CoreOS-specific operator for that purpose: https://github.com/coreos/container-linux-update-operator. In standard CoreOS installations, once system updates are installed, the node is automatically rebooted using a semaphore. Instead, this uses the Kubernetes API to drain the pods from the node for a clean shutdown.
Kured has a feature to stop reboots if there are triggered Prometheus alerts; that’s a nice touch.
In Kured – A Kubernetes Reboot Daemon