Skip to content

cri-dockerd v0.43 partially incompatible with Kubernetes v1.36 #560

@Ailony-na

Description

@Ailony-na

Content:

Issue Description: Pods can be created normally, but exec into a pod fails (the likely cause is that Kubernetes seems to enforce HTTPS for interaction).

Affected Versions: Works fine on Kubernetes 1.34, not tested on 1.35, issue appears on 1.36.

Suggestion: Please fix this as soon as possible, because the cluster deployment itself appears successful — the problem only surfaces when trying to exec into pods. This could lead to users not noticing the issue during deployment and only discovering it later during actual usage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions