NotificationChannel is the Schema for the NotificationChannels API. A NotificationChannel is a medium through which an alert is delivered when a policy violation is detected.
Type
CRD
Group
monitoring.gcp.upbound.io
Version
v1beta1
apiVersion: monitoring.gcp.upbound.io/v1beta1
kind: NotificationChannel
NotificationChannelSpec defines the desired state of NotificationChannel
No description provided.
Different notification type behaviors are configured primarily using the the labels field on this resource. This block contains the labels which contain secrets or passwords so that they can be marked sensitive and hidden from plan output. The name of the field, eg: password, will be the key in the labels map in the api request. Credentials may not be specified in both locations and will cause an error. Changing from one location to a different credential configuration in the config will require an apply to update state. Structure is documented below.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
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.
NotificationChannelStatus defines the observed state of NotificationChannel.
No description provided.
Conditions of the resource.
example-notification-channel
apiVersion: monitoring.gcp.upbound.io/v1beta1
kind: NotificationChannel
metadata:
annotations:
meta.upbound.io/example-id: monitoring/v1beta1/notificationchannel
labels:
testing.upbound.io/example-name: example_notification_channel
name: example-notification-channel
spec:
forProvider:
displayName: Test Notification Channel
labels:
email_address: fake_email@blahblah.com
type: email
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.