Repository navigation
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
enyst
left a comment
enyst
left a comment
There was a problem hiding this comment.
I'm an AI agent based on Opus 5.5, helping Engel Nyst (@enyst) with project work.
- Rebase: main removed
llms.txtandllms-full.txtin #815 (Mintlify generates them now), so dropping those two files from this PR clears the conflict. #871 edits the samedocs.jsonline. - Object storage: on GKE,
filestore.type: gcsis the chart default and the obvious production choice. It always uses the app's Workload Identity/ADC, and the chart has no key Secret option for it (values.yaml#L145-L166). A sentence saying so would help, because "configure its credentials" suggests a Secret. - If #879 merges first, the LLM section can link to it (see inline).
- Optional: add a Google GKE card next to Amazon EKS in
enterprise/k8s-install/index.mdx.
| store and configure its credentials before installing. | ||
|
|
||
| The evaluation used the chart's optional RustFS store on Persistent Disk CSI, | ||
| following the tested AKS configuration. It required a credential Secret and a |
There was a problem hiding this comment.
This refers to the AKS evaluation from #871, which readers of this page won't have seen. Suggest:
| following the tested AKS configuration. It required a credential Secret and a | |
| which required a credential Secret and a |
| Configure your provider through the bundled gateway in the shared Helm installation | ||
| values. For Vertex AI, provider credentials belong to the LiteLLM gateway; users | ||
| select the configured model in OpenHands. The validated configuration and model | ||
| checks are recorded in the companion Google gateway guide. |
There was a problem hiding this comment.
Once #879 lands, this can link to it:
| checks are recorded in the companion Google gateway guide. | |
| checks are in the [Google LLM Gateway](/enterprise/integrations/google-llm-gateway) guide. |
|
Thank you for reviewing this. Clarified GCS authentication and its separation from Vertex credentials, removed the unexplained AKS reference, and added the GKE card. The branch also follows main’s generated-file policy. The guide preserves the tested RustFS setup without claiming live GCS validation. I’ll add the Google gateway link once #879 merges. |
This branch was successfully deployed
2 participants
Adds a Google GKE preparation page following the published Amazon EKS approach: cluster requirements, Ubuntu platform and Sysbox pools, Persistent Disk CSI, object storage, database and ingress, followed by the shared Helm installation guide. Includes an Installation Skill section linking to the existing GKE skill; its proposed licensed-customer-path update is prepared separately.
Validation Scope records licensed Helm chart 0.74.0 / OpenHands 1.67.0 on GKE Standard: trusted HTTPS, GitHub login, normal Canvas loading, a Sysbox sandbox, workspace read/write, Vertex gateway inference and a completed tool-using conversation. The configuration used bundled PostgreSQL, RustFS and manual wildcard TLS.
Autopilot, Cloud SQL, GCS, reattachment/expansion, cross-zone recovery, autoscaling, node replacement, backup/restore and automatic certificate renewal were not covered. Google AI Studio was not tested. Concrete configuration requirements remain in the instructions, without blanket claims that the Helm installation is unsuitable for production.
Local structure, link-target and whitespace checks passed.