1 of 178 pain cards, shown in full — score, summary and a real quote from the thread it came from.
21
Kubernetes operators face CPU throttling and OOM from misconfigured resource requests and
We're seeing production issues because CPU limits cause throttling even when the node has spare capacity, and memory limits above requests lead to OOM kills fo…
“CPU request is how much CPU is reserved for your pod if it needs it. The limit is a hard cap. Hit it and the kernel throttles the pod, even when the node still has spare CPU. That is the usual cause of CPU throttling on Kubernetes. It does not protect the neighboring pods. In my simple Web API test, adding a CPU limit took typical latency from 23 ms to 87 ms, (4x slower), with the limited pod throttled in half of all CFS windows, and the average CPU graph looked fine the whole time.”
Performance & Reliability
10 posts
Pro
177 more pains are available in Pro
The blurred cards below are placeholders. No locked title, quote, score or id is sent to the browser.
🔒 Pro
52
Recurring workflow breakdown reported across multiple threads
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
WORKFLOW
4 posts
🔒 Pro
59
Users hit the same limit and describe identical workarounds
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
INTEGRATIONS
7 posts
🔒 Pro
66
Integration drops data during sync and nobody gets notified
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
PERMISSIONS
10 posts
🔒 Pro
73
Manual step repeats daily because the export omits one field
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
REPORTING
13 posts
🔒 Pro
80
Permission model blocks the person who actually does the work
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
BILLING
16 posts
🔒 Pro
53
Bulk operation silently skips rows past a hidden threshold
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
NOTIFICATIONS
19 posts
🔒 Pro
60
Recurring workflow breakdown reported across multiple threads
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
WORKFLOW
22 posts
🔒 Pro
67
Users hit the same limit and describe identical workarounds
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
INTEGRATIONS
25 posts
🔒 Pro
74
Integration drops data during sync and nobody gets notified
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
PERMISSIONS
28 posts
🔒 Pro
81
Manual step repeats daily because the export omits one field
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
REPORTING
31 posts
🔒 Pro
54
Permission model blocks the person who actually does the work
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
BILLING
34 posts
🔒 Pro
61
Bulk operation silently skips rows past a hidden threshold
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
NOTIFICATIONS
37 posts
🔒 Pro
68
Recurring workflow breakdown reported across multiple threads
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
WORKFLOW
40 posts
🔒 Pro
75
Users hit the same limit and describe identical workarounds
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
INTEGRATIONS
43 posts
🔒 Pro
82
Integration drops data during sync and nobody gets notified
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
PERMISSIONS
46 posts
🔒 Pro
55
Manual step repeats daily because the export omits one field
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
REPORTING
49 posts
🔒 Pro
62
Permission model blocks the person who actually does the work
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
BILLING
52 posts
🔒 Pro
69
Bulk operation silently skips rows past a hidden threshold
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
NOTIFICATIONS
55 posts
🔒 Pro
76
Recurring workflow breakdown reported across multiple threads
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
WORKFLOW
58 posts
🔒 Pro
83
Users hit the same limit and describe identical workarounds
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
INTEGRATIONS
61 posts
🔒 Pro
56
Integration drops data during sync and nobody gets notified
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
PERMISSIONS
4 posts
🔒 Pro
63
Manual step repeats daily because the export omits one field
Independent complaints cluster into one recurring pain with quotes from the threads they came from.
“We lose an afternoon every week to this and support keeps telling us it works as intended.”
REPORTING
7 posts
🔒 Pro
70
Permission model blocks the person who actually does the work
Several unrelated accounts describe the same failure in the same order of steps.
“I built a script to patch it, but it breaks whenever they change the field names.”
BILLING
10 posts
🔒 Pro
77
Bulk operation silently skips rows past a hidden threshold
The workaround costs hours a week and depends on a person remembering it.
“Nobody on the team can explain why it only fails for some of our records.”
NOTIFICATIONS
13 posts
Page 1 of 8 · 178 pains · 25 per page
Grafana is a Pro marketplace
Create a free account, then upgrade to Pro to unlock all 178 cards in Grafana.