Repository navigation
docs(hosting): document community kubernetes deployment - #19512
Merged
Merged
Conversation
Closed
Member
|
关联 #19513 :请将中文 Kubernetes 部署章节中两处「访问授权码」统一为「锁屏密码」,「该授权码」也改为「该密码」,与当前界面及现有 Docker 部署文档保持一致。Secret 的 |
Contributor
|
@88250 让 AI 直接改了提交 |
Member
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
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.
Description
Adds a short Kubernetes Hosting section immediately after Docker Hosting in the English, Simplified Chinese, Japanese, and Turkish READMEs, with matching table-of-contents entries. Existing Docker instructions and limitations are preserved.
The guide identifies the chart as community-maintained by HelmForge and uses the official SiYuan image. It covers installation, Secret-based access-code retrieval, HTTPS/WebSocket ingress, network policy, a single workspace writer, Recreate upgrade downtime, PVC retention, consistent backups, and the limits of Helm rollback.
I maintain the HelmForge chart; chart support remains with HelmForge. This follows the documentation contribution approved in #19343 (comment).
Type of change
Validation
Checklist
devbranch and has no merge conflicts.