bootkube: decouple temporary kube-proxy from controller manager phase 2

[sttts]

Blocks #580.

[sttts]

/assign @deads2k @abhinavdahiya

[sttts]

must be base64 I guess

[sttts]

fixed

[abhinavdahiya]

why are there so many secrets with same content? they can easily use one.
please add any new secrets to pkg/asset/manifests.

/hold

[sttts]

why are there so many secrets with same content? they can easily use one.
please add any new secrets to pkg/asset/manifests.

They are temporary as the other manifests in that go file. I don't want to make them more official than they are supposed to be. They are technical debt that needs to be addressed.

[deads2k]

Do you know where this comes from? I would just as soon delete the entire checkpointer and not wait for that pod.

@sjenning same question.

[sttts]

Am fine with deleting the checkpointer right away.

[abhinavdahiya]

#591

[sttts]

rebased and removed all checkpointer code from here.

[sttts]

@squeed this is for you. What should we do here? The kube-proxy is temporary and is must be decoupled from the controller manager. Hence, this temporary file.

[sttts]

Rebased onto #591.

[abhinavdahiya]

/lgtm
/hold cancel

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, sttts

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [abhinavdahiya]

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

[wking]

I dunno what the tf-fmt and tf-lint complaints are about. Maybe just a CI hiccup?

/test tf-fmt
/test tf-lint

[wking]

Do we need to use the admin kubeconfig here (vs. the kubelet kubeconfig)? It may not be a big deal either way if we're going to drop this in the next week or so.