jiebi/CodeConvo huggingface dataset:
Change:
In we mentioned swagger 1.2 however as of 1.5 we will support OpenAPI (swagger 2.0) spec. We should update docs to reflect that.
I believe this is pending with the 1.5 changes that are coming out.
Excellent, is there any staging area with that change I can look at?
I don't see any doc changes for OpenAPI. Please link to the change if I am wrong, otherwise we should at lets mention OpenAPI in the docs and later on (1.6 maybe) remove swagger 1.2 references completely.

Discussion:
What constitutes a compatible change and how to change the API are detailed by the [API change document](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/docs/devel/api_changes.md). <del> ## API Swagger definitions </del> <ins> ## OpenAPI and Swagger definitions </ins> <del> Complete API details are documented using [Swagger v1.2](http://swagger.io/). The Kubernetes apiserver (aka "master") exposes an API that can be used to retrieve the Swagger Kubernetes API spec located at `/swaggerapi`. You can also enable a UI to browse the API documentation at `/swagger-ui` by passing the `--enable-swagger-ui=true` flag to apiserver. </del> <ins> Complete API details are documented using [Swagger v1.2](http://swagger.io/) and [OpenAPI](https://www.openapis.org/). The Kubernetes apiserver (aka "master") exposes an API that can be used to retrieve the Swagger v1.2 Kubernetes API spec located at `/swaggerapi`. You can also enable a UI to browse the API documentation at `/swagger-ui` by passing the `--enable-swagger-ui=true` flag to apiserver. </ins> <del> We also host a version of the [latest API documentation](http://kubernetes.io/docs/api-reference/README/). This is updated with the latest release, so if you are using a different version of Kubernetes you will want to use the spec from your apiserver. </del> <ins> We also host a version of the [latest v1.2 API documentation UI](http://kubernetes.io/kubernetes/third_party/swagger-ui/). This is updated with the latest release, so if you are using a different version of Kubernetes you will want to use the spec from your apiserver. Staring kubernetes 1.4, OpenAPI spec is also available at `/swagger.json`. While we are transitioning from Swagger v1.2 to OpenAPI (aka Swagger v2.0), some of the tools such as kubectl and swagger-ui are still using v1.2 spec. OpenAPI spec is in Beta as of Kubernetes 1.5. </ins> Kubernetes implements an alternative Protobuf based serialization format for the API that is primarily intended for intra-cluster communication, documented in the [design proposal](https://github.com/kubernetes/kubernetes/blob/{{ page.githubbranch }}/docs/proposals/protobuf.md) and the IDL files for each schema are located in the Go packages that define the API objects.
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: Links in the Terminology section point to (obsolete?) documents. Proposed Solution: Point them at master. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
thanks! Addressed in PR

Discussion:
* Node: A single virtual or physical machine in a Kubernetes cluster. * Cluster: A group of nodes firewalled from the internet, that are the primary compute resources managed by Kubernetes. * Edge router: A router that enforces the firewall policy for your cluster. This could be a gateway managed by a cloudprovider or a physical piece of hardware. <del> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/networking.md). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/admin/ovs-networking.md). * Service: A Kubernetes [Service](https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/user-guide/services.md) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </del> <ins> * Cluster network: A set of links, logical or physical, that facilitate communication within a cluster according to the [Kubernetes networking model](/docs/admin/networking/). Examples of a Cluster network include Overlays such as [flannel](https://github.com/coreos/flannel#flannel) or SDNs such as [OVS](/docs/admin/ovs-networking/). * Service: A Kubernetes [Service](/docs/user-guide/services/) that identifies a set of pods using label selectors. Unless mentioned otherwise, Services are assumed to have virtual IPs only routable within the cluster network. </ins> ## What is Ingress?
Change:
Add trademark footer to properly indicate trademark guidelines around kubernetes. Something like:
Do we want to remove " 2016 The Kubernetes Authors | Distributed under CC BY 4.0" or add to it?
I'd add to it. I'd also specify that "Documentation Distributed under CC BY 4.0" Other than that, LGTM!

Discussion:
<a href="https://github.com/kubernetes/kubernetes" class="button">Contribute to the K8s codebase</a> </div> </div> <del> <div id="miceType" class="center">&copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Distributed under <a href="https://github.com/kubernetes/kubernetes.github.io/blob/master/LICENSE" class="light-text">CC BY 4.0</a></div> </del> <ins> <div id="miceType" class="center"> &copy; {{ 'now' | date: "%Y" }} The Kubernetes Authors | Documentation Distributed under <a href="https://github.com/kubernetes/kubernetes.github.io/blob/master/LICENSE" class="light-text">CC BY 4.0</a> </div> <div id="miceType" class="center"> Copyright &copy; {{ 'now' | date: "%Y" }} The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">https://www.linuxfoundation.org/trademark-usage</a> </div> </ins> </main> </footer>
Change:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a Bug Report <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: The image link to hpa_example is broken. Proposed Solution: Rework the page so that people know how to create their own image, or remove the link from the walkthrough page: Page to Update:** <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Fixed in PR

Discussion:
## Step One: Run & expose php-apache server To demonstrate Horizontal Pod Autoscaler we will use a custom docker image based on the php-apache image. <del> The image can be found [here](/docs/user-guide/horizontal-pod-autoscaling/image). </del> <ins> The Dockerfile can be found [here](/docs/user-guide/horizontal-pod-autoscaling/image/Dockerfile). </ins> It defines an [index.php](/docs/user-guide/horizontal-pod-autoscaling/image/index.php) page which performs some CPU intensive computations. First, we will start a deployment running the image and expose it as a service:
Change:
This is a... [ ] Feature Request [X] Bug Report Problem: Incorrect example at "Service Account Tokens". The documentation states: But in the example the serviceAccountName field has been set in the container field. Proposed Solution: Replace: With: Page to Update:
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
/lifecycle frozen /remove-lifecycle stale

Discussion:
metadata: # ... spec: <ins> serviceAccountName: bob-the-bot </ins> containers: - name: nginx image: nginx:1.7.9 <del> serviceAccountName: bob-the-bot </del> ``` Service account bearer tokens are perfectly valid to use outside the cluster and
Change:
This is a Bug Report Problem: does not have correct instructions. Proposed Solution: In , Make a note of the external IP address exposed by your service should be Make a note of the external IP address () exposed by your service Also note the value of Port. In this example, the port is 8080 should be Also note the value of and . In this example, the port is 8080 and NodePort is Use the external IP address to access the Hello World application should be Use the external IP address () to access the Hello World application where is the external IP address of your Service, and is the value of in your Service description should be where is the external IP address () of your Service, and is the value of in your Service description. If you are using minukube, typing will automatically open the Hello World application in a browser. Page to Update: Kubernetes Version: Additional Information: These corrections will really help new k8s/minikube users. Thanks!
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
/remove-lifecycle stale /assign

Discussion:
Session Affinity:   None Events:         <none> <del> Make a note of the external IP address exposed by your service. In this example, the external IP address is 104.198.205.71. Also note the value of Port. In this example, the port is 8080. </del> <ins> Make a note of the external IP address (`LoadBalancer Ingress`) exposed by your service. In this example, the external IP address is 104.198.205.71. Also note the value of `Port` and `NodePort`. In this example, the `Port` is is 8080 and the `NodePort` is 32377. </ins> 1. In the preceding output, you can see that the service has several endpoints: 10.0.0.6:8080,10.0.1.6:8080,10.0.1.7:8080 + 2 more. These are internal

hello-world-2895499144-o4z13 ...  10.0.1.7   gke-cluster-1-default-pool-e0b8d269-1afc hello-world-2895499144-segjf ...  10.0.2.5   gke-cluster-1-default-pool-e0b8d269-cpuc <del> 1. Use the external IP address to access the Hello World application: </del> <ins> 1. Use the external IP address (`LoadBalancer Ingress`) to access the Hello World application: </ins> curl http://<external-ip>:<port> <del> where `<external-ip>` is the external IP address of your Service, and `<port>` is the value of `Port` in your Service description. </del> <ins> where `<external-ip>` is the external IP address (`LoadBalancer Ingress`) of your Service, and `<port>` is the value of `NodePort` in your Service description. If you are using minikube, typing `minikube service my-service` will automatically open the Hello World application in a browser. </ins> The response to a successful request is a hello message:
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 [ ] Bug Report [x] Documentation request Problem: Can we use equality-based requirement selectors like this in yaml/json files: Proposed Solution: Clearly mention if this is possible and if so include a small example. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/remove-lifecycle stale /assign

Discussion:
The latter selects all resources with key equal to `tier` and value distinct from `frontend`, and all resources with no labels with the `tier` key. One could filter for resources in `production` excluding `frontend` using the comma operator: `environment=production,tier!=frontend` <ins> One usage scenario for equality-based label requirement is for Pods to specify node selection criteria. For example, the sample Pod below selects nodes with the label "`accelerator=nvidia-tesla-p100`". ```yaml apiVersion: v1 kind: Pod metadata: name: cuda-test spec: containers: - name: cuda-test image: "k8s.gcr.io/cuda-vector-add:v0.1" resources: limits: nvidia.com/gpu: 1 nodeSelector: accelerator: nvidia-tesla-p100 ``` </ins> ### _Set-based_ requirement
Change:
This is a... [x] Bug Report Problem: There is no directory in the tar bundle. Example: Proposed Solution: Recommend people to execute in the bundle? Page to Update:

Discussion:
Here are a few methods to install kubectl. <del> ## Install kubectl Binary Via curl </del> <ins> ## Install kubectl binary via curl </ins> Download the latest release with the command:

sudo mv ./kubectl /usr/local/bin/kubectl ``` <del> ## Extract kubectl from Release .tar.gz or Compiled Source If you downloaded a pre-compiled [release](https://github.com/kubernetes/kubernetes/releases), kubectl will be under `platforms/<os>/<arch>` from the tar bundle. If you compiled Kubernetes from source, kubectl should be either under `_output/local/bin/<os>/<arch>` or `_output/dockerized/bin/<os>/<arch>`. Copy or move kubectl into a directory already in your PATH (e.g. `/usr/local/bin`). For example: ```shell # OS X sudo cp platforms/darwin/amd64/kubectl /usr/local/bin/kubectl # Linux sudo cp platforms/linux/amd64/kubectl /usr/local/bin/kubectl ``` Next make it executable with the following command: ```shell sudo chmod +x /usr/local/bin/kubectl ``` The kubectl binary doesn't have to be installed to be executable, but the rest of the walkthrough will assume that it's in your PATH. If you prefer not to copy kubectl, you need to ensure it is in your path: ```shell # OS X export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH # Linux export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH ``` </del> ## Download as part of the Google Cloud SDK kubectl can be installed as part of the Google Cloud SDK:

gcloud components install kubectl ``` <del> Do check that the version is sufficiently up-to-date using `kubectl version`. </del> <ins> Check that the version is sufficiently up-to-date using `kubectl version`. </ins> <del> ## Install with brew </del> <ins> ## Install with Homebrew on macOS </ins> <del> If you are on MacOS and using brew, you can install with: </del> <ins> If you are on macOS and using [Homebrew](https://brew.sh/) package manager, you can install with: </ins> ```shell brew install kubectl
Change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: [update demo] link doesn't do anything. It links to the same page. Proposed Solution: ? Page to Update:

Discussion:
replicationcontroller "my-nginx-v4" rolling updated ``` <del> You can also run the [update demo](/docs/tasks/run-application/rolling-update-replication-controller/) to see a visual representation of the rolling update process. </del> ## Troubleshooting If the `timeout` duration is reached during a rolling update, the operation will
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: On Ubuntu in addition to installing Docker one need to install package "aufs-tools" as dockerd may call aufs tools like "auplink" up on need. This may be relevant for Docker on CentOS 7 too, I do not know with certainty. Proposed Solution: Replace line apt-get install -y with the line apt-get install -y aufs-tools Page to Update: Kubernetes Version: Kubernetes 1.5.1 Additional Information: Ubuntu 16.10
The root problem may be a missing dependency in the docker package on Ubuntu and derivatives. But needs to be addressed for kubeadm until it is resolved up stream by OS vendor.
cc:

Discussion:
EOF apt-get update # Install docker if you don't have it already. <del> apt-get install -y docker.io </del> <ins> apt-get install -y docker-engine </ins> apt-get install -y kubelet kubeadm kubectl kubernetes-cni ```
Change:
This is a... [ x] Feature Request Problem: I am missing a definition of "containerized applications". Proposed Solution: It would be nice if this term ("containerized applications") would be a hyperlink to a place where I can find more details about what this term means in the context of kubernetes. Page to Update:

Discussion:
<div class="row"> <div class="col-md-9"> <h2>Kubernetes Basics</h2> <del> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its containerized applications for yourself.</p> </del> <ins> <p>This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and includes an interactive online tutorial. These interactive tutorials let you manage a simple cluster and its <a href="/docs/concepts/overview/what-is-kubernetes/#why-containers">containerized applications</a> for yourself.</p> </ins> <p>Using the interactive tutorials, you can learn to:</p> <ul> <li>Deploy a containerized application on a cluster</li>
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: Link points to non-existent page Proposed Solution: Fix the link. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--

Discussion:
* Kubernetes API Versions * [1.6](/docs/api-reference/v1.6/) * [1.5](/docs/api-reference/v1.5/) <del> * Federation API * [v1 Operations](docs/reference/federation/v1/operations.html) * [v1 Model Definitions](docs/reference/federation/v1/definitions.html) * [federation/v1beta1 Operations](docs/reference/federation/v1beta1/operations.html) * [federation/v1beta1 Model Definitions](docs/reference/federation/v1beta1/definitions.html) * [extensions/v1beta1 Operations](docs/reference/federation/extensions/v1beta1/operations.html) * [extensions/v1beta1 Model Definitions](docs/reference/federation/extensions/v1beta1/definitions.html) </del> ## CLI Reference
Change:
This is a... [ X ] Bug Report Problem: The for the Docker based single node cluster instructions is outdated Proposed Solution: fix the link: Page to Update:

Discussion:
## Introduction This document describes how to build a high-availability (HA) Kubernetes cluster.  This is a fairly advanced topic. <del> Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such as the simple [Docker based single node cluster instructions](/docs/getting-started-guides/docker), </del> <ins> Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such as [Minikube](/docs/getting-started-guides/minikube/) </ins> or try [Google Container Engine](https://cloud.google.com/container-engine/) for hosted Kubernetes. Also, at this time high availability support for Kubernetes is not continuously tested in our end-to-end (e2e) testing.  We will
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: is inconsistent about whether a persistent volume can be of the FlexVolume type. The table in omits FlexVolume, but the table at the end of the Access Modes subsection in includes FlexVolume. Proposed Solution: Fix the doc to be consistent and correct. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--

Discussion:
* AzureFile * AzureDisk * FC (Fibre Channel) <ins> * FlexVolume </ins> * Flocker * NFS * iSCSI
Change:
If you visit the browser is trying to download the page because it is served as . I can't understand why. But it's actually trying to do a redirect: Could something be hinting github pages or nginx to interpret this as a non-HTML content? have you seen this in other redirections before?
any ideas?
I think I know what it is. There is a typo in the directive in .
Yup, that did the trick.

Discussion:
title: Daemon Sets redirect_from: - "/docs/admin/daemons/" <del> - "/docs/admin/daemons/.html" </del> <ins> - "/docs/admin/daemons.html" </ins> --- * TOC
Change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: It is not clear if LXD nodes are running Docker containers.
cc:
Thanks for the report. Yes, the LXD nodes serve as "machines" for running kubelet, the docker processes are then run inside of LXD. I'll put up a pull request to include a diagram and description
Yes. Took time to figure it out.
if you have time, we really appreciate if you can send a patch to the documentation to make ease other people’s potential pains in the future.
see PR above.
Thanks.

Discussion:
{% capture overview %} ## Overview <del> Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally a Kubernetes developer can spawn all the instances locally and test code as they commit. This page will show you how to deploy a cluster on a local machine. </del> <ins> Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally, a Kubernetes developer can spawn all necessary nodes inside local containers and test new configurations as they are committed. This page will show you how to deploy a cluster to LXD containers on a local machine. </ins> {% endcapture %} <del> The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. </del> <ins> The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](https://kubernetes.io/docs/tutorials/kubernetes-basics/cluster-intro/) for more info). </ins> {% capture prerequisites %} ## Prerequisites