Skip to content

feat(planner): add runtime-configurable minimum endpoints - #13038

Merged
tedzhouhk merged 10 commits into
mainfrom
hzhou-codex/dyn-3675-runtime-min-endpoints
Aug 12, 2026
Merged

tedzhouhk merged 10 commits into
mainfrom
hzhou-codex/dyn-3675-runtime-min-endpoints

Conversation

@tedzhouhk

@tedzhouhk tedzhouhk commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Add prefill_min_endpoint and decode_min_endpoint. Use min_endpoint for aggregated deployments, to apply the same minimum to prefill and decode in disaggregated deployments, or to supply the active role in a single-component deployment when its role-specific value is unset; role-specific values replace it for their role.
  • Add a loopback-only GET/PATCH /v1/min-endpoints runtime API, including aggregated-mode support through min_endpoint.
  • Enforce effective per-role floors across load/throughput scaling, GPU and power budgets, rollout handling, and the orchestrator's final target boundary.
  • Keep endpoint maxima governed by the existing GPU and power budgets; this change does not add per-role maximum endpoint fields.
  • Update replay/AI Simulate integration, operator examples, and English/Chinese Planner documentation.

Why

Disaggregated deployments need independent prefill and decode replica floors that operators can adjust without restarting the Planner. Aggregated deployments use min_endpoint; disaggregated deployments can use it to set the same minimum for both roles. In single-component deployments, min_endpoint supplies the active role when its role-specific value is unset.

Minimum endpoint footprints are budget-validated at startup. Runtime updates are process-local, atomic with respect to Planner ticks, budget-validated before mutation, and active on the next stable tick.

Developer and user impact

  • Existing configurations retain their current behavior: min_endpoint remains the aggregated minimum, applies to both prefill and decode in disaggregated deployments, and supplies the active role in single-component deployments when its role-specific value is unset.
  • Disaggregated mode accepts both component fields; single-role modes accept only their active field; aggregated mode accepts only min_endpoint.
  • The control API binds to 127.0.0.1:9086 by default and can be disabled with control_api_port: 0.
  • No Kubernetes Service, authentication, persistence, or per-role maximum endpoints are added.

Agentic review

Three independent review passes covered API/lifecycle behavior, scaling and budget invariants, and compatibility/tests/docs. The review found two P1, two P2, and two P3 issues; all were fixed with regression coverage. The final review found no remaining P0-P3 findings.

Where should the reviewer start?

  1. components/src/dynamo/planner/config/planner_config.py
  2. components/src/dynamo/planner/control_api.py
  3. components/src/dynamo/planner/core/base.py
  4. components/src/dynamo/planner/plugins/orchestrator/engine_adapter.py
  5. components/src/dynamo/planner/tests/unit/test_control_api.py
  6. components/src/dynamo/planner/tests/unit/test_power_budget.py

Validation

  • 1166 passed, 5 skipped — complete Planner test suite
  • 80 passed — AI Simulate sweeper and Planner provider tests
  • 56 passed — focused configuration and runtime API tests after the documentation update and latest-main merge
  • Targeted mypy: no issues in 5 changed Planner source files
  • Generated Python, Rust, and Kubernetes API references: fresh
  • python -m compileall
  • git diff --check
  • Relevant pre-commit hooks: isort, black, flake8, codespell, YAML, Ruff, AI Simulate docs sync, and Fern asset-path checks
  • The repository-wide pytest marker report remains blocked locally by unrelated missing optional SGLang and KVBM modules.

Related Issues

  • Internal tracking: DYN-3675
  • Confirmed — no matching public GitHub issue

Summary by CodeRabbit

  • New Features

    • Added separate minimum endpoint settings for prefill and decode workloads. min_endpoint configures aggregated deployments, applies the same minimum to both roles in disaggregated deployments, or supplies the active role in single-component deployments when its role-specific value is unset.
    • Added a localhost-only runtime API to view and update active endpoint minimums atomically.
    • Added validation to prevent unsupported settings and reject changes that exceed GPU or power budgets.
    • Improved scaling and budget enforcement to respect component-specific endpoint floors.
  • Documentation

    • Updated planner configuration, deployment examples, and scaling guidance for the new settings and runtime API.
  • Bug Fixes

    • Preserved rollout behavior while enforcing endpoint minimums during scale-down.

Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
@github-actions github-actions Bot added feat documentation Improvements or additions to documentation deployment::k8s Relates to dynamo deployment in kubernetes planner labels Aug 11, 2026
@tedzhouhk
tedzhouhk marked this pull request as ready for review August 11, 2026 19:02
@tedzhouhk
tedzhouhk requested review from a team as code owners August 11, 2026 19:02

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 5 potential issues.

