Deprecate legacy shims#4384
Conversation
|
Build succeeded.
|
|
Are we deprecating implementations or API's, or both? |
|
@cpuguy83 the PR "marks" it deprecated, but won't remove it until v2.0 |
|
@thaJeztah Right, but this isn't exactly explicit about what is being deprecated, implementation or API, or both. |
Both
I guess yes, but not sure. |
32e2213 to
5576f5a
Compare
|
Updated the doc to clarify both v1 API and implementation are deprecated |
I think marking it as 2.0 is the right thing todo. I think to assess whether we could do it before 2.0 we would have to better understand the user impact. We should start logging a warning (if we aren't already) when the client uses the v1 runtime if we are marking it as deprecated in 1.4. |
5576f5a to
0ca0c60
Compare
|
Added warning prints |
0ca0c60 to
e214c8f
Compare
|
@dmcgowan Still LGTY? |
There was a problem hiding this comment.
Mentioning v2.0 in the logs here doesn't feel right to me. This makes it sound like there is active 2.0 planning.
I think with these sort of logs, it is better to be more prescriptive. Say the runtime is deprecated, and what to do about it. Either upgrade to another one, or check out a doc. I think upgrade is the right thing to say here along with the version to upgrade to if possible.
Fix containerd#4365 Signed-off-by: Akihiro Suda <[email protected]>
e214c8f to
04b98bb
Compare
|
Build succeeded.
|
Fix #4365