specs-go: mark LinuxMemory.Kernel as deprecated#1233
specs-go: mark LinuxMemory.Kernel as deprecated#1233hqhq merged 1 commit intoopencontainers:mainfrom
Conversation
Support for kernel-memory limits was deprecated in the kernel, and documented as "NOT RECOMMENDED" (or "SHOULD NOT" use) in v1.1.0-rc.1 through commit f02cd4a. This patch marks the field as deprecated in the go implementation of the spec, so that linters and editors produces a warning and consumers get notified of its status. Signed-off-by: Sebastiaan van Stijn <[email protected]>
thaJeztah
requested review from
AkihiroSuda,
crosbymichael,
cyphar,
dqminh,
giuseppe,
hqhq,
kolyshkin,
mrunalp,
tianon,
utam0k and
vbatts
as code owners
|
FWIW I did not (yet) update the KernelTCP field, as there was some discussion about KernelTCP on the linked PR; https://github.com/opencontainers/runtime-spec/pull/1093/files#r589703045, as well as opencontainers/runc#3174 (comment)
|
|
If people have suggestions for the |
4 participants
Support for kernel-memory limits was deprecated in the kernel, and documented as "NOT RECOMMENDED" (or "SHOULD NOT" use) in v1.1.0-rc.1 through commit f02cd4a.
This patch marks the field as deprecated in the go implementation of the spec, so that linters and editors produces a warning and consumers get notified of its status.