About LWCN
About Last Week in Cloud Native
Last Week in Cloud Native (LWCN) is a weekly newsletter dedicated to keeping the Cloud Native community informed about the latest releases, news, and developments in the CNCF ecosystem.
- π Published: every Monday
- π Language: English
- πΆ Price: free, no paywall
- π§βπ» Publisher: Mario Fahlandt
Our Mission
We believe staying current with the rapidly evolving Cloud Native landscape shouldn’t require hours of research. LWCN distills the most important updates from across the ecosystem into a concise, actionable weekly digest β written in a neutral, journalistic tone, with no marketing fluff.
Who We Are
LWCN is published by Mario Fahlandt, a Cloud Native practitioner and long-time contributor to the CNCF ecosystem. Mario works hands-on with Kubernetes and platform engineering in production environments and is active in the open source community around CNCF projects.
The newsletter is curated by Cloud Native practitioners with hands-on experience in:
- Kubernetes Operations - Managing production clusters at scale
- CNCF Projects - Contributing to and implementing projects like Helm, ArgoCD, Prometheus, and more
- Platform Engineering - Building internal developer platforms using Cloud Native technologies
- DevOps & GitOps - Implementing CI/CD pipelines and GitOps workflows
Our Methodology
Every week, we follow a systematic approach to curate the most relevant content:
1. Release Monitoring
We track 200+ CNCF and Cloud Native projects for new releases, including:
- Graduated projects (Kubernetes, Prometheus, Envoy, etc.)
- Incubating projects (Argo, Flux, Linkerd, etc.)
- Sandbox projects and emerging technologies
The project list is automatically synced from the official CNCF Landscape API plus a manually curated list of additional repositories.
2. News Aggregation
We monitor multiple sources for Cloud Native news:
- Official CNCF announcements
- Project blogs and changelogs
- Hacker News discussions (topics only, not sentiment)
- Community forums and social media
- Conference talks and keynotes
3. AI-Assisted Curation
We use Google Gemini to summarize the high volume of releases and news. The AI operates under a strict editorial policy (see below) that forbids marketing language, vendor pitches, and subjective opinions. The AI only extracts what changed and what it means technically.
4. Human Review
Every issue is reviewed before publishing to ensure:
- Technical accuracy
- Relevance to practitioners
- Balanced coverage across the ecosystem
- Compliance with our editorial policy
5. Data-Driven “Numbers of the Week”
The weekly statistics (top projects by commits and merged pull requests) are computed directly from the GitHub API by our Go pipeline β not generated by the AI. Numbers are facts, not opinions.
Editorial & AI Policy
To keep LWCN trustworthy and neutral, we follow a public editorial policy:
- No marketing speak. Words like “revolutionary”, “groundbreaking”, “game-changing”, “seamless” and similar hype language are explicitly banned in our AI prompts.
- No vendor pitches. Promotional phrasing from release notes, corporate blogs, or sponsored posts is stripped out of the editorial sections. (Clearly labeled sponsored/partner snippets are allowed in their own disclosed section β see “Independence & Sponsorship” below.)
- Facts only. For every release or news item we report what changed (features, bug fixes, deprecations, breaking changes, CVEs) and what it means technically.
- No opinions. Subjective takes from blog posts, Hacker News comments, or community members are not reproduced. We report topics and facts, not sentiment.
- Attribution. When we include non-factual claims (e.g. roadmap intent), we attribute them explicitly (“According to the release notes⦔).
- Transparency. The full AI prompt policy is open source and visible in
internal/ai/gemini.go.
What We Cover
- π Notable Releases - Major version updates, security patches, and feature releases
- π° Cloud Native News - Industry trends, CNCF announcements, and community updates
- π¬ Community Buzz - Topics being discussed in the community (not opinions)
- π Numbers of the Week - Top projects by commits and merged PRs, computed directly from GitHub
Corrections Policy
If you spot a factual error, please open an issue on GitHub. We correct mistakes as soon as possible and note significant corrections at the bottom of the affected issue.
- π Report a correction: github.com/mfahlandt/lwcn/issues
Independence & Sponsorship
LWCN is an independent project. We are not officially affiliated with the CNCF or the Linux Foundation, and editorial decisions are never for sale.
LWCN may include sponsored or partnered snippets in the newsletter. Whenever we do, the following rules apply:
- Clear labeling. Every sponsored or partnered item is prefixed with a visible tag such as
[Sponsored]or[Partner]and, where applicable, the sponsor’s name. You will always know when you are reading paid placement. - Visually separated. Sponsored snippets are placed in their own section or clearly demarcated block β never mixed into the neutral editorial “Notable Releases”, “This Week in Cloud Native”, “Community Buzz” or “Numbers of the Week” sections.
- Editorial independence. Sponsors cannot influence which CNCF projects, releases, CVEs or news items appear in the editorial sections, nor how they are covered. Neutrality rules (no hype, facts only) still apply to sponsor copy: we may reject or rewrite submissions that read like pure marketing.
- Relevance requirement. We only accept sponsorships that are genuinely relevant to the Cloud Native / CNCF audience (tools, services, events, jobs, learning material in the ecosystem).
- No deceptive practices. No native advertising disguised as editorial, no paid link-insertions into the editorial text, no pay-to-play rankings in “Numbers of the Week”.
- Disclosure. If a sponsor is a current or former client or has any other material relationship with the publisher, that relationship is disclosed in the snippet.
Interested in sponsoring? Reach out via GitHub Issues or contact Mario directly.
Privacy
We take your privacy seriously:
- No email tracking pixels, no cross-site tracking
- Google Analytics only loads after explicit cookie consent, with IP anonymization
- Full details in our Privacy Policy (Datenschutz) and Imprint (Impressum)
Open Source & Transparency
LWCN is open source. Our curation tools, website, AI prompts, and methodology are all public:
- π Repository: github.com/mfahlandt/lwcn
- π§ Tech Stack: Hugo (PaperMod theme), Go, GitHub Actions, GitHub Pages
- π€ AI Integration: Google Gemini API for content summarization (under strict editorial policy)
- π Data Sources: CNCF Landscape API, GitHub REST API, curated RSS feeds, Hacker News API
We welcome contributions, feedback, and suggestions from the community.
Contact Us
Have a suggestion, correction, or want to contribute?
- GitHub Issues: Report issues or suggest improvements
- Pull Requests: Contributions are welcome!
- LinkedIn: Connect with Mario Fahlandt
Subscribe
Never miss an issue:
- Email: subscribe via the form on the homepage (delivered through Buttondown, double opt-in, one-click unsubscribe)
- LinkedIn Newsletter: follow the weekly LinkedIn edition
- RSS: Newsletter Feed
LWCN is an independent project published by Mario Fahlandt and is not officially affiliated with the CNCF, though we are proud supporters of the Cloud Native ecosystem.