Remove old comment and log line from zone_reconciler.go

[mboersma]

/kind cleanup

What needs cleanup:

A comment in zone_reconciler.go of the privatedns service mentions that a log line should be removed after some time, since it's just there to notify users of a workaround that is no longer needed.

Describe the solution you'd like

Read the comment and the PR it references and verify that it should now be safe to remove this log line. Then remove the comment and log line following it.

Files to change: 1

• zone_reconciler.go

  • cluster-api-provider-azure/azure/services/privatedns/zone_reconciler.go

    Lines 43 to 45 in a0dcdea

    	// TODO: Remove this log in future release. This is only required because older clusters created before https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/1791 will not have capz ownership tags.
    	log.V(1).Info("Tag the DNS manually from azure to manage it with capz."+
    	"Please see https://capz.sigs.k8s.io/topics/custom-dns.html#manage-dns-via-capz-tool", "private DNS", zoneSpec.ResourceName())

[mboersma]

/help
/good-first-issue

[k8s-ci-robot]

@mboersma:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mboersma]

/assign @Tea4menono

See #3827

[k8s-ci-robot]

@mboersma: GitHub didn't allow me to assign the following users: Tea4menono.

Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Tea4menono

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.