Skip to content

Support Parsing ZTP Script via per-switch Configmap - #165

Open
hardikdr wants to merge 1 commit into
ironcore-dev:mainfrom
hardikdr:feat/config-map-ztp
Open

Support Parsing ZTP Script via per-switch Configmap#165
hardikdr wants to merge 1 commit into
ironcore-dev:mainfrom
hardikdr:feat/config-map-ztp

Conversation

@hardikdr

Copy link
Copy Markdown
Member

Proposed Changes

Add strict ConfigMap-based ZTP mode

Adds --ztp-mode:

  • templates (default): existing leaf/spine template behavior
  • configmap: serves the ZTP script from the ConfigMap referenced by the matching Switch.spec.ztp

ConfigMap mode matches the ZTP client source IP to spec.ztp.sourceAddress and never falls back to templates.

@hardikdr
hardikdr requested a review from a team as a code owner August 25, 2026 11:33
@github-actions github-actions Bot added api-change documentation Improvements or additions to documentation labels Aug 25, 2026
@hardikdr
hardikdr requested review from Giluerre and byteocean August 25, 2026 11:33
@hardikdr
hardikdr force-pushed the feat/config-map-ztp branch from 5c7cf44 to 5d9bafb Compare August 25, 2026 11:35
@hardikdr hardikdr added ok-to-image and removed documentation Improvements or additions to documentation ok-to-image labels Aug 25, 2026
Signed-off-by: Hardik Dodiya <hardik.dodiya@sap.com>
@hardikdr
hardikdr force-pushed the feat/config-map-ztp branch from 5d9bafb to ea29a54 Compare August 25, 2026 11:55
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Aug 25, 2026
@hardikdr hardikdr added the area/switch-automation Automation processes for network switch management and operations. label Aug 26, 2026
@hardikdr hardikdr added this to Roadmap Aug 26, 2026
@peanball

Copy link
Copy Markdown
Member

Is this feature to iterate quicker on ZTP script variants during development? I thought the point of us using templates was so we don't have to maintain individual ZTP scripts for each of the switches.

Going forward, we should also have fewer instructions in the ZTP, which should be uniform for all switches (install the agent, which does the rest), right?

@hardikdr

hardikdr commented Aug 27, 2026

Copy link
Copy Markdown
Member Author

Is this feature to iterate quicker on ZTP script variants during development?

Going forward, we should also have fewer instructions in the ZTP, which should be uniform for all switches (install the agent, which does the rest), right?

That's correct.

Agree, the idea is exactly what you have described. This PR is only an option to additionally be able to start the switch with custom ZTP(experimental/during dev) if required, without changing the template here.
We can discuss whether we need such a feature at all; otherwise, we can close this one. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api-change area/switch-automation Automation processes for network switch management and operations. do-not-merge documentation Improvements or additions to documentation

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants