fix (platform): update configure section

[guowenatk]

Content Description

Update vcluster platform configure section structure

Preview Link

https://deploy-preview-1499--vcluster-docs-site.netlify.app/docs/platform/next/configure/introduction

Internal Reference

Closes DOC-1107

@netlify /docs

Note

Restructures the platform configure section by splitting the monolithic config.mdx into organized subsections.

• New structure
  • Added introduction.mdx explaining values.yaml configuration types
  • Added installation-options/overview.mdx for installation modes
  • Added platform-configs/overview.mdx for platform configuration reference
  • Added agent-settings/ directory with overview, security-context, customization, agent-upgrade, and troubleshooting pages
• Deleted files
  • Removed config.mdx (content redistributed to new files)
  • Removed high-availability.mdx (content consolidated elsewhere)
  • Removed single-sign-on/ directory (consolidated into platform-configs/single-sign-on.mdx)
• Updated links
  • Fixed internal references in impersonate.mdx, agent-config.mdx, preserve-license.mdx
  • Updated SSO provider partials with new import paths
  • Fixed domain.mdx references in versioned docs

^{Generated by Claude for commit 4425903. Updates automatically on new commits.}

[netlify]

✅ Deploy Preview for vcluster-docs-site ready!

Name	Link
🔨 Latest commit	0e0988d
🔍 Latest deploy log	https://app.netlify.com/projects/vcluster-docs-site/deploys/6945587ea07fe200086b6c13
😎 Deploy Preview	https://deploy-preview-1499--vcluster-docs-site.netlify.app/docs
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

DOC-1107: Platform Docs Structure Improvement Project 1

[loft-bot]

Claude finished @guowenatk's task in 2m 5s —— View job

---

PR Review Summary

Remaining Issues to Fix

After reviewing the latest commit (4425903), most of the previously identified issues have been addressed. However, a few items still need attention:

Priority	File	Line	Issue
🔴 Critical	agent-upgrade.mdx	14	Missing import for GlossaryTerm component (will cause build failure)
🟡 Medium	overview.mdx	38	Terminology: {} is an empty object, not "empty list"
🟡 Medium	overview.mdx	70	Absolute URL path instead of relative file path
🟡 Medium	saml.mdx	22	List numbering jumps from 1 to 3
🟢 Minor	introduction.mdx	12	Extra space before period

What's Been Fixed Since Last Review

• ✅ Missing imports for InterpolatedCodeBlock in security-context.mdx and overview.mdx
• ✅ Typo "Cofigure" → "Configure" in security-context.mdx
• ✅ British spelling "behaviour" → "behavior" across files
• ✅ Broken anchor link #understanding-agent-values
• ✅ Typo value: → vault: in platform-configs/overview.mdx

What's Good

• ✅ New section structure is logical and well-organized
• ✅ Links in SSO partials use correct relative paths with .mdx extension
• ✅ YAML code blocks have correct indentation
• ✅ vCluster trademark used correctly throughout
• ✅ No use of "easy", "simple", "obvious" terms

I've added inline comments with specific suggestions for each remaining issue.

[loft-bot]

Claude finished @guowenatk's task in 1m 14s —— View job

---

PR Review Summary

• Gather context and understand PR changes
• Read CONTRIBUTING.md for style guide
• Review documentation files for remaining issues
• Check additional files for issues
• Provide summary of findings

Remaining Issues to Fix

After reviewing the latest commit (0e0988d), the critical issues from previous reviews have been addressed. However, a few minor items still need attention:

Priority	File	Line	Issue
🟡 Medium	saml.mdx	22	List numbering jumps from 1 to 3
🟡 Medium	overview.mdx (agent-settings)	39	Terminology: {} is an empty object, not "empty list"
🟡 Medium	overview.mdx (agent-settings)	70	Absolute URL path instead of relative file path
🟢 Minor	introduction.mdx	12	Extra space before period

What's Been Fixed Since Last Review

• ✅ Missing import for GlossaryTerm in agent-upgrade.mdx
• ✅ Missing import for InterpolatedCodeBlock in security-context.mdx
• ✅ Missing import for InterpolatedCodeBlock in overview.mdx
• ✅ Typo "Cofigure" → "Configure" in security-context.mdx

What's Good

• ✅ New section structure is logical and well-organized
• ✅ All component imports are now present
• ✅ Links in SSO partials use correct relative paths with .mdx extension
• ✅ YAML code blocks have correct indentation
• ✅ vCluster trademark used correctly throughout
• ✅ No use of "easy", "simple", "obvious" terms

I've added inline comments with specific suggestions for each remaining issue.

[loft-bot]

List numbering issue: Step numbers jump from 1 to 3, skipping step 2.

Suggested change

	3. Obtain the necessary values from your SAML identity provider (IdP) for the required fields.
	2. Obtain the necessary values from your SAML identity provider (IdP) for the required fields.

[loft-bot]

Terminology: {} is an empty object in YAML/JSON, not an empty list. An empty list would be [].

Suggested change

	- An empty `agentValues` list means that agents installed on connected host clusters will inherit the same configuration as the platform running on the primary host cluster.
	- An empty `agentValues` object means that agents installed on connected host clusters will inherit the same configuration as the platform running on the primary host cluster.

[loft-bot]

Link format: Per the style guide, links should use relative file paths with .mdx extension rather than absolute URL paths.

Suggested change

	If you haven't already, you need to [create access key](/docs/platform/api/authentication#create-an-access-key) to be able to login to the platform.
	If you haven't already, you need to [create access key](../../api/authentication.mdx#create-an-access-key) to be able to login to the platform.

[loft-bot]

Extra space: There's an extra space before the period.

Suggested change

	- There are both vCluster Platform and vCluster Platform agent running on the primary host cluster . The vCluster Platform manages the primary host cluster through its vCluster Platform Agent as well.
	- There are both vCluster Platform and vCluster Platform agent running on the primary host cluster. The vCluster Platform manages the primary host cluster through its vCluster Platform Agent as well.