jiebi/CodeConvo huggingface dataset:
Change:
max-width: 80%; border: 1px solid rgb(222, 226, 230); border-radius: 5px; <ins> margin-bottom: 1rem; padding-top: 1rem; padding-bottom: 1rem; // mermaid diagram - sequence diagram .actor { fill: #326ce5 !important; } text.actor { font-size: 18px !important; stroke: white !important; fill: white !important; } .activation0 { fill: #c9e9ec !important; } </ins> } /* HEADER */

Discussion:
This is a Feature Request What would you like to be Replace the sequence diagram on with the one by . This is the follow-up of . Why is this needed There are several pros to use mermaid to draw the sequence diagram: mermaid format is more readable easy to modify better styling Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/assign
/kind cleanup /language en /triage accepted /priority backlog
Change:
cid: docsHome layout: docsportal_home class: gridPage gridPageHome <del> linkTitle: "Home" </del> <ins> linkTitle: "Documentation" </ins> main_menu: true weight: 10 hide_feedback: true

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: "Home" button at footer is linked to docs home page instead of K8s site home page Proposed Solution: Either that button should be linked to K8s site home page or that button should be renamed to "Documentation" instead of "Home" ! <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Thanks I'd change it to read “Documentation”. /priority backlog /help /triage accepted /language en
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 : Thanks I'd change it to read “Documentation”. /priority backlog /help /triage accepted /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
Change:
lrwxrwxrwx  ... Feb 6 21:47 annotations -> ..data/annotations lrwxrwxrwx  ... Feb 6 21:47 labels -> ..data/labels <del> /etc/..2982_06_02_21_47_53.299460680: </del> <ins> /etc/podinfo/..2982_06_02_21_47_53.299460680: </ins> total 8 -rw-r--r--  ... Feb  6 21:47 annotations -rw-r--r--  ... Feb  6 21:47 labels

Discussion:
the file labels and annotations should be in the directory /etc/podinfo not /etc !
Hi What's the URL of the web page that isn't right? /triage needs-information
/triage accepted
/assign
Change:
<ins> --- title: cAdvisor id: cadvisor date: 2021-12-09 full_link: https://github.com/google/cadvisor/ short_description: > Tool that provides understanding of the resource usage and perfomance characteristics for containers aka: tags: - tool --- cAdvisor (Container Advisor) provides container users an understanding of the resource usage and performance characteristics of their running {{< glossary_tooltip text="containers" term_id="container" >}}. <!--more--> It is a running daemon that collects, aggregates, processes, and exports information about running containers. Specifically, for each container it keeps resource isolation parameters, historical resource usage, histograms of complete historical resource usage and network statistics. This data is exported by container and machine-wide. </ins>

