Skip to content

feat: Update CoCo pattern docs for v4 GA (Trustee 1.0, OSC 1.11)#645

Open
butler54 wants to merge 1 commit intovalidatedpatterns:mainfrom
butler54:coco-100-update
Open

feat: Update CoCo pattern docs for v4 GA (Trustee 1.0, OSC 1.11)#645
butler54 wants to merge 1 commit intovalidatedpatterns:mainfrom
butler54:coco-100-update

Conversation

@butler54
Copy link
Copy Markdown
Contributor

Summary

  • Update confidential containers (CoCo) pattern documentation for v4 GA release
  • Upgrade component versions: Trustee 1.0, OpenShift Sandboxed Containers (OSC) 1.11, OCP 4.17+
  • Add multi-cluster deployment support with ACM/MultiClusterHub
  • Add new tested environments and version history page (coco-pattern-tested-environments.adoc)
  • Update Azure requirements with terminology and guidance fixes
  • Add missing technical terms to spellcheck wordlist

Test plan

  • Super-linter (slim-v7) passes locally — all GITLEAKS checks pass
  • Spellcheck passes for all CoCo pattern files with updated wordlist
  • CI super-linter (v8) passes on GitHub

🤖 Generated with Claude Code

Update confidential containers pattern documentation for the v4 GA release:
- Upgrade component versions: Trustee 1.0, OSC 1.11, OCP 4.17+
- Add multi-cluster deployment support with ACM/MCH
- Add new tested environments and version history page
- Update Azure requirements with terminology and guidance fixes
- Add missing technical terms to spellcheck wordlist

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@ocpdocs-previewbot
Copy link
Copy Markdown

🤖 Thu Feb 19 07:05:29 - The preview is ready at:
https://645--patternsdocs-pr.netlify.app

@gaurav-nelson
Copy link
Copy Markdown
Collaborator

@butler54 Thank you for your PR.

  1. Is this ready for review and merge?

@beraldoleal
Copy link
Copy Markdown

@butler54 is there a way to see the preview? The link is broken.

Copy link
Copy Markdown

@beraldoleal beraldoleal left a comment

Choose a reason for hiding this comment

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

LGTM, just minor comments.

- `oc exec -n hello-openshift -it insecure-policy -- bash` to get a shell into a confidential container

- https://github.com/validatedpatterns/coco-pattern/blob/main/charts/hub/trustee/templates/kbs.yaml[Trustee's configuration] specifies the list of secrets which the KBS can access with the `kbsSecretResources` attribute.
- https://github.com/butler54/trustee-chart[Trustee's configuration] specifies the list of secrets which the KBS can access with the `kbsSecretResources` attribute. These are mapped to Vault paths (e.g. `secret/data/hub/kbsres1`).
Copy link
Copy Markdown

Choose a reason for hiding this comment

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



This pattern uses https://docs.redhat.com/en/documentation/openshift_sandboxed_containers/1.7/html/user_guide/deploying-on-azure#deploying-cc_azure-cc[Red Hat OpenShift sandbox containers] to deploy and configure confidential containers on Microsoft Azure.
This pattern uses https://docs.redhat.com/en/documentation/openshift_sandboxed_containers/1.11/html/deploying_confidential_containers/cc-overview[Red Hat OpenShift sandbox containers] to deploy and configure confidential containers on Microsoft Azure. On Azure, confidential containers run as "peer pods" — VMs from the `Standard_DCas_v5` family provisioned directly on the Azure hypervisor rather than nested inside OpenShift worker nodes.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

s/sandbox/Sandboxed/g

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants