baremetal: Remove nodeDNSIP from platform status

[cybertron]

Use of this field is being removed in [0] and [1]. Once those two
PRs have merged there will no longer be any use for it.

0: openshift/machine-config-operator#1569
1: openshift/installer#3304

[cybertron]

/hold

Until the dependencies merge.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cybertron
To complete the pull request process, please assign soltysh
You can assign the PR to them by writing /assign @soltysh in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[abhinavdahiya]

/cc @mandre @jcpowermac @rgolangh I think we need something similar for openstack, vpshere and RHV.

[soltysh]

When and where this was deprecated, why that information was not exposed to consumers of the API before?

[cybertron]

Good point, we never actually deprecated this. It was just discovered that we no longer need it thanks to some other changes. For the moment I guess we should deprecate it and leave it in the api. It won't be used by anything, but at least it won't break any consumers.

What is the process for deprecating a field like this?

[deads2k]

@smarterclayton I'm inclined to simply remove instantly and backport quickly to avoid deps. Otherwise, this field become unmaintained and potentially risky. We don't expose general read rights on these resources.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.