Comments (4)
I'm thinking we punt on this for now until it becomes "well tested"
It seems risky and we have many other moving parts. Also, removing the kubelet from the bucket of "system things" doesn't empty the bucket. We still have docker and the kernel so the advantages are small.
OpenStack has a mandate to support a seamless upgrade and side-by-side running of N-1 and N to support upgrading the core components followed by agents on what may be thousands of hosts. What is the equivalent Kubernetes claim to support upgrading Kubernetes core components, followed by rolling kubelet updates? At what point is the gap too large?
from poc-topsail.
The idea here could be to update the self-hosted kubelet via kubernetes primitives, and maybe even update the system-kubelet via this mechanism. The gap for the system-kubelet shouldn't get too wide, that's for sure.
In the end this doesn't free us from providing a path for infrastructure updates, but what's the majority of these updates? Is it kernel, os, libs, docker, kubelet? It could be a benefit to have a "speedway" to rollout kubelet updates.
from poc-topsail.
Love the conversation --
The containerized kubelet is definitely maturing.
Base images like CoreOS, Ubuntu Core, Project Atomic, Photon, and ContainerOS manage those 'system level' updates for you automatically.
The reason CoreOS encourages HA clusters is because any 1 node is supposed to be able to go down.
CoreOS's and ContainerOS do an active-passive upgrade for the kernel & etc.
Atomic uses rpm-os-tree which is sort of git-like.
Do you guys know anybody who has traction using this stuff?
from poc-topsail.
@stealthybox we've actually looked into CoreOS and Atomic, and they are considerations if/when we can get past the dependency for OS-level requirements for Ceph (this is a requirement for our openstack-helm repository). CoreOS' locksmith+etcd feature is extremely useful for auto-draining hosts during kernel-level upgrades, etc. i'm not sure I understand your question though on "who has traction on using" these things. for our part, this is part of our internal roadmap, but we are working directly with those vendors and the community to gauge and document these general use-cases. docs are going to be spread across several repos within the https://www.github.com/att-comdev namespace. but again, these are all side/parallel tasks in an effort to build a stable underlay for our much larger effort: openstack-helm. this repo just happened to be an open PoC, so community discussions and input are very welcome. 👍
from poc-topsail.
Related Issues (5)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from poc-topsail.