watchCacheInterval serves as an abstraction over a source of watchCacheEvents. It maintains a window of events over an underlying source and these events can be served using the exposed Next() API. The main intent for doing things this way is to introduce an upper bound of memory usage for starting a watch and reduce the maximum possible time interval for which the lock would be held while events are copied over. The source of events for the interval is typically either the watchCache circular buffer, if events being retrieved need to be for resource versions > 0 or the underlying implementation of Store, if resource version = 0. Furthermore, an interval can be either valid or invalid at any given point of time. The notion of validity makes sense only in cases where the window of events in the underlying source can change over time - i.e. for watchCache circular buffer. When the circular buffer is full and an event needs to be popped off, watchCache::startIndex is incremented. In this case, an interval tracking that popped event is valid only if it has already been copied to its internal buffer. However, for efficiency we perform that lazily and we mark an interval as invalid iff we need to copy events from the watchCache and we end up needing events that have already been popped off. This translates to the following condition: watchCacheInterval::startIndex >= watchCache::startIndex. When this condition becomes false, the interval is no longer valid and should not be used to retrieve and serve elements from the underlying source. Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> |
||
---|---|---|
.github | ||
api | ||
build | ||
CHANGELOG | ||
cluster | ||
cmd | ||
docs | ||
hack | ||
LICENSES | ||
logo | ||
pkg | ||
plugin | ||
staging | ||
test | ||
third_party | ||
vendor | ||
.generated_files | ||
.gitattributes | ||
.gitignore | ||
.golangci.yaml | ||
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 |
Kubernetes (K8s)

Kubernetes, also known as K8s, 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 K8s
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 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.
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.