fix(kubernetes): move agent-sandbox to v0.5.4
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 253
Description
https://github.com/kubernetes-sigs/agent-sandbox/releases/tag/v0.5.4
v0.5.4 contains a breaking change to the Suspended condition that we now use after the stop/start functionality in https://github.com/NVIDIA/OpenShell/pull/2653
Also, the release manifest changed from manifest.yaml to sandbox.yaml. We need up update any scripts/docs that refer to this manifest. The manifest name switched in v0.5.2.
v0.5.1 and earlier manifest path (current): https://github.com/kubernetes-sigs/agent-sandbox/releases/download/v0.5.0/manifest.yaml
v0.5.2 and later manifest path (new): https://github.com/kubernetes-sigs/agent-sandbox/releases/download/v0.5.4/sandbox.yaml
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by searching the repository for references to agent-sandbox, v0.5.0, manifest.yaml, and the Suspended condition. Compare those references with the v0.5.4 release information linked in the issue and inspect the stop/start integration introduced by pull request #2653. Done means the version is updated, references use sandbox.yaml where required, and the existing checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100