jiebi/CodeConvo huggingface dataset:
Change:
title: v1.18 Release Notes weight: 10 card: <del> name: download </del> <ins> name: release-notes </ins> weight: 20 anchors: - anchor: "#"

Discussion:
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: has a heading, “Download Kubernetes”. However, this heading isn't followed by a button labelled Download as you might expect. Instead, there are links to the release notes. Proposed Solution: Either: Rename the heading to “Release Notes”(?) or Add a button (maybe using a shortcode), Download, that links to (and set this up to be updated automatically when a new version is released). The button should be under the “Download Kubernetes” heading. or Add a button (maybe using a shortcode), Download, that links to The button should be under the “Download Kubernetes” heading. This will take readers to the right page but they will have to find the download links themselves. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.18 Additional Information: /language en
If we wanna go with either option 1 or option 3, I can help with that. Not sure what is the best way to automagically keep the link updated in option 2. Is there some Hugo site param that can be used for that?
let's go with a thing we can implement, and if someone (you? me?) feels strongly they can log a new issue to track the idea of making it even better.
Change:
<p>While mainly a C++ and Java shop, Amadeus also wanted to be able to adopt new technologies more easily. Some of its developers had started using languages like <a href="https://www.python.org/">Python</a> and databases like <a href="https://www.couchbase.com/">Couchbase</a>, but Mountain wanted still more options, he says, "in order to better adapt our technical solutions to the products we offer, and open up entirely new possibilities to our developers." Working with recent technologies and cool new things would also make it easier to attract new talent.</p> <del> <p>All of those needs led Mountain and his team on a search for a new platform. "We did a set of studies and proofs of concept over a fairly short period, and we considered many technologies," he says. "In the end, we were left with three choices: build everything on premise, build on top of <a href="http://kubernetes.io/">Kubernetes</a> whatever happens to be missing from our point of view, or go with <a href="https://www.openshift.com/">OpenShift</a> and build whatever remains there."</p> </del> <ins> <p>All of those needs led Mountain and his team on a search for a new platform. "We did a set of studies and proofs of concept over a fairly short period, and we considered many technologies," he says. "In the end, we were left with three choices: build everything on premise, build on top of <a href="https://kubernetes.io/">Kubernetes</a> whatever happens to be missing from our point of view, or go with <a href="https://www.openshift.com/">OpenShift</a> and build whatever remains there."</p> </ins> <p>The team decided against building everything themselves—though they'd done that sort of thing in the past—because "people were already inventing things that looked good," says Mountain.</p>

Discussion:
to /assign
Page related to issue: /language en
/retitle Update hyperlinks in 'Amadeus Case Study' page to utilize HTTPS instead of HTTP
Which is the page we should fix?
/triage accepted
Change:
容器漏洞扫描和操作系统依赖安全性 | 作为镜像构建的一部分，您应该扫描您的容器里的已知漏洞。 镜像签名和执行 | 对容器镜像进行签名，以维护对容器内容的信任。 禁止特权用户 | 构建容器时，请查阅文档以了解如何在具有最低操作系统特权级别的容器内部创建用户，以实现容器的目标。 <ins> 使用带有较强隔离能力的容器运行时 | 选择提供较强隔离能力的[容器运行时类](/zh/docs/concepts/containers/runtime-class/)。 </ins> <!-- ## Code

Discussion:
! Chinese page link can not open
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions 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
/language zh
/assign
/kind bug
Change:
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

Discussion:
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
Change:
?()      | filter             | {.users[?(@.name=="e2e")].user.password} | secret range, end | iterate list | {range .items[*]}[{.metadata.name}, {.status.capacity}] {end} | [127.0.0.1, map[cpu:4]] [127.0.0.2, map[cpu:8]] ""       | quote interpreted string | {range .items[*]}{.metadata.name}{"t"}{end} | 127.0.0.1    127.0.0.2 <ins> Below are some examples using jsonpath: ```shell $ kubectl get pods -o json $ kubectl get pods -o=jsonpath='{@}' $ kubectl get pods -o=jsonpath='{.items[0]}' $ kubectl get pods -o=jsonpath='{.items[0].metadata.name}' $ kubectl get pods -o=jsonpath='{range .items[*]}{.metadata.name}{"t"}{.status.startTime}{"n"}{end}' ``` </ins>

Discussion:
<!-- 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: No examples Proposed Solution: Add this text: Here's a small example of how to see the structure of data and how to select some parts of it using jsonpaths 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
Change:
In cases when objects represent a physical entity, like a Node representing a physical host, when the host is re-created under the same name without deleting and re-creating the Node, Kubernetes treats the new host as the old one, which may lead to inconsistencies. {{< /note >}} <del> Below are three types of commonly used name constraints for resources. </del> <ins> Below are four types of commonly used name constraints for resources. </ins> ### DNS Subdomain Names

Discussion:
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: Pod / Service names can not start with an alphanumeric character in kubernetes, but should be possible according to RFC1123 Proposed Solution: Change documentation in sections and to: or change kubernetes name check to use the specification in RFC1123. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 19.11 <!--Additional Information:--
Kubernetes does not strictly follow the RFC.
this might be true, but the documentation says otherwise. eg.
According to the validation logic, starting with alphanumeric characters should be okay. Can you paste the error message you have got?
I tried locally, and getting this error !
Just double checked the validation logic for core v1 Service. Its name must be a RFC1035 label rather than a RFC1123 label. This is something we need to fix in the docs. Related code:
/triage accepted /kind bug /assign
Change:
... resources: {} ... <ins> status: </ins> qosClass: BestEffort ```

Discussion:
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 location of qosClass is not correct in the last example, which is a result of the following command: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /language en /priority backlog /sig scheduling
/help
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 : /help 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
Change:
The pod index is available in the {{< glossary_tooltip text="annotation" term_id="annotation" >}} `batch.kubernetes.io/job-completion-index` as a string representing its decimal value. In order for the containerized task process to obtain this index, <del> you can publish the value of the annotation using the [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/#the-downward-api) </del> <ins> you can publish the value of the annotation using the [downward API](/docs/concepts/workloads/pods/downward-api/) </ins> mechanism. For convenience, the control plane automatically sets the downward API to expose the index in the `JOB_COMPLETION_INDEX` environment variable.

Discussion:
This is a Bug Report <!--Required Information--Problem: The link is dead. The content from the section seems moved into top of the document and glossary in . Proposed Solution: remove fragment from the link change link to or Page to Update: /docs/concepts/workloads/pods/downward-api /docs/tasks/inject-data-application/downward-api-volume-expose-pod-information /docs/tasks/job/indexed-parallel-processing-static
/assign
/language en /triage accepted /help We should find existing hyperlinks to and replace those with links to
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /language en /triage accepted /help 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
/unassign As has already opened a PR
/assign
GitHub didn't allow me to assign the following users: hs0210. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
Change:
{{< kat-button >}} <del> {{< note >}}If you installed Minikube locally, run `minikube start`.{{< /note >}} </del> <ins> {{< note >}} If you installed Minikube locally, run `minikube start`. {{< /note >}} </ins> 2. Open the Kubernetes dashboard in a browser:

Discussion:
This is a Bug Report <!--Required Information--Problem: Text formatting issue under the Create a Minikube cluster heading. The text is listed erroneously (this appears to be a simple authoring/build issue with the content. Proposed Solution: Fix the typo or the build issue for this section of the page. Page to Update:
/labels language/en /assign
Relevant to issue
/language en /kind bug /priority important-longterm
Change:
<ins> --- title: 가비지(Garbage) 수집 id: garbage-collection date: 2022-01-14 full_link: /ko/docs/concepts/architecture/garbage-collection/ short_description: > 쿠버네티스가 클러스터 자원을 정리하기 위해 사용하는 다양한 방법을 종합한 용어이다. aka: tags: - fundamental - operation --- 쿠버네티스가 클러스터 자원을 정리하기 위해 사용하는 다양한 방법을 종합한 용어이다. <!--more--> 쿠버네티스는 [사용되지 않는 컨테이너와 이미지](/ko/docs/concepts/architecture/garbage-collection/#containers-images), [실패한 파드](/ko/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection), [타겟 리소스가 소유한 오브젝트](/docs/concepts/overview/working-with-objects/owners-dependents/), [종료된 잡](/ko/docs/concepts/workloads/controllers/ttlafterfinished/), 그리고 만료되거나 실패한 리소스를 정리하기 위해 가비지 수집을 사용한다. </ins>

Discussion:
This is a Feature Request Translate in Korean What would you like to be Translate in Korean Why is this needed This file is not translated yet. Comments Page to translate : /language ko /assign Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
Resolved by page: /close
Closing this issue. <detailsIn response to : Resolved by 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
Change:
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:

Discussion:
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
Change:
/docs/tasks/administer-cluster/certificate-rotation/     /docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/ 301 /docs/tasks/administer-cluster/cilium-network-policy/     /docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/ 301 /docs/tasks/administer-cluster/configure-namespace-isolation/     /docs/concepts/services-networking/network-policies/ 301 <ins> /docs/tasks/administer-cluster/configure-multiple-schedulers/     /docs/tasks/extend-kubernetes/configure-multiple-schedulers/ 301 </ins> /docs/tasks/administer-cluster/configure-pod-disruption-budget/     /docs/tasks/run-application/configure-pdb/ 301 /docs/tasks/administer-cluster/cpu-constraint-namespace/     /docs/tasks/administer-cluster/manage-resources/cpu-constraint-namespace/ 301 /docs/tasks/administer-cluster/cpu-default-namespace/     /docs/tasks/administer-cluster/manage-resources/cpu-default-namespace 301

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Move to be in the same section as the content that currently exists within (that section is titled “Extend Kubernetes”). Consider moving to as well. Redirects will be helpful too. Why is this needed is showing the reader how to extend Kubernetes (by implementing a custom scheduler) more than it is explaining how to administer a cluster. Comments
/priority backlog
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. 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
/sig scheduling
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. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/assign
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-testing, kubernetes/test-infra and/or . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /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
Change:
# change is that the Hugo version is now an overridable argument rather than a fixed # environment variable. <del> FROM golang:1.15-alpine </del> <ins> FROM golang:1.16-alpine </ins> LABEL maintainer="Luc Perkins <lperkins@linuxfoundation.org>" RUN apk add --no-cache  curl  <ins> gcc  g++  musl-dev  build-base  libc6-compat ARG HUGO_VERSION RUN mkdir $HOME/src &&  cd $HOME/src &&  curl -L https://github.com/gohugoio/hugo/archive/refs/tags/v${HUGO_VERSION}.tar.gz | tar -xz &&  cd "hugo-${HUGO_VERSION}" &&  go install --tags extended FROM golang:1.16-alpine RUN apk add --no-cache  </ins> git  openssh-client  rsync  <del> build-base  libc6-compat  </del> npm &&  npm install -D autoprefixer postcss-cli <del> ARG HUGO_VERSION </del> RUN mkdir -p /usr/local/src &&  cd /usr/local/src &&  <del> curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz &&  mv hugo /usr/local/bin/hugo &&  </del> addgroup -Sg 1000 hugo &&  adduser -Sg hugo -u 1000 -h /src hugo <ins> COPY --from=0 /go/bin/hugo /usr/local/bin/hugo </ins> WORKDIR /src USER hugo:hugo

Discussion:
This is a Feature Request What would you like to be Right now, building container images for local use of this repository via does not work with Apple Silicon chips. This is because the Dockerfile downloads the Hugo binary for amd64 architecture. I have been able to workaround this issue by explicitly asking for , however, containers built in this way have very poor performance. Instead, I would like to contribute a Dockerfile that works for arm64 architecture, in a way that contributors can build container images that work in architectures that are not amd64. Why is this needed Provide a better contributor experience while creating new documentation pages and testing them locally using containers.
I created pull request with a Dockerfile and Makefile target that I have tested to address this issue.
/retitle Docs build container image only supports AMD64 architecture
/priority backlog /triage accepted
Change:
sudo kubeadm init --control-plane-endpoint "LOAD_BALANCER_DNS:LOAD_BALANCER_PORT" --upload-certs ``` - You can use the `--kubernetes-version` flag to set the Kubernetes version to use. <del> It is recommended that the versions of kubeadm, kubelet, kubectl and Kubernetes match. </del> <ins> It is recommended that the versions of kubeadm, kubelet, kubectl and Kubernetes match. </ins> - The `--control-plane-endpoint` flag should be set to the address or DNS and port of the load balancer. - The `--upload-certs` flag is used to upload the certificates that should be shared <del> across all the control-plane instances to the cluster. If instead, you prefer to copy certs across control-plane nodes manually or using automation tools, please remove this flag and refer to [Manual certificate distribution](#manual-certs) section below. </del> <ins> across all the control-plane instances to the cluster. If instead, you prefer to copy certs across control-plane nodes manually or using automation tools, please remove this flag and refer to [Manual certificate distribution](#manual-certs) section below. </ins> {{< note >}} The `kubeadm init` flags `--config` and `--certificate-key` cannot be mixed, therefore if you want <del> to use the [kubeadm configuration](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2) you must add the `certificateKey` field in the appropriate config locations (under `InitConfiguration` and `JoinConfiguration: controlPlane`). </del> <ins> to use the [kubeadm configuration](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2) you must add the `certificateKey` field in the appropriate config locations (under `InitConfiguration` and `JoinConfiguration: controlPlane`). </ins> {{< /note >}} {{< note >}}

Discussion:
This is a Bug Report Formatting is off (broken HTML rendering) on page since earlier this week (Wednesday sometime?) per my comment in - I'm adding as a separate ticket for tracking. Some fixes to Hugo were made in and but the issues on this page are persisting. Problem: Seeing poor formatting and plaintext HTML due to some incorrect syntax on the page: ! - screenshot taken in FireFox, but replicated in Chromium (Brave) as well. Page to Update: Thank you! [EDIT] heh - I switched GitHub accounts - the comments I was referring to were by my other account
thanks for the report. cc possibly caused by the hugo bump too? /sig docs cluster-lifecycle /kind bug
Relates to tracking issue
This is almost fixed. There are some leftovers related to the ordered list. /assign