Our agent found a bug with WireGuard in Google Kubernetes Engine

https://lovable.dev/blog/hunting-networking-bugs-in-kubernetes

by vikeri • 3 months ago

68 36 3 months ago

soupdiver• 3 months ago

hate how it all has the same tone now

came to say this. it's the AI writing cadence, I can smell it from 1000ft: - Lots of "The" headings - Always "why it matters" - Machine gun style cadence of short sentences

i_think_so3• 3 months ago

I hate that AI has stolen my emdashes and I can't use them without looking like slop. But I will die defending markdown as my preferred note taking format. They're not taking that away from me.

kandros• 3 months ago

convergence that we see in all kind of medium when some things are considered “working better” (true or not)

AI writing takes these to an extreme but we have see the same happening everywhere even before AI

Groxx• 3 months ago

I can't tell if my main source of hate there is the homogeneity itself, or that it's excessively marketing-flavored (fluffy and aggrandizing, mere inches from "our incredible journey..." at all times).

parliament32• 3 months ago

This piece might be a record for how quick it took me to smell the AI-tone and close the tab.. one paragraph! I'm sure it's an interesting bug but I can't stomach reading any more slop.

SaucyWrong• 3 months ago

Came here to say this. It’s a shame that I’m so exhausted reading slop that I’m probably missing many interesting stories from the industry

cootsnuck• 3 months ago

I think "AI-tone" is a much better way to characterize this stuff than accusing people of using AI. The problem has always been the same. Putting out slop feels disrespectful to the people you want to read/watch your stuff.

Makes me think of how pre-chatGPT I still could barely handle most recipe blogs because of their well known attempts at "filling space". And yea the problem is significantly magnified now everywhere else.

Anyway, my point is, whether or not someone uses AI is almost secondary in a way (even though it can seem pretty obvious to most of us when it's being used). All that matters is if the writing seems like it cares more about throwing words at people instead of actually conveying its points in a way to elicit understanding.

emkoemko3• 3 months ago

yup, if you can't be bothered to write a article i can't be bothered to read it... i don't get why people are so lazy

jbaiter• 3 months ago

Isn't this like the #1 problem people have with wireguard? I've had clients with the MTU issue every time I've set it up for more than a few clients. Also how on earth is "connection reset by peer" dreaded?

arm32• 3 months ago

Yes, almost without fail—the term "MTU" is included whenever someone mentions an issue with WireGuard. Big ol' nothin'burger here.

Aachen2• 3 months ago

A bug in Wireguard? What did Google change, since it affects only them? Any lessons learned about modifying cryptographic software?

...

Skipping past the investigation bit (minimising my daily slop intake), it's a wrong MTU value causing failing connections when Wireguard is disabled:

When we disabled WireGuard, we expected the configuration to change to use the full 1500 bytes. However, some nodes in the cluster hadn't been restarted [and were] using the old 1420-byte MTU.
[paraphrased] This particularly affected Valkey connections because they were distributed across nodes with mismatched MTU settings. So your API pod might not connect. The fix was rerolling all the nodes to get a consistent MTU configuration

Aachen2• 3 months ago

Three downvotes but not one comment. Should I just not post informational comments here or what's the message these faceless votes are trying to get across?

aliasxneo• 3 months ago

This article reeks of desperation. I'm pretty sure Lovable's days are numbered.

yellow_lead• 3 months ago

I think the credit belongs to Sascha still. Look at this:

The agent surfaced a suspicious issue: the anetd pods in our Google Kubernetes Engine cluster were restarting constantly, around 120 restarts per pod over six days, which is almost one crash per hour. Surely, this couldn't be right!
Sascha dug into the crash dumps. The stack trace pointed to a concurrent map-access panic, multiple goroutines trying to read and write to the same data structure at the same time without proper locking. But the key detail was where the panic happened: inside the Wireguard module of anetd.

AI: Your anted pod is crashing.

Engineer: Looks in the logs and finds a stack trace.

Your agent didn't find the bug. It's really that simple.

therealpygon2• 3 months ago

100% but it doesn’t benefit an AI company to properly assign credit. Their AI identified a generic problem, not this problem, and then their AI was guided like a child into the correct spot to start searching for a a bug that it eventually traced.

Enginerrrd• 3 months ago

100% but it doesn’t benefit an AI company to properly assign credit.

Does credibility really mean nothing anymore?

emkoemko3• 3 months ago

just noticed your comment, yea the title is misleading and the whole article is annoying AI slop

binoct• 3 months ago

A new bug appears, it’s in an encryption layer. You solve this by deciding to disable the encryption layer because user experience is better without the errors. You write it up as a recruitment piece for your engineering team.

There may be some good answers and lessons, but they didn’t make it into the article. Saying it’s on a cloud provider’s private network so encryption between your nodes isn’t necessary is a bold choice. Also, what happened to the root cause? Why did it start failing a week ago? Was a downgrade of the offending code not possible?

Not all bug investigations are worth really digging into. Sometimes the right call is to find any fix and move on. But all the nuance, judgement, implications, and lessons learned failed to make it into this post. And they are what make reading incident reports interesting for most engineers.

emkoemko3• 3 months ago

am i missing something?

'Sascha dug into the crash dumps. The stack trace pointed to a concurrent map-access panic, multiple goroutines trying to read and write to the same data structure at the same time without proper locking. But the key detail was where the panic happened: inside the Wireguard module of anetd.'

this is person right? not a agent... and this whole article seems like it was written by AI...

_caw• 3 months ago

A dead simple, deterministic threshold alert on the pod restart metric in any monitoring tool could also surface this same issue.

In fact, it happened to me today at work!

bzmrgonz• 3 months ago

Which agent did you guys let loose on clickhouse log server??

Our agent found a bug with WireGuard in Google Kubernetes Engine

Related Stories