Skip to content

Interface based approach #19

Closed
Closed

Description

@vincepri

We should consider offering interfaces for to allow third-party implementations and allow custom sinks. This issue can serve as umbrella for proposals / thoughts.

This issue was initially raised on the mailing list https://groups.google.com/d/msg/kubernetes-sig-architecture/wCWiWf3Juzs/nLtAC41tCwAJ.

Activity

  1. dims commented on Nov 15, 2018

    @dims
    Member
  2. munnerz commented on Nov 15, 2018

    @munnerz
    Member

    I got started on adding a SetLogger function as a PoC for this after talking with @dims earlier in #20.

    The PR is focused around github.com/go-logr/log, and behaves similarly to klog.SetOutput.

    I couldn't work out a way to avoid changing the public facing API for the Verbose type however, without creating distinct types for each V level (which would mean we couldn't support arbitrary V levels).

    Keen to hear thoughts on the implementation/design. It seems useful to have something like this whilst kubernetes itself doesn't support a more structured log format/is still transitioning to whatever log package comes next.

  3. fejta-bot commented on Feb 13, 2019

    @fejta-bot

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle stale

  4. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 13, 2019
  5. fejta-bot commented on Mar 15, 2019

    @fejta-bot

    Stale issues rot after 30d of inactivity.
    Mark the issue as fresh with /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
    /lifecycle rotten

  6. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 15, 2019
  7. detiber commented on Mar 15, 2019

    @detiber

    /remove-lifecycle rotten

  8. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Mar 15, 2019
  9. DirectXMan12 commented on Mar 15, 2019

    @DirectXMan12

    I'm not convinced we need this any more. We now have support for klog as a logr backend, and vice-versa should be merging soon.

  10. vincepri commented on Mar 15, 2019

    @vincepri
    MemberAuthor

    Agreed, this probably can be closed.

  11. detiber commented on Mar 15, 2019

    @detiber

    /close

  12. k8s-ci-robot commented on Mar 15, 2019

    @k8s-ci-robot

    @detiber: Closing this issue.

    Details

    In response to this:

    /close

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions