monitoring-central/jsonnet: Duplicate certificate resources #294
Labels
bug
Something isn't working
Comments
|
It is also arguable that we're already migrating monitoring-central to Go as well and we don't need to bother with jsonnet bugs 🤷 |
|
@ArthurSens Can you check if we ported the bug to Go? |
|
This came up here again. |
meysholdt
moved this to Scheduled
in ☁️ DevX by 🚚 Delivery and Operations Experience Team
ArthurSens
moved this from Scheduled
to Proposals
in ☁️ DevX by 🚚 Delivery and Operations Experience Team
ArthurSens
moved this from Proposals
to Scheduled
in ☁️ DevX by 🚚 Delivery and Operations Experience Team
ArthurSens
moved this to Backlog
in ☁️ DevX by 🚚 Delivery and Operations Experience Team
ArthurSens
moved this to 🧊Backlog
in 🚚 Security, Infrastructure, and Delivery Team (SID)
We never migrated monitoring-central to go, so the bug was not backported 🙂 The bug is not causing any real issues, besides the creation of a resource that does nothing. Since we're moving away from jsonnet for monitoring-central too so we can just leave this undone 😅 |
Repository owner
moved this from 🧊Backlog
to ✨Done
in 🚚 Security, Infrastructure, and Delivery Team (SID)
Nov 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're currently deploying duplicate certificates for Grafana and VictoriaMetrics. This is a problem especially when they are battling for ownership of their secret and one of those certificates is misconfigured.
Since when creating an Ingress we already create a certificate, we should deploy a separate certificate to it.
The text was updated successfully, but these errors were encountered: