docs(k8s-install): OHE-3033 fix the bundled object store values - #691
Open
aivong-openhands wants to merge 1 commit into
Open
docs(k8s-install): OHE-3033 fix the bundled object store values#691aivong-openhands wants to merge 1 commit into
aivong-openhands wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
aivong-openhands
changed the title
Step 3 told operators to set filestore.ephemeral: true, a key the chart no longer has. It was replaced with minio.enabled and a flat filestore config by #1015 on 2026-08-04, and the docs update did not travel with that change. Following the page left an install with no object store: the unknown key was silently accepted, minio.persistence configured a subchart that minio.enabled never deployed because it defaults to false, and filestore.type fell back to gcs. Nothing errored and the app came up with an empty FILE_STORE. Sets minio.enabled: true and filestore.type: s3, the pair the chart's own values comment names, and says which one does the deploying. Also drops the same non-existent key from the EKS page's external-S3 example, where it was harmless but implied the key exists.
aivong-openhands
force-pushed
the
aivong/fix-bundled-store-values
branch
from
August 5, 2026 15:52
886db3f to
333ff50
Compare
aivong-openhands
marked this pull request as ready for review
August 5, 2026 16:04
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The Step 3 values tell operators to configure the bundled object store with
filestore.ephemeral: true, and the chart has no such key. It was removed on 2026-08-04 by OpenHands/OpenHands-Cloud#1015, a breaking chart change that replaced it withminio.enabledand a flat filestore config; the docs update did not travel with it, so the published page has been wrong since. Following the page as written leaves an install with no object store at all:ephemeralis silently ignored because unknown values are accepted without warning,minio.persistence.enabledconfigures a subchart thatminio.enablednever deploys since it defaults tofalse, andfilestore.typefalls back to itsgcsdefault. Nothing errors, and the app comes up with an emptyFILE_STORE. The bundled store needsminio.enabled: truetogether withfilestore.type: s3, which is what the chart's own values comment says, so this sets both and explains whyenabledis the load-bearing one.The external-S3 example on the EKS page sets the same non-existent key to
false. Harmless there, since the rest of that block is correct and an ignored key changes nothing, but it implies the key exists and is worth removing while it is in hand.Validation
AWS_S3_ENDPOINT, andFILE_STOREresolving togoogle_cloud. So an operator following the page today is silently configured for GCS on a cluster with no GCS credentials, which is worse than an obvious failure.FILE_STORE=s3withAWS_S3_ENDPOINT=http://<release>-minio:9000.ephemeralmentions are sandbox ephemeral-storage sizing, which is a different and correct setting.This PR was drafted by an AI agent on behalf of the user.