Immutable solution version
Middleware on Kubernetes: one DaemonSet per cluster, name each cluster
Complete solution
Guide Middleware on Kubernetes: one DaemonSet per cluster, name each cluster: On Kubernetes, run exactly one Middleware agent DaemonSet per cluster; a second install fights the first and data goes missing. Use this when you hit exactly this in Middleware on Kubernetes. Not for different errors or different tools.
TL;DR: On Kubernetes, run exactly one Middleware agent DaemonSet per cluster; a second install fights the first and data goes missing. If you manage several clusters from one context, set a distinct cluster name per install so data lands under the right cluster. CrashLoopBackOff with OOMKilled means the memory limit is too low, raise it rather than restarting and hoping.
On Kubernetes, run exactly one Middleware agent DaemonSet per cluster; a second install fights the first and data goes missing. If you manage several clusters from one context, set a distinct cluster name per install so data lands under the right cluster. CrashLoopBackOff with OOMKilled means the memory limit is too low, raise it rather than restarting and hoping. Check the agent pod logs with kubectl logs on the DaemonSet pods; missing data with healthy pods usually means the cluster name or API key is wrong. Keep the API key in a secret, not inline in the manifest.
Context: Official docs (docs.middleware.io, Kubernetes agent): documents the Kubernetes install traps: only one DaemonSet per cluster, a distinct cluster name for clusters that share a context, and crash loops from memory limits.
When to use
You hit exactly this: Middleware on Kubernetes: one DaemonSet per cluster, name each cluster in Middleware on Kubernetes.
When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.
Compatibility
Middleware on Kubernetes.
Evidence
Official docs (docs.middleware.io, Kubernetes agent): documents the Kubernetes install traps: only one DaemonSet per cluster, a distinct cluster name for clusters that share a context, and crash loops from memory limits. Resolved: On Kubernetes, run exactly one Middleware agent DaemonSet per cluster; a second install fights the first and data goes missing. If you manage several clusters from one context, set a distinct cluster name per install so data lands under the right cluster. CrashLoopBackOff with OOMKilled means the memory limit is too low, raise it rather than restarting and hoping. Check the agent pod logs with kubectl logs on the DaemonSet pods; missing data with healthy pods usually means the cluster name or API key is wrong. Keep the API key in a secret, not inline in the manifest.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_1JJRlHOJrb68wIYl6KWoHQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Middleware on Kubernetes: one DaemonSet per cluster, name each cluster <span>— Vectle</span></a>