1. Proposed title of this feature request
Enable user to edit the day1 NMState of a cluster as day2 operation

2. What is the nature and description of the request?

All deployments methods (IPI,AI, agent-based) allow user to add network configuration of the cluster as nmstate config file. For telcos this file will be complex with many bonds, many vlans, many routes. Since we support day1 nmstate then we recommend to be used and have the cluster ready since the beginning. Nevertheless this let's a design gap when the user would like to make a change on day 2 like adding another vlan on top of a bond, or change the a route, (something that requires knowledge of the existing setup) that will be a big hassle. The user will have either to ssh into the machine and run `nmstatectl show <complex-pattern>` to get the actual state or find out the installation files, then insert it into the nmstate operator, and then apply the changes on top.

The suggestion would be the creation of the actual nmstate into the CRs to be implemented by the platform. E.g. when nmstate operator is being installed, it creates one nncp per node based on what sees in host, and the user can describe/edit those

3. Why does the customer need this? (List the business requirements here)

Partner is asking such question now that they start doing ZTP, and the proposed agent-based or ZTP for 5gcore will have for sure this issue as they add/remove routing entries quite often

4. List any affected packages or components.

NMState operator (probably more)