Re-add inadvertently-dropped deprecation notices

[johngmyers]

No description provided.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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 [hakman]

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

[hakman]

/retest

[johngmyers]

/retest

[johngmyers]

/retest

[hakman]

@johngmyers Seems that something is broken with kubelet, probably when populating the API server URL:

E1119 02:45:17.151948    6143 run.go:74] "command failed" err="failed to run Kubelet:
  failed to initialize kubelet client: host must be a URL or a host:port pair: \"https://\""

[johngmyers]

I have not been able to reproduce this in my own environment.

[hakman]

I have not been able to reproduce this in my own environment.

I have been able to reproduce, but don't understand why it happens yet. On new nodes, /var/lib/kubelet/kubeconfig has clusters[0].cluster.server: https://.

[hakman]

/lgtm cancel

[johngmyers]

I think it's running a kops built off of the branch against a nodeup built off of the presumed merge or vice versa.

[hakman]

Seems similar to what I managed to find. Let's see if manual rebase helped.

[johngmyers]

#14566 was able to bring the cluster up after a rebase.

[hakman]

Maybe something is broken with automated rebase?

[johngmyers]

I suspect pull-kops-build is misconfigured.

[hakman]

If it would be misconfigured, manual rebase would not help use the correct nodeup binary.
/lgtm

[johngmyers]

It could be that a rebase causes pull-kops-build to rerun and update nodeup, whereas another PR landing on master doesn't.

[hakman]

pull-kops-build doesn't actually push things (or at least it's not supposed to).

[johngmyers]

Okay, I'm not sure what uploads nodeup to the bucket.

[hakman]

Each job uploads its own build to the bucket, diferent dirs. Not very optimal, but works ok.