Migrate to structured logging in cluster-bootstrap

[hiroki-it]

What type of PR is this?

/kind feature

What this PR does / why we need it:

I've worked on migrating to structured logging in cluster-bootstrap :)

In changing loggers and log messages, I read the following documents.

https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/migration-to-structured-logging.md

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1602-structured-logging
- [Other doc]: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/migration-to-structured-logging.md

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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-sigs/prow repository.

[k8s-ci-robot]

Hi @hiroki-it. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hiroki-it
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• staging/src/k8s.io/cluster-bootstrap/OWNERS

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

[neolit123]

it seems cleaner after the diff, but this part of the code is included in community owned tools like kubeadm or external tools that don't benefit from struct logging.

does the KEP actually target cluster-bootstrap or is this your proposal for a change target @hiroki-it ?

/sig insrumentation

[k8s-ci-robot]

@neolit123: The label(s) sig/insrumentation cannot be applied, because the repository doesn't have them.

In response to this:

it seems cleaner after the diff, but this part of the code is included in community owned tools like kubeadm or external tools that don't benefit from struct logging.

does the KEP actually target cluster-bootstrap or is this your proposal for a change target @hiroki-it ?

/sig insrumentation

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-sigs/prow repository.

[neolit123]

/sig instrumentation

[dgrisonnet]

/assign @shiva1333
/triage accepted

[k8s-ci-robot]

@dgrisonnet: GitHub didn't allow me to assign the following users: shiva1333.

Note that only kubernetes 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 @shiva1333
/triage accepted

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-sigs/prow repository.

[dgrisonnet]

/ok-to-test

[hiroki-it]

@neolit123

it seems cleaner after the diff, but this part of the code is included in community owned tools like kubeadm or external tools that don't benefit from struct logging.
does the KEP actually target cluster-bootstrap or is this your proposal for a change target @hiroki-it ?

Thanks for checking PR!

Sorry, I mistakenly thought cluster-bootstrap was a package related to Kubernetes itself, and I didn't realize cluster-bootstrap was a package used by those tools not Kubernetes.

I will check the KEP documentation to see if it is a target 👍