Discussion:
Kubernetes manages the lifecycle of all images through its image manager, which is part of the kubelet, with the cooperation of cadvisor. Needs pop up note on cadvisor
/kind feature /language en I think by pop up note, you're talking about a . Good suggestion, thanks! To fix this, someone should: add a new glossary entry read for context look in copy an existing item to use as a template (make sure to change everything that needs changing) add a glossary tooltip for cadvisor to /help /triage accepted
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 : /kind feature /language en add a new glossary entry /triage accepted 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 backlog
Change:
1. API server内のPodは、猶予期間を越えるとPodが「死んでいる」と見なされるように更新される。 削除中のPodに対して`kubectl describe`コマンドを使用すると、Podは「終了中」と表示される。 Podが実行されているNode上で、Podが終了しているとマークされている(正常な終了期間が設定されている)とkubeletが認識するとすぐに、kubeletはローカルでPodの終了プロセスを開始します。 <del> 1. Pod内のコンテナの1つが`preStop`[フック](/ja/docs/concepts/containers/container-lifecycle-hooks/#hook-details)を定義している場合は、コンテナの内側で呼び出される。猶予期間が終了した後も `preStop`フックがまだ実行されている場合は、一度だけ猶予期間を延長される(2秒)。 </del> <ins> 1. Pod内のコンテナの1つが`preStop`[フック](/ja/docs/concepts/containers/container-lifecycle-hooks)を定義している場合は、コンテナの内側で呼び出される。猶予期間が終了した後も`preStop`フックがまだ実行されている場合は、一度だけ猶予期間を延長される(2秒)。 </ins> {{< note >}} `preStop`フックが完了するまでにより長い時間が必要な場合は、`terminationGracePeriodSeconds`を変更する必要があります。 {{< /note >}}

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted
Change:
- **trafficDistribution** (string) <del> TrafficDistribution offers a way to express preferences for how traffic is distributed to Service endpoints. Implementations can use this field as a hint, but are not required to guarantee strict adherence. If the field is not set, the implementation will apply its default routing strategy. If set to "PreferClose", implementations should prioritize endpoints that are topologically close (e.g., same zone). This is an alpha field and requires enabling ServiceTrafficDistribution feature. </del> <ins> TrafficDistribution offers a way to express preferences for how traffic is distributed to Service endpoints. Implementations can use this field as a hint, but are not required to guarantee strict adherence. If the field is not set, the implementation will apply its default routing strategy. If set to "PreferClose", implementations should prioritize endpoints that are topologically close (e.g., same zone). This is an beta field and requires enabling ServiceTrafficDistribution feature. </ins>

Discussion:
This is a documentation mismatch 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: I was looking over the release notes and when looking into i noticed that the docs show that it's still in alpha yet when we look into the , , and it says that it's now in a beta state. Proposed Solution: We'll want to update the docs to prevent any confusion for future users Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
I believe you're correct thank you for spotting it! It looks like this is part of the auto generated docs. I will add a PR with a fix. /sig network
/retitle shows as alpha despite graduating to beta in v1.31 For this repo, we can take the docs part as a given.
/language en
The same upstream change would fix
/triage accepted
/assign
Change:
font-size: 16px; background-color: #3371e3; text-decoration: none; <ins> text-align: center; </ins> } <del> h5 { </del> <ins> body.cid-training h5 { </ins> font-size: 16px; font-weight: 500; line-height: 1.5em; margin-bottom: 2em; } <del> .white-text { </del> <ins> body.cid-training .white-text { </ins> color: #fff; } <del> .padded { </del> <ins> body.cid-training .padded { </ins> padding-top: 100px; padding-bottom: 100px; } <del> .blue-bg { </del> <ins> body.cid-training .blue-bg { </ins> background-color: #3371e3; } <del> .lighter-gray-bg { </del> <ins> body.cid-training .lighter-gray-bg { </ins> background-color: #f4f4f4; } <del> .two-thirds-centered { </del> <ins> body.cid-training .two-thirds-centered { </ins> width: 66%; max-width: 950px; margin-left: auto; margin-right: auto; } <del> .landscape-section { </del> <ins> body.cid-training .landscape-section { </ins> margin-left: auto; margin-right: auto; max-width: 1200px; width: 100%; } <del> #landscape { </del> <ins> body.cid-training #landscape { </ins> opacity: 1; visibility: visible; overflow: hidden;

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 Update to mention the new Kubernetes Security Specialist Certification Why is this needed There is a Kubernetes Security Specialist Certification, coming in November 2020. Comments /kind feature /language en
/priority important-soon
let's collaborate to put everything in place to make this into a Good First Issue.
Design-wise, it's much easier to place 2 certification logos than 3. do you have any thoughts on how to adjust things design-wise to incorporate the 3rd certification?
/sig security
/triage accepted
/cc
Change:
* [扩大 Deployment 规模以承担更多负载](#scaling-a-deployment)。 * [暂停 Deployment ](#pausing-and-resuming-a-deployment) 以应用对 PodTemplateSpec 所作的多项修改， 然后恢复其执行以启动新的上线版本。 <del> * [使用 Deployment 状态](#deployment-status) 来判定上线过程是否出现停滞。 </del> <ins> * [使用 Deployment 状态](#deployment-status)来判定上线过程是否出现停滞。 </ins> * [清理较旧的不再需要的 ReplicaSet](#clean-up-policy) 。 <!--

Discussion:
There are some bugs: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" "image updated to 1.9.1" should be changed to "image updated to 1.16.1" The content of this article has many "", it could be changed to "deployment". For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
/language zh
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted 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
looks like docs is already updated to nginx:1.16.1. Do you mind closing this issue?
There should still be a few places left unfinished.
Could you please edit the issue which needs to be still updated?
Bug1: ,nginx%3Dnginx%3A1.9.1,-%2D%2Drecord%3Dtrue%0A3 "nginx=nginx:1.9.1" should be changed to "nginx=nginx:1.16.1" Bug2: ,nginx%3Dnginx%3A1.91,-%2D%2Drecord%3Dtrue "nginx=nginx:1.91" should be changed to "nginx=nginx:1.161" Bug3: "image updated to 1.9.1" should be changed to "image updated to 1.16.1" Bug4: The content of this article has many "", it could be changed to "deployment".

For example: ,,-%E8%BE%93%E5%87%BA%E7%B1%BB%E4%BC%BC%E4%BA%8E "kubectl rollout history " could be changed to "kubectl rollout history deployment/nginx-deployment"
Thanks for clarifying. /assign
/retitle [zh] Localization bugs / work required for Deployment concept
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
/triage accepted
Change:
ClusterIP range is subdivided. Dynamic allocated ClusterIP addresses will be allocated preferently from the upper range allowing users to assign static ClusterIPs from the lower range with a low risk of collision. See <del> [Avoiding collisions](/docs/concepts/services-networking/service/#avoiding-collisions) </del> <ins> [Avoiding collisions](/docs/reference/networking/virtual-ips/#avoiding-collisions) </ins> for more details. - `SizeMemoryBackedVolumes`: Enable kubelets to determine the size limit for memory-backed volumes (mainly `emptyDir` volumes).

Discussion:
This is a Bug Report Problem: Links for Avoiding collisions are broken in: (at point) Proposed Solution: Update in both pages with Other possible solutions: Page to Update:
/language en /area blog
/retitle Broken links for "Avoiding collisions" in 'Service' and 'Feature Gates' page /remove-area blog
I think the link became broken during the revision process of the Service concept page. We should make an update to direct it to the correct location, which I believe is /priority backlog /triage accepted
/assign
/sig docs PR raised
Similar to
Change:
--- title: Tutorial Interativo - Expondo seu aplicativo weight: 20 <ins> headless: true toc_hide: true _build: list: never publishResources: false </ins> --- <!DOCTYPE html>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
readinessProbe: tcpSocket: port: 8080 <del> initialDelaySeconds: 5 </del> <ins> initialDelaySeconds: 15 </ins> periodSeconds: 10 livenessProbe: tcpSocket: port: 8080 initialDelaySeconds: 15 <del> periodSeconds: 20 </del> <ins> periodSeconds: 10 </ins>

Discussion:
This is a Bug Report Problem: The intial definiton given in doesn't describe that if the first probe time will be = . For example: The pod will be marked as after 60s, (tested in k8s v1.22.10). Moreover, the given if i read this code correctly, then the check is done for and the check for is done after assuming that value of Proposed Solution: Allign code and the documentation. Page to Update:
/sig docs /language en
/assign
I did tested this on the k8s 1.27 and it's still same.
I believe this is a corner case. Why do you set initialDelaySeconds to be shorter than perdioSeconds in the first place? I'm not objecting the clarification, BTW. What I am wondering is if there is a real case people will do this.
Okay. I get it now. The example manifest has a problem to fix. Thanks for raising up this.
/triage accepted
thanks :)
Change:
- kow3ns title: Safely Drain a Node content_type: task <del> min-kubernetes-server-version: 1.5 </del> weight: 310 ---

Discussion:
The PR improperly set the minim version to 1.5 when there is no such version. Public link: Markdown file: ! !
/assign
kubernetes 1.5 release end of life (1 October 2017) already passed so this page needs updation
/kind bug
I guess it is mentioned because in v1.5: As per release It totally depends upon the docs and /sig node what they want to mention. If it is mentioned because of the time this feature went beta this page might be right.
/retitle “Safely Drain a Node” states that you need Kubernetes 1.5 or later /language en That statement is correct and its inclusion does not, to me, feel misleading. /priority awaiting-more-evidence
Just to confirm the version indicates the complete functionality is not available until v1.5 is released? PDB is . Only confusing area is what functionality in the document is for 1.5 and what is available now?
Try this: The page does not say you need to wait for an upcoming release. I think you have misunderstood what is actually a clear statement We could drop the shortcode as we assume everyone is using Kubernetes 1.21 or later.
/triage accepted Drop the version-check would be desireable.
/priority important-longterm
For SIG Docs, this is only a backlog priority I think. We've other work that we'd want to prioritize. Help here is still very welcome!
Change:
} ``` <ins> {{<note>}} The keys and the values in the map must be strings. In other words, you cannot use numeric, boolean, list or other types for either the keys or the values. {{</note>}} </ins> Here are some examples of information that could be recorded in annotations: * Fields managed by a declarative configuration layer. Attaching these fields

Discussion:
This is a Feature Request Currently only key validity is specified. There is no mention on that e.g. numeric, boolean, list or other types for annotation values are not permitted.
/triage accepted /sig architecture
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-contributor-experience at . /lifecycle stale
/remove-lifecycle stale /assign
Change:
requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: <del> - key: kubernetes.io/os </del> <ins> - key: topology.kubernetes.io/zone </ins> operator: In values: <del> - linux </del> <ins> - antarctica-east1 - antarctica-west1 </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: kubernetes.io/os </del> <ins> - key: topology.kubernetes.io/zone </ins> operator: In values: <del> - linux </del> <ins> - antarctica-east1 - antarctica-west1 </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:
to validate the request. If an expression evaluates to false, the validation check is enforced according to the `spec.failurePolicy` field. <ins> {{< note >}} You can quickly test CEL expressions in [CEL Playground](https://playcel.undistro.io). {{< /note >}} </ins> To configure a validating admission policy for use in a cluster, a binding is required. The following is an example of a ValidatingAdmissionPolicyBinding.:

Discussion:
Hello there, I would like to suggest adding a link to the CEL Playground in the Kubernetes documentation. CEL (Common Expression Language) is used in Kubernetes APIs, such as the , and the CEL Playground can help users easily test expressions. The playground also includes a set of examples and the . I believe the link would be useful on the following pages: The CEL Playground is available at and the source code can be found at I also invite you to test and contribute to the project. Thank you.
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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 docs
/transfer website The repo is not quite the right place to track this.
/language en /kind feature
If we add a link, I would add it to: (and I wouldn't add it to the reference page ; instead, we can have link to the three pages I listed above)
/wg api-expression
@ Hey which particular points on these links would you want the CEL playground. I will be glad for more clarification on this?
IMHO, a mention similar to the mention of on the would help: but saying that users can quickly test CEL expressions in the playground.
Hi I've opened a PR () with some suggestions for adding the CEL Playground link. Please take a look and let me know your thoughts. Inviting to share their thoughts as well.
I'm supportive of this. It's a wonderful tool and the community will benefit from being more aware of it.
/triage accepted