feat: add initial release of OpenSandbox Controller Helm Chart#242
feat: add initial release of OpenSandbox Controller Helm Chart#242chanzhi82020 wants to merge 1 commit intoalibaba:mainfrom
Conversation
|
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. |
|
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" |
|
close, duplicate with #342 |
Summary
Testing
scripts/install.sh, E2E validation viascripts/e2e-test.sh, Helm lint for template syntax, and manual verification of Server API accessibility and Pool creation)Breaking Changes
Checklist
scripts/e2e-test.shfor end-to-end validation; unit tests to be added in follow-up)