@@ -284,7 +284,7 @@ field](https://api.slack.com/methods/chat.postMessage#arg_username) to the
284284payload, defaulting to the name of the reporting controller.
285285
286286This Provider type supports the configuration of a [ proxy URL] ( #https-proxy )
287- and/or [ TLS certificates ] ( #tls-certificates ) .
287+ and/or [ certificate secret reference ] ( #certificate-secret-reference ) .
288288
289289###### Slack example
290290
@@ -363,7 +363,7 @@ In both cases the Event metadata is attached as facts, and the involved object a
363363The severity of the Event is used to set the color of the message.
364364
365365This Provider type supports the configuration of a [proxy URL](#https-proxy)
366- and/or [TLS certificates ](#tls-certificates ), but lacks support for
366+ and/or [certificate secret reference ](#certificate-secret-reference ), but lacks support for
367367configuring a [Channel](#channel). This can be configured during the
368368creation of the Incoming Webhook Workflow in Microsoft Teams.
369369
@@ -403,7 +403,7 @@ The Event will be formatted into a [DataDog Event](https://docs.datadoghq.com/ap
403403API endpoint of the provided DataDog [Address](#address).
404404
405405This Provider type supports the configuration of a [proxy URL](#https-proxy)
406- and/or [TLS certificates ](#tls-certificates ).
406+ and/or [certificate secret reference ](#certificate-secret-reference ).
407407
408408The metadata of the Event is included in the DataDog event as extra tags.
409409
@@ -459,7 +459,7 @@ The Event will be formatted into a [Slack message](#slack) and send to the
459459` /slack ` endpoint of the provided Discord [ Address] ( #address ) .
460460
461461This Provider type supports the configuration of a [ proxy URL] ( #https-proxy )
462- and/or [ TLS certificates ] ( #tls-certificates ) , but lacks support for
462+ and/or [ certificate secret reference ] ( #certificate-secret-reference ) , but lacks support for
463463configuring a [ Channel] ( #channel ) . This can be configured [ during the creation
464464of the address] ( https://discord.com/developers/docs/resources/webhook#create-webhook )
465465
@@ -507,7 +507,7 @@ The Provider's [Channel](#channel) is used to set the `environment` on the
507507Sentry client.
508508
509509This Provider type supports the configuration of
510- [TLS certificates ](#tls-certificates ).
510+ [certificate secret reference ](#certificate-secret-reference ).
511511
512512# ##### Sentry example
513513
@@ -555,7 +555,7 @@ a unique identifier with the topic identifier (`-1234567890:1`) for the forum ch
555555or the username (`@username`) of the target channel.
556556
557557This Provider type does not support the configuration of a [proxy URL](#https-proxy)
558- or [TLS certificates ](#tls-certificates ).
558+ or [certificate secret reference ](#certificate-secret-reference ).
559559
560560# ##### Telegram example
561561
@@ -623,7 +623,7 @@ The Event will be formatted into a [Lark Message card](https://open.larksuite.co
623623with the metadata written to the message string.
624624
625625This Provider type does not support the configuration of a [proxy URL](#https-proxy)
626- or [TLS certificates ](#tls-certificates ).
626+ or [certificate secret reference ](#certificate-secret-reference ).
627627
628628# ##### Lark example
629629
@@ -660,7 +660,7 @@ The Event will be formatted into a [Slack message](#slack) and send as a
660660payload the provided Rocket [Address](#address).
661661
662662This Provider type does support the configuration of a [proxy URL](#https-proxy)
663- and [TLS certificates ](#tls-certificates ).
663+ and [certificate secret reference ](#certificate-secret-reference ).
664664
665665# ##### Rocket example
666666
@@ -742,7 +742,7 @@ You can optionally add [attributes](https://cloud.google.com/pubsub/docs/samples
742742to the Pub/Sub message using a [`headers` key in the referenced Secret](#http-headers-example).
743743
744744This Provider type does not support the configuration of a [proxy URL](#https-proxy)
745- or [TLS certificates ](#tls-certificates ).
745+ or [certificate secret reference ](#certificate-secret-reference ).
746746
747747# ##### Google Pub/Sub with JSON Credentials and Custom Headers Example
748748
@@ -788,7 +788,7 @@ with the metadata added to the [`details` field](https://docs.opsgenie.com/docs/
788788as a list of key-value pairs.
789789
790790This Provider type does support the configuration of a [proxy URL](#https-proxy)
791- and [TLS certificates ](#tls-certificates ).
791+ and [certificate secret reference ](#certificate-secret-reference ).
792792
793793# ##### Opsgenie example
794794
@@ -831,7 +831,7 @@ The provider will also send [Change Events](https://developer.pagerduty.com/api-
831831for `info` level `Severity`, which will be displayed in the PagerDuty service's timeline to track changes.
832832
833833This Provider type supports the configuration of a [proxy URL](#https-proxy)
834- and [TLS certificates ](#tls-certificates ).
834+ and [certificate secret reference ](#certificate-secret-reference ).
835835
836836The [Channel](#channel) is used to set the routing key to send the event to the appropriate integration.
837837
@@ -916,7 +916,7 @@ global:
916916` ` `
917917
918918This Provider type does support the configuration of a [proxy URL](#https-proxy)
919- and [TLS certificates ](#tls-certificates ).
919+ and [certificate secret reference ](#certificate-secret-reference ).
920920
921921# ##### Prometheus Alertmanager example
922922
@@ -988,7 +988,7 @@ The [Channel](#channel) is used to set the ID of the room to send the message
988988to.
989989
990990This Provider type does support the configuration of a [proxy URL](#https-proxy)
991- and [TLS certificates ](#tls-certificates ).
991+ and [certificate secret reference ](#certificate-secret-reference ).
992992
993993# ##### Webex example
994994
@@ -1184,11 +1184,36 @@ stringData:
11841184 proxy: "http://username:password@proxy_url:proxy_port"
11851185` ` `
11861186
1187- # ## TLS certificates
1187+ # ## Certificate secret reference
11881188
11891189` .spec.certSecretRef` is an optional field to specify a name reference to a
1190- Secret in the same namespace as the Provider, containing the TLS CA certificate.
1191- The secret must be of type `kubernetes.io/tls` or `Opaque`.
1190+ Secret in the same namespace as the Provider, containing TLS certificates for
1191+ secure communication. The secret must be of type `kubernetes.io/tls` or `Opaque`.
1192+
1193+ # ### Supported configurations
1194+
1195+ - **CA-only**: Server authentication (provide `ca.crt` only)
1196+ - **mTLS**: Client certificate authentication (provide `tls.crt` + `tls.key`, optionally with `ca.crt`)
1197+
1198+ # ### Providers supporting client certificate authentication
1199+
1200+ The following webhook-based providers support client certificate authentication :
1201+
1202+ | Provider Type | Description |
1203+ |---------------------|--------------------------------|
1204+ | `alertmanager` | Prometheus Alertmanager |
1205+ | `discord` | Discord webhooks |
1206+ | `forwarder` | Generic forwarder |
1207+ | `grafana` | Grafana annotations API |
1208+ | `matrix` | Matrix rooms |
1209+ | `msteams` | Microsoft Teams |
1210+ | `opsgenie` | Opsgenie alerts |
1211+ | `pagerduty` | PagerDuty events |
1212+ | `rocket` | Rocket.Chat |
1213+ | `slack` | Slack API |
1214+ | `webex` | Webex messages |
1215+
1216+ Support for client certificate authentication is being expanded to additional providers over time.
11921217
11931218# ### Example
11941219
0 commit comments