ironcore-dev / ironcore-dev/network-operator

Support Multiple Providers in a Single Operator Deployment

Open
#143 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/switch-automation enhancement
Dominant language
Go
Stars
11
Forks
7
Avg merge
1d 7h
Merged PRs (30d)
40

Description

Background

Currently, the network-operator is designed to run with a single provider per deployment, specified via the --provider flag at startup (cmd/main.go:90). The provider is selected globally for all controllers and applied uniformly to all network devices managed by that operator instance.

Available providers:

  • openconfig (default) - Standards-based YANG models
  • cisco-nxos-gnmi - Cisco NX-OS specific implementation

This architecture requires deploying separate operator instances when managing devices from different vendors or requiring different protocol implementations, which:

  • Increases operational overhead (multiple deployments, RBAC configs, webhooks)
  • Complicates multi-vendor network environments
  • Limits flexibility in heterogeneous infrastructure

Proposed Enhancement

Enable the operator to support multiple providers simultaneously within a single deployment, allowing different devices to use different providers based on their vendor, capabilities, or configuration requirements.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at cmd/main.go:90 and trace how the --provider flag is selected and passed to controllers. Compare the openconfig and cisco-nxos-gnmi providers and identify the device configuration or selection rules needed for per-device choice. Done means one operator deployment can manage devices using different providers without separate operator instances.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.