93c8014f34
Tests that are written as if they had the entire apiserver for themselves have
been a recurring problem. Ensuring that would limit us to start a new apiserver
and potentially other components (scheduler, resource claim controller) in
serial tests, which is slower.
Therefore all tests should create a test namespace and derive their driver name
from that, then create slices, classes and claims so that each test only uses
its own instances. If they don't, one test may allocate devices published by
another test. We cannot enforce how tests create their objects because there
may be many different valid ways, but we can detect incorrect allocation by
watching claims and checking their allocation result.
This detects the missing driver name selector in the explicit extended resource
tests (fixed in master already) like this:
Claim all-explicitextendedresource-dk28h/my-pod-extended-resources-xtcgq has allocated device v1.DeviceRequestAllocationResult{Request:"container-0-request-0", Driver:"driver-all-evictclusterwithrule-slh8g", Pool:"cluster", Device:"device-700", AdminAccess:(*bool)(nil), Tolerations:[]v1.DeviceToleration(nil), BindingConditions:[]string(nil), BindingFailureConditions:[]string(nil), ShareID:(*types.UID)(nil), ConsumedCapacity:map[v1.QualifiedName]resource.Quantity(nil)} from a driver in some other test (driver-all-evictclusterwithrule-slh8g):
<*v1.ResourceClaim | 0x2d8b54b4820>:
[...]
The ResourceClaim status simulates device allocation. To avoid false positives,
it needs to use unique driver names like the other tests.
Kubernetes (K8s)
Kubernetes, also known as K8s, is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for the 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 K8s
See our documentation on kubernetes.io.
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 K8s
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.
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.
Community Meetings
The Calendar has the list of all the meetings in the Kubernetes community in a single location.
Adopters
The User Case Studies website has real-world use cases of organizations across industries that are deploying/migrating to Kubernetes.
Governance
Kubernetes project is governed by a framework of principles, values, policies and processes to help our community and constituents towards our shared goals.
The Kubernetes Community is the launching point for learning about how we organize ourselves.
The Kubernetes Steering community repo is used by the Kubernetes Steering Committee, which oversees governance of the Kubernetes project.
Roadmap
The Kubernetes Enhancements repo provides information about Kubernetes releases, as well as feature tracking and backlogs.