github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-08 20:50:24 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #8602 from caesarxuchao/rC-to-rc

Browse Source 
in docs, update replicationController to replicationcontroller
This commit is contained in:
Dawn Chen
2015-05-21 09:49:35 -07:00
parent 8fe43514ea 5b8b5a0844
commit fdb44a9ad2
14 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/man/kube-apiserver.1.md
View File

@@ -9,7 +9,7 @@ kube-apiserver \- Provides the API for kubernetes orchestration.
# DESCRIPTION
The **kubernetes** API server validates and configures data for 3 types of objects: pods, services, and replicationControllers. Beyond just servicing REST operations, the API Server does two other things as well: 1. Schedules pods to worker nodes. Right now the scheduler is very simple. 2. Synchronize pod information (where they are, what ports they are exposing) with the service configuration.
The **kubernetes** API server validates and configures data for 3 types of objects: pods, services, and replicationcontrollers. Beyond just servicing REST operations, the API Server does two other things as well: 1. Schedules pods to worker nodes. Right now the scheduler is very simple. 2. Synchronize pod information (where they are, what ports they are exposing) with the service configuration.
The the kube-apiserver several options.

2
docs/man/kube-controller-manager.1.md
View File

@@ -9,7 +9,7 @@ kube-controller-manager \- Enforces kubernetes services.
# DESCRIPTION
The **kubernetes** controller manager is really a service that is layered on top of the simple pod API. To enforce this layering, the logic for the replicationController is actually broken out into another server. This server watches etcd for changes to replicationController objects and then uses the public Kubernetes API to implement the replication algorithm.
The **kubernetes** controller manager is really a service that is layered on top of the simple pod API. To enforce this layering, the logic for the replicationcontroller is actually broken out into another server. This server watches etcd for changes to replicationcontroller objects and then uses the public Kubernetes API to implement the replication algorithm.
The kube-controller-manager has several options.

2
docs/man/man1/kube-apiserver.1
View File

@@ -10,7 +10,7 @@ kube\-apiserver \- Provides the API for kubernetes orchestration.
.SH DESCRIPTION
.PP
The \fBkubernetes\fP API server validates and configures data for 3 types of objects: pods, services, and replicationControllers. Beyond just servicing REST operations, the API Server does two other things as well: 1. Schedules pods to worker nodes. Right now the scheduler is very simple. 2. Synchronize pod information (where they are, what ports they are exposing) with the service configuration.
The \fBkubernetes\fP API server validates and configures data for 3 types of objects: pods, services, and replicationcontrollers. Beyond just servicing REST operations, the API Server does two other things as well: 1. Schedules pods to worker nodes. Right now the scheduler is very simple. 2. Synchronize pod information (where they are, what ports they are exposing) with the service configuration.
.PP
The the kube\-apiserver several options.

2
docs/man/man1/kube-controller-manager.1
View File

@@ -10,7 +10,7 @@ kube\-controller\-manager \- Enforces kubernetes services.
.SH DESCRIPTION
.PP
The \fBkubernetes\fP controller manager is really a service that is layered on top of the simple pod API. To enforce this layering, the logic for the replicationController is actually broken out into another server. This server watches etcd for changes to replicationController objects and then uses the public Kubernetes API to implement the replication algorithm.
The \fBkubernetes\fP controller manager is really a service that is layered on top of the simple pod API. To enforce this layering, the logic for the replicationcontroller is actually broken out into another server. This server watches etcd for changes to replicationcontroller objects and then uses the public Kubernetes API to implement the replication algorithm.
.PP
The kube\-controller\-manager has several options.

2
docs/man/man1/kubectl-get.1
View File

@@ -166,7 +166,7 @@ of the \-\-template flag, you can filter the attributes of the fetched resource(
$ kubectl get pods
// List a single replication controller with specified NAME in ps output format.
$ kubectl get replicationController web
$ kubectl get replicationcontroller web
// List a single pod in JSON output format.
$ kubectl get \-o json pod web\-pod\-13je7