When starting from an install-config, the NMStateConfig resources are generated from the network settings in agent-config.yaml by the agent create cluster-manifests. However, when starting from ZTP manifests (with no install-config), the dependencies mean that even when running agent create image, the NMStateConfig resources will be overwritten. This is expected when the NMStateConfig contains network config, but it also has the effect of preventing the user setting options in agent-config.yaml that have no equivalents in ZTP (e.g. rendezvousIP).

This can be worked around by replacing the correct NMStateConfig manifest in cluster-manifests and running agent create image again, but this is highly non-obvious to users.

Ideally it would be possible to use the agent-config.yaml in conjunction with the ZTP manifests.