chore: publish blog post on Medium

[SebTardif]

Summary

Publish a blog post on Medium introducing Attune and the patterns behind safe in-place pod right-sizing in Kubernetes.

Content

Reuse the article written for the Kubernetes blog (kubernetes/website#55963) with minor adaptations for Medium's audience:

• Slightly more accessible intro (Medium readers may not all be K8s operators)
• Same technical depth in the patterns sections
• Same Attune implementation section
• Add a canonical URL pointing to the primary publication (kubernetes.io/blog if published there first, or dev.to if that goes live first)

Why Medium

• Broader tech audience beyond the Kubernetes-specific community
• Cross-posting with a canonical URL avoids SEO duplication
• Publications like ITNEXT and Better Programming have large followings in the infrastructure space and accept guest submissions
• Incremental reach on top of dev.to (chore: write dev.to article announcing Attune #120) and the Kubernetes blog (chore: submit guest post to CNCF blog #122)

Publication Strategy

1. Wait for the primary publication to go live first (K8s blog PR blog: Hands-off right-sizing without killing Pods kubernetes/website#55963 or dev.to chore: write dev.to article announcing Attune #120)
2. Use Medium's "Import a story" feature with the canonical URL to avoid duplicate content penalties
3. Optionally submit to a Medium publication for wider distribution:
   • ITNEXT (Kubernetes/DevOps focus, large following)
   • Better Programming (general dev audience)
   • DevOps.dev (DevOps-specific)

Medium-Specific Formatting

• Medium uses a rich text editor, not Markdown. The import tool handles basic conversion.
• Code blocks render adequately but lack syntax highlighting for YAML. Review after import.
• Images must be uploaded inline (no external image references).
• Add 5 tags for discoverability: kubernetes, devops, cloud-native, autoscaling, open-source

Prerequisites

• A Medium account (free tier is sufficient for publishing)
• The primary article must be published first so the canonical URL exists
• If submitting to a publication (ITNEXT, etc.), apply to become a writer first

Effort

~30 minutes (import + formatting review + tag selection). Most of the work is already done.

Related

• chore: submit guest post to CNCF blog #122 Kubernetes blog submission (primary)
• chore: write dev.to article announcing Attune #120 dev.to article (secondary)
• Draft content: chore: submit guest post to CNCF blog #122 (comment)

[SebTardif]

Dependency: Do not publish until the primary article is live. Publishing order:

1. Wait for blog: Hands-off right-sizing without killing Pods kubernetes/website#55963 (K8s blog, tracked in chore: submit guest post to CNCF blog #122)
2. If K8s blog is accepted: publish dev.to (chore: write dev.to article announcing Attune #120) first with canonical URL to kubernetes.io, then cross-post here
3. If K8s blog is rejected: dev.to (chore: write dev.to article announcing Attune #120) becomes primary, then cross-post here with canonical URL to dev.to

Publishing on Medium before the K8s blog PR is resolved would disqualify the K8s blog submission (they require original, unpublished content).

[SebTardif]

Related community announce landed on r/FinOps (not a substitute for this issue):

https://www.reddit.com/r/FinOps/comments/1vfu906/selfpromotion_free_oss_for_underused_kubernetes/

Tracked in #480 (closed). This issue remains open until the blog/article for this channel is published.