[chore][exporter/loadbalancing] migrate from using deprecated k8s API

[odubajDT]

Link to tracking issue

Part of #43891

[axw]

Code looks good. Does this impact Kubernetes version compatibility at all?

I feel it would be worth adding a changelog entry even if it's not meant to have any user impact, so users can find the change in the release notes in case of any unexpected behaviour.

[odubajDT]

Code looks good. Does this impact Kubernetes version compatibility at all?

I feel it would be worth adding a changelog entry even if it's not meant to have any user impact, so users can find the change in the release notes in case of any unexpected behaviour.

If I am correct, this should shift the k8s version to 1.21 (instead of 1.17), so realistically, this should not affect users using the latest collector builds.

I am not completely sure about the changelog, if yes, it should cover all components linked in the issue and not only the loadbalancing exporter

[axw]

If I am correct, this should shift the k8s version to 1.21 (instead of 1.17), so realistically, this should not affect users using the latest collector builds.

Thanks, that was my read of the docs too. I think we should still call this out as a breaking change, despite Kubernetes 1.20 being ~5 years old. Doesn't hurt does it?

I am not completely sure about the changelog, if yes, it should cover all components linked in the issue and not only the loadbalancing exporter

This PR is only changing the loadbalancing exporter though. We can add an entry for each component change?

[odubajDT]

If I am correct, this should shift the k8s version to 1.21 (instead of 1.17), so realistically, this should not affect users using the latest collector builds.

Thanks, that was my read of the docs too. I think we should still call this out as a breaking change, despite Kubernetes 1.20 being ~5 years old. Doesn't hurt does it?

I am not completely sure about the changelog, if yes, it should cover all components linked in the issue and not only the loadbalancing exporter

This PR is only changing the loadbalancing exporter though. We can add an entry for each component change?

I agree it would not hurt, but effectively it should realistically not affect any user. If you would agree, I would add a changelog entry for all components in this PR, since some of the PRs were already merged.

[axw]

I agree it would not hurt, but effectively it should realistically not affect any user. If you would agree, I would add a changelog entry for all components in this PR, since some of the PRs were already merged.

Ah ok, didn't see the others. SGTM.