remove "Start watching journald" to avoid plugin log spam

[grosser]

atm we see lots of this, would be nice to not have it 🤷

Start logs from plugin  ...
I1019 21:25:24.665373     571 log_watcher.go:80] Start watching journald","pattern":"plugin-logs"}
End logs from plugin ...

(if it's not there then the output is empty and the "logs from plugin" goes away)

I know this can be avoided by setting log-level to <=2 but it's pretty verbose even for info level "hey this plugin did nothing" 🤷

[k8s-ci-robot]

Hi @grosser. 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/test-infra repository.

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[vteratipally]

I know this can be avoided by setting log-level to <=2 but it's pretty verbose even for info level

Makes sense. Thank you for the PR

[vteratipally]

/remove-lifecycle stale
/ok-to-test
/lgtm

[grosser]

rebased to get tests passing, needs another lgtm

[vteratipally]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grosser, vteratipally

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

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