View 1 additional finding in Devin Review.

Open in Devin Review

@coderabbitai

coderabbitai Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The planner now supports independent prefill and decode endpoint floors, legacy fallback behavior, and a loopback runtime API for atomic updates. Budget, scaling, replay, orchestration, tests, examples, and documentation use the new settings.

Changes

Planner endpoint floors

Layer / File(s) Summary
Configuration and runtime control API
aisimulate/src/aisimulate/sweeper/config.py, components/src/dynamo/planner/config/*, components/src/dynamo/planner/control_api.py, components/src/dynamo/planner/core/base.py
Adds validated prefill and decode floors, legacy inheritance, control API port configuration, atomic runtime updates, budget validation, locking, and centralized cleanup.
Role-specific budget and scaling enforcement
components/src/dynamo/planner/core/budget.py, components/src/dynamo/planner/core/load_scaling.py, components/src/dynamo/planner/core/state_machine.py, components/src/dynamo/planner/core/throughput_scaling.py, components/src/dynamo/planner/environment/base.py
Applies separate endpoint floors to GPU, power, load, throughput, state-machine, and startup footprint calculations.
Orchestration and replay wiring
components/src/dynamo/planner/plugins/orchestrator/engine_adapter.py, components/src/dynamo/planner/simulation/provider.py, components/src/dynamo/planner/offline/replay_adapter.py
Carries endpoint settings through replay and applies component-specific floors during stable deployment reconciliation and budget clamping.
Planner regression and API coverage
components/src/dynamo/planner/tests/*
Adds coverage for configuration, runtime API validation, locking, shutdown, budgets, scaling, rollout behavior, replay, and configuration identity.
Planner references and examples
deploy/operator/config/samples/*, docs/fern/pages/*, docs/fern/translations/zh-CN/*
Documents endpoint inheritance, mode restrictions, runtime API behavior, budget validation, and control API settings.

Estimated code review effort: 4 (Complex) | ~60 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 29.59% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the main change: runtime-configurable minimum endpoints for the Planner.
Description check ✅ Passed The description covers the change, rationale, reviewer starting points, related issue status, and validation results, despite using different section headings than the template.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (6)
components/src/dynamo/planner/tests/unit/test_control_api.py (1)

109-110: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Move the aiohttp.test_utils import to module scope.

aiohttp is required by these tests. Import TestClient and TestServer once with the other third-party imports.

  • components/src/dynamo/planner/tests/unit/test_control_api.py#L109-L110: Remove the local import.
  • components/src/dynamo/planner/tests/unit/test_control_api.py#L154-L154: Remove the duplicate local import.
Proposed change
 from unittest.mock import AsyncMock, patch
 
+from aiohttp.test_utils import TestClient, TestServer
 import pytest
@@
-    from aiohttp.test_utils import TestClient, TestServer
@@
-    from aiohttp.test_utils import TestClient, TestServer

As per coding guidelines, “Keep imports at the top of the file.” As per path instructions, .ai/python-guidelines.md requires imports at module scope.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/tests/unit/test_control_api.py` around lines
109 - 110, Move the aiohttp TestClient and TestServer import to module scope
alongside the other third-party imports in
components/src/dynamo/planner/tests/unit/test_control_api.py (anchor lines
109-110). Remove both local or duplicate imports at lines 109-110 and 154-154,
leaving the tests to reuse the single module-level import.

Sources: Coding guidelines, Path instructions

components/src/dynamo/planner/environment/base.py (1)

457-463: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Reuse this helper for the runtime budget check.

minimum_power_footprint_fits implements the startup power-footprint rule. The new runtime path in components/src/dynamo/planner/core/base.py Lines 236-265 re-implements the same rule inline: it sums prefill_min_endpoint * p_watts and decode_min_endpoint * d_watts and compares the total against total_gpu_power_limit.

Two implementations of one rule will drift. A change to the tolerance, the rounding, or the None-watts policy in one place will not reach the other, and a PATCH could then accept a floor that startup rejects.

Call minimum_power_footprint_fits from the runtime check as well.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/environment/base.py` around lines 457 - 463,
Update the runtime budget check in the core planner path to call
minimum_power_footprint_fits instead of duplicating the power-footprint
calculation and comparison inline. Pass the runtime budget,
prefill_min_endpoint, decode_min_endpoint, p_watts, and d_watts arguments so
runtime validation uses the same rule as the startup check.
components/src/dynamo/planner/control_api.py (1)

45-51: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Narrow the exception caught around request.json().

except Exception converts every failure into a 400. request.json() raises json.JSONDecodeError for a malformed body and aiohttp.ContentTypeError for a wrong Content-Type. It also propagates transport errors when the client disconnects mid-body. The current handler reports a disconnect as "request body must be valid JSON", which hides the real cause from the logs.

Catch only the decode and content-type errors.

As per coding guidelines: "Prefer failing fast over hiding errors; remove try/except blocks where possible, catch only specific exceptions".

♻️ Proposed refactor
+import json
...
     async def handle_patch(request: web.Request) -> web.Response:
         try:
             payload = await request.json()
-        except Exception:
+        except (json.JSONDecodeError, web.HTTPException, ValueError):
             return _error("request body must be valid JSON", 400)

aiohttp.ContentTypeError subclasses ValueError, so the tuple above covers a wrong Content-Type as well. Confirm the exact aiohttp 3.9 exception hierarchy before you finalize the tuple.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/control_api.py` around lines 45 - 51, Update
handle_patch to catch only the specific JSON parsing and content-type exceptions
raised by request.json(), including json.JSONDecodeError and the appropriate
aiohttp.ContentTypeError hierarchy for the supported aiohttp version. Preserve
the existing 400 response for malformed JSON or incorrect content types, while
allowing transport and client-disconnect errors to propagate.

Sources: Coding guidelines, Linters/SAST tools

components/src/dynamo/planner/config/defaults.py (1)

40-41: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Consider defaulting control_api_port to 0.

The control API is unauthenticated. It accepts PATCH requests that change scaling floors. The bind address 127.0.0.1 limits access to the pod network namespace, but any sidecar, ephemeral debug container, or process running in that pod can change planner scaling behavior without credentials. A default of 0 (disabled) makes the surface opt-in and keeps existing deployments unchanged.

If default-on is intentional, document the pod-local trust assumption next to this default.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/config/defaults.py` around lines 40 - 41,
Change the default value of control_api_port in the configuration defaults to 0
so the unauthenticated control API is disabled unless explicitly enabled,
preserving existing opt-in behavior through configured nonzero values.
components/src/dynamo/planner/offline/replay_adapter.py (1)

486-486: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Replace the index slice with an explicit predicate.

excluded_fields[:6] selects the flat top-level fields and leaves the dotted paths for the structural handling below. The count is correct after this change: indices 0-5 are the six flat entries.

The coupling is fragile. A contributor who adds a flat field after index 5, or who adds one without bumping the slice, gets no error. The result is a silently wrong planner_config_digest, which is the replay identity contract.

Select by shape instead of by position.

♻️ Proposed refactor
-        for field in excluded_fields[:6]:
+        # Flat top-level fields only; dotted paths need the structural
+        # handling below and must not be popped here.
+        for field in (f for f in excluded_fields if "." not in f):
             parent = decision_config
             parts = field.split(".")

The parts split then always yields one element, so the inner loop becomes a no-op and can be removed in a follow-up.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/offline/replay_adapter.py` at line 486, Replace
the positional slice in the excluded_fields loop with an explicit predicate that
selects only flat top-level field names (those without a dot), while leaving
dotted paths for the structural handling below. Preserve the existing
planner_config_digest replay identity behavior without relying on field ordering
or a fixed count.
components/src/dynamo/planner/config/planner_config.py (1)

44-50: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

resolve_min_endpoint is untyped at both parameters. The shared root cause is the signature resolve_min_endpoint(config: object, component: str). The object annotation forces every field read through getattr, and the bare str lets any value other than "prefill" resolve to the decode floor. One signature change fixes both.

  • components/src/dynamo/planner/config/planner_config.py#L44-L50: annotate config with a Protocol that declares min_endpoint, prefill_min_endpoint, and decode_min_endpoint, then replace the three getattr calls with direct attribute access.
  • components/src/dynamo/planner/config/planner_config.py#L47-L47: annotate component as Literal["prefill", "decode"] so a misspelled role fails type checking instead of silently returning the decode floor.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@components/src/dynamo/planner/config/planner_config.py` around lines 44 - 50,
Update components/src/dynamo/planner/config/planner_config.py lines 44-50 in
resolve_min_endpoint: define and use a Protocol declaring min_endpoint,
prefill_min_endpoint, and decode_min_endpoint, then access those attributes
directly instead of getattr. Annotate component at lines 47-47 as
Literal["prefill", "decode"] so invalid roles fail type checking; update the
config parameter to use the Protocol.

Sources: Coding guidelines, Linters/SAST tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@components/src/dynamo/planner/core/base.py`:
- Around line 172-175: Make planner diagnostics finalization idempotent in
_shutdown_runtime: initialize _diagnostics_finalized alongside the other state
fields, and only call self._recorder.finalize() when the flag is false, setting
it before or during the first finalization attempt. Preserve the existing
exception logging while ensuring repeated shutdown calls do not write the report
again.
- Around line 819-820: Bound lock acquisition in both public methods
get_min_endpoints and patch_min_endpoints using a timeout while waiting for
self._config_lock. On timeout, raise a distinct retryable exception and map it
to HTTP 503 in control_api.py; preserve the existing validation error behavior
and next-stable-tick semantics when the lock is acquired.

In
`@docs/fern/pages/developer-guide/knowledge-base/modular-components/planner/planner-guide.md`:
- Line 214: Update the documentation prose in the planner guide to use
“built-in” instead of “builtin” when describing targets, while preserving
identifiers such as builtin_load_propose unchanged.

---

Nitpick comments:
In `@components/src/dynamo/planner/config/defaults.py`:
- Around line 40-41: Change the default value of control_api_port in the
configuration defaults to 0 so the unauthenticated control API is disabled
unless explicitly enabled, preserving existing opt-in behavior through
configured nonzero values.

In `@components/src/dynamo/planner/config/planner_config.py`:
- Around line 44-50: Update
components/src/dynamo/planner/config/planner_config.py lines 44-50 in
resolve_min_endpoint: define and use a Protocol declaring min_endpoint,
prefill_min_endpoint, and decode_min_endpoint, then access those attributes
directly instead of getattr. Annotate component at lines 47-47 as
Literal["prefill", "decode"] so invalid roles fail type checking; update the
config parameter to use the Protocol.

In `@components/src/dynamo/planner/control_api.py`:
- Around line 45-51: Update handle_patch to catch only the specific JSON parsing
and content-type exceptions raised by request.json(), including
json.JSONDecodeError and the appropriate aiohttp.ContentTypeError hierarchy for
the supported aiohttp version. Preserve the existing 400 response for malformed
JSON or incorrect content types, while allowing transport and client-disconnect
errors to propagate.

In `@components/src/dynamo/planner/environment/base.py`:
- Around line 457-463: Update the runtime budget check in the core planner path
to call minimum_power_footprint_fits instead of duplicating the power-footprint
calculation and comparison inline. Pass the runtime budget,
prefill_min_endpoint, decode_min_endpoint, p_watts, and d_watts arguments so
runtime validation uses the same rule as the startup check.

In `@components/src/dynamo/planner/offline/replay_adapter.py`:
- Line 486: Replace the positional slice in the excluded_fields loop with an
explicit predicate that selects only flat top-level field names (those without a
dot), while leaving dotted paths for the structural handling below. Preserve the
existing planner_config_digest replay identity behavior without relying on field
ordering or a fixed count.

In `@components/src/dynamo/planner/tests/unit/test_control_api.py`:
- Around line 109-110: Move the aiohttp TestClient and TestServer import to
module scope alongside the other third-party imports in
components/src/dynamo/planner/tests/unit/test_control_api.py (anchor lines
109-110). Remove both local or duplicate imports at lines 109-110 and 154-154,
leaving the tests to reuse the single module-level import.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9efb9d19-d23f-4705-9f39-f683320d74a7

📥 Commits

Reviewing files that changed from the base of the PR and between e0c4917 and 302cbcd.

📒 Files selected for processing (31)
  • aisimulate/src/aisimulate/sweeper/config.py
  • aisimulate/tests/sweeper/test_config.py
  • components/src/dynamo/planner/config/defaults.py
  • components/src/dynamo/planner/config/planner_config.py
  • components/src/dynamo/planner/control_api.py
  • components/src/dynamo/planner/core/base.py
  • components/src/dynamo/planner/core/budget.py
  • components/src/dynamo/planner/core/load_scaling.py
  • components/src/dynamo/planner/core/state_machine.py
  • components/src/dynamo/planner/core/throughput_scaling.py
  • components/src/dynamo/planner/environment/base.py
  • components/src/dynamo/planner/offline/replay_adapter.py
  • components/src/dynamo/planner/plugins/orchestrator/engine_adapter.py
  • components/src/dynamo/planner/simulation/provider.py
  • components/src/dynamo/planner/tests/offline/test_replay_adapter_fpm.py
  • components/src/dynamo/planner/tests/plugins/orchestrator/test_engine_adapter.py
  • components/src/dynamo/planner/tests/unit/test_budget.py
  • components/src/dynamo/planner/tests/unit/test_control_api.py
  • components/src/dynamo/planner/tests/unit/test_planner_config.py
  • components/src/dynamo/planner/tests/unit/test_planner_sweep_config_provider.py
  • components/src/dynamo/planner/tests/unit/test_power_budget.py
  • components/src/dynamo/planner/tests/unit/test_throughput_scaling.py
  • deploy/operator/config/samples/nvidia.com_v1beta1_dynamographdeploymentrequest.yaml
  • docs/fern/pages/developer-guide/knowledge-base/modular-components/planner/overview.md
  • docs/fern/pages/developer-guide/knowledge-base/modular-components/planner/planner-design.md
  • docs/fern/pages/developer-guide/knowledge-base/modular-components/planner/planner-guide.md
  • docs/fern/pages/kubernetes/auto-deployment/dynamo-planner.mdx
  • docs/fern/pages/reference/components/planner-configuration.mdx
  • docs/fern/pages/reference/kubernetes-api/dynamo-graph-deployment-request.mdx
  • docs/fern/translations/zh-CN/pages/developer-guide/knowledge-base/modular-components/planner/planner-design.md
  • docs/fern/translations/zh-CN/pages/developer-guide/knowledge-base/modular-components/planner/planner-guide.md

@datadog-official

This comment has been minimized.

Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
…runtime-min-endpoints

Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
Signed-off-by: hongkuanz <hongkuanz@nvidia.com>
@github-actions

github-actions Bot commented Aug 11, 2026 •

Copy link
Copy Markdown
Contributor

@jasonqinzhou jasonqinzhou left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

COMMENT · 8.5/10 · high confidence

What this PR does

This PR adds independently configurable prefill and decode endpoint floors, plus a loopback runtime API for changing them without restarting the Planner. It carries the effective floors through scaling, GPU and power budgets, rollout reconciliation, replay, AI Simulate, operator examples, and Planner documentation.

The update thoughtfully removes the confusing legacy framing, brings the branch onto the Linux-stable generated references from main, and preserves focused coverage for runtime atomicity, budget infeasibility, cleanup, and replay determinism.

Why this score

This is now strong 8.5/10 work and merits COMMENT rather than changes requested: the prior generated-reference blocker is fixed, all 56 focused current-head tests pass, and the three generated-reference checks are fresh. One non-blocking documentation mismatch remains: the revised min_endpoint wording mentions aggregated and disaggregated modes but omits the still-active fallback in prefill-only and decode-only modes.

Signed-off-by: hongkuanz <hongkuanz@nvidia.com>

@jthomson04 jthomson04 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving comment-only change in operator.

@tedzhouhk
tedzhouhk merged commit 813c30b into main Aug 12, 2026
119 checks passed
@tedzhouhk
tedzhouhk deleted the hzhou-codex/dyn-3675-runtime-min-endpoints branch August 12, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deployment::k8s Relates to dynamo deployment in kubernetes documentation Improvements or additions to documentation feat planner size/XXL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants