feat: Add an example of using Agent Sandbox and Kata on GKE cluster

[maqiuyujoyce]

Fixes #176.

This PR added instructions to install Kata on a cluster cluster and use Kata container as the agent runtime.

I verified locally that the script and the doc works.

[netlify]

✅ Deploy Preview for agent-sandbox canceled.

Name	Link
🔨 Latest commit	40994de
🔍 Latest deploy log	https://app.netlify.com/projects/agent-sandbox/deploys/6953250051d41400084cce09

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: maqiuyujoyce
Once this PR has been reviewed and has the lgtm label, please assign janetkuo for approval. 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:

• 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]

Welcome @maqiuyujoyce!

It looks like this is your first PR to kubernetes-sigs/agent-sandbox 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/agent-sandbox has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @maqiuyujoyce. Thanks for your PR.

I'm waiting for a github.com 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.

[maqiuyujoyce]

@zvonkok FYI!

[aditya-shantanu]

This is great.

I'd recommend cleaning up this to make sure there is a single place we can share all Kata instructions. Thoughts ?

[janetkuo]

It's not clear how this example relates to Agent Sandbox. Would you clarify that?

[zvonkok]

The guide targets nested VMs; sooner or later, we need to have instructions for bare-metal machines as well. Future use cases with accelerators do not work with CSP nested virtualization offerings.
We can leverage Kata Peer Pods if we need accelerator support on CSP that offer only VMs and no bare-metal machines are available.

[janetkuo]

/ok-to-test

[k8s-ci-robot]

@maqiuyujoyce: The following test 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	40994de	link	true	/test presubmit-test-autogen-up-to-date

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.