DowntimeSchedule is the Schema for the DowntimeSchedules API. Provides a Datadog DowntimeSchedule resource. This can be used to create and manage Datadog downtimes.
Type
CRD
Group
datadog.upbound.io
Version
v1alpha1
apiVersion: datadog.upbound.io/v1alpha1
kind: DowntimeSchedule
DowntimeScheduleSpec defines the desired state of DowntimeSchedule
No description provided.
(Block, Optional) (see below for nested schema)
(Set of String) A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope. A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope.
(Set of String) States that will trigger a monitor notification when the notify_end_types action occurs. States that will trigger a monitor notification when the notify_end_types action occurs.
(Set of String) Actions that will trigger a monitor notification if the downtime is in the notify_end_types state. Actions that will trigger a monitor notification if the downtime is in the notify_end_types state.
(Block, Optional) (see below for nested schema)
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
(Block, Optional) (see below for nested schema)
(Set of String) A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope. A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope.
(Set of String) States that will trigger a monitor notification when the notify_end_types action occurs. States that will trigger a monitor notification when the notify_end_types action occurs.
(Set of String) Actions that will trigger a monitor notification if the downtime is in the notify_end_types state. Actions that will trigger a monitor notification if the downtime is in the notify_end_types state.
(Block, Optional) (see below for nested schema)
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
DowntimeScheduleStatus defines the observed state of DowntimeSchedule.
No description provided.
(Block, Optional) (see below for nested schema)
(Set of String) A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope. A list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match all provided monitor tags. Setting monitor_tags to [*] configures the downtime to mute all monitors for the given scope.
(Set of String) States that will trigger a monitor notification when the notify_end_types action occurs. States that will trigger a monitor notification when the notify_end_types action occurs.
(Set of String) Actions that will trigger a monitor notification if the downtime is in the notify_end_types state. Actions that will trigger a monitor notification if the downtime is in the notify_end_types state.
(Block, Optional) (see below for nested schema)
Conditions of the resource.
downtime-schedule-example
apiVersion: datadog.upbound.io/v1alpha1
kind: DowntimeSchedule
metadata:
annotations:
meta.upbound.io/example-id: datadog/v1alpha1/downtimeschedule
labels:
testing.upbound.io/example-name: downtime_schedule_example
name: downtime-schedule-example
spec:
forProvider:
displayTimezone: America/New_York
message: Message about the downtime
monitorIdentifier:
monitorTags:
- test:123
- data:test
muteFirstRecoveryNotification: true
notifyEndStates:
- alert
- warn
notifyEndTypes:
- canceled
- expired
recurringSchedule:
recurrence:
- duration: 1h
rrule: FREQ=DAILY;INTERVAL=1
start: 2050-01-02T03:04:05
timezone: America/New_York
scope: env:us9-prod7 AND team:test123