You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc-site/docs/components/kubernetes/notification-service.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ By default, Zero uses Helm to bundle the service, you just need to enable it and
25
25
[See the Helm chart][notification-available-values] for all the available configuration options. In the `application` section you can set up your API keys and application-related parameters.
26
26
27
27
### Setting up API keys
28
-
Zero will create a Kubernetes secret containing the API keys and mounted the secret to the deployment using values from `zero-project.yml`.
28
+
Zero will create a secret in AWS SecretsManager, and external-secret is created to poll the values then mounted as a secret to the deployment using values from `zero-project.yml`.
29
29
30
30
[See Documentation][notification-service-config] on how to configure service with environment variables
description="If enabled, will inject slack_api_key env-vars from secret manager to notification service"
112
-
type=bool
113
-
default=false
114
-
}
115
-
116
-
variable"notification_service_sendgrid_enabled" {
117
-
description="If enabled, will inject sendgrid_api_key env-vars from secret manager to notification service"
118
-
type=bool
119
-
default=false
120
-
}
121
-
122
110
variable"notification_service_highly_available" {
123
111
description="If enabled, will make sure a minimum of 2 pods are running and use a horizontal pod autoscaler to make scale the number of pods based on CPU. Recommended for Production."
0 commit comments