fd5b2efa76
migrate the cpumanager code to contextual logging design musings: - golang contexts "[...] carries deadlines, cancellation signals, and other request-scoped values across API boundaries and between processes." (see: https://pkg.go.dev/context#pkg-overview). Thus, it generally makes sense to add contexts to most of the APIs and functions as the resource management is done in the admission flow, when ultimately we process a request and we have time bounds; - however, receiving a context from the outside and depending on it kind also conflicts with the goal of having uniform logging and " - attach key/value pairs that get included in all log messages - add names that describe which component or operation triggered a log messages" (see: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/3077-contextual-logging#summary) Some of this conflict is due to the transitional nature of the PRs which we do when updating the codelet codebase. We can envision a final state on which the top level caller adds identifying information like pod UID and pod namespace/name pair; but up until all the calling chain is updated and wired, the results are gonna be inconsistent. - continuing from the point above, the most realistic transition plan for the kubelet is outlined in https://github.com/kubernetes/kubernetes/issues/130069 . Since we do want to move in parallel and migrate on a subsystem-by-subsystem basis, each subsystem will be in charge to add the data they want to their contexts. I think this is the only reasonnable way forward, and the cost will be overhead and redundancy. We should do sweeping changes to uniform the flows once we completed the full transition to ensure uniformity. - there are some well known packages which want to operate by design only in in-memory data structure, which arguably can't block. Shoehorning a context feels not great. Instead, we intentionally pass only the logger, which still is the core idea of contextual logging (see: https://github.com/kubernetes/kubernetes/pull/125912#discussion_r1935919144) examples are the topology subpackage and the cpu_assignment logic (takeByTopology and friends) Signed-off-by: Francesco Romani <fromani@redhat.com>
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.