Skip to content

Updates for coco 1.1#408

Open
a-mccarthy wants to merge 4 commits into
NVIDIA:mainfrom
a-mccarthy:coco-1.1
Open

Updates for coco 1.1#408
a-mccarthy wants to merge 4 commits into
NVIDIA:mainfrom
a-mccarthy:coco-1.1

Conversation

@a-mccarthy
Copy link
Copy Markdown
Collaborator

No description provided.

Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
@a-mccarthy a-mccarthy self-assigned this May 22, 2026
@github-actions
Copy link
Copy Markdown

Documentation preview

https://nvidia.github.io/cloud-native-docs/review/pr-408

Comment thread confidential-containers/release-notes.rst Outdated
* A Kubernetes cluster with cluster administrator privileges.
Refer to the :ref:`Supported Software Components <coco-supported-software-components>` table for supported Kubernetes versions.

* containerd version 2.2.2 installed.
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.

Just for me to understand - why are we removing this here? Maybe I don't have the complete oversight right now, and this is listed somewhere else?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

we list it in the platform support page. We added it b/c there was a hard requirement for 2.2.2 being installed. In this release we now support 2.3.

Do you still think it is valuable to call this out to folks here as well as in the support matrix?

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.

might be a bit confusing. yes, we list containerd in the support matrix but we also list QEMU. While QEMU comes from kata-deploy, containerd doesn't ... so users still need to ensure they have containerd running. Maybe we can collapse this into the prior point about 'A Kubernetes cluster with cluster administrator privileges" => to something like:
"A Kubernetes cluster with cluster administrator privileges using containerd on the nodes", "Refer to the ... table for supported Kubernetes and containerd versions"?

@fidencio thoughts?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I think we should keep the note about containerd as we know from past experiences that people tend to just ignore when it's not that explicit.

Copy link
Copy Markdown
Contributor

@manuelh-dev manuelh-dev left a comment

Choose a reason for hiding this comment

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

LGTM with 2 minor aspects to discuss

Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Copy link
Copy Markdown

@fidencio fidencio left a comment

Choose a reason for hiding this comment

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

lgtm, thanks @a-mccarthy!

EDITED: Just noticed a few things to change.

- 10.1 \+ Patches
* - `Containerd <https://github.com/containerd/containerd>`__
- 2.2.2
- 2.2.2 or 2.3.x
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

should we do a 2.2.2+ or 2.3.x ?

@@ -297,7 +297,6 @@ The minimum required version is 3.29.0.
$ helm install kata-deploy "${CHART}" \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We need to pass that added values.yaml here.

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.

+1 ... apart from the currently open comments, this PR LGTM

@fidencio fidencio self-requested a review May 27, 2026 18:58
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.

3 participants