Skip to content

Allow for configurable forceSyncPeriod for resources #2682

Description

@loganjohnson-wk

Pre-submission Checklist

  • I have searched existing issues and this is not a duplicate
  • This is a Datadog Operator issue (CRDs, reconciliation, etc.), not a Datadog Agent or Datadog service problem (dashboards, monitors, etc.)

Operator version

1.22.0

Operator Helm chart version

2.17.0

Bug Report

What happened:
We have ~6k SLOs in one environment and with them re-syncing every hour due to the defaultForceSyncPeriod here we are hitting our API limit for slo_get. It has been raised but we do not need to be re-syncing SLOs every hour, most of our other operators re-reconcile on a 4-8 hour cadence. I understand the concern of not wanting the UI to drift from what is in the cluster for an extended period of time, either from manual changes or other edits, but I'd like to have the option to either shorten or extend it depending on the use case. For SLOs I'd like to spread it out but I could see other cases where one may want to keep it in sync more often.

What I expected:
I would like to be able to configure the forceSyncPeriod to override the defaultForceSyncPeriod to change when resources are re-synced to Datadog.

There is likely some conversation around if this should be configurable per type (monitor, dashboard, SLO, ect.) or a global definition to replace the default 60 minutes for all of them.

Steps to Reproduce

  1. Install the operator as usual
  2. Apply any resource to the cluster
  3. Wait 1 hour and the resource will be re-applied and the .status.lastForceSyncTime is updated
  4. Repeat

Environment

Kubernetes version: 1.30.0
Helm version: 3.17.2
Cloud provider: AWS

Additional Context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingoss/1Relatively recent, community engagementpending

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions