Accessing pod logs tail about dotnet-kube-client HOT 9 CLOSED

Published v2.2.6.

from dotnet-kube-client.

Yep, pretty sure I can expose it on both :)

from dotnet-kube-client.

Shipped in PSKubectl, can verify it works :)

from dotnet-kube-client.

It works in PSKubectl:

https://github.com/felixfbecker/PSKubectl/blob/d409ff4a3d4bf8e669aaceb4feb2c215b9f9b22a/src/Cmdlets/GetKubeLogCmdlet.cs#L39-L46

from dotnet-kube-client.

Hmm, interesting question - if you run your kubectl command with —v=10 (note the double dash) it should log the API calls it is making which may be of some assistance. I’ll take a look tonight myself and see if anything stands out...

from dotnet-kube-client.

I suspect it haven’t exposed the query parameters needed to scan from the end of the log yet - the API docs list a few promising candidates.

from dotnet-kube-client.

Yeah I just used this command line: kc logs --tail=20 podname -v=10

And it shows the api call of:
GET /api/v1/namespaces/default/pods/dev-madras-aggregator-97988547-vsrnh/log?tailLines=20

I'm assuming the dashboard is using this method or something similar.

I'd love to be able to ask for the last X lines of the logs AND be able to monitor for new incoming lines (ala StreamLogs). But that last monitoring part is just a bonus, if I can ask for say the last 100 lines then refreshing manually is perfectly workable.

from dotnet-kube-client.

Will add it this weekend and publish a new set of packages :)

from dotnet-kube-client.

Sweet! I just upgraded to the v2.2.6 nuget and the Logs() method is perfecto! Thanks a ton for the super quick turn-around @tintoy.

I'm experimenting with the StreamLogs() method and am clearly using it wrong. I can get the first pull of data but am not seeing updates even though I've implemented IObserver. OnNext is never called. Then it stops working at all after I've called this method a couple of times. Has anyone used StreamLogs() successfully?

from dotnet-kube-client.