Skip to content

Add guidance to disable scheduler connection attempts in in high-scale environments #4888

@MyMirelHub

Description

@MyMirelHub

What content needs to be created or modified?

Documentation is missing guidance for the dapr.io/scheduler-host-address annotation. In environments with 100+ sidecar pods, all sidecars connecting to the scheduler by default causes resource exhaustion.

Describe the solution you'd like

Add documentation covering:

  • Warning about default scheduler connection behavior at scale
  • Usage of dapr.io/scheduler-host-address: "" for services not using Dapr Actors/Jobs
  • Helm chart annotation examples

Where should the new material be placed?

  • Primary: /operations/hosting/kubernetes/kubernetes-production/

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions