Enabling user alerts¶
This is administrator-facing documentation associated with this user guide. Please read that one first.
Important
Alertmanager should no longer be access via an Ingress, since this circumvents access control and audit logs. Please find the updated access method in the user guide linked above.
Perform the following configuration changes in wc-config.yaml
:
- Set
user.alertmanager.enabled=true
. - Ensure
user.alertmanager.ingress.enabled
is false.
For v0.18 and below include the following changes:
- Update the
user.namespaces
list to includealertmanager
. - Set
user.alertmanager.namespace=alertmanager
.
Then apply Welkin Apps.
Example¶
Please find below an example taken from wc-config.yaml
, which was tested with compliantkubernetes-apps v0.17.0 and also applies to version v0.18:
user:
## This only controls if the namespaces should be created, user RBAC is always created.
createNamespaces: true
## List of user namespaces to create.
namespaces:
- alertmanager
- demo1
- demo2
- demo3
## List of users to create RBAC rules for.
adminUsers:
- cristian.klein@elastisys.com
- lars.larsson@elastisys.com
- admin@example.com
## User controlled alertmanager configuration.
alertmanager:
enabled: true
## Namespace in which to install alertmanager
namespace: alertmanager
## Create basic-auth protected ingress to alertmanager
ingress:
enabled: false
Note
For versions after v0.18 alertmanager
may not be listed under user.namespaces
and the option user.alertmanager.namespace
is deprecated.