fringe bane
Hi, everyone.
We have used originally, the tridentctl to setup and update our NetApp's backend. We did follow the official documentation and configured successfully TridentBackendConfig. So, we bound the existing backend config with TridentBackendConfig. We can see it is in the Bound phase as excepted:
NAMESPACE NAME BACKEND NAME BACKEND UUID PHASE STATUS
trident backend-ontap-nas ontapnas 8d4029d1-6294-4423-b065-967fbd1e611c Bound Success
In the original config, we have dataLIF configured with some IP. We want to remove this IP by applying an updated TridentBackendConfig , which doesn't include the dataLIF value. The TridentBackendConfig yaml was applied successfully , but the dataLIF IP still exists (we did expect it will be removed). Is that an expected behaviour? If so, how can we remove dataLIF IP or any other value, which was pre-exists before the TridentBackendConfig was configured, using TridentBackendConfig ?
Thanks a lot in advance.
heady lodge