b9c5c55c09
The original logic was that dumping can stop (for example, due to loosing the connection to the apiserver) and then will start again as long as the container exists. That it duplicates output on restarts is better than skipping output that might not have been dumped yet. But that logic then also dumped the output of containers that have terminated multiple times: - logging is started, dumps all output and stops because the container has terminated - next check finds the container again, sees no active logger, repeats This wasn't a problem for short-lived logging in a custom namespace (the way how it is done for CSI drivers in Kubernetes E2E), but other testsuites (like the one from PMEM-CSI) keep logging running for the entire test suite duration: there duplicate output became a problem when adding driver redeployment as part of the suite's run. To avoid duplicated output for terminated containers, which containers have been handled is now stored permanently. For terminated containers, restarting of dumping is prevented. This comes with the risk that if the previous dumping ended before capturing all output, some output will get lost. Marking the start and stop of the log was also useful when streaming to a single writer and thus gets enabled.
Kubernetes
Kubernetes is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications.
Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.
Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If your company wants to help shape the evolution of technologies that are container-packaged, dynamically scheduled, and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.
To start using Kubernetes
See our documentation on kubernetes.io.
Try our interactive tutorial.
Take a free course on Scalable Microservices with Kubernetes.
To use Kubernetes code as a library in other applications, see the list of published components.
Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.
To start developing Kubernetes
The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.
If you want to build Kubernetes right away there are two options:
You have a working Go environment.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make
You have a working Docker environment.
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release
For the full story, head over to the developer's documentation.
Support
If you need support, start with the troubleshooting guide, and work your way through the process that we've outlined.
That said, if you have questions, reach out to us one way or another.