Description of problem:
A customer using RedHat Satellite 6.16.2 to control Microshift hosts (4.16) are having an ever increasing list of network interfaces facts corresponding to the pods internal interfaces.
The main problem is that these interfaces doesn't have a good prefix name (as they are a 16 hex character) so is not easy to setup a good "ignore interfaces with matching identifier" rule.
How reproducible:

Always

**

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Deploy Satellite

2. Deploy host with microshift and subscribe to satellite

3. Deploy some pods on the microshift host

Actual behavior:

facts related to network interfaces continue to grow. Current behavior of "ignore interfaces with matching identifier" only cover wildcard substitution (SQL like %) so rules to clean interfaces aren't rich enough for a good skip/clean method

Expected behavior:

These pods interfaces can be skipped.
Maybe a good idea would be to add regular expression evaluation to "ignore interfaces with matching identifier" so maybe we can add an exclusion rule like:
[0-9a-fA-F]{15}

Business Impact / Additional info: