Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scheduler: Adds notes about Scheduler namespace controller #4334

Closed
wants to merge 1 commit into from
Closed

Scheduler: Adds notes about Scheduler namespace controller #4334

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion daprdocs/content/en/concepts/dapr-services/scheduler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,10 @@ The Scheduler service Docker container is started automatically as part of `dapr

The Scheduler service is deployed as part of `dapr init -k`, or via the Dapr Helm charts. For more information on running Dapr on Kubernetes, visit the [Kubernetes hosting page]({{< ref kubernetes >}}).

+{{% alert title="Note" color="primary" %}}
+The Scheduler will delete all Jobs in a Kubernetes Namespace (including [Actor Reminders]({{< ref actors-timers-reminders.md >}}) if the [`SchedulerReminders`]({{< ref support-preview-features.md >}}) feature is enabled) when that Namespace is deleted.
+{{% /alert %}}

## Related links

[Learn more about the Jobs API.]({{< ref jobs_api.md >}})
[Learn more about the Jobs API.]({{< ref jobs_api.md >}})
4 changes: 4 additions & 0 deletions ...ocs/content/en/operations/hosting/kubernetes/kubernetes-persisting-scheduler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ description: "Configure Scheduler to persist its database to make it resilient t
The [Scheduler]({{< ref scheduler.md >}}) service is responsible for writing jobs to its embedded Etcd database and scheduling them for execution.
By default, the Scheduler service database writes this data to a Persistent Volume Claim of 1Gb of size using the cluster's default [storage class](https://kubernetes.io/docs/concepts/storage/storage-classes/). This means that there is no additional parameter required to run the scheduler service reliably on most Kubernetes deployments, although you will need additional configuration in some deployments or for a production environment.

{{% alert title="Note" color="primary" %}}
+The Scheduler will delete all Jobs in a Kubernetes Namespace (including [Actor Reminders]({{< ref actors-timers-reminders.md >}}) if the [`SchedulerReminders`]({{< ref support-preview-features.md >}}) feature is enabled) when that Namespace is deleted.
{{% /alert %}}

## Production Setup

In case your Kubernetes deployment does not have a default storage class or you are configuring a production cluster, defining a storage class is required.
Expand Down
Loading