PodFromCoreObject required fix

[adisos]

PodFromCoreObject should not always issue an error / ignore pods not scheduled or not assigned IP addresses.
Only on live cluster mode this is relevant, as opposed to handling pod resources from dir.

[elevran]

@adisos - might a workaround (instead of passing the "live or file based mode" to PodToCoreObject) be to assign a fake IP to all Pods read from files?
Can probably set up a network+netmask from netip and then call Next() on it to generate the addresses (careful no to overlap with CIDR's being queried - CGNAT or localhost ranges may be a reasonable base)

[adisos]

@adisos - might a workaround (instead of passing the "live or file based mode" to PodToCoreObject) be to assign a fake IP to all Pods read from files? Can probably set up a network+netmask from netip and then call Next() on it to generate the addresses (careful no to overlap with CIDR's being queried - CGNAT or localhost ranges may be a reasonable base)

Right, sounds good. Will consider this option as well to handle this issue.

[shireenf-ibm]

A merged PR127 resolves this bug (by assigning a fake IP to Pods from files).
However, keeping this issue open in order to consider using the netip for generating the fake ips in the future.