Skip to content

Configure CDI annotation prefixes in toolkit container when CDI is enabled - #3088

Draft
cdesiniotis wants to merge 1 commit into
NVIDIA:mainfrom
cdesiniotis:add-cdi-annotation-prefix-to-toolkit-ctr
Draft

cdesiniotis wants to merge 1 commit into
NVIDIA:mainfrom
cdesiniotis:add-cdi-annotation-prefix-to-toolkit-ctr

Conversation

@cdesiniotis

Copy link
Copy Markdown
Contributor

Description

This aligns the transformToolkitCtrForCDI() method with the transformDevicePluginCtrForCDI() to ensure the same prefixes are configured with both components.

Without explicitly configuring the CDI annotation prefixes in the toolkit container, the nvidia-ctk-installer was NOT adding these annotation prefixes to containerd's (or crio's) container_annotations allowlist. As a consequence, any container annotations set by the k8s-device-plugin, in its AllocateResponse, were not making it into the OCI runtime spec for the container.

Checklist

  • No secrets, sensitive information, or unrelated changes
  • Lint checks passing (make lint)
  • Generated assets in-sync (make validate-generated-assets)
  • Go mod artifacts in-sync (make validate-modules)
  • Test cases are added for new code paths

Testing

…abled

This aligns the transformToolkitCtrForCDI() method with the
transformDevicePluginCtrForCDI() to ensure the same prefixes are
configured with both components.

Without explicitly configuring the CDI annotation prefixes in the
toolkit container, the nvidia-ctk-installer was NOT adding these
annotation prefixes to containerd's (or crio's) container_annotations
allowlist. As a consequence, any container annotations set by the
k8s-device-plugin, in its AllocateResponse, were not making it
into the OCI runtime spec for the container.

Signed-off-by: Christopher Desiniotis <cdesiniotis@nvidia.com>

@tariq1890 tariq1890 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks @cdesiniotis !

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants