Use prometheus-podman-exporter and mysqld_exporter images from oko quay#1925
Use prometheus-podman-exporter and mysqld_exporter images from oko quay#1925vyzigold wants to merge 1 commit into
Conversation
Now that we have a workflow setup to automatically build prometheus-podman-exporter and mysqld_exporter latest images whenever there is new content in openstack-k8s-operators/prometheus-podman-exporter and openstack-k8s-operators/mysqld_exporter main branches. We can consume those images by default instead of relating on upstream images, which may have slightly different content. Closes: https://redhat.atlassian.net/browse/OSPRH-29306
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vyzigold The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
OpenStackControlPlane CRD Size Report
Threshold reference
|
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 4m 14s |
|
"CRD size report". First time seeing this. Interesting check, although I'm not sure it reports correct numbers. I'm pretty sure the default images aren't stored in the oscp CRD, so there shouldn't be a change to the size. And even if they were, it should grow by a few bytes, not shrink by 11kB. |
|
/test functional |
|
recheck |
|
/test openstack-operator-build-deploy-kuttl-4-18 |
Now that we have a workflow setup to automatically build prometheus-podman-exporter and mysqld_exporter latest images whenever there is new content in openstack-k8s-operators/prometheus-podman-exporter and openstack-k8s-operators/mysqld_exporter main branches. We can consume those images by default instead of relating on upstream images, which may have slightly different content.
Related PRs:
openstack-k8s-operators/edpm-ansible#1179
openstack-k8s-operators/telemetry-operator#900
Closes: https://redhat.atlassian.net/browse/OSPRH-29306