jiebi/CodeConvo huggingface dataset:
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: includes a statement about the future. These are best left to and GitHub issues rather than documentation - see . Proposed Solution: Remove the section at Consider making this change in the branch for the next release, so that the update happens at a time when changes are expected. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /help /priority backlog /language en /kind cleanup
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: includes a statement about the future. These are best left to and GitHub issues rather than documentation - see . Remove the section at <!--Kubernetes Version:--/help /priority backlog /language en /kind cleanup </details
/assign

Discussion:
glossary_tooltip text="kubelet" term_id="kubelet" >}} and {{< glossary_tooltip text="kube-apiserver" term_id="kube-apiserver" >}} (`--feature-gates=HugePageStorageMediumSize=true`). <del> ## Future - NUMA locality guarantees as a feature of quality of service. - LimitRange support. </del>
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: Documentation contains an error: URL: chapter: kubeadm blocks when removing managed containers: Text in doc: Inspecting the logs for docker may also be useful: Error: This command runs into an error (on my ubuntu 18.04 distribution): Proposed Solution: Replace command with: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version: v1.18--<!--Additional Information:--
/sig cluster-lifecycle /good-first-issue /help /kind bug it should have been or just let's go with:
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /sig cluster-lifecycle /good-first-issue /help /kind bug Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign

Discussion:
Inspecting the logs for docker may also be useful: ```sh <del> journalctl -ul docker </del> <ins> journalctl -u docker </ins> ``` ## Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state
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: There seems to be a wrong spelling in concepts/containers/images/#multi-architecture-images-with-manifests Proposed Solution: Correct the typo Before: A manifest can reference image manifests for architecturew-specific versions of an container After A manifest can reference image manifests for architecture-specific versions of an container Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 <!--Additional Information:--
Thanks /help /kind bug /priority backlog /language en
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Thanks /help /kind bug /priority backlog /language en Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign

Discussion:
## Multi-architecture Images with Manifests <del> As well as providing binary images, a container registry can also server a [container image manifest](https://github.com/opencontainers/image-spec/blob/master/manifest.md). A manifest can reference image manifests for architecturew-specific versions of an container. The idea is that you can have a name for an image (for example: `pause`, `example/mycontainer`, `kube-apiserver`) and allow different systems to fetch the right binary image for the machine architecture they are using. </del> <ins> As well as providing binary images, a container registry can also server a [container image manifest](https://github.com/opencontainers/image-spec/blob/master/manifest.md). A manifest can reference image manifests for architecture-specific versions of an container. The idea is that you can have a name for an image (for example: `pause`, `example/mycontainer`, `kube-apiserver`) and allow different systems to fetch the right binary image for the machine architecture they are using. </ins> Kubernetes itself typically names container images with a suffix `-$(ARCH)`. For backward compatibility, please generate the older images with suffixes. The idea is to generate say `pause` image which has the manifest for all the arch(es) and say `pause-amd64` which is backwards compatible for older configurations or YAML files which may have hard coded the images with suffixes.
Change:
This URL returns 404: The cause is an incorrect path in the responsible for redirecting it.

Discussion:
/docs/tasks/access-application-cluster/access-cluster.md     /docs/tasks/access-application-cluster/access-cluster/ 301! /docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/     /docs/tasks/access-application-cluster/configure-access-multiple-clusters/ 301 <del> /docs/tasks/access-kubernetes-api/access-kubernetes-api/custom-resources/custom-resource-definitions/     /docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/ 301 </del> <ins> /docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/     /docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/ 301 </ins> /docs/tasks/access-kubernetes-api/access-kubernetes-api/custom-resources/custom-resource-definition-versioning/     /docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/ 301 /docs/tasks/access-kubernetes-api/access-kubernetes-api/http-proxy-access-api/     /docs/tasks/extend-kubernetes/http-proxy-access-api/ 301 /docs/tasks/access-kubernetes-api/configure-aggregation-layer/   /docs/tasks/extend-kubernetes/configure-aggregation-layer/ 301
Change:
This is a Feature Request The HTML partials, and frontpage-, contain a element which duplicates the element found in the body of the page. This became an issue as the docsy theme updates page anchors in the script . This script depends upon the element and failed to find the H1 - H6 level headings on the page to udpate. What would you like to be Investigate how to include the announcement banner on the docs pages (front page, docs, blog, and so on) without the element. Investigate changes to the corresponding stylesheet. Why is this needed Clean up or adjust the preexisting, related code as well as the current templates and stylesheet. Provide a flexible way to add and remove content such as announcement or banners on the pages. Comments For additional information, see PR .
/assign
/kind cleanup /priority important-soon
/reopen There might be more to do here.
Reopened this issue. <detailsIn response to : /reopen There might be more to do here. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I don't think there's any more work that needs doing here! you can close this off :)
Good. The only thing noted is some different styling per main section (docs vs case studies). /close
Closing this issue. <detailsIn response to : Good. The only thing noted is some different styling per main section (docs vs case studies). /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
{{ if .Page.Param "announcement" }} <section lang="en" id="announcement" style="background-color:{{ .Page.Param "announcement_bg" }}"> <aside> <del> <div class="content announcement main-section"> </del> <ins> <div class="content announcement main-section" data-nosnippet> </ins> <h4 class="announcement"> {{ T "announcement_title" | markdownify }}

