github/containerd
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

Clarify text on ctr support/inclusion

Browse Source 
Add some clarifying language around the expectations on `ctr`.

Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com>
This commit is contained in:
Phil Estes 2019-08-07 14:35:17 -04:00
parent 2ff1ef4f6c
commit 0bc5df0354
No known key found for this signature in database
GPG Key ID: 0F386284C03A1162
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
RELEASES.md
View File

@ -271,10 +271,15 @@ version of Kubernetes which supports that version of CRI.
### `ctr` tool ### `ctr` tool
The `ctr` tool provides the ability to introspect and understand the containerd The `ctr` tool provides the ability to introspect and understand the containerd
API. At this time, it is not considered a primary offering of the project. It API. It is not considered a primary offering of the project and is unsupported in
may be completely refactored or have breaking changes in _minor_ releases. that sense. While we understand it's value as a debug tool, it may be completely
refactored or have breaking changes in _minor_ releases.
We will try not break the tool in _patch_ releases. Targeting `ctr` for feature additions reflects a misunderstanding of the containerd
architecture. Feature addition should focus on the client Go API and additions to
`ctr` may or may not be accepted at the discretion of the maintainers.
We will do our best to not break compatibility in the tool in _patch_ releases.
### Daemon Configuration ### Daemon Configuration