Configure TLS for Alertmanager - #1989
Conversation
|
Skipping CI for Draft Pull Request. |
OpenStackControlPlane CRD Size Report
Threshold reference
|
|
This needs the related telemetry-operator PR and afterwards the operator dependency bump PR merged first to get the new telemetry-operator CRD fields used in this PR. I'm leaving this as a draft until then. |
|
The related telemetry-operator PR: openstack-k8s-operators/telemetry-operator#949 |
Now that COO and telemetry-operator finally support TLS for alertmanager, we can generate the certificates and configure TLS similar to all other services. Jira: https://redhat.atlassian.net/browse/OSPRH-5177 Generated-By: Claude-Code claude-opus-4-6
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 9m 27s |
|
recheck The dependent telemetry-operator PR merged and a dependency bump in openstack-operator happened, meaning this can now be tested, reviewed and merged. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danpawlik, jlarriba, stuggi, vyzigold The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
a759b85
into
openstack-k8s-operators:main
Now that COO and telemetry-operator finally support TLS for alertmanager, we can generate the certificates and configure TLS similar to all other services.
Jira: https://redhat.atlassian.net/browse/OSPRH-5177
Generated-By: Claude-Code claude-opus-4-6