{{ if .Page.Param "announcement" }} <section lang="en" id="fp-announcement" style="background-color:{{ .Page.Param "announcement_bg" }}"> <del> <main> <div class="content announcement main-section"> </del> <ins> <aside > <div class="content announcement main-section" data-nosnippet> </ins> <h3> {{ T "announcement_title" |  markdownify }}

<p>{{ T "announcement_message" | markdownify }}</p> </div> <del> </main> </del> <ins> </aside> </ins> </section> {{ end }}  No newline at end of file

min-height: 30vh; } <del> #fp-announcement main { </del> <ins> #fp-announcement aside { </ins> padding-top: 125px; padding-bottom: 35px; }
Change:
Searching keyword including space is not working. If you search one keyword, for example, "command", it will work. But, if "command and args" is input, the search result shows "Fetching results..." and do not return the result.
Hello, Thank you for pointing out the issue! I confirmed the same problem happens when searching the keyword "command and args" (). And I'll investigate the cause of this problem and fix it. /assign
BTW this applies to users using Bing search from China. See PR
are these symptoms still occurring? We're seeing different reports.
I have confirmed that this issue has dissapeared! Thank you for dealing with!
I'm glad to hear that!
I've had this problem now. But it disappeared because I used a different browser (chrome to Firefox).

