Skip to content

tree: add ROADMAP.md #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jlebon merged 1 commit into from
Jul 23, 2026
Merged

tree: add ROADMAP.md #118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,8 @@ The Bootc Operator then exposes this bootc API to the Kubernetes control plane
in pure operator declarative fashion: you define the desired state your hosts
should be in, and the operator handles the reconciliation. This includes image
updates, but also future bootc enhancements like dynamic config overlays,
sysexts, etc. See the [PRD](docs/PRD.md) for more details.
sysexts, etc. See the [PRD](docs/PRD.md) for more details and the
[Roadmap](ROADMAP.md) for what's ahead.

## Highlights

Expand Down
17 changes: 17 additions & 0 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Bootc Operator Roadmap

## Vision

The Bootc Operator aims to be the standard Kubernetes operator for managing
bootc-based node OS images. It acts as a bridge between bootc and Kubernetes,
surfacing all relevant host features to the control plane in a distro-agnostic
way.

## Roadmap

The immediate goal is to ship [v0.1](https://github.com/bootc-dev/bootc-operator/issues?q=is%3Aissue%20state%3Aopen%20milestone%3Av0.1), which we consider the MVP state.

Afterwards, here are various categories in which we'd like to make progress:
* Usability gaps: [expose Prometheus metrics](https://github.com/bootc-dev/bootc-operator/issues/102), [emit K8s Events](https://github.com/bootc-dev/bootc-operator/issues/101), [support phased staging](https://github.com/bootc-dev/bootc-operator/issues/114), [manage operator manifests](https://github.com/bootc-dev/bootc-operator/issues/14), [publish AI skills](https://github.com/bootc-dev/bootc-operator/issues/27)
* Quality of life improvements: [integrate soft-reboot](https://github.com/bootc-dev/bootc-operator/issues/117), [support maintenance windows](https://github.com/bootc-dev/bootc-operator/issues/105), [limit staging I/O](https://github.com/bootc-dev/bootc-operator/issues/61), [surface download progress](https://github.com/bootc-dev/bootc-operator/issues/116), [simplify operator configuration](https://github.com/bootc-dev/bootc-operator/issues/92), [support cross-pool rollout ordering](https://github.com/bootc-dev/bootc-operator/issues/110)
* Major features: [add automatic rollback](https://github.com/bootc-dev/bootc-operator/issues/104), [enforce signature verification](https://github.com/bootc-dev/bootc-operator/issues/64), [enable transient `/etc` and/or `/var`](https://github.com/bootc-dev/bootc-operator/issues/73), support [config overlays](https://github.com/bootc-dev/bootc/issues/22), integrate [sysexts](https://github.com/bootc-dev/bootc/issues/7), [implement pull-through caching](https://github.com/bootc-dev/bootc-operator/issues/107), [integrate with trusted-cluster-operator](https://github.com/bootc-dev/bootc-operator/issues/17)