SVC and POD discovery

[henderiw]

added service and pod discovery

[henderiw]

For SVC discovery i added an option to define the domain name -> defaults to cluster.local but it might be that someone uses another domain, so i allow it to be modified in the discovery rule.

For SVC i use address = dns-name, hostname = name of the service

For POD i use address = first ip of the pod and hostname = name pf the pod

Any objections?

For SVC we could also use the port in the SVC definition versus the one in the connection profile. Thoughts. I use the one in the connection profile for now, but not sure if this is ok.

[henderiw]

Type: Feature

Why?

When the xNF is deployed in the cluster where the Config-server is running we can discover the xNF through POD IP or SVC hostname/dns-name. This avoids a user to configure labelSelectors for the targets rather than IP addresses. Also in k8s when the pod moves the IP address can change and this avoid a user the reconfigure the IP(s) for the respective xNF

What?

When discovery is configured with a service selector or pos selector the IP/Hostname information is retrieved from the respective KRM resources matching the label selector. For Each selected item a IP/Hostname is identified that is retrieved and used as the address for the Target CR that is created as a consequence for

Release Note:

• Discovery support the usage of label-selector for pods and services within the cluster. Target addresses are automatically derived from the matching KRM objects.