update k8s registry domain

[cpanato]

What type of PR is this?
/kind cleanup

Any specific area of the project related to this PR?

/area plugins

What this PR does / why we need it:

• update k8s registry domain

part of kubernetes/k8s.io#4780

/assign @leogr

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

[cpanato]

/assign @jasondellaluce

[leogr]

Since the rules can also run on environments not up-to-date, I'd keep both domains (ie k8s.grc.io and registry.k8s.io).

@LucaGuerra @darryk10 @loresuso wdyt?

[darryk10]

I agree on keeping them both. Some k8s version will still remain in the old domain so it makes sense to whitelist them both. In the future we would consider removing the old one.

[cpanato]

sound good and thanks for the feedback, i will update those and add a comment
@leogr @darryk10

[cpanato]

@leogr @darryk10 added this date to we remove the k8s reference after December
the k8s registry will be frozen on 3rd of April 2023 (https://kubernetes.io/blog/2023/02/06/k8s-gcr-io-freeze-announcement/) so we give some extra time for people to update the clusters.
wdyt?

[leogr]

LGTM

/hold for a second opinion cc @falcosecurity/rules-maintainers @falcosecurity/plugins-maintainers

[poiana]

LGTM label has been added.

Git tree hash: 890f19f92c5002b381bcc06a73be8083ee408446

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, leogr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[LucaGuerra]

/unhold

LGTM, thanks!