How do I manage and version Alertmanager configurations via Kubernetes CRDs?

In this guide, we will manage and version Alertmanager configurations using Kubernetes Custom Resource Definitions (CRDs) with Pulumi. This allows for declarative management of Alertmanager’s configuration, making it easier to version and apply changes.

We will define a CustomResourceDefinition (CRD) for Alertmanager configurations and create an instance of this CRD. The CRD will allow us to store Alertmanager configurations in Kubernetes and manage them using Pulumi.

Below is the Pulumi program to achieve this:

import * as pulumi from "@pulumi/pulumi";
import * as k8s from "@pulumi/kubernetes";

// Define the AlertmanagerConfig CRD
const alertmanagerConfigCRD = new k8s.apiextensions.v1.CustomResourceDefinition("alertmanagerConfigCRD", {
    metadata: {
        name: "alertmanagerconfigs.monitoring.coreos.com",
    },
    spec: {
        group: "monitoring.coreos.com",
        versions: [{
            name: "v1alpha1",
            served: true,
            storage: true,
            schema: {
                openAPIV3Schema: {
                    type: "object",
                    properties: {
                        spec: {
                            type: "object",
                            properties: {
                                receivers: {
                                    type: "array",
                                    items: {
                                        type: "object",
                                        properties: {
                                            name: { type: "string" },
                                            emailConfigs: {
                                                type: "array",
                                                items: {
                                                    type: "object",
                                                    properties: {
                                                        to: { type: "string" },
                                                    },
                                                },
                                            },
                                        },
                                    },
                                },
                            },
                        },
                    },
                },
            },
        }],
        scope: "Namespaced",
        names: {
            plural: "alertmanagerconfigs",
            singular: "alertmanagerconfig",
            kind: "AlertmanagerConfig",
            shortNames: ["amcfg"],
        },
    },
});

// Create an instance of the AlertmanagerConfig CRD
const alertmanagerConfig = new k8s.apiextensions.CustomResource("exampleAlertmanagerConfig", {
    apiVersion: "monitoring.coreos.com/v1alpha1",
    kind: "AlertmanagerConfig",
    metadata: {
        name: "example-alertmanager-config",
        namespace: "default",
    },
    spec: {
        receivers: [{
            name: "team-email",
            emailConfigs: [{
                to: "team@example.com",
            }],
        }],
    },
}, { dependsOn: alertmanagerConfigCRD });

Key Points

We defined a CustomResourceDefinition (CRD) for Alertmanager configurations.
We created an instance of the AlertmanagerConfig CRD to manage Alertmanager configurations.
The CRD allows us to store and version Alertmanager configurations in Kubernetes.

Summary

In this guide, we managed and versioned Alertmanager configurations using Kubernetes Custom Resource Definitions (CRDs) with Pulumi. This approach enables declarative management of Alertmanager configurations, making it easier to version and apply changes.

Deploy this code

Want to deploy this code? Sign up for a free Pulumi account to deploy in a few clicks.

New to Pulumi?

Want to deploy this code? Sign up with Pulumi to deploy in a few clicks.