jiebi/CodeConvo huggingface dataset:
Change:
The script actually defaults to k8s version 1.1.8, but the docs says it is 1.1.4
Thank you for the PR, Mike!

Discussion:
Internet to download the necessary files, while worker nodes do not. 3. These guide is tested OK on Ubuntu 14.04 LTS 64bit server, but it can not work with Ubuntu 15 which uses systemd instead of upstart. <del> 4. Dependencies of this guide: etcd-2.2.1, flannel-0.5.5, k8s-1.1.4, may work with higher versions. </del> <ins> 4. Dependencies of this guide: etcd-2.2.1, flannel-0.5.5, k8s-1.1.8, may work with higher versions. </ins> 5. All the remote servers can be ssh logged in without a password by using key authentication.

#### Configure and start the Kubernetes cluster The startup process will first download all the required binaries automatically. <del> By default etcd version is 2.2.1, flannel version is 0.5.5 and k8s version is 1.1.4. </del> <ins> By default etcd version is 2.2.1, flannel version is 0.5.5 and k8s version is 1.1.8. </ins> You can customize your etcd version, flannel version, k8s version by changing corresponding variables `ETCD_VERSION` , `FLANNEL_VERSION` and `KUBE_VERSION` like following. ```shell <del> $ export KUBE_VERSION=1.0.5 </del> <ins> $ export KUBE_VERSION=1.1.8 </ins> $ export FLANNEL_VERSION=0.5.0 $ export ETCD_VERSION=2.2.0 ```
Change:
This page is woefully out of date: docs/user-guide/known-issues/ We should move the content to the 1.0 release notes and delete the page. cc
already contains this info. I'll delete the file.
cc I can't see how to delete a file using this new edit-in-place interface. Maybe it's a permission issue?
These items are all in flight - But I have no power to assign or merge anything.
Nice work, David. :)

Discussion:
- title: Other Resources section: <del> - title: Known Issues path: /docs/user-guide/known-issues/ </del> - title: Kubernetes Issue Tracker on GitHub path: https://github.com/kubernetes/kubernetes/issues/ - title: Report a Security Vulnerability

* [Troubleshooting your application](/docs/user-guide/application-troubleshooting) - Useful for users who are deploying code into Kubernetes and wondering why it is not working. * [Troubleshooting your cluster](/docs/admin/cluster-troubleshooting) - Useful for cluster administrators and people whose Kubernetes cluster is unhappy. <del> You should also check the [known issues](/docs/user-guide/known-issues) for the release you're using. </del> <ins> You should also check the known issues for the [release](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md) you're using. </ins> ### Getting help

<del> --- --- This document summarizes known issues with existing Kubernetes releases. Please consult this document before filing new bugs. ### Release 1.0.1 * `exec` liveness/readiness probes leak resources due to Docker exec leaking resources (#10659) * `docker load` sometimes hangs which causes the `kube-apiserver` not to start.  Restarting the Docker daemon should fix the issue (#10868) * The kubelet on the master node doesn't register with the `kube-apiserver` so statistics aren't collected for master daemons (#10891) * Heapster and InfluxDB both leak memory (#10653) * Wrong node cpu/memory limit metrics from Heapster (https://github.com/GoogleCloudPlatform/heapster/issues/399) * Services that set `type=LoadBalancer` can not use port `10250` because of Google Compute Engine firewall limitations * Add-on services can not be created or deleted via `kubectl` or the Kubernetes API (#11435) * If a pod with a GCE PD is created and deleted in rapid succession, it may fail to attach/mount correctly leaving PD data inaccessible (or corrupted in the worst case). (http://issue.k8s.io/11231#issuecomment-122049113) * Suggested temporary work around: introduce a 1-2 minute delay between deleting and recreating a pod with a PD on the same node. * Explicit errors while detaching GCE PD could prevent PD from ever being detached (#11321) * GCE PDs may sometimes fail to attach (#11302) * If multiple Pods use the same RBD volume in read-write mode, it is possible data on the RBD volume could get corrupted. This problem has been found in environments where both apiserver and etcd rebooted and Pods were redistributed. * A workaround is to ensure there is no other Ceph client using the RBD volume before mapping RBD image in read-write mode. For example, `rados -p poolname listwatchers image_name.rbd` can list RBD clients that are mapping the image. </del>
Change:
I wish /docs/admin/cluster-components/dns/ page existed It's linked from

Discussion:
automatically assigned the `default` service account of the same namespace.  If you get the raw json or yaml for a pod you have created (e.g. `kubectl get pods/podname -o yaml`), you can see the `spec.serviceAccount` field has been <del> [automatically set](working-with-resources/#resources-are-automatically-modified). </del> <ins> [automatically set](/docs/user-guide/working-with-resources/#resources-are-automatically-modified). </ins> You can access the API using a proxy or with a client library, as described in [Accessing the Cluster](/docs/user-guide/accessing-the-cluster/#accessing-the-api-from-a-pod).

TODO: Test and explain how to use additional non-K8s secrets with an existing service account. TODO explain: <del> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </del>  No newline at end of file <ins> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </ins>
Change:
In issuing the push to in the "Rolling Updates" section: docker push read: gcloud docker push
PR submitted:
cc
Thanks, Al; confirmed that is the command by talking to the GCR team today.

Discussion:
```shell docker build -t gcr.io/PROJECT_ID/hello-node:v2 . <del> docker push gcr.io/PROJECT_ID/hello-node:v2 </del> <ins> gcloud docker push gcr.io/PROJECT_ID/hello-node:v2 </ins> ``` Building and pushing this updated image should be much quicker as we take full advantage of the Docker cache.
Change:
Secrets and ConfigMap are logically siblings to one another and this should be reflected in the doc. Currently, the ConfigMap docs are linked to from 'Configuring Kubernetes' and the Secrets docs are linked only from the 'Concept Guide'. I suggest we do one of the following: Link from 'Concept Guide' to ConfigMap and remove the link to the ConfigMap docs from the 'Configuring Kubernetes' list Link from 'Configuring Kubernetes' to the Secrets docs and remove the link in the Concept Guide. We also need to add a stanza in the Concept Guide for ConfigMap, whether we link to the existing docs from there or not. Thoughs, ?
Added information on Secretes to ConfigMap, and they're both under the same header in guides. Should fix this the rest of the way with the site reorg.

Discussion:
``` Minikube contains a built-in Docker daemon that for running containers. <del> If you use another Docker daemon for building your containers, you will have to publish them to a registry before minikube can pull them. </del> <ins> If you use another Docker daemon for building your containers, you will have to publish them to a registry before minikube can pull them. </ins> You can use minikube's built in Docker daemon to avoid this extra step of pushing your images. Use the built-in Docker daemon with: ```shell eval $(minikube docker-env) ``` <del> This command sets up the Docker environment variables so a Docker client can communicate with the minikube Docker daemon: </del> <ins> This command sets up the Docker environment variables so a Docker client can communicate with the minikube Docker daemon. Minikube currently supports only docker version 1.11.1 on the server, which is what is supported by Kubernetes 1.3. With a newer docker version you'll get this [issue](https://github.com/kubernetes/minikube/issues/338). </ins> ```shell docker ps
Change:
I wish /docs/admin/cluster-components/ Didn't have a broken link to Cluster Logging with ELK

Discussion:
docs/user-guide/logging/#cluster-level-logging-to-google-cloud-logging) * [Cluster-level Logging with Elasticsearch and Kibana]( <del> docs/user-guide/logging/#cluster-level-logging-with-elasticsearch-and-kibana) </del> <ins> docs/getting-started-guides/logging-elasticsearch/) </ins> ## Node components
Change:
Below command has a syntax error Add a single quotation or double quotation for the template part can make it work. PR will be sent later.

Discussion:
```shell $ export SERVICE_IP=$(kubectl get service nginx-service -o go-template={% raw %}{{.spec.clusterIP}}{% endraw %}) <del> $ export SERVICE_PORT=$(kubectl get service nginx-service -o go-template={% raw %}{{(index .spec.ports 0).port}}{% endraw %}) </del> <ins> $ export SERVICE_PORT=$(kubectl get service nginx-service -o go-template='{% raw %}{{(index .spec.ports 0).port}}{% endraw %}') </ins> $ curl http://${SERVICE_IP}:${SERVICE_PORT} ```
Change:
For any section deeplink, the linked section title and some content is now obscured in the viewport by the floating header menu. Example: ! This occurs regardless of browser window width: ! Yay responsive design, but :cry: being able to actually read the content w/o scrolling.
Thanks to for the fix!

Discussion:
width: 100% $toc-margin: 15px <del> $header-clearance: 40px </del> <ins> $header-clearance: $header-height + 20px </ins> * + h2, * + h3, * + h4, * + h5, * + h6 margin-top: 30px

padding-bottom: 10px border-bottom: 1px solid #cccccc <ins> // Make sure anchor links aren't hidden by the header &:before display: block content: " " margin-top: -$header-clearance height: $header-clearance visibility: hidden </ins> h1 font-size: 32px padding-right: 60px
Change:
I wish /docs/samples/ didn't have a broken Petstore link
For the record, the broken link in question is located here: The actual link should be to . At least, that's what it is in the project. Not sure which one we should change ( makes more sense to me).

Discussion:
- title: Nodejs + Mongo path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/nodesjs-mongodb - title: Petstore <del> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8spetstore/ </del> <ins> path: https://github.com/kubernetes/kubernetes/tree/release-1.2/examples/k8petstore/ </ins>
Change:
Step 2 of says that it uses the generated earlier. In fact it also uses the ca- generated earlier.

Discussion:
### Configure TLS Worker nodes require three keys: `ca.pem`, `worker.pem`, and `worker-key.pem`.  We've already generated <del> `ca.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </del> <ins> `ca.pem` and `ca-key.pem` for use on the Master.  The worker public/private keypair should be generated for each Kubernetes node. </ins> 1.  Create the file `worker-openssl.cnf` with the following contents.

IP.1 = $ENV::WORKER_IP ``` <del> 2.  Generate the necessary TLS assets for this worker. This relies on the worker's IP address, and the `ca.pem` file generated earlier in the guide. </del> <ins> 2.  Generate the necessary TLS assets for this worker. This relies on the worker's IP address, and the `ca.pem` and `ca-key.pem` files generated earlier in the guide. </ins> ```shell # Export this worker's IP address.

mkdir -p /etc/cni/net.d # Make the network configuration file <del> cat >/etc/rkt/net.d/10-calico.conf <<EOF </del> <ins> cat >/etc/cni/net.d/10-calico.conf <<EOF </ins> { "name": "calico-k8s-network", "type": "calico",
Change:
In there is initial check for but then it is not put in checks. I mean there are checks like but then in consecutive code there are things like following where is not mentioned.

Discussion:
lsb_dist="$(echo ${lsb_dist} | tr '[:upper:]' '[:lower:]')" case "${lsb_dist}" in <del> amzn|centos|debian|ubuntu) </del> <ins> amzn|centos|debian|ubuntu|fedora) </ins> ;; *) <del> echo "Error: We currently only support ubuntu|debian|amzn|centos." </del> <ins> echo "Error: We currently only support ubuntu|debian|amzn|centos|fedora." </ins> exit 1 ;; esac

ifconfig docker0 down yum -y -q install bridge-utils && brctl delbr docker0 && service docker restart ;; <del> centos) </del> <ins> centos|fedora) </ins> DOCKER_CONF="/etc/sysconfig/docker" sed -i "/^OPTIONS=/ s|( --mtu=.*)?'$| --mtu=${FLANNEL_MTU} --bip=${FLANNEL_SUBNET}'|" ${DOCKER_CONF} if ! command_exists ifconfig; then
Change:
When I try creating the example given in that page, I get this error: Indeed, after I change the value of from a map to a list containing that map, the create succeeds. Here is the corrected source:

Discussion:
role: db ingress: - from: <del> podSelector: matchLabels: role: frontend </del> <ins> - podSelector: matchLabels: role: frontend </ins> ports: - protocol: tcp port: 6379
Change:
Here "Cluster" is a broken link: Perhaps this is an issue with : there is no in master branch, but there in branch. Same issue with below on the same page.

Discussion:
Here is the same information in a picture which shows how the pods might be placed on specific nodes. <del> ![Cluster](https://raw.githubusercontent.com/kubernetes/kubernetes/{{page.githubbranch}}/examples/blog-logging/diagrams/cloud-logging.png) </del> <ins> ![image](/images/blog-logging/diagrams/cloud-logging.png) </ins> This diagram shows four nodes created on a Google Compute Engine cluster with the name of each VM node on a purple background. The internal and public IPs of each node are shown on gray boxes and the pods running in each node are shown in green boxes. Each pod box shows the name of the pod and the namespace it runs in, the IP address of the pod and the images which are run as part of the pod's execution. Here we see that every node is running a fluentd-cloud-logging pod which is collecting the log output of the containers running on the same node and sending them to Google Cloud Logging. A pod which provides the [cluster DNS service](/docs/admin/dns) runs on one of the nodes and a pod which provides monitoring support runs on another node.

One of the nodes is now running the counter pod: <del> ![Counter Pod](https://raw.githubusercontent.com/kubernetes/kubernetes/{{page.githubbranch}}/examples/blog-logging/diagrams/27gf-counter.png) </del> <ins> ![image](/images/blog-logging/diagrams/27gf-counter.png) </ins> When the pod status changes to `Running` we can use the kubectl logs command to view the output of this counter pod.
Change:
Connect with Proxies references kube ui. It should use the kube dashboard instead.
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale

Discussion:
### Accessing the cluster with a browser <del> We install two UIs on Kubernetes. The original KubeUI and [the newer kube dashboard](/docs/tasks/web-ui-dashboard/). When you create a cluster, the script should output URLs for these interfaces like this: KubeUI is running at ```https://${MASTER_IP}:6443/api/v1/namespaces/kube-system/services/kube-ui/proxy```. </del> <ins> We install [the kubernetes dashboard](/docs/tasks/web-ui-dashboard/). When you create a cluster, the script should output URLs for these interfaces like this: </ins> kubernetes-dashboard is running at ```https://${MASTER_IP}:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy```.

kubectl proxy -p 8001 ``` <del> Then, you can access urls like ```http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/kube-ui/proxy/``` without the need for client certificates in your browser. </del> <ins> Then, you can access urls like ```http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy/``` without the need for client certificates in your browser. </ins> ## What Kubernetes features do not work on CenturyLink Cloud

* Container Resource Monitoring * [Setup instructions](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/) * GUI <del> * [Setup instructions](https://github.com/kubernetes/kube-ui) cluster. </del> <ins> * [Setup instructions](https://github.com/kubernetes/dashboard) </ins> ## Troubleshooting

$ kubectl cluster-info Kubernetes master is running at https://108.59.85.141 KubeDNS is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kube-dns/proxy <del> KubeUI is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kube-ui/proxy </del> <ins> kubernetes-dashboard is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy </ins> Grafana is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy Heapster is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-heapster/proxy InfluxDB is running at https://108.59.85.141/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy

</source> # Example: <del> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kube-ui </del> <ins> # I0204 06:55:31.872680       5 servicecontroller.go:277] LB already exists and doesn't need update for service kube-system/kubernetes-dashboard </ins> <source> type tail format multiline
Change:
I wish /docs/getting-started-guides/docker/ I wish this page existed

Discussion:
(backward-compatible) changes to the way the Kubernetes cluster DNS server processes DNS queries, to facilitate the lookup of federated services (which span multiple Kubernetes clusters). <del> See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more </del> <ins> See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more </ins> details on Cluster Federation and multi-site support. ## References

<ins> # *Stop.  This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes* The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md) </ins>

### SEE ALSO <del> * [kubectl](kubectl.md)	 - kubectl controls the Kubernetes cluster manager </del> <ins> * [kubectl](../kubectl.md)	 - kubectl controls the Kubernetes cluster manager </ins> ###### Auto generated by spf13/cobra on 12-Aug-2016
Change:
Does not run under as defined in the docs. This is the fix: I think wanted me to do one work on the cheat anyways ... Just leaving this here for now.

Discussion:
$ kubectl get services --sort-by=.metadata.name # List pods Sorted by Restart Count <del> $ kubectl get pods --sort-by=.status.containerStatuses[0].restartCount </del> <ins> $ kubectl get pods --sort-by='.status.containerStatuses[0].restartCount' </ins> # Get the version label of all pods with label app=cassandra $ kubectl get pods --selector=app=cassandra rc -o 'jsonpath={.items[*].metadata.labels.version}'

# List Names of Pods that belong to Particular RC # "jq" command useful for transformations that are too complex for jsonpath <del> $ sel=$(./kubectl get rc <rc-name> --output=json | jq -j '.spec.selector | to_entries | .[] | "(.key)=(.value),"') </del> <ins> $ sel=$(kubectl get rc <rc-name> --output=json | jq -j '.spec.selector | to_entries | .[] | "(.key)=(.value),"') </ins> $ sel=${sel%?} # Remove trailing comma <del> $ pods=$(kubectl get pods --selector=$sel --output=jsonpath={.items..metadata.name})` </del> <ins> $ pods=$(kubectl get pods --selector=$sel --output=jsonpath={.items..metadata.name}) $ echo $pods </ins> # Check which nodes are ready <del> $ kubectl get nodes -o jsonpath='{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}'| tr ';' "n"  | grep "Ready=True" </del> <ins> $ kubectl get nodes -o jsonpath='{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}'| tr ';' "n"  | grep "Ready=True" </ins> ``` ## Modifying and Deleting Resources

$ kubectl attach <podname> -i                             # Attach to Running Container $ kubectl port-forward <podname> <local-and-remote-port>  # Forward port of Pod to your local machine $ kubectl port-forward <servicename> <port>               # Forward port to service <del> $ kubectl exec <pod-name> -- ls /                         # Run command in existing pod (1 container case) $ kubectl exec <pod-name> -c <container-name> -- ls /     # Run command in existing pod (multi-container case) </del> <ins> $ kubectl exec <pod-name> -- ls /                         # Run command in existing pod (1 container case) $ kubectl exec <pod-name> -c <container-name> -- ls /     # Run command in existing pod (multi-container case) </ins> ```
Change:
This is a Bug Report Problem: includes dead link to at the bottom of the page
I guess it is here -

Discussion:
## References <del> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) </del> <ins> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) </ins> ## What's next - [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The reference link at the bottom of the docs page on appears to be broken. the link points to , which redirects to This returns a 404 not found page on github. Proposed Solution: Looking though github, it appears that the kube-dns was moved in github to cluster/addons about 4 months ago under dns. the can be found at now and possibly parts of it were also moved into Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--

Discussion:
## References <del> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) </del> <ins> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) </ins>
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x ] Bug Report Problem: The link to Docker Volumes is broken: it does not exist anymore. Proposed Solution: Fix the link to point to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
looks like there's a redirect to the correct page on Docker so this link isn't broken anymore. It's probably still worth updating to point users to the right page to begin with
Updated w/ PR

Discussion:
: A service defines a set of pods and a means by which to access them, such as single stable IP address and corresponding DNS name. [**Volume**](/docs/user-guide/volumes/) <del> : A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/userguide/dockervolumes/), adding provisioning of the volume directory and/or device. </del> <ins> : A volume is a directory, possibly with some data in it, which is accessible to a Container as part of its filesystem.  Kubernetes volumes build upon [Docker Volumes](https://docs.docker.com/engine/tutorials/dockervolumes/), adding provisioning of the volume directory and/or device. </ins> [**Secret**](/docs/user-guide/secrets/) : A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request.