Skip to content
This repository was archived by the owner on Mar 9, 2022. It is now read-only.
This repository was archived by the owner on Mar 9, 2022. It is now read-only.

Use per-pod shim. #1075

@Random-Liu

Description

@Random-Liu

We should start testing per-pod shim introduced by containerd/containerd#3004.

And for containerd 1.3, we should switch to using that for Kubernetes.

We observed memory regression in golang 1.12 kubernetes/kubernetes#74917.
Since we have a per-container containerd-shim now, the overall memory usage is pretty sensitive to golang runtime memory overhead.

Moving to per-pod shim should make this much better.

/cc @crosbymichael FYI

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions