fix: Ensure scalingAdapter is included in generated DGD for autoscaling

[AsadShahid04]

• Add scalingAdapter to generated DynamoGraphDeployment when planner is present
• Checks for planner components and enables scaling adapter automatically
• Fixes issue where DGDR with AI Configurator generates incomplete DGD spec
• Ensures DGDSAs (DynamoGraph Deployment Scaling Adapters) can be created

Fixes #6491

Summary by CodeRabbit

• New Features
  • Scaling adapter is now automatically enabled for deployments with specific component configurations, streamlining setup and ensuring proper scaling functionality initialization without manual configuration.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

👋 Hi AsadShahid04! Thank you for contributing to ai-dynamo/dynamo.

Just a reminder: The NVIDIA Test Github Validation CI runs an essential subset of the testing framework to quickly catch errors.Your PR reviewers may elect to test the changes comprehensively before approving your changes.

🚀

[coderabbitai]

Walkthrough

The PR modifies the DynamoGraphDeploymentRequest controller to automatically initialize the ScalingAdapter field in generated DynamoGraphDeployment resources when components with planners are present, addressing a bug where the adapter object was missing and preventing scaling adapters from being created.

Changes

Cohort / File(s)	Summary
Scaling Adapter Initialization deploy/operator/internal/controller/dynamographdeploymentrequest_controller.go	Added conditional logic in generateDGDSpec to initialize dgd.Spec.ScalingAdapter to {Enabled: true} when shouldEnableScalingAdapter returns true. Added new helper method shouldEnableScalingAdapter that checks if DGD has non-nil Spec.Components with at least one component containing a non-nil Planner.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: ensuring scalingAdapter is included in generated DGD for autoscaling functionality.
Description check	✅ Passed	The description covers the main changes, references the fixed issue (#6491), and explains the problem being addressed. While it doesn't strictly follow the template structure, it contains sufficient detail about what was changed and why.
Linked Issues check	✅ Passed	The pull request successfully addresses issue #6491 by adding logic to automatically enable scalingAdapter when planner components are detected, which enables DGDSAs creation for autoscaling.
Out of Scope Changes check	✅ Passed	All changes are directly related to the stated objective: adding scalingAdapter logic to the DynamoGraphDeploymentRequest controller for autoscaling support.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@deploy/operator/internal/controller/dynamographdeploymentrequest_controller.go`:
- Around line 1656-1662: The current check only initializes
dgd.Spec.ScalingAdapter when it's nil, but misses the case when ScalingAdapter
exists with Enabled: false; update the logic in the r.shouldEnableScalingAdapter
handling to also set dgd.Spec.ScalingAdapter.Enabled = true when
dgd.Spec.ScalingAdapter != nil && dgd.Spec.ScalingAdapter.Enabled == false, and
still create a new &dgdv1alpha1.ScalingAdapter{Enabled: true} when nil; keep the
existing logger.Info call (or adjust message) so the controller logs that
scalingAdapter was enabled on the generated DGD for autoscaling support; target
the block referencing r.shouldEnableScalingAdapter, dgd.Spec.ScalingAdapter, and
the ScalingAdapter.Enabled field.

🪄 Autofix (Beta)

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: Pro

Run ID: fb63d100-7519-4877-868b-449456112e7d

📥 Commits

Reviewing files that changed from the base of the PR and between 06f1701 and 017700b.

📒 Files selected for processing (1)

• deploy/operator/internal/controller/dynamographdeploymentrequest_controller.go