Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Kubelet status manager sync the status of local Pods **What this PR does / why we need it**: In the kubelet, when using `--pod-manifest-path` the kubelet creates static pods but doesn't update the status accordingly in the `PodList`. This PR fixes the incorrect status of each Pod in the kubelet's `PodList`. This is the setup used to reproduce the issue: **manifest**: ```bash cat ~/kube/staticpod.yaml ``` ```yaml apiVersion: v1 kind: Pod metadata: labels: app: nginx name: nginx namespace: default spec: hostNetwork: true containers: - name: nginx image: nginx:latest imagePullPolicy: IfNotPresent volumeMounts: - name: os-release mountPath: /usr/share/nginx/html/index.html readOnly: true volumes: - name: os-release hostPath: path: /etc/os-release ``` **kubelet**: ```bash ~/go/src/k8s.io/kubernetes/_output/bin/kubelet --pod-manifest-path ~/kube/ --cloud-provider="" --register-node --kubeconfig kubeconfig.yaml ``` You can observe this by querying the kubelet API `/pods`: ```bash curl -s 127.0.0.1:10255/pods | jq . ``` ```json { "kind": "PodList", "apiVersion": "v1", "metadata": {}, "items": [ { "metadata": { "name": "nginx-nodeName", "namespace": "default", "selfLink": "/api/v1/namespaces/default/pods/nginx-nodeName", "uid": "0fdfa64c73d9de39a9e5c05ef7967e72", "creationTimestamp": null, "labels": { "app": "nginx" }, "annotations": { "kubernetes.io/config.hash": "0fdfa64c73d9de39a9e5c05ef7967e72", "kubernetes.io/config.seen": "2017-12-12T18:42:46.088157195+01:00", "kubernetes.io/config.source": "file" } }, "spec": { "volumes": [ { "name": "os-release", "hostPath": { "path": "/etc/os-release", "type": "" } } ], "containers": [ { "name": "nginx", "image": "nginx:latest", "resources": {}, "volumeMounts": [ { "name": "os-release", "readOnly": true, "mountPath": "/usr/share/nginx/html/index.html" } ], "terminationMessagePath": "/dev/termination-log", "terminationMessagePolicy": "File", "imagePullPolicy": "IfNotPresent" } ], "restartPolicy": "Always", "terminationGracePeriodSeconds": 30, "dnsPolicy": "ClusterFirst", "nodeName": "nodeName", "hostNetwork": true, "securityContext": {}, "schedulerName": "default-scheduler", "tolerations": [ { "operator": "Exists", "effect": "NoExecute" } ] }, "status": { "phase": "Pending", "conditions": [ { "type": "PodScheduled", "status": "True", "lastProbeTime": null, "lastTransitionTime": "2017-12-12T17:42:51Z" } ] } } ] } ``` The status of the nginx `Pod` will remain in **Pending** state phase. ```bash curl -I 127.0.0.1 HTTP/1.1 200 OK ``` It's reported as expected on the apiserver side: ```bash kubectl get po --all-namespaces -w NAMESPACE NAME READY STATUS RESTARTS AGE default nginx-nodeName 0/1 Pending 0 0s default nginx-nodeName 1/1 Running 0 2s ``` It doesn't work either with a standalone kubelet: ```bash ~/go/src/k8s.io/kubernetes/_output/bin/kubelet --pod-manifest-path ~/kube/ --cloud-provider="" --register-node false ``` **Special notes for your reviewer**: **Release note**: ```release-note NONE ``` |
||
---|---|---|
.github | ||
api | ||
build | ||
cluster | ||
cmd | ||
docs | ||
examples | ||
Godeps | ||
hack | ||
logo | ||
pkg | ||
plugin | ||
staging | ||
test | ||
third_party | ||
translations | ||
vendor | ||
.bazelrc | ||
.generated_files | ||
.gitattributes | ||
.gitignore | ||
.kazelcfg.json | ||
BUILD.bazel | ||
CHANGELOG-1.2.md | ||
CHANGELOG-1.3.md | ||
CHANGELOG-1.4.md | ||
CHANGELOG-1.5.md | ||
CHANGELOG-1.6.md | ||
CHANGELOG-1.7.md | ||
CHANGELOG-1.8.md | ||
CHANGELOG-1.9.md | ||
CHANGELOG-1.10.md | ||
CHANGELOG.md | ||
code-of-conduct.md | ||
CONTRIBUTING.md | ||
labels.yaml | ||
LICENSE | ||
Makefile | ||
Makefile.generated_files | ||
OWNERS | ||
OWNERS_ALIASES | ||
README.md | ||
SUPPORT.md | ||
WORKSPACE |
Kubernetes

Kubernetes is an open source system for managing containerized applications across multiple hosts; providing 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 you are a company that 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 Kubernetes
See our documentation on kubernetes.io.
Try our interactive tutorial.
Take a free course on Scalable Microservices with Kubernetes.
To start developing Kubernetes
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.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/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.