fix: address api_server_authorized_ip_ranges false positives

[simar7]

Discussed in #4331

^{Originally posted by huornlmj March 15, 2023}

Description

Trivy will ignore "authorized_ip_ranges" and will complain if it doesn't find the now deprecated term "api_server_authorized_ip_ranges"

CRITICAL: Cluster does not limit API access to specific IP addresses.

What did you expect to happen?

Not get a false positive, and for Trivy to observe the newer construct as a pass

What happened instead?

A failed scan

[nikpivkin]

@simar7 Isn't this problem solved? However, there is a link to api_server_authorized_ip_ranges in several places.

[simar7]

@simar7 Isn't this problem solved? However, there is a link to api_server_authorized_ip_ranges in several places.

Oh you might be right - what do you mean by link in several places?

[nikpivkin]

@simar7 Here and here. There should be links to authorized_ip_ranges here.

[simar7]

I see. Should those rules be deprecated as well? (And their documentation removed)

[nikpivkin]

@simar7 we just need to fix the links

[simar7]

Closed with aquasecurity/defsec#1381