Skip to content

docs(secureguard): add user-facing guide pages#2197

Open
scheeles wants to merge 5 commits into
mainfrom
docs/secureguard-migrate-user-docs
Open

docs(secureguard): add user-facing guide pages#2197
scheeles wants to merge 5 commits into
mainfrom
docs/secureguard-migrate-user-docs

Conversation

@scheeles

@scheeles scheeles commented Jun 25, 2026

Copy link
Copy Markdown
Member

What this does

Migrates the user-facing SecureGuard documentation into the Hugo site under
content/secureguard/main/.

Pages added/updated

  • Overview (_index.en.md) — enriched
  • getting-started, architecture, installation
  • eso-basics, openbao-basics
  • user-guide, advanced-configuration, federation
  • security-hardening, upgrade-guides, troubleshooting, glossary

documentation

NONE

scheeles added 2 commits June 13, 2026 18:07
Add the main documentation tree for the new SecureGuard product, which is
still under development. The product is intentionally not published publicly:

- Omitted from data/products.yaml (kept as a commented-out reservation block,
  following the existing KDP convention), so it does not appear in the product
  dropdown or on the homepage.
- Pages carry sitemapexclude, searchexclude and private front matter, so they
  are excluded from sitemap.xml and the site search index.

The pages remain reachable via their direct URL only.
Migrate the user-facing SecureGuard documentation from the product repo
into the Hugo site under content/secureguard/main/. Adds getting-started,
architecture, installation, ESO/OpenBao basics, user guide, advanced
configuration, federation, security hardening, upgrade guides,
troubleshooting, and glossary pages, and enriches the section overview.

Pages remain hidden (private/sitemapexclude/searchexclude) until the
public announcement. Developer-only docs (API reference, dev notes,
example manifests) stay in the product repo and are linked via GitHub URLs.

documentation: NONE
Signed-off-by: Sebastian Scheele <sebastian@loodse.com>
@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 25, 2026
@scheeles

Copy link
Copy Markdown
Member Author

/hold

@kubermatic-bot kubermatic-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 25, 2026
serg added 3 commits June 25, 2026 23:04
Updated the date for the Advanced Configuration page.

Signed-off-by: Sergey Furtak <contact@sergfurtak.com>
Updated the date for the Advanced Configuration page.

Signed-off-by: Sergey Furtak <contact@sergfurtak.com>
Signed-off-by: Sergey Furtak <contact@sergfurtak.com>
@serg serg closed this Jun 26, 2026
@serg serg reopened this Jun 26, 2026
@scheeles scheeles closed this Jun 26, 2026
@scheeles scheeles reopened this Jun 26, 2026
@scheeles scheeles changed the base branch from add-secureguard-docs to main June 26, 2026 13:15
@scheeles scheeles closed this Jun 26, 2026
@scheeles scheeles reopened this Jun 26, 2026
@kubermatic-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mgoltzsche for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants