jiebi/CodeConvo huggingface dataset:
Change:
* [Daemon Sets](http://kubernetes.io/docs/admin/daemons/) which ensure that all or some of the nodes in your cluster run a copy of a Pod. * [Deployments](http://kubernetes.io/docs/user-guide/deployments/) which provide declarative updates for Pods and Replica Sets (the next-generation [Replication Controller](http://kubernetes.io/docs/user-guide/replication-controller/)) The Details page for a Deployment lists resource details, as well as new and old Replica Sets. The resource details also include information on the [RollingUpdate](http://kubernetes.io/docs/user-guide/rolling-updates/) strategy, if any. <del> * [Pet Sets](http://kubernetes.io/docs/user-guide/load-balancer/) (nominal Services, also known as load-balanced Services) for legacy application support. </del> <ins> * [Pet Sets](http://kubernetes.io/docs/user-guide/petset/) (nominal Services, also known as load-balanced Services) for legacy application support. </ins> * [Replica Sets](http://kubernetes.io/docs/user-guide/replicasets/) for using label selectors. * [Jobs](http://kubernetes.io/docs/user-guide/jobs/) for creating one or more Pods, ensuring that a specified number of them successfully terminate, and tracking the completions. * [Replication Controllers](http://kubernetes.io/docs/user-guide/replication-controller/)

Discussion:
[ ] Feature Request [x] Bug Report /kind bug Flex volume docs still stay the feature is Alpha. We made it GA in Kube 1.8 time frame. We have to update the docs to reflect it. /sig storage Kubernetes version: 1.9 or master
Create new docs issue
Fixed in
Change:
<!--more--> Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling. <ins> The applications that run inside containers are called containerized applications. The process of bundling these applications and their dependencies into a container image is called containerization. </ins>

Discussion:
This is a Feature Request What would you like to be Add Abbreviation of in as this word mentioned in . Why is this needed This change will help to understand about containerized applications for the people who are unfamiliar with . Comments kind/feature
/assign
When you say ”abbreviation”, do you mean “explanation”? We might like to borrow from or We also already have - maybe we can expand that? /language en
Hi Yes, basic Explanation/information about . Yes, my idea is same to expand this by adding about . WDYT? If you think it's better to borrow from here, i can follow the same. Please provide your opinion.
Hi Can you please comment on above.
I recommend expanding rather than adding a new entry for “containerized application”. I don't mind whether or not you borrow from the Cloud Native Glossary - feel free to do it whichever way you prefer.
Thanks for your comment, I will work on it and raise PR soon.
Fixed it here .
Should we make this change? Any objections?
Personally, I like what's done here, and I was just waiting for someone with "better experience" in the glossary entries to approve it.
Hi Thanks for sharing your feedback. Can anyone else please comment on it.
/triage accepted
Change:
requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: topology.kubernetes.io/zone </del> <ins> - key: kubernetes.io/os </ins> operator: In values: <del> - antarctica-east1 - antarctica-west1 </del> <ins> - linux </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:

Discussion:
Description of Node Affinity example pod spec "pods/pod-with-node-" contains an error: does not apply. The spec shows instead that key "" should be "". Under the Node Affinity Weight section, the following note is also out-of-place: It needs to be moved to the previous section.
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
This issue is a duplicate of . /triage duplicate

Just above this anchor #node-affinity-per-scheduling-profile, the note block is referring to the Pod spec pod-with-node- 2 above, but it's placement appears to refer to the one immediately above. It takes a little bouncing around the page to sort it out :)
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

Only minor confusion, after the first example Pod spec, where "In this example, the following rules apply:" the bullet points that follow are misleading where first bullet refers to the example below, the second to the example above.
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

! The label with the key not exist in the example for node affinity:
/kind bug /language en /triage accepted Thanks for reporting this. I would fix this discrepancy by copying the example manifest to make a new example, that does use the key key. The Git history might show a previous version that already did, which would make it easier to write the copy. The reason I'd make that copy is because I suspect that more than one page relies on the same example (and that's why an unhelpful change has slipped through).
/assign
Change:
requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: topology.kubernetes.io/zone </del> <ins> - key: kubernetes.io/os </ins> operator: In values: <del> - antarctica-east1 - antarctica-west1 </del> <ins> - linux </ins> preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference:

Discussion:
pods/pod-with-node-affinity.yaml
Page: /language zh
/triage accepted The YAML file was not sync'ed with English version.
/assign
Change:
} 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];

Discussion:
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).
Change:
### kubectlの自動補完を有効にする <del> すべてのシェルセッションにてkubectlの補完スクリプトをsourceできるようにしなければなりません。 </del> <ins> 次に、kubectl補完スクリプトがすべてのシェルセッションで読み込まれるように設定する必要があります。 </ins> これを行うには複数の方法があります: <del> - 補完スクリプトを`~/.bash_profile`内でsourceする: </del> <ins> - 補完スクリプトを`~/.bash_profile`内で読み込ませる: </ins> ```bash echo 'source <(kubectl completion bash)' >>~/.bash_profile

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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted
Change:
``` 크론 잡을 삭제하면 생성된 모든 잡과 파드가 제거되고 추가 잡 생성이 중지된다. <del> [가비지(garbage) 수집](/ko/docs/concepts/workloads/controllers/garbage-collection/)에서 잡 제거에 대해 상세한 내용을 읽을 수 있다. </del> <ins> [가비지(garbage) 수집](/ko/docs/concepts/architecture/garbage-collection/)에서 잡 제거에 대해 상세한 내용을 읽을 수 있다. </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:
{{% capture overview %}} An [Ingress](/docs/concepts/services-networking/ingress/) is an API object that defines rules which allow external access <del> to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress. {{< caution >}} For the Ingress resource to work, the cluster **must** also have an Ingress controller running. {{< /caution >}} </del> <ins> to services in a cluster. An [Ingress controller](/docs/concepts/services-networking/ingress-controllers/) fulfills the rules set in the Ingress. </ins> This page shows you how to set up a simple Ingress which routes requests to Service web or web2 depending on the HTTP URI.

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 page has a cautionary note about a prerequisite: this note belongs on the page, however the best place for it is in the Prerequisites section. Proposed Solution: Edit the page to move the caution note to be the very first thing inside the prerequisites section. Page to Update: /language en /kind cleanup /good-first-issue
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: The page has a cautionary note about a prerequisite: Caution: For the Ingress resource to work, the cluster must also have an Ingress controller running. Edit the page to move the caution note to be the very first thing inside the prerequisites section. /kind cleanup /good-first-issue 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
If you are looking to work on this and would like help, please reply here. I'll watch for replies.
Isn't there an effort underway to move minikube related pages onto the minikube site? and
I can work on this one! Should I?
I am looking to start contributing. looks like ..I can start with this.
Go for it! Contributions welcome. Bear in mind when it comes to deciding if you want to work on this. I think this example only happens to use Minikube; a separate PR could rework it to explain how to try out Ingress with a different kind of learning environment.
I'm reviewing the content and looks like the tutorial is explaining how to deploy the Ingress Controller, which is exactly what the caution note is mentioning. IMHO, the caution node should be removed instead of moved to other section.
another good point is that is saying the user could use Kubernetes playgrounds (Katacoda, play-with-k8s) which are not Minikube.
Sure, it's OK to remove the caution note. sounds like it could be a new separate issue(?)
Change:
</td> <td> <p><code>taints</code> specifies the taints the Node API object should be registered with. <del> If this field is unset, i.e. nil, in the <code>kubeadm init</code> process it will be defaulted to <code>'node-role.kubernetes.io/master=&quot;&quot;'</code>. If you don't want to taint your control-plane node, set this field to an empty list, i.e. <code>taints: []</code> in the YAML file. This field is </del> <ins> If this field is unset, i.e. nil, in the <code>kubeadm init</code> process it will be defaulted with a control-plane taint for control-plane nodes. If you don't want to taint your control-plane node, set this field to an empty list, i.e. <code>taints: []</code>, in the YAML file. This field is </ins> solely used for Node registration.</p> </td> </tr>

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: while cleaning up mentions of the legacy "master" taint in kubeadm docs: saw the following: it seems the generated reference API docs for kubeadm still include the "master" taint. Proposed Solution: cleanup mentions of the old taint from kubeadm's API reference docs at perhaps these need to be synced with: for dev-1.25 and main at k/website we removed the old taint from there before 1.24 was released. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
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
/sig cluster-lifecycle /priority important-soon /kind cleanup
cc
Change:
<tr><td>Open the <code>/_data/concepts.yaml</code> file.</td><td>Open the /_data/concepts.yaml file.</td></tr> </table> <ins> ### Use the international standard for punctuation inside quotes <table> <tr><th>Do</th><th>Don't</th></tr> <tr><td>events are recorded with an associated "stage".</td><td>events are recorded with an associated "stage."</td></tr> <tr><td>The copy is called a "fork".</td><td>The copy is called a "fork."</td></tr> </table> </ins> ## Inline code formatting ### Use code style for inline code and commands

Discussion:
This is a... [x] Feature Request [ ] Bug Report Problem: From : We should document that K8s follows the international standard for punctuation inside quotes. For example, the American standard: the international standard: Proposed Solution: Add a page for punctuation to the .
Change:
status to master if node status does not change. Kubelet will ignore this frequency and post node status immediately if any change is detected. It is only used when node lease feature is enabled. nodeStatusReportFrequency's <del> default value is 1m. But if nodeStatusUpdateFrequency is set explicitly, </del> <ins> default value is 5m. But if nodeStatusUpdateFrequency is set explicitly, </ins> nodeStatusReportFrequency's default value will be set to nodeStatusUpdateFrequency for backward compatibility. <del> Default: "1m"</td> </del> <ins> Default: "5m"</td> </ins> </tr>

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. Page to Update:
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
I would like to take up this ticket.
Change:
This would create a CSR for the username "jbeda", belonging to two groups, "app1" and "app2". <del> See [Managing Certificates](/docs/concepts/cluster-administration/certificates/) for how to generate a client cert. </del> <ins> See [Managing Certificates](/docs/tasks/administer-cluster/certificates/) for how to generate a client cert. </ins> ### Static Token File

Discussion:
This is a clean up 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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed is a task page. A better home for it would be within Comments Be sure to add Netlify redirects (see ) from the old to the new page. /language en /kind cleanup
/assign
From (I agree)
/sig auth
/triage accepted
I left notes (PR ) about how to create a new task page from the page. Does this sound like a good approach?
Change:
Kubernetes documentation welcomes improvements from all contributors, new and experienced! --> <del> 本网站由 [Kubernetes SIG（特别兴趣小组） Docs](/zh/docs/contribute/#参与docs特别兴趣小组) 维护. </del> <ins> 本网站由 [Kubernetes SIG（特别兴趣小组） Docs](/zh/docs/contribute/#get-involved-with-SIG-Docs) 维护. </ins> Kubernetes 文档项目的贡献者:

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: Chinese page is different with English version page. Proposed Solution: Update Chinese page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
thanks reviews and approvement from xichengliudui, tengqm and idealhack
Change:
This page shows how to attach handlers to Container lifecycle events. Kubernetes supports the postStart and preStop events. Kubernetes sends the postStart event immediately after a Container is started, and it sends the preStop event immediately before the <del> Container is terminated. </del> <ins> Container is terminated. A Container may specify one handler per event. </ins>

Discussion:
begins by stating: I suggest appending the following sentence: This was not obvious to me. In other programming contexts, multiple handlers per event are allowed; for example, in client-side JavaScript, more than one click handler may be specified.
/kind feature /language en /priority backlog /triage accepted /good-first-issue That's a nice improvement.
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 : /kind feature /language en /priority backlog /triage accepted /good-first-issue 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:
other = "Đóng góp" [main_copyright_notice] <del> other = """The Linux Foundation &reg;. Đã đăng ký Bản quyền. The Linux Foundation đã đăng ký và sử dụng nhãn hiệu. Để biết danh sách các nhãn hiệu của The Linux Foundation, xem <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">Trademark Usage page</a>""" </del> <ins> other = """The Linux Foundation &reg;. Tất cả các quyền được bảo lưu. The Linux Foundation đã đăng ký thương hiệu và sử dụng thương hiệu. Để xem danh sách các thương hiệu của The Linux Foundation, vui lòng xem trang <a href="https://www.linuxfoundation.org/trademark-usage" class="light-text">Sử dụng Thương hiệu của chúng tôi</a>""" </ins> [main_documentation_license] <del> other = """Các tác giả Kubernetes | Tài liệu được phân phối theo <a href="https://git.k8s.io/website/LICENSE" class="light-text">CC BY 4.0</a>""" [main_edit_this_page] other = "Sửa trang này" [main_github_create_an_issue] other = "Tạo một Issue" </del> <ins> other = """Tác giả Kubernetes | Tài liệu phân phối dưới <a href="https://git.k8s.io/website/LICENSE" class="light-text">CC BY 4.0</a>""" </ins> [main_github_invite] <del> other = "Quan tâm đến việc hacking mã nguồn Kubernetes?" </del> <ins> other = "Có quan tâm đến việc đóng góp vào mã nguồn chính của Kubernetes?" </ins> [main_github_view_on] other = "Xem trên GitHub" [main_kubernetes_features] <del> other = "Các tính năng của Kubernetes" </del> <ins> other = "Tính năng Kubernetes" </ins> [main_kubeweekly_baseline] <del> other = "Muốn nhận những tin tức Kubernetes mới nhất? Đăng kí KubeWeekly." </del> <ins> other = "Muốn nhận tin tức Kubernetes mới nhất không? Đăng ký KubeWeekly." </ins> [main_kubernetes_past_link] <del> other = "Xem các bản tin trước đây" </del> <ins> other = "Xem những bản tin trước đó" </ins> [main_kubeweekly_signup] <del> other = "Đăng kí" </del> <ins> other = "Đăng ký" </ins> [main_page_history] <del> other ="Lịch sử trang" </del> <ins> other ="Lịch sử Trang" </ins> [main_page_last_modified_on] <del> other = "Trang được sửa lần cuồi vào" </del> <ins> other = "Trang được chỉnh sửa lần cuối vào" </ins> [main_read_about] other = "Đọc về"

Discussion:
Đề nghị thay thế "lạc thú" bằng "lỗi thời" !
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
Please raise the issue in english putting the language code before the issue in [] example [vi] Issue title here It will be good practice to write the description and title of the issue in English only.
Thank you! BTW i'd commited about this change, waiting for review.
Fixed in