Re:Major AWS Outage Happening
by SOLAR_FIELDS on Monday October 20, 2025 @06:08PM
(#45650055)
This reminds me of the time that Google’s Paris data center flooded and caught on fire a few years ago. We weren’t actually hosting compute there, but we were hosting compute in AWS EU datacenter nearby and it just so happened that the dns resolver for our Google services elsewhere happened to be hosted in Paris (or more accurately it routed to Paris first because it was the closest). The temp fix was pretty fun, that was the day I found out that /etc/hosts of deployments can be globally modified in Kubernetes easily AND it was compelling enough to want to do that. Normally you would never want to have an /etc/hosts entry controlling routing in kube like this but this temporary kludge shim was the perfect level of abstraction for the problem at hand.
[ Parent
| on HN ]
Re:Major AWS Outage Happening
by citizenpaul on Monday October 20, 2025 @06:22PM
(#45650174)
> temporary kludge shim was the perfect level of abstraction for the problem at hand.
Thats some nice manager deactivating jargon.
Manager deactivating jargon is a great phrase - it’s broadly applicable and also specific.
Re:Major AWS Outage Happening
by johndubchak on Monday October 20, 2025 @07:20PM
(#45650638)
+1...hee hee
Re:Major AWS Outage Happening
by SOLAR_FIELDS on Monday October 20, 2025 @06:45PM
(#45650385)
Yeah that sentence betrays my BigCorp experience it’s pulling from the corporate bullshit generator for sure
Couldn't you just patch your coredns deployment to specify different forwarders?
Re:Major AWS Outage Happening
by SOLAR_FIELDS on Monday October 20, 2025 @10:37PM
(#45651857)
Probably. This was years ago so the details have faded but I do recall that we did weigh about 6 different valid approaches of varying complexity in the war room before deciding this /etc/hosts hack was the right approach for our situation