Define the Switch Deletion Lifecycle

Summary

Define the expected behavior when a Switch resource is deleted.

Currently, the resource primarily provides the switch-specific information used by the operator to generate its ZTP script. It is unclear whether deleting the resource should also affect the physical switch.

Basic example

Possible behaviors include:

• Delete only the Kubernetes resource, without changing the physical switch.
• Reset or decommission the physical switch.
• Perform limited cleanup of configuration managed by the operator.

Motivation

The deletion behavior should be defined before implementing cleanup or reset logic. The appropriate workflow may also depend on how Switch resources are created and managed by external systems.

Start by reviewing the Switch resource definition and the operator workflow that generates its ZTP script. Determine how Switch resources are created and managed by external systems, then document an agreed deletion contract covering the Kubernetes resource and any physical-switch cleanup; done means the expected lifecycle is explicit before implementation begins.