Discussion:
} window.getPaginationAnchors = (pages) => { <del> var pageAnchors = '', searchTerm  = window.location.search.split("=")[1].split("&")[0]; </del> <ins> var pageAnchors = '', searchTerm  = window.location.search.split("=")[1].split("&")[0].replace(/%20/g, ' '); </ins> var currentPage = window.location.search.split("=")[2]; currentPage = (!currentPage) ?  1 : currentPage.split("&")[0];

} window.renderBingSearchResults = () => { <del> var searchTerm  = window.location.search.split("=")[1].split("&")[0], </del> <ins> var searchTerm  = window.location.search.split("=")[1].split("&")[0].replace(/%20/g,' '), </ins> page        = window.location.search.split("=")[2], q           = "site:kubernetes.io " + searchTerm;

ajaxConf.beforeSend = function(xhr){ xhr.setRequestHeader('Ocp-Apim-Subscription-Key', '51efd23677624e04b4abe921225ea7ec'); }; $.ajax(ajaxConf).done(function(res) { <ins> if (res.webPages == null) return; // If no result, 'webPages' is 'undefined' </ins> var paginationAnchors = window.getPaginationAnchors(Math.ceil(res.webPages.totalEstimatedMatches / 10)); res.webPages.value.map(ob => { results += window.getResultMarkupString(ob); })
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: ! The space between lines in button is too wide, causing ugly labels especially when the window is not wide or in localized pages which use more characters for the button text (i.e. ). The new docsy theme narrows this page width so it tends to happen more. Proposed Solution: The current stylesheet specifies 0px as vertical padding and set 40px as line-height. The problem can be fixed by specifying a reasonable vertical padding and less line-height. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--I've written a code to fix this problem. I'll send a PR to fix this problem. /assign
/kind cleanup

Discussion:
.button { display: inline-block; border-radius: 6px; <del> padding: 0 20px; line-height: 40px; </del> <ins> padding: 6px 20px; line-height: 1.3rem; </ins> color: white; background-color: $blue; text-decoration: none;

{{ end }} {{ end }} </ul> <del> <br> <button id="btn-concepts" class="button" onClick="location.href='{{ .button_path | relLangURL }}';" aria-label="{{ .title }}">{{ .button }}</button> <br> <br> </del> <ins> {{ if .button }} <br> <button id="btn-concepts" class="button" onClick="location.href='{{ .button_path | relLangURL }}';" aria-label="{{ .title }}">{{ .button }}</button> <br> <br> {{ end }} </ins> </div> {{ end }}  No newline at end of file
Change:
This is a Bug Report <!--Required Information--Problem: The page has a section. This section contains link to a Handler documentation. This link does not work: Proposed Solution: Update the link to the handler documentation on the page in the section of the page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en
/assign I'm going to fix the link to the correct one.

Discussion:
performed periodically by the [kubelet](/docs/admin/kubelet/) on a Container. To perform a diagnostic, the kubelet calls a <del> [Handler](https://godoc.org/k8s.io/kubernetes/pkg/api/v1#Handler) implemented by </del> <ins> [Handler](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#handler-v1-core) implemented by </ins> the Container. There are three types of handlers: * [ExecAction](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#execaction-v1-core):

In general, Pods remain until a human or {{< glossary_tooltip term_id="controller" text="controller" >}} process explicitly removes them. <del> The control plane cleans up terminated Pods (with a phase of `Succeeded` or </del> <ins> The control plane cleans up terminated Pods (with a phase of `Succeeded` or </ins> `Failed`), when the number of Pods exceeds the configured threshold (determined by `terminated-pod-gc-threshold` in the kube-controller-manager). This avoids a resource leak as Pods are created and terminated over time.
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: At 181 line: Link to OpenAPI v3.0 validation is broken. Yes. Most validation can be specified in the CRD using . Proposed Solution: Yes. Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation). Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign

Discussion:
| Feature | Description | CRDs | Aggregated API | | ------- | ----------- | ---- | -------------- | <del> | Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/extend-api-custom-resource-definitions/#validation).  Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks | </del> <ins> | Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation).  Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks | </ins> | Defaulting | See above | Yes, either via [OpenAPI v3.0 validation](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#defaulting) `default` keyword (GA in 1.17), or via a [Mutating Webhook](/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook) (though this will not be run when reading from etcd for old objects). | Yes | | Multi-versioning | Allows serving the same object through two API versions. Can help ease API changes like renaming fields. Less important if you control your client versions. | [Yes](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning) | Yes | | Custom Storage | If you need storage with a different performance mode (for example, a time-series database instead of key-value store) or isolation for security (for example, encryption of sensitive information, etc.) | No | Yes |
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: The carousel is not working Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
It seems the class of carousel images changed /assign

Discussion:
<li data-target="#myCarousel" data-slide-to="3"></li> </ol> <div class="carousel-inner" role="listbox"> <del> <div class="item active"> </del> <ins> <div class="item carousel-item active"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates1.svg" > </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates2.svg"> </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates3.svg"> </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates4.svg"> </div> </div>
Change:
The announcement banner text (merged in ) is being used as the Google search snippet for docs pages. This may not have been your intention. !
SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. I'd characterize this as a Google bug. There are a lot of Google people in the Kubernetes ecosystem but probably not from the web search side. Do you agree with that characterization? /triage awaiting-more-evidence
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : SIG Docs doesn't have a good way to improve Google's indexing algorithm. The text is in an HTML element which should mark it as an aside: content only indirectly related to the main content. /triage awaiting-more-evidence Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority awaiting-more-evidence
I can't find anything suggesting Google has ever ignored elements, and I can find a comment from someone at Google saying they explicitly ignore them ( via ). The supported way to mark something not to go in a snippet is the attribute: , . I can raise a feature request with the search team to ask them to treat like but from a Kubernetes users perspective, changing the site will get to a better outcome quicker.
It sounds useful to add to the announcements.
I would adjust to "fix now"
Yikes, sorry guys! I would also mark as fix now
/priority fix-now
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /priority fix-now Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-priority awaiting-more-evidence /priority critical-urgent

Discussion:
{{ if .Page.Param "announcement" }} <section lang="en" id="announcement" style="background-color:{{ .Page.Param "announcement_bg" }}"> <aside> <del> <div class="content announcement main-section"> </del> <ins> <div class="content announcement main-section" data-nosnippet> </ins> <h4 class="announcement"> {{ T "announcement_title" | markdownify }}

{{ if .Page.Param "announcement" }} <section lang="en" id="fp-announcement" style="background-color:{{ .Page.Param "announcement_bg" }}"> <del> <main> <div class="content announcement main-section"> </del> <ins> <aside > <div class="content announcement main-section" data-nosnippet> </ins> <h3> {{ T "announcement_title" |  markdownify }}

<p>{{ T "announcement_message" | markdownify }}</p> </div> <del> </main> </del> <ins> </aside> </ins> </section> {{ end }}  No newline at end of file

min-height: 30vh; } <del> #fp-announcement main { </del> <ins> #fp-announcement aside { </ins> padding-top: 125px; padding-bottom: 35px; }
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: Stylesheet does not limit width of <olfor larger screens. The config details in overflow its container. (I use mozilla firefox if it's required) Proposed Solution: Find a way to add, "width:52%;" attribute for <oltags in Stylesheet under " screen and (min-width: 992px)" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind bug /language en I'll try to make a PR to fix this if its fine.
I'm not sure that fixing just for elements is the right approach. Maybe fix it for or, if there need to be exceptions, ?
/priority important-longterm
I see. I suggested changing just <oltag previously since the generated stylesheet had mentioned for lot of them individually.
I built website locally and navigated to "http://localhost:1313/docs/reference/generated/kubectl/kubectl-commands#config". It says error 404. When i manually add .html to the url then i can view the page. Is this normal?

Discussion:
clear: both; } <del> .body-content > h3, .body-content > h4, .body-content > h5, .body-content > h6, .body-content > p, .body-content > ul > li, .body-content > ul > li { width: 52%; } .body-content table { </del> <ins> .body-content > * { </ins> width: 52%; }