Use service when resolving k8s ips

[marctc]

This PR tries to address #933.

Resolving k8s IPs should try first to resolve via service instead of pods.

[grcevski]

LGTM! Looks good, but I think we should remove the logging we added in the previous PR, since using the function I think creates new logger object every time and it will trigger regardless of the logging level.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.81%. Comparing base (3f9fe7f) to head (9e6339f).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #992      +/-   ##
==========================================
+ Coverage   80.73%   80.81%   +0.08%     
==========================================
  Files         134      134              
  Lines       10718    10721       +3     
==========================================
+ Hits         8653     8664      +11     
+ Misses       1560     1553       -7     
+ Partials      505      504       -1     

Flag	Coverage Δ
integration-test	56.04% <0.00%> (-0.18%)	⬇️
k8s-integration-test	59.56% <100.00%> (+0.07%)	⬆️
oats-test	36.30% <0.00%> (-0.05%)	⬇️
unittests	50.71% <100.00%> (+0.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.