Seems like a data issue where the municipality was double-counted and one in Quebec for some reason.
See, there's a bunch of stuff that I deploy using terraform (VPC, DNS, EKS) and a bunch of stuff that I deploy with FluxCD. But in between, there's some awkward stuff like the monitoring stack that requires cloudy things and Kube things, and they're tightly coupled.
Right now I end up going with terraform and the awful helm provider. Many of these helm charts have sub-charts, nested values etc, but thankfully the monitoring stack doesn't change that much. It's still not ideal but it works as a one-shot deployment that sets up buckets, policies, IAM roles for service accounts, more policies for the roles, and finally the helm charts with values from the outputs of those clouds resources.
Deleted Comment
This makes me worried that they're going to add some "analytics" tracking scripts in there that come with those damned annoying cookie pop-ups.
Details here: https://digital.gov/guides/dap/common-questions-about-dap/
> The fundamental problem that we’ve observed is that weather.gov reflects its organizational silos (Conway's Law) more than its users’ needs. A lack of overall strategy, feedback/monitoring, and tools have perpetuated this problem.
Wow, my org would not have the guts to write that down in a public README!