feat: Add Arc + Fleet hybrid setup for DocumentDB portal visibility#267
Open
hossain-rayhan wants to merge 4 commits intodocumentdb:mainfrom
Open
feat: Add Arc + Fleet hybrid setup for DocumentDB portal visibility#267hossain-rayhan wants to merge 4 commits intodocumentdb:mainfrom
hossain-rayhan wants to merge 4 commits intodocumentdb:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Introduces initial scaffolding for deploying the DocumentDB Kubernetes Operator via Azure AKS/Arc Extensions, including a draft extension manifest, Arc-specific Helm values, local testing script, and supporting documentation/design plan.
Changes:
- Added Azure Arc extension manifest (
extension.yaml) and Arc override values (values-arc.yaml) for Helm-based deployment. - Added a Kind-based local test script to simulate Arc extension install flows.
- Added extension README plus a detailed Azure Arc integration design/rollout plan.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 17 comments.
Show a summary per file
| File | Description |
|---|---|
| operator/arc-extension/values-arc.yaml | Adds Arc-oriented Helm values overrides for extension deployments |
| operator/arc-extension/test-arc-extension.sh | Adds local Kind + Arc testing harness for installation/verification/cleanup |
| operator/arc-extension/extension.yaml | Adds draft Azure extension manifest and release train definitions |
| operator/arc-extension/README.md | Adds end-user installation/configuration/troubleshooting guide |
| docs/designs/azure-arc/azure-arc-integration-plan.md | Adds detailed two-phase Arc integration + billing plan |
added 3 commits
March 2, 2026 10:37
Signed-off-by: Rayhan Hossain <rhossain@microsoft.com>
Signed-off-by: Rayhan Hossain <rhossain@microsoft.com>
Signed-off-by: Rayhan Hossain <rhossain@microsoft.com>
0f16bd3 to
0d834ed
Compare
Signed-off-by: Rayhan Hossain <rhossain@microsoft.com>
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.
Summary
Adds a new deployment guide for setting up DocumentDB across hybrid environments (AKS + on-premises) using Azure Fleet Manager. This enables Azure Portal visibility for all DocumentDB installations without requiring Azure extension registration.
Motivation
Customers need to track DocumentDB Kubernetes operator installations across diverse environments (cloud and on-prem) for billing and management purposes. This solution provides immediate portal visibility while the full Azure Arc extension integration is being developed.
What's Included
New:
documentdb-playground/arc-hybrid-setup-with-fleet/README.mdAGENT-INSTRUCTIONS.mddocumentdb-instance.yamlsetup-fleet-hub.ps1setup-arc-member.ps1setup-arc-member.shcleanup.shUpdated:
docs/designs/azure-arc/azure-arc-integration-plan.mdarc-hybrid-setup-with-fleet/as interim solutionArchitecture
Azure Fleet Manager (hubless)
├── AKS Member (native portal visibility)
└── Arc Member (Kind/on-prem with token-based portal access)
└── DocumentDB Operator + Instance on both
Key Features
Testing
Manually validated end-to-end: