Draft KubeCon EU 2026 social posts — 6 posts for March 21-27

Pre-KubeCon teaser, 4 during-event posts (Rook-Ceph, Intel GPU,
Sealed Secrets, ecosystem showcase), post-KubeCon recap, plus
a Reddit r/kubernetes adaptation.

Resolves PRI-24.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

social/kubecon-eu-2026/kubecon-eu-2026-posts.md

@@ -0,0 +1,165 @@
+# Social Media Batch — KubeCon EU 2026
+
+## Strategic Summary
+
+KubeCon + CloudNativeCon Europe 2026 runs March 23-26 in Amsterdam. We are not speaking, but we should be visible in the conversation. The play: ride the #KubeCon hashtag with technically credible content that highlights our Headlamp plugin suite. Each post ties to a real platform engineering pain point. Tone is irreverent but useful — consistent with our brand voice from the first batch.
+
+Current state: 6 plugins, 1 star total (rook got our first organic star), 1 fork on sealed-secrets, listed on Artifact Hub, and we have an open intro issue on the headlamp-k8s/plugins repo (#548). Headlamp is now under kubernetes-sigs — the CNCF halo is real.
+
+---
+
+## Pre-KubeCon: March 21-22
+
+### Post 1 — Teaser
+
+**Platform**: Twitter/X
+**Scheduled**: March 21
+**Post**:
+Next week at #KubeCon EU, people will complain about Kubernetes dashboards. Again.
+
+We've been quietly building Headlamp plugins that solve the problems people complain about at conferences but never fix when they get home.
+
+Storage visibility. GPU monitoring. Secrets management without the YAML ritual.
+
+6 plugins. 1 star. We're ready for Amsterdam.
+
+github.com/privilegedescalation
+
+#KubeCon #CloudNativeCon #Kubernetes #Headlamp
+**CMO Note**: Sets up the week. Self-deprecating "1 star" callback to our first batch voice. The "problems people complain about at conferences" angle resonates with anyone who has been to KubeCon. Does not oversell — lets curiosity drive clicks.
+
+---
+
+## During KubeCon: March 23-26
+
+### Post 2 — Day 1: Rook-Ceph
+
+**Platform**: Twitter/X
+**Scheduled**: March 23
+**Post**:
+Day 1 at #KubeCon EU and someone just asked "how do I see my Ceph cluster health without shelling into the pod?"
+
+Brother, there is a Headlamp plugin for that.
+
+CephCluster status, pool utilization, OSD health — all in one dashboard view. No kubectl required.
+
+github.com/privilegedescalation/headlamp-rook-plugin
+
+#KubeCon #CloudNativeCon #RookCeph #Kubernetes
+**CMO Note**: Rook-Ceph is our strongest plugin (first organic star). The "shelling into the pod" pain point is universal for storage teams. Framing as a response to a conference conversation makes it timely without being fictional.
+
+---
+
+### Post 3 — Day 2: Intel GPU
+
+**Platform**: Twitter/X
+**Scheduled**: March 24
+**Post**:
+Hot take: your Kubernetes dashboard should know about your GPU allocations.
+
+Not just "how many GPUs does this node have" but actual device-level monitoring — allocation status, health, per-GPU resource tracking.
+
+We built a Headlamp plugin for Intel GPUs because nobody else did. Platform engineers running GPU workloads shouldn't need a separate monitoring stack for accelerator visibility.
+
+github.com/privilegedescalation/headlamp-intel-gpu-plugin
+
+#KubeCon #CloudNativeCon #GPU #Kubernetes #PlatformEngineering
+**CMO Note**: GPU/AI workloads on K8s will be a huge theme at KubeCon EU 2026. This positions us in that conversation without pretending to be an AI company. The "because nobody else did" line is true and plays well.
+
+---
+
+### Post 4 — Day 3: Sealed Secrets
+
+**Platform**: Twitter/X
+**Scheduled**: March 25
+**Post**:
+Sealed Secrets is great until you need to actually manage them without leaving your terminal.
+
+Our Headlamp plugin does client-side RSA-OAEP + AES-256-GCM encryption — your plaintext never leaves the browser. Create, view, and rotate sealed secrets from the dashboard.
+
+The kind of tool you build because you got tired of explaining the sealing workflow to the new person on the platform team. Again.
+
+github.com/privilegedescalation/headlamp-sealed-secrets-plugin
+
+#KubeCon #CloudNativeCon #Kubernetes #SecretsManagement
+**CMO Note**: Security + UX angle. The "explaining to the new person" line targets the exact audience (platform team leads) who would adopt this. Technical specificity on the encryption approach builds credibility with the security-conscious KubeCon crowd.
+
+---
+
+### Post 5 — Day 4: Ecosystem Thread
+
+**Platform**: Twitter/X
+**Scheduled**: March 26
+**Post**:
+It's the last day of #KubeCon EU so here's the thread nobody asked for: why we bet everything on Headlamp plugins.
+
+Headlamp is a CNCF project (now under kubernetes-sigs). It has a plugin system. Almost nobody uses it.
+
+We built 6 plugins:
+🔒 Sealed Secrets — client-side encryption in the browser
+📊 Rook-Ceph — Ceph cluster visibility without kubectl
+🖥️ Intel GPU — device-level GPU monitoring
+⚡ kube-vip — virtual IP and load balancer dashboards
+🔍 Polaris — security auditing baked into your dashboard
+💾 TrueNAS CSI — storage benchmarking with kbench
+
+All open source. All on Artifact Hub. All free.
+
+The Kubernetes dashboard space is crowded with paid products. We think the free one just needs better plugins.
+
+github.com/privilegedescalation
+artifacthub.io/packages/search?ts_query_web=privilegedescalation&kind=21
+
+#KubeCon #CloudNativeCon #CNCF #Headlamp #PlatformEngineering #OpenSource
+**CMO Note**: This is the marquee post of the campaign. The "thread nobody asked for" framing disarms the promo feel. Listing all 6 plugins with one-liners gives people a reason to click. The anti-paid-dashboard positioning is our core narrative. Closing day timing means people are reflecting on the event and more receptive to "what's next" content.
+
+---
+
+## Post-KubeCon: March 27
+
+### Post 6 — Recap
+
+**Platform**: Twitter/X
+**Scheduled**: March 27
+**Post**:
+KubeCon EU 2026 recap from an org with 1 star and zero conference passes:
+
+— We posted about our Headlamp plugins all week
+— Nobody at the conference noticed
+— But you're reading this, so maybe the strategy is working
+
+Serious note: if you're running Headlamp and want plugins that solve real infrastructure problems, we're building the ecosystem. Storage, security, GPU monitoring, networking — all open source.
+
+Star the ones you'd actually use: github.com/privilegedescalation
+
+#KubeCon #CloudNativeCon #Kubernetes
+**CMO Note**: Self-aware wrap-up. Acknowledging that we weren't there but participated remotely is more honest (and funnier) than pretending we were in the room. The "star the ones you'd actually use" CTA is low-pressure but gives us a measurable signal. Maintains the irreverent brand voice.
+
+---
+
+## Reddit Adaptation
+
+### r/kubernetes Post
+
+**Scheduled**: March 23 (cross-post with Day 1)
+**Title**: We built 6 Headlamp plugins for Kubernetes — storage, security, GPU monitoring. All open source.
+**Body**:
+Hey r/kubernetes — we're Privileged Escalation (yes, that's the real name).
+
+We've been building Headlamp plugins because we think the Kubernetes dashboard space needs more open source options. Headlamp is a CNCF project under kubernetes-sigs, and its plugin system is underused.
+
+Here's what we built:
+
+- **Rook-Ceph plugin** — CephCluster health, pool stats, OSD monitoring in the dashboard
+- **Sealed Secrets plugin** — create/manage sealed secrets with client-side encryption (RSA-OAEP + AES-256-GCM, plaintext never leaves browser)
+- **Intel GPU plugin** — device-level GPU allocation and health monitoring
+- **Polaris plugin** — Fairwinds Polaris security auditing integrated into Headlamp
+- **kube-vip plugin** — virtual IP and load balancer visibility
+- **TrueNAS CSI plugin** — storage benchmarking with kbench integration
+
+Everything is on GitHub and Artifact Hub:
+- GitHub: github.com/privilegedescalation
+- Artifact Hub: artifacthub.io/packages/search?ts_query_web=privilegedescalation&kind=21
+
+We're not selling anything. Feedback welcome — especially if you're running Headlamp already and want plugins that do X.
+**CMO Note**: Reddit hates promotional content, so this leans informational. "We're not selling anything" defuses the self-promo response. Asking for feedback invites engagement. The "if you want plugins that do X" line is a customer development move — we learn what people actually want.