Skip to content

fix(gke): remove CAP_ prefix from capability names in TCPXO manifests#428

Merged
yuanchen8911 merged 1 commit intoNVIDIA:mainfrom
yuanchen8911:fix/capability-prefix
Mar 19, 2026
Merged

fix(gke): remove CAP_ prefix from capability names in TCPXO manifests#428
yuanchen8911 merged 1 commit intoNVIDIA:mainfrom
yuanchen8911:fix/capability-prefix

Conversation

@yuanchen8911
Copy link
Copy Markdown
Contributor

Summary

Remove CAP_ prefix from Kubernetes capability names in TCPXO demo manifest and documentation. The Kubernetes API spec expects capability names without the prefix (e.g., NET_ADMIN not CAP_NET_ADMIN).

Files changed:

  • demos/workloads/training/gke-nccl-test-tcpxo.yaml
  • docs/integrator/gke-tcpxo-networking.md

Reference: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container

Test plan

  • Verify TCPXO test works with corrected capability names

@yuanchen8911 yuanchen8911 requested a review from a team as a code owner March 18, 2026 21:33
@yuanchen8911 yuanchen8911 requested a review from mchmarny March 18, 2026 22:00
Kubernetes capability entries should omit the CAP_ prefix per the API
spec. Use NET_ADMIN and NET_BIND_SERVICE instead of CAP_NET_ADMIN and
CAP_NET_BIND_SERVICE.

Signed-off-by: Yuan Chen <yuanchen97@gmail.com>
@yuanchen8911 yuanchen8911 force-pushed the fix/capability-prefix branch from 280e3d7 to 3c05ac3 Compare March 19, 2026 15:22
@yuanchen8911 yuanchen8911 merged commit 437126c into NVIDIA:main Mar 19, 2026
22 checks passed
xdu31 pushed a commit to xdu31/aicr that referenced this pull request Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants