Remove messages about kodata in task logs

[tomgeorge]

Changes

Change the loggers in entrypoint, creds-init, and pullrequest-init to use the default Zap sugared logger.

Previously, these loggers cluttered Task output with messages about being unable to fetch ko information.

This addresses #1145

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added) No functionality changed
• Includes docs (if user facing) N/A
• Commit messages follow commit message best practices

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task to build and release this image.

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

[tekton-robot]

Hi @tomgeorge. Thanks for your PR.

I'm waiting for a tektoncd 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.

[vdemeester]

/ok-to-test

[tekton-robot]

The following is the coverage report on pkg/.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	54.1%	55.3%	1.2

[vdemeester]

/lgtm

[chmouel]

very cool thanks for fixing this

/lgtm

[afrittoli]

Thank you for addressing this issue!

The kantive logging package gives features like the ability of changing log level at run time - while that is appropriate for the controllers I think we don't really need it for the tasks, so I think this change is nice.

Pipeline resources and entrypoint did not honor the config settings in from the logging configuration map anyways, and this doesn't change that.

What I think would be nice to have - but it's not related to this PR - is some documentation in https://github.com/tektoncd/pipeline/blob/master/docs/install.md#configuring-tekton-pipelines about how to configure logging and what part of Tekton are affected by it.

/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

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

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

[bobcatfish]