chore: Use klog structured logging

[dargudear-google]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
To have structured logging with klog

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #13

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dargudear-google
Once this PR has been reviewed and has the lgtm label, please assign aramase for approval. For more information see the 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:

• OWNERS

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

[k8s-ci-robot]

Hi @dargudear-google. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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]

@dargudear-google: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test

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.

[aramase]

/retitle chore: Use klog structured logging
/ok-to-test

[aramase]

/triage accepted

[codecov-commenter]

Codecov Report

❌ Patch coverage is 21.27660% with 37 lines in your changes missing coverage. Please review.
✅ Project coverage is 44.08%. Comparing base (9f4597d) to head (d7ea22c).
⚠️ Report is 63 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/main.go	0.00%	30 Missing ⚠️
internal/controller/secretsync_controller.go	53.84%	6 Missing ⚠️
internal/controller/conditions.go	75.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #148       +/-   ##
===========================================
- Coverage   56.32%   44.08%   -12.25%     
===========================================
  Files          12       12               
  Lines        1051     1082       +31     
===========================================
- Hits          592      477      -115     
- Misses        415      572      +157     
+ Partials       44       33       -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[aramase]

First pass.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale