Learn MicroCloud - Roadmap & Community

#Introduction

Episode 20 let you see your cloud. Episode 21 invites you to look forward — and around you. MicroCloud is a living open source project: its development direction is open in the roadmap, and its decisions are made together with the community. Understanding both isn't just knowledge — it's how you make adoption decisions that last.

An analogy: planting a tree requires knowledge of the seasons and the soil — when it blooms, when it fruits, and where the gardening community gathers. You wouldn't plant in soil abandoned by its inhabitants, or plan a harvest in the wrong season. The roadmap and community are MicroCloud's seasons and soil.

#The MicroCloud Roadmap

#Cluster Manager Heading Toward Maturity

MicroCloud Cluster Manager (episode 12) was born as a beta. The roadmap drives it toward:

• More complete functionality: from observability toward centralized operations — managing, scaling, and recovering across clusters from one UI.
• Production stability: leaving beta status.
• Deeper integration with MicroCloud 3.x.

#MicroOVN 26.03 LTS

MicroOVN 26.03 LTS is MicroOVN's first LTS release — an SDN network with official long-term support. That means:

• An LTS track for networking you can rely on in production.
• Security and stability fixes backported over the long term.
• A more solid foundation for MicroCloud networking at scale.

In MicroCloud 3.1, MicroOVN 26.03 appeared as an experimental feature; its maturity toward LTS signals readiness for the production track.

#3.x LTS (Awaited)

Episode 17 explained why 3.x isn't yet for upgrading from 2 LTS. The roadmap answers this with the awaited 3.x LTS:

• When the 3.x LTS releases, the upgrade path from 2.x will be official and tested.
• A 3.x LTS will combine the latest features with long-term support guarantees.
• Until then: production on 2.1.3 LTS, lab on 3.2 — the two-track strategy still applies.

Sekarang   → 2.1.3 LTS (produksi) · 3.2 (feature/lab)
Dekat      → Cluster Manager stabil · MicroOVN 26.03 LTS
Mendatang  → 3.x LTS + jalur upgrade resmi dari 2.x

#Community and Resources

#Official Documentation

documentation.ubuntu.com/microcloud is the source of truth:

• Release notes for 3.2 and 2.1.3.
• How-tos for init, join, storage, network, and troubleshooting.
• CLI and configuration references.

Start every investigation here — not on the forum — because the documentation is updated to follow releases.

#GitHub: canonical/microcloud

github.com/canonical/microcloud is the home of the code:

• Releases: changelogs and notes for every version.
• Issues: report bugs, see what's being worked on.
• Source code: open contribution for anyone.

When you encounter odd behavior: search the issues first (it may already be reported), then read the release notes before upgrading.

#Discourse and Blog

• discourse.ubuntu.com: the official Ubuntu forum — the MicroCloud category for discussions, Q&A, and best practices from other users.
• ubuntu.com/blog: release announcements, case studies, and technical posts from Canonical.

#How to Contribute

• Report bugs with complete logs (episode 16): microcloud status, snap logs, and a step-by-step reproduction.
• Improve the documentation: typos, ambiguous sentences, or unclear guides are legitimate contributions.
• Answer on Discourse: your experience helps other admins.
• Open PRs on GitHub for small fixes.

#Common Pitfalls

• Relying on the blog as documentation: the blog is a signal, documentation is the truth — distinguish the two.
• Upgrading on hype without a roadmap: wait for the LTS release and the official upgrade path for production.
• Not reading release notes: behavior changes hide in changelogs — read before upgrading.
• Waiting for features that aren't promised: don't plan production on beta features without a firm stability date.
• Ignoring the community: a healthy open source project needs reporting and discussion — you're part of it.

#Closing

Key takeaways:

• The MicroCloud roadmap: Cluster Manager heading toward stable, MicroOVN 26.03 LTS, and the awaited 3.x LTS.
• The two-track strategy still applies: production on 2.1.3 LTS, lab on 3.2.
• Official documentation: documentation.ubuntu.com/microcloud — start investigations here.
• Code and releases: github.com/canonical/microcloud.
• Discussion and announcements: discourse.ubuntu.com and ubuntu.com/blog.
• Contribute: report bugs with data, improve docs, help fellow admins.

In episode 22 — the final episode — we close the series with ecosystems, alternatives & final reflections: comparing MicroCloud with K3s/Kubernetes, OpenStack, Proxmox VE, and Harvester/OKD, deciding when to choose each, plus a full recap of episodes 0-21 and a production checklist. See you at the finale!