f9a6ac077e
For AWS EBS, a volume can only be attached to a node in the same AZ. The scheduler must therefore detect if a volume is being attached to a pod, and ensure that the pod is scheduled on a node in the same AZ as the volume. So that the scheduler need not query the cloud provider every time, and to support decoupled operation (e.g. bare metal) we tag the volume with our placement labels. This is done automatically by means of an admission controller on AWS when a PersistentVolume is created backed by an EBS volume. Support for tagging GCE PVs will follow. Pods that specify a volume directly (i.e. without using a PersistentVolumeClaim) will not currently be scheduled correctly (i.e. they will be scheduled without zone-awareness). |
||
|---|---|---|
| .. | ||
| developer-guides | ||
| adding-an-APIGroup.md | ||
| api_changes.md | ||
| api-conventions.md | ||
| automation.md | ||
| cherry-picks.md | ||
| cli-roadmap.md | ||
| client-libraries.md | ||
| coding-conventions.md | ||
| collab.md | ||
| development.md | ||
| e2e-tests.md | ||
| faster_reviews.md | ||
| flaky-tests.md | ||
| getting-builds.md | ||
| git_workflow.png | ||
| how-to-doc.md | ||
| instrumentation.md | ||
| issues.md | ||
| kubectl-conventions.md | ||
| kubemark-guide.md | ||
| logging.md | ||
| making-release-notes.md | ||
| owners.md | ||
| profiling.md | ||
| pull-requests.md | ||
| README.md | ||
| releasing.md | ||
| scheduler_algorithm.md | ||
| scheduler.md | ||
| update-release-docs.md | ||
| writing-a-getting-started-guide.md | ||
PLEASE NOTE: This document applies to the HEAD of the source tree
If you are using a released version of Kubernetes, you should refer to the docs that go with that version.
The latest release of this document can be found [here](http://releases.k8s.io/release-1.1/docs/devel/README.md).Documentation for other releases can be found at releases.k8s.io.
Kubernetes Developer Guide
The developer guide is for anyone wanting to either write code which directly accesses the Kubernetes API, or to contribute directly to the Kubernetes project. It assumes some familiarity with concepts in the User Guide and the Cluster Admin Guide.
The process of developing and contributing code to the Kubernetes project
-
On Collaborative Development (collab.md): Info on pull requests and code reviews.
-
GitHub Issues (issues.md): How incoming issues are reviewed and prioritized.
-
Pull Request Process (pull-requests.md): When and why pull requests are closed.
-
Faster PR reviews (faster_reviews.md): How to get faster PR reviews.
-
Getting Recent Builds (getting-builds.md): How to get recent builds including the latest builds that pass CI.
-
Automated Tools (automation.md): Descriptions of the automation that is running on our github repository.
Setting up your dev environment, coding, and debugging
-
Development Guide (development.md): Setting up your development environment.
-
Hunting flaky tests (flaky-tests.md): We have a goal of 99.9% flake free tests. Here's how to run your tests many times.
-
Logging Conventions (logging.md]: Glog levels.
-
Profiling Kubernetes (profiling.md): How to plug in go pprof profiler to Kubernetes.
-
Instrumenting Kubernetes with a new metric (instrumentation.md): How to add a new metrics to the Kubernetes code base.
-
Coding Conventions (coding-conventions.md): Coding style advice for contributors.
Developing against the Kubernetes API
-
API objects are explained at http://kubernetes.io/third_party/swagger-ui/.
-
Annotations (docs/user-guide/annotations.md): are for attaching arbitrary non-identifying metadata to objects. Programs that automate Kubernetes objects may use annotations to store small amounts of their state.
-
API Conventions (api-conventions.md): Defining the verbs and resources used in the Kubernetes API.
-
API Client Libraries (client-libraries.md): A list of existing client libraries, both supported and user-contributed.
Writing plugins
-
Authentication Plugins (docs/admin/authentication.md): The current and planned states of authentication tokens.
-
Authorization Plugins (docs/admin/authorization.md): Authorization applies to all HTTP requests on the main apiserver port. This doc explains the available authorization implementations.
-
Admission Control Plugins (admission_control)
Building releases
-
Making release notes (making-release-notes.md): Generating release nodes for a new release.
-
Releasing Kubernetes (releasing.md): How to create a Kubernetes release (as in version) and how the version information gets embedded into the built binaries.