Merge pull request #29436 from lixiaobing10051267/masterPath

Automatic merge from submit-queue

Give the complete and correct path to client/kubectl/apiserver related

for client/kubectl, “client/unversioned","kubectl/describe.go","kubectl/stop.go", it is not easy to find the location, better add "pkg/".
for apiserver, "registry/daemon", also better add "pkg/", and daemon not exists, should be "daemonset".
This commit is contained in:
k8s-merge-robot 2016-07-25 12:56:20 -07:00 committed by GitHub
commit 2f545e1f45

View File

@ -195,15 +195,15 @@ some discussion of this topic).
#### Client #### Client
- Add support for DaemonSet commands to kubectl and the client. Client code was - Add support for DaemonSet commands to kubectl and the client. Client code was
added to client/unversioned. The main files in Kubectl that were modified are added to pkg/client/unversioned. The main files in Kubectl that were modified are
kubectl/describe.go and kubectl/stop.go, since for other calls like Get, Create, pkg/kubectl/describe.go and pkg/kubectl/stop.go, since for other calls like Get, Create,
and Update, the client simply forwards the request to the backend via the REST and Update, the client simply forwards the request to the backend via the REST
API. API.
#### Apiserver #### Apiserver
- Accept, parse, validate client commands - Accept, parse, validate client commands
- REST API calls are handled in registry/daemon - REST API calls are handled in pkg/registry/daemonset
- In particular, the api server will add the object to etcd - In particular, the api server will add the object to etcd
- DaemonManager listens for updates to etcd (using Framework.informer) - DaemonManager listens for updates to etcd (using Framework.informer)
- API objects for DaemonSet were created in expapi/v1/types.go and - API objects for DaemonSet were created in expapi/v1/types.go and