Skip to content

Migrate from deprecated CRI v1alpha2 API to v1, prepare for containerd 2.0 #1659

Open
@yvjessestephens

Description

@yvjessestephens

Description

v1.33 of GKE will move to containerd 2.0 which does not support v1alpha2 of the CRI API. Google identified these daemonsets as mounting a volume using a path on which the containerd socket could be reached:

newrelic-logging daemonset

  • /var

nrk8s-kubelet daemonset

  • /
  • /run/containerd/containerd.sock

Merely mounting these paths is not a definitive indicator that v1alpha2 of the CRI API is actually used, it just indicates that these daemonsets potentially use the API and therefore potentially use the deprecated version of the API.
GKE can tell the v1alpha2 API is being called, but it can't tell definitively which workload is calling the API. It's using this path mechanism as a best guess.

See Google's doc about migrating to containerd 2.0 here.

Acceptance Criteria

  • Migrate to v1 of the CRI API
  • OR confirm that v1alpha2 of the CRI API is not used

Design Consideration/Limitations

This will make the nri-bundle chart compatible with an upcoming release of GKE, which is scheduled for late April 2025. See kuberentes release summary here.
GKE will block the upgrade to v1.33 until the v1alpha2 API is no longer in use.

Dependencies

N/A

Additional context

As of newrelic/nri-bundle chart version 5.0.115

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions