Features deprecated in this release include. The 2.0 release will remove any feature deprecated in 1.x. Add collectible resources to metadata gc ( #6804)Įxisting CRI configurations will be supported until 2.0.Īny functionality split out of CRI will have their configuration migrated to new plugins.ĭeprecated configuration versions and configurations for deprecated features will be removed in 2.0.Add unpack interface for client ( #6749).Migrate off from /gogo/protobuf ( #6841).Remove all gogoproto extensions ( #6829).Remove enumvalue_customname, goproto_enum_prefix and enum_customname ( #6708).Services are being refactored to allow ttrpc implementations, which can be served via shim and accessed using the new sandbox management capability. The version of ttrpc has been updated this release to support streaming, allowing existing grpc services to use ttrpc. The new sandbox and distribution interfaces provide one example of this,īut it also being done for image and network management. Out of the single CRI plugin into smaller-scoped containerd plugins, such that they can be used and tested independently. A major effort in this release and before 2.0 involves moving functionality The CRI plugin is the most complex containerd plugin with a wide range of functionality.
Pull the pin level 7 code#
There are multiple places in the code today which are being targeted for refactoring to make long term support easier and to provide more extension points. Updated to allow the shims to specify the protocol which is supported. Have access to a stable ttrpc library in the implementation language. The gRPC support allows implementation of a wider range of shim implementations which may not Existing ttrpc shim support is not goingĪway and will continue to be recommended for the best performance and lowest shim memory overhead.
The Node Resource Interface is a common framework for plugging extensions into OCI-compatible container runtimes. To allow for further plugin development and integration into existing plugins. Pull and push operations to be done in containerd whether requested from clients or plugins. The transfer service provides a simple interface to transfer artifact objects between any source and destination. CRI Sandbox API Implementation ( #7228).This API makes it easier to manage these groups of containers at a higher level and offers new extension points for shim implementations and clients. The sandbox API provides a new way of managing containerd's shim, providing more flexibility and functionality for multi-container environments such as Pods and VMs. The previous 1.6 release has also become a long term stable release for users who prefer releases with mostly stability improvements and wish to wait a few releases for new functionality. This release still adheres to our backwards compatibility guarantees and users who do not use or enable new functionality should use this release with the same stability expectations.
Some functionality in this release may be considered experimental or unstable, but will become stable or default in 2.0. This release is the last major release of containerd 1.x before 2.0. The eighth major release of containerd includes new functionality alongside many improvements. Welcome to the v1.7.0 release of containerd! Release Notes containerd/containerd v1.7.0: containerd 1.7.0
This PR contains the following updates: Package
0 kommentar(er)
