The etcd distributed key/value store is starting to play a key role in the management of fleets of Kubernetes clusters in the enterprise.
Currently an incubation-level project being advanced under the auspices of the Cloud Native Computing Foundation (CNCF), the open source etcd project was originally launched by IBM. Since it became a CNCF, the etcd data store is being more widely employed to provide a single, consistent source of truth about the status of a Kubernetes environment, including all clusters and pods and the application instances within them at any given point in time. The Kubernetes application programming interface (API) server stores each cluster’s state data in etcd, which Kubernetes clusters employ to reconfigure themselves when changes occur.
TiKV is now the latest project to graduate from the Cloud Native Computing Foundation, an initiative that’s meant to help advance Kubernetes and other container technologies.
The Cloud Native Computing Foundation (CNCF) is now hosting an open source distributed transactional key-value database optimized for stateful applications running in a container.
Based on concepts put forward by Google in the form of a Spanner database service it provides as a cloud service, the TiKV database is designed from the ground up to automatically scale out as more compute and storage resources are required by containerized applications.
The annual KubeCon + CloudNativeCon Europe event ran as a virtual conference in August this year, five months later than planned due to the COVID-19 pandemic. Key takeaways included: the cloud native community strives to be inclusive, and it is possible for everyone to contribute in their own way; there is an increasing importance in understanding end-user adoption patterns of technologies; it is essential to recognize and discuss the topics of security, observability, and energy efficiency as more organizations move to the cloud; and the community should always remember (and empathise with) the people, systems, and businesses involved in adopting cloud technologies.
The Kubernetes project has decided the time has come to stop existing in a state of permanent beta.
The decision, included in the Changelog for version 1.19 of the container-wrangling code and explained in a blog post, reflects the fact that Kubernetes offers plenty of REST APIs and they can evolve … or not.
Starting with version 1.19 of Kubernetes, developers will be required to advance APIs that they are developing into a stable state within 9 months. These changes are intended to encourage follow-through on feature development and avoid APIs getting stuck in beta.
The Kubernetes project released the long-anticipated 1.19 iteration of the all-consuming cloud infrastructure platform coming in just a day past its already-delayed target date. The update was notable for both its content and gestation.
After a slightly prolonged development circle, the Kubernetes project has emitted version 1.19 of the system for managing containerised applications.
Today, the Kubernetes team officially released version 1.19 of the most popular open-source container-orchestration system. The 1.19 release boasts 34 enhancements despite the disruption caused by COVID-19. 9 of the enhancements are Alpha enhancements, 15 are in Beta stage, and the remaining 10 are Stable.
The Technical Oversight Committee (TOC) for Kubernetes tomorrow plans to release version 1.19 of the platform that, in addition to adding debugging and storage management tools, brings closure to some capabilities that have been under development for a long time.