Steven Hawkins
Steven Hawkins
> I don't recall it, but I'm very tired right now shrug. I don't recall anything either.
How reproducible is this? And is there any chance you could try this with the latest 6.0 snapshot?
> where I can get the latest 6.0 snapshot? Maven central snapshots. There was a nightly job added to keep it updated https://github.com/fabric8io/kubernetes-client/blob/0be7c02912e17ee1460340ab462be64afc3396f5/.github/workflows/release-snapshots.yaml
This is expected behavior for the close call - it will close the shared resources of the client and any derived client. There is currently no notion of KubernetesClient pooling...
> Do you still need to close the KubernetesClient after using it? Yes > If necessary, what is the significance of using okhttpclient (ConnectionPool) in the lower layer? Closing the...
Your view is that the DefaultKubernetesClient is a KubernetesClient pool - that has never been the design / implementation. Regardless of the methods you call it is logically a single...
This seems doable, but to be non-breaking would need to introduce another DSL method - withUploadMonitor(monitor).upload(...) - or new upload methods - .monitoredUpload(...) - as the return value from upload...
> for knowing the waiting time of file upload can't we add a timer and log it ? The request seems to be more for a programmatic monitor. It could...
@deod use the dsl to get a Pod (client.pods()...), then use pod.getStatus().getContainerStatuses().get(index).getRestartCount() - where index is the appropriate container index.
@rohanKanojia as far as I can tell the first container restartCount is typically reported as the pod restarts in kubectl. I'm not sure what it does when there are multiple...