How to get the log message ?

[kubernetes]

How to get the log message ?

[wandergeek]

Would like to know the same.

[rkamudhan]

@wandergeek I created a PR for this in Kubernetes.

[wandergeek]

Wicked. Can you please link me to the PR?

…

On Tue, 18 Dec 2018 at 9:28 am, Kuralamudhan Ramakrishnan < ***@***.***> wrote: @wandergeek <https://github.com/wandergeek> I created a PR for this in Kubernetes. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAkfNA9dbQURSyDmSlGiJNieubStD2uAks5u6BqogaJpZM4Y4Ie0> .

[mtgto]

I had same issue and add klog.InitFlags, so I can see log in console.
my example:

diff --git a/main.go b/main.go
index d816771..4cb0056 100644
--- a/main.go
+++ b/main.go
@@ -38,6 +38,11 @@ var (
 )

 func main() {
+       flagset := flag.NewFlagSet("klog", flag.ExitOnError)
+       klog.InitFlags(flagset)
+       flagset.Set("logtostderr", "true")
+       flagset.Set("v", "4")
+
        flag.Parse()

        // set up signals so we handle the first shutdown signal gracefully

[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

[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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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.