ironcore-dev / ironcore-dev/roadmap
Declarative Underlay Network Provisioning
@byteocean is already working on this.
Since Jan 27, 2026.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Summary
This enhancement focuses on enabling underlay networking automation using Kubernetes-native APIs and workflows. The goal is to onboard and configure switches declaratively, using Kubernetes as the control plane, to reduce the overhead of manual configuration of SONiC-based switches and prevent configuration errors due to manual efforts.
The initial focus will be on onboarding switches using ZTP (Zero Touch Provisioning), assuming SONiC as the base OS, and managing configuration through Kubernetes CRs. This should later evolve into a pluggable provider-style architecture for underlay infrastructure, similar to the pattern used in Metal Automation.
Scope
✅ In Scope
- Onboarding network switches using ZTP (e.g., SONiC-based) via Kubernetes-native mechanisms.
- Define CRDs and control flows to configure switches declaratively via Kubernetes.
- Architect the system for provider-style extensions (e.g., SONiC, NetConf, gNMI backends).
- Lay foundation to support incremental expansion to routers in future iterations.
❌ Out of Scope
- Router configuration and onboarding (to be handled as a follow-up enhancement).
- Support for vendor-specific hardware beyond generic SONiC-capable devices in this phase.
Responsible Areas
- Networking
- Metal Automation
Contributors
- @byteocean
- @hardikdr
- @afritzler
- @damyan
- @maxmoehl
Acceptance Criteria
-
Networking
- Kubernetes-native ZTP onboarding mechanism for switches is implemented.
- Switch configuration can be applied declaratively using CRDs.
- Architecture allows support for multiple backend protocols (e.g., SONiC).
- Support sufficient dynamic configurations using Agent and Controller for the first PoC. Eg Neibhour discovery etc.
- Necessary adaptations to bootstrap onie-installer from the switch operator.
-
Common
- Documentation of the full provisioning flow (from unboxed switch to configured).
- Sample manifests and user guides are provided.
Action Items
- Assign labels (e.g.,
area/networking,area/metal-automation,kind/epic) - Set milestone (
H2/2025) - Assign dependent sub-issues in each required area
- Assign an owner to the issue using the GitHub "Assignee" field
- List all contributors in the "Contributors" section above
- Add this issue to the
Roadmapproject
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.