Alibaba is creating their own container platform.
This is the part I hope is Open Sourced.
We enhanced the upstream services from two aspects; we call one the new controller, we call the other one statefulsets. The first thing we do is we introduce a so-called "in-place upgrade," which means if the container images’ only component is getting upgraded in a spec, the controller will not recreate a new pod. Instead, the Kubelet will just restart the pod with the new image, and the pod is kept the same. The benefit of this feature is that in this way, the pod states are preserved; the pod states, including the IP and all the PV configuration, they are all kept the same during the upgrade, and you avoid a lot of unnecessary rescheduling, because you still need to call the scheduler and go through the all the scheduling pods if you want to start a new pod. If you do the in-place upgrade, those offhand can be just eliminated.
This is encouraging news and signals I am on the right track. Companies are seeing:
- That Kubernetes ecosystem offers the ability to create value added abstractions on top of the base structures
- You can create code that in effect lives at the architectural level instead of application level
Links:
https://github.com/alibaba/AliOS-Things
https://www.alibabacloud.com/blog/security-authentication-framework-in-alios-things-umesh_573441
https://github.com/alibaba/AliOS-Things?spm=a2c65.11461447.0.0.475ed1cdv1AXO1
https://www.alibabacloud.com/blog/security-authentication-framework-in-alios-things-umesh_573441
https://github.com/alibaba/AliOS-Things?spm=a2c65.11461447.0.0.475ed1cdv1AXO1
Not open source yet (maybe eventually we be here?)
https://github.com/search?q=org%3Aalibaba+kubernetes&unscoped_q=kubernetes
I asked question on infoQ:
https://www.infoq.com/presentations/alibaba-kubernetes/?itm_source=infoq&itm_campaign=user_page&itm_medium=link#anch170917
No comments:
Post a Comment