74be9f04fa
The way gingko handles interrupts is: - It starts running AfterSuite hooks in a separate goroutine (this includes cleanupAction hooks) - Once AfterSuite hook is done executing it calls os.Exit(1) on test suite. So how cleanupFunc() that runs via defer in test can be interrupted is: - cleanupFunc starts running via defer (or AfterEach hook) but first thing that function does is to remove cleanupHandle from framework.RemoveCleanupAction. - Test suite receives interrupt from user and AfterSuite block starts executing - remember that while cleanupFunc is running in goroutine#1, AfterSuite is running concurrently in goroutine#2. - AfterSuite hook has bunch of CleanupActions it needs to run which were registered via framework.AddCleanupAction(cleanupFunc) but once cleanupFunc starts executing via defer in the test, it will remove the cleanupHandle from framework's aftersuite hooks. - So if AfterSuite did not had anything to run (because those actions were removed via framework.RemoveCleanupAction then it will simply go to the last framework.AfterEach action and call os.Exit(1) - So if os.Exit(1) is called before cleanupFunc has a chance to finish in defer, it will not complete. |
||
|---|---|---|
| .github | ||
| api | ||
| build | ||
| CHANGELOG | ||
| cluster | ||
| cmd | ||
| docs | ||
| hack | ||
| LICENSES | ||
| logo | ||
| pkg | ||
| plugin | ||
| staging | ||
| test | ||
| third_party | ||
| translations | ||
| vendor | ||
| .bazelrc | ||
| .bazelversion | ||
| .generated_files | ||
| .gitattributes | ||
| .gitignore | ||
| .kazelcfg.json | ||
| BUILD.bazel | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| Makefile.generated_files | ||
| OWNERS | ||
| OWNERS_ALIASES | ||
| README.md | ||
| SECURITY_CONTACTS | ||
| SUPPORT.md | ||
| WORKSPACE | ||
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.