Skip to content

Add URL validation for Config Secret in Alertmanager #8193

@nutmos

Description

@nutmos

Component(s)

No response

What is missing? Please describe.

Nowadays, we have the sanitize methods to sanitize configuration. Mostly sanitize methods will check Alertmanager secrets for the mutually exclusive values or version support but the URLs are mostly checked at the CR when converting.

Since there are several URL values implemented in the Alertmanager, we should validate URL for the config from secrets too.

Describe alternatives you've considered.

Continue from #8188

Environment Information.

Environment

Kubernetes Version:
Prometheus-Operator Version:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions