jiebi/CodeConvo huggingface dataset:
Code change:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.

Related discussion:
text: kubectl get statefulset web ``` ``` <del> NAME      DESIRED   CURRENT   AGE web       2         1         20s </del> <ins> NAME   READY   AGE web    2/2     37s </ins> ``` ### Ordered Pod creation
Code change:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.

Related discussion:
text: image again: ```shell <del> kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.8"}]' </del> <ins> kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"registry.k8s.io/nginx-slim:0.8"}]' </ins> ``` ``` statefulset.apps/web patched
Code change:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.

Related discussion:
text: used in this tutorial. Follow the necessary steps, based on your environment, storage configuration, and provisioning method, to ensure that all storage is reclaimed. <del> {{< /note >}} </del>  No newline at end of file <ins> {{< /note >}} </ins>
Code change:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.

Related discussion:
text: spec: containers: - name: nginx <del> image: registry.k8s.io/nginx-slim:0.8 </del> <ins> image: registry.k8s.io/nginx-slim:0.7 </ins> ports: - containerPort: 80 name: web
Code change:
I wish /docs/getting-started-guides/docker/ I wish this page existed

Related discussion:
text: (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
Code change:
I wish /docs/getting-started-guides/docker/ I wish this page existed

Related discussion:
text: <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>
Code change:
I wish /docs/getting-started-guides/docker/ I wish this page existed

Related discussion:
text: ### 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
Code change:
Cites looking at a cephfs example, that promptly 404's once clicked
It appears this should actually point to: not

Related discussion:
text: __Important: You must have your own Ceph server running with the share exported before you can use it__ <del> See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/cephfs/) for more details. </del> <ins> See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/volumes/cephfs/) for more details. </ins> ### gitRepo
Code change:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:

Related discussion:
text: path: /docs/getting-started-guides/ovirt/ - title: OpenStack Heat path: /docs/getting-started-guides/openstack-heat/ <del> - title: CoreOS on Multinode Cluster path: /docs/getting-started-guides/coreos/coreos_multinode_cluster/ </del> - title: rkt section: - title: Running Kubernetes with rkt
Code change:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:

Related discussion:
text: [CoreOS](http://coreos.com) templates for CloudStack are built [nightly](http://stable.release.core-os.net/amd64-usr/current/). CloudStack operators need to [register](http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/templates.html) this template in their cloud before proceeding with these Kubernetes deployment instructions. This guide uses an [Ansible playbook](https://github.com/runseb/ansible-kubernetes). <del> This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/docs/getting-started-guides/coreos/coreos_multinode_cluster). </del> <ins> This is completely automated, a single playbook deploys Kubernetes. </ins> This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.
Code change:
A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?
Thank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:

Related discussion:
text: These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS. <del> [**Multi-node Cluster**](/docs/getting-started-guides/coreos/coreos_multinode_cluster) Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion. <hr/> </del> [**Easy Multi-node Cluster on Google Compute Engine**](https://github.com/rimusz/coreos-multi-node-k8s-gce/blob/master/README.md) Scripted installation of a single master, multi-worker cluster on GCE. Kubernetes components are managed by [fleet](https://github.com/coreos/fleet).
Code 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] --- [x] Feature Request [ ] Bug Report Problem: The port-forward command description is misleading. As a user I would expect the command to forward the complete traffic from port 6000 to 5000 locally, not only the data from both ports like the explanation in the detailed command page mentions. Proposed Solution: You could change the description to something like in the detail command description () or change the command to the version it describes. (kubectl port-forward my-pod 5000:6000 -with colon) 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

Related discussion:
text: $ kubectl logs -f my-pod -c my-container              # stream pod container logs (stdout, multi-container case) $ kubectl run -i --tty busybox --image=busybox -- sh  # Run pod as interactive shell $ kubectl attach my-pod -i                            # Attach to Running Container <del> $ kubectl port-forward my-pod 5000:6000               # Forward port 6000 of Pod to your to 5000 on your local machine </del> <ins> $ kubectl port-forward my-pod 5000:6000               # Listen on port 5000 on the local machine and forward to port 6000 on my-pod </ins> $ kubectl exec my-pod -- ls /                         # Run command in existing pod (1 container case) $ kubectl exec my-pod -c my-container -- ls /         # Run command in existing pod (multi-container case) $ kubectl top pod POD_NAME --containers               # Show metrics for a given pod and its containers
Code change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1
I think this is an issue that needs to be fixed in socks shop.
This merged PR should resolve the issue

Related discussion:
text: * GCEPersistentDisk * AWSElasticBlockStore <ins> * AzureFile * FC (Fibre Channel) </ins> * NFS * iSCSI * RBD (Ceph Block Device) <ins> * CephFS * Cinder (OpenStack block storage) </ins> * Glusterfs <ins> * VsphereVolume </ins> * HostPath (single node testing only -- local storage is not supported in any way and WILL NOT WORK in a multi-node cluster)
Code change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1
I think this is an issue that needs to be fixed in socks shop.
This merged PR should resolve the issue

Related discussion:
text: ### Access Modes <del> A `PersistentVolume` can be mounted on a host in any way supported by the resource provider.  Providers will have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume.  For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only.  Each PV gets its own set of access modes describing that specific PV's capabilities. </del> <ins> A `PersistentVolume` can be mounted on a host in any way supported by the resource provider.  As shown in the table below, providers will have different capabilities and each PV's access modes are set to the specific modes supported by that particular volume.  For example, NFS can support multiple read/write clients, but a specific NFS PV might be exported on the server as read-only.  Each PV gets its own set of access modes describing that specific PV's capabilities. </ins> The access modes are:
Code change:
This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1
I think this is an issue that needs to be fixed in socks shop.
This merged PR should resolve the issue

Related discussion:
text: > __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many.  For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time. <ins> | Volume Plugin        | ReadWriteOnce| ReadOnlyMany| ReadWriteMany| | :---                 |     :---:    |    :---:    |    :---:     | | AWSElasticBlockStore | x            | -           | -            | | AzureFile            | x            | x           | x            | | CephFS               | x            | x           | x            | | Cinder               | x            | -           | -            | | FC                   | x            | x           | -            | | FlexVolume           | x            | x           | -            | | GCEPersistentDisk    | x            | x           | -            | | Glusterfs            | x            | x           | x            | | HostPath             | x            | -           | -            | | iSCSI                | x            | x           | -            | | NFS                  | x            | x           | x            | | RDB                  | x            | x           | -            | | VsphereVolume        | x            | -           | -            | </ins> ### Recycling Policy Current recycling policies are:
Code change:
Problem: this page should mention concept as a way to create an external LB to an application. Page to Update:
There are some offhanded mentions of Ingress in samples, but they're likely to be more confusing than not. Agreed: more/better docs needed.
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

Related discussion:
text: This page shows how to create an External Load Balancer. When creating a service, you have the option of automatically creating a <del> cloud network load balancer. This provides an externally-accessible IP address that sends traffic to the correct port on your cluster nodes _provided your cluster runs in a supported environment and is configured with the correct cloud load balancer provider package_. </del> <ins> cloud network load balancer. This provides an externally-accessible IP address that sends traffic to the correct port on your cluster nodes _provided your cluster runs in a supported environment and is configured with the correct cloud load balancer provider package_. For information on provisioning and using an Ingress resource that can give services externally-reachable URLs, load balance the traffic, terminate SSL etc., please check the [Ingress](/docs/concepts/services-networking/ingress/) documentation. </ins> {% endcapture %}
Code 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: This page has extra spaces before the commands: I am not sure it's a more systemic problem, but this causes commands to not to show up on the bash history (undesirable). Proposed Solution: Page to Update: /assign
A cursory look through the rest of the docs under Configure Pods and Containers showed that one out of four docs also had this issue. I'll make this change as I update the callouts.

Related discussion:
text: 1. Create the Pod: <del> kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml </del> <ins> kubectl create -f https://k8s.io/docs/tasks/configure-pod-container/pod-redis.yaml </ins> 1. Verify that the Pod's Container is running, and then watch for changes to the Pod: <del> kubectl get --watch pod redis </del> <ins> kubectl get --watch pod redis </ins> The output looks like this: <del> NAME      READY     STATUS    RESTARTS   AGE redis     1/1       Running   0          13s </del> <ins> NAME      READY     STATUS    RESTARTS   AGE redis     1/1       Running   0          13s </ins> 1. In another terminal, get a shell to the running Container: <del> kubectl exec -it redis -- /bin/bash </del> <ins> kubectl exec -it redis -- /bin/bash </ins> 1. In your shell, go to `/data/redis`, and create a file: <del> root@redis:/data/redis# echo Hello > test-file </del> <ins> root@redis:/data/redis# echo Hello > test-file </ins> 1. In your shell, list the running processes: <del> root@redis:/data/redis# ps aux </del> <ins> root@redis:/data/redis# ps aux </ins> The output is similar to this: <del> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND redis        1  0.1  0.1  33308  3828 ?        Ssl  00:46   0:00 redis-server *:6379 root        12  0.0  0.0  20228  3020 ?        Ss   00:47   0:00 /bin/bash root        15  0.0  0.0  17500  2072 ?        R+   00:48   0:00 ps aux </del> <ins> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND redis        1  0.1  0.1  33308  3828 ?        Ssl  00:46   0:00 redis-server *:6379 root        12  0.0  0.0  20228  3020 ?        Ss   00:47   0:00 /bin/bash root        15  0.0  0.0  17500  2072 ?        R+   00:48   0:00 ps aux </ins> 1. In your shell, kill the redis process: <del> root@redis:/data/redis# kill <pid> </del> <ins> root@redis:/data/redis# kill <pid> </ins> where `<pid>` is the redis process ID (PID). 1. In your original terminal, watch for changes to the redis Pod. Eventually, you will see something like this: <del> NAME      READY     STATUS     RESTARTS   AGE redis     1/1       Running    0          13s redis     0/1       Completed  0         6m redis     1/1       Running    1         6m </del> <ins> NAME      READY     STATUS     RESTARTS   AGE redis     1/1       Running    0          13s redis     0/1       Completed  0         6m redis     1/1       Running    1         6m </ins> At this point, the Container has terminated and restarted. This is because the redis Pod has a
Code 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: This page has extra spaces before the commands: I am not sure it's a more systemic problem, but this causes commands to not to show up on the bash history (undesirable). Proposed Solution: Page to Update: /assign
A cursory look through the rest of the docs under Configure Pods and Containers showed that one out of four docs also had this issue. I'll make this change as I update the callouts.

Related discussion:
text: 1. Get a shell into the restarted Container: <del> kubectl exec -it redis -- /bin/bash </del> <ins> kubectl exec -it redis -- /bin/bash </ins> 1. In your shell, goto `/data/redis`, and verify that `test-file` is still there.
Code change:
This is a Bug Report This issue appeared recently within kubernetes/website. Links in follow the next pattern , see a square bracket inside of the . I tried to follow in order to find a source of the issue, but wasn't able to do so. my best guesses: Source for generation for 1_17 branch was corrupted. Backend was replaced by something else but not commited (i don't believe in this). This can be temporary content (on ein PR) as toolset for kubernetes-sigs/reference-docs .
/kind bug /priority backlog
ping
I am looking now
, you are referring to a link problem in the reference? I don't immediately see a problem. Can you provide an example of a command that has a link issue? Thanks! I see a link that appears incorrectly formatted, such as the flag in the command, Though, the link does work for me.
I plan on updating the build instructions and README.
any link that follow pattern . If we ware talking about from the root of the kubernetes-sigs/reference-docs, it would be any link in usage block. Almost all of them are anchor links, so problem isn't visible at first. search for or , last symbol of the link is clearly not suppose to be a link (at least its not a link in source yaml) P.S. Is it worth time to update build instructions now? Isn't going to change generator backend to htmlwriter?
, I have a feeling there is a miscommunication. I am not sure what you are referring to. I thought you are logging an issue specifically to the kubectl reference. Please provide a specific example.
ok. for on link to for on link yourself why is in link. diff for kubernetes/website (kubectl-) and see how links are formed. -become right bracket in the href attribute. P.S. just updated one of the search links as i forgot to copy/paste last element of the link (). P.P.S. looks like regular expression issue.
I see. I think we are referring to the same problem -- the right bracket.
Should I close issue or you prefer to have it opened untill kubernetes-sigs/reference-docs is opened?
, I would leave this issue open as a reminder for next release. Thanks! NOTE: The links were manually fixed for the 1.17 release (search/replace).
got it!

Related discussion:
text: - title: kube-proxy CLI path: /docs/admin/kube-proxy/ <del> - title: kub-scheduler CLI </del> <ins> - title: kube-scheduler CLI </ins> path: /docs/admin/kube-scheduler/ - title: kubelet CLI
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue
I'll work on that! /remove-help /assign

Related discussion:
text: date: 2018-04-12 full_link: /docs/tasks/administer-cluster/running-cloud-controller/ short_description: > <del> Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud. </del> <ins> Cloud Controller Manager is a Kubernetes component that embeds cloud-specific control logic. </ins> aka: tags:
Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: is out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue
I'll work on that! /remove-help /assign

Related discussion:
text: - architecture - operation --- <del> Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud. </del> <ins> Cloud Controller Manager is a Kubernetes component that embeds cloud-specific control logic. </ins> <!--more--> <del> Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code. </del> <ins> Originally part of the kube-controller-manager, the cloud-controller-manager is responsible to decoupling the interoperability logic between Kubernetes and the underlying cloud infrastructure, enabling cloud providers to release features at a different pace compared to the main project. </ins>