Add status method to Sandbox Client and also add unit tests associated with it.

[SHRUTI6991]

Description

This PR adds two changes:

1. New status method which returns the SandboxStatus. It internally calls the K8 API to check the status of the Pod.
2. Unit tests associated with the sandbox_client.

Testing Logs

--- Starting Sandbox Client Test (Namespace: default, Port: 8888) ---
Mode: Local Port-Forward fallback

--- Testing Pod Name Discovery ---
Pod name annotation not found, falling back to sandbox name.
--- Pod Name Discovery Test Passed (Fallback) ---

--- Testing Sandbox Status ---
Sandbox status: Running
--- Sandbox Status Test Passed ---

--- Testing Command Execution ---
Executing command: 'echo 'Hello from the sandbox!''
Stdout: Hello from the sandbox!
Stderr: 
Exit Code: 0

--- Command Execution Test Passed! ---

--- Testing File Operations ---
Writing content to 'test.txt'...
Reading content from 'test.txt'...
Read content: 'This is a test file.'

[netlify]

✅ Deploy Preview for agent-sandbox canceled.

Name	Link
🔨 Latest commit	9cecb36
🔍 Latest deploy log	https://app.netlify.com/projects/agent-sandbox/deploys/698caf2e2a66a7000809e25c

[k8s-ci-robot]

Hi @SHRUTI6991. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[SHRUTI6991]

/assign @barney-s

[janetkuo]

/ok-to-test

[janetkuo]

Could we move it outside of status() to reduce overhead?

[janetkuo]

self.claim_name could be None when SandboxClient is initialized with api_url, so it's misleading to report SandboxNotCreated

[SHRUTI6991]

I am curious, wouldn't the __enter__ method initialize the claim_name with a different claim_name if only api_url is provided.

For this PR, I have removed this check and currently only calling the API to report the accurate status.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aditya-shantanu, SHRUTI6991
Once this PR has been reviewed and has the lgtm label, please ask for approval from barney-s. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• clients/python/agentic-sandbox-client/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[vicentefb]

If i'm not mistaken, this PR will be affected by this one #121 , right ?

[SHRUTI6991]

Oh nice, we are exposing the Sandbox status directly. Yes let me hold on to my current PR.

[k8s-ci-robot]

@SHRUTI6991: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
presubmit-test-autogen-up-to-date	9cecb36	link	true	/test presubmit-test-autogen-up-to-date
presubmit-agent-sandbox-unit-test	9cecb36	link	true	/test presubmit-agent-sandbox-unit-test
presubmit-agent-sandbox-e2e-test	9cecb36	link	true	/test presubmit-agent-sandbox-e2e-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.