Skip to content

feat: add initial release of OpenSandbox Controller Helm Chart#242

Closed
chanzhi82020 wants to merge 1 commit intoalibaba:mainfrom
chanzhi82020:feat-helm-chart-support
Closed

feat: add initial release of OpenSandbox Controller Helm Chart#242
chanzhi82020 wants to merge 1 commit intoalibaba:mainfrom
chanzhi82020:feat-helm-chart-support

Conversation

@chanzhi82020
Copy link
Copy Markdown

Summary

  • Introduce the initial release (v0.1.0) of the OpenSandbox Controller Helm Chart, which provides a complete deployment solution for the OpenSandbox Kubernetes Controller and associated Server component. This change enables SDK integration and sandbox pool management, with configurable replicas/resources, comprehensive RBAC, high availability support, and multiple environment configuration options (default/e2e).
  • The Helm chart unifies deployment of core controller, FastAPI-based Server control plane, and sandbox pool management, reducing manual deployment complexity and enabling standardized configuration for development/production environments.

Testing

  • Not run (explain why)
  • Unit tests (will be added in follow-up PR to cover template rendering logic)
  • Integration tests (pending completion of CI pipeline integration)
  • e2e / manual verification (Completed local deployment via scripts/install.sh, E2E validation via scripts/e2e-test.sh, Helm lint for template syntax, and manual verification of Server API accessibility and Pool creation)

Breaking Changes

  • None (This is a new feature addition with no changes to existing code/functionality, fully backward compatible)
  • Yes (describe impact and migration path)

Checklist

  • Linked Issue or clearly described motivation (Motivation: Provide a standardized, configurable Helm deployment solution for OpenSandbox Controller and Server to simplify Kubernetes integration and SDK usage)
  • Added/updated docs (if needed) (Comprehensive README.md, examples directory with production-ready configs, NOTES.txt for post-install guidance, and script documentation)
  • Added/updated tests (if needed) (Added scripts/e2e-test.sh for end-to-end validation; unit tests to be added in follow-up)
  • Security impact considered (Added optional API key authentication for Server, complete RBAC resource isolation, and restricted service access via ClusterIP by default)
  • Backward compatibility considered (No changes to existing OpenSandbox functionality; Helm chart is additive and can be disabled/enabled independently)

@gemini-code-assist
Copy link
Copy Markdown

Important

Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Feb 25, 2026

CLA assistant check
All committers have signed the CLA.

@Spground
Copy link
Copy Markdown
Collaborator

Thank you for your contribution, but the PR is duplicate with #232.

@chanzhi82020
Copy link
Copy Markdown
Author

Thank you for your contribution, but the PR is duplicate with #232.

The chart package in PR #232 only supports the deployment of the controller. To use OpenSandbox properly, users still need to manually start the server and pool, and then configure network connectivity — this is not user-friendly. The current commit addresses this complexity: it supports one-click deployment of all services required by OpenSandbox and provides a built-in, optional pre-warmed agent pool. Could we optimize the content of the chart package in PR #232 to support the use case targeted by this PR?

@Spground
Copy link
Copy Markdown
Collaborator

Spground commented Feb 25, 2026

Thank you for your contribution, but the PR is duplicate with #232.

The chart package in PR #232 only supports the deployment of the controller. To use OpenSandbox properly, users still need to manually start the server and pool, and then configure network connectivity — this is not user-friendly. The current commit addresses this complexity: it supports one-click deployment of all services required by OpenSandbox and provides a built-in, optional pre-warmed agent pool. Could we optimize the content of the chart package in PR #232 to support the use case targeted by this PR?

It's very useful for users to get an one-click deployment solution, which is on our planning. However, it's more maintainable to make individual component be independent helm chart. Then we can compose all components together as an App Chart by sub-chart provided by helm.

# app/Chart.yaml
apiVersion: v2
name: app
description: A Helm chart for my full application
type: application
version: 0.1.0

dependencies:
  - name: controller
    version: "0.1.0"
    repository: "https://my-helm-repo.example.com/charts" 
  - name: server
    version: "0.2.0"
    repository: "https://my-helm-repo.example.com/charts"
  - name: ingress
    version: "0.3.0"
    repository: "https://my-helm-repo.example.com/charts"

@Spground
Copy link
Copy Markdown
Collaborator

Spground commented Mar 5, 2026

close, duplicate with #342

@Spground Spground closed this Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants