jiebi/CodeConvo huggingface dataset:
Code change:
[outdated_blog__message] other = "这篇文章已经一年多了，较旧的文章可能包含过时的内容。请检查从发表以来，页面中的信息是否变得不正确。" <ins> [post_create_issue] other = "登记一个问题" </ins> [prerequisites_heading] other = "准备开始"

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign
Code change:
### Needs UX Review * Issues that are suggestions for improving the user interface of the site. <del> * Fixing broken site elements. </del> <ins> * Fixing broken site elements. </ins> ## Prioritizing Issues

Related discussion:
text: <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:
Code change:
[javascript_required] other = "必须[启用](https://www.enable-javascript.com/) JavaScript 才能查看此页内容" <del> [katacoda_removal_warning] other = """本页面上的此在线教程在 <time datetime="2022-06-15">2022 年 6 月 15 日</time>后[无法继续使用](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html)。""" </del> [latest_release] other = "最新发行版本："

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign
Code change:
A [cluster-level logging](/docs/concepts/cluster-administration/logging/) mechanism is responsible for saving container logs to a central log store with search/browsing interface. <ins> ### Network Plugins [Network plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins) are software components that implement the container network interface (CNI) specification. They are responsible for allocating IP addresses to pods and enabling them to communicate with each other within the cluster. </ins> ## {{% heading "whatsnext" %}}

Related discussion:
text: I was reading this page to learn about an addon that the installation page mentions as indispensable, i.e. the CNI addon. Strangely it isn't even mentioned on the page.
/retitle Mention network plugins in “Kubernetes Components” It does make sense to mention network plugins as an example of an add-on. /triage accepted /language en /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
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-contributor-experience at . /lifecycle rotten
/remove-lifecycle rotten
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
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-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /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
/reopen This is still a valid issue.
Reopened this issue. <detailsIn response to : /reopen This is still a valid issue.
Code change:
A [cluster-level logging](/docs/concepts/cluster-administration/logging/) mechanism is responsible for saving container logs to a central log store with search/browsing interface. <ins> ### Network Plugins [Network plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins) are software components that implement the container network interface (CNI) specification. They are responsible for allocating IP addresses to pods and enabling them to communicate with each other within the cluster. </ins> ## {{% heading "whatsnext" %}}

Related discussion:
text: 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
/lifecycle frozen
Page to be modified: What needs to be : A section about Network Plugins under Addons Where can you find more information about Network Plugins on our docs: Does that sound right? If yes, we can open this up for contributions as a good-first issue. I understand there are several other higher-priority issues, but I also think this is low-hanging fruit that can be completed easily.
/assign
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: nginx spec: affinity: nodeAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 1 preference: matchExpressions: - key: disktype operator: In values: - ssd containers: - name: nginx image: nginx imagePullPolicy: IfNotPresent </ins>

Related discussion:
text: This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Code change:
body.cid-community #navigation-items { padding: 0.25em; <del> width: 100vw; </del> <ins> width: 100%; </ins> max-width: initial; margin-top: 2.5em;

Related discussion:
text: 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: Proposed Solution: Page to Update: /assign
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
During my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.
/area web-development
I tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.
I see, In that case I'll try to find anymore pages that might be having the same issue.
Similar issue is present in case study
Code change:
--> ### 内置快照 <del> etcd 支持内置快照，因此备份 etcd 集群很容易。快照可以从使用 `etcdctl snapshot save` 命令的活动成员中获取，也可以通过从 etcd [数据目录](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/configuration.md#--data-dir)复制 `member/snap/db` 文件，该 etcd 数据目录目前没有被 etcd 进程使用。获取快照通常不会影响成员的性能。 </del> <ins> etcd 支持内置快照。快照可以从使用 `etcdctl snapshot save` 命令的活动成员中获取， 也可以通过从 etcd [数据目录](https://etcd.io/docs/current/op-guide/configuration/#--data-dir) 复制 `member/snap/db` 文件，该 etcd 数据目录目前没有被 etcd 进程使用。获取快照不会影响成员的性能。 </ins> 下面是一个示例，用于获取 `$ENDPOINT` 所提供的键空间的快照到文件 `snapshotdb`： <del> ```sh </del> <ins> ```shell </ins> ETCDCTL_API=3 etcdctl --endpoints $ENDPOINT snapshot save snapshotdb <del> # exit 0 </del> <ins> ``` </ins> <del> # verify the snapshot </del> <ins> 验证快照: ```shell </ins> ETCDCTL_API=3 etcdctl --write-out=table snapshot status snapshotdb <ins> ``` ```console </ins> +----------+----------+------------+------------+ |   HASH   | REVISION | TOTAL KEYS | TOTAL SIZE | +----------+----------+------------+------------+

Related discussion:
text: " etcd "client.cert " etcd etcd " " etcd client.key etcd "
~ GitHub is not the right place for support requests.~ ~If you're looking for help, oyu could ask on .~ ~You can also post your question on the or the forum. There are other support venues with contributions from the wider community of Kubernetes users.~
/triage accepted /kind bug
/remove-kind support
Thanks
/language zh
/priority backlog
Code change:
/docs/user-guide/persistent-volumes/index     /docs/concepts/storage/persistent-volumes/ 301 /docs/user-guide/persistent-volumes/index.md     /docs/concepts/storage/persistent-volumes/ 301 /docs/user-guide/persistent-volumes/walkthrough/     /docs/tasks/configure-pod-container/configure-persistent-volume-storage/ 301 <del> /docs/user-guide/petset/     /docs/concepts/workloads/controllers/statefulset/ 301 /docs/user-guide/petset/bootstrapping/     /docs/concepts/workloads/controllers/statefulset/ 301 </del> /docs/user-guide/pod-preset/     /docs/tasks/inject-data-application/podpreset/ 301 /docs/user-guide/pod-security-policy/     /docs/concepts/policy/pod-security-policy/ 301 /docs/user-guide/pod-states/     /docs/concepts/workloads/pods/pod-lifecycle/ 301

Related discussion:
text: This is a... [ ] Feature Request [x] Bug Report Problem: There is a link missing that was supposed to be in section Differences between alpha PetSets and beta StatefulSets under it in the second point StatefulSet guards against split brain which ends with following text TODO: Link to doc about fencing. Change it and add the link that is required. Proposed Solution: Add link which is missing Page to Update:
PetSet has long been replaced by StatefuSet and StatefulSet has been GA'ed in 1.9. So we are going to remove this page to avoid further confusion.
Code change:
# Install Docker CE apt-get update && apt-get install -y  containerd.io=1.2.13-2  <del> docker-ce=5:19.03.11~3-0~~ubuntu-$(lsb_release -cs)  docker-ce-cli=5:19.03.11~3-0~~ubuntu-$(lsb_release -cs) </del> <ins> docker-ce=5:19.03.11~3-0~ubuntu-$(lsb_release -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) </ins> ``` ```shell

Related discussion:
text: 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 is an error in the command to Install Docker CE for Ubuntu 16.04+ Proposed Solution: Update the command whicht tells to Install Docker CE for Ubuntu. The command sais: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0ubuntu-$(lsbrelease -cs) But it should be: apt-get update && apt-get install -y   docker-ce=5:19.03.11~3-0~ubuntu-$(lsbrelease -cs)  docker-ce-cli=5:19.03.11~3-0~ubuntu-$(lsb_release -cs) so it should be only 1 character of ~ instead of 2 ~~ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign
Code change:
- Administrators should limit access to etcd to admin users - Secret data in the API server is at rest on the disk that etcd uses; admins may want to wipe/shred disks used by etcd when no longer in use <ins> - If you configure the secret through a manifest (JSON or YAML) file which has the secret data encoded as base64, sharing this file or checking it in to a source repository means the secret is compromised. Base64 encoding is not an encryption method and is considered the same as plain text. </ins> - Applications still need to protect the value of secret after reading it from the volume, such as not accidentally logging it or transmitting it to an untrusted party. - A user who can create a pod that uses a secret can also see the value of that secret.  Even

Related discussion:
text: <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: identified for Kubernetes Secrets should indicate that the secrets stored in YAML files must be protected. Proposed Solution: Add Risk Bullet: If a Base64 encoded secret is shared, it should be considered Compromised. For Example: Checking into source control, placing on a document share, or emailing All of these expose your secret to everyone who has access. Base64 is considered so secrets encoded as Base64 require additional controls to ensure only authorized users/systems can access them. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Add the bullet above under the following section:
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
issue solved.
Code change:
you implement yourself * using the [Operator Framework](https://operatorframework.io) * [Publish](https://operatorhub.io/) your operator for other people to use <del> * Read [CoreOS' original article](https://coreos.com/blog/introducing-operators.html) that introduced the Operator pattern </del> <ins> * Read [CoreOS' original article](https://web.archive.org/web/20170129131616/https://coreos.com/blog/introducing-operators.html) that introduced the Operator pattern (this is an archived version of the original article). </ins> * Read an [article](https://cloud.google.com/blog/products/containers-kubernetes/best-practices-for-building-kubernetes-operators-and-stateful-apps) from Google Cloud about best practices for building Operators

Related discussion:
text: 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: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Following a series of acquisitions it looks like that article is no longer published. I couldn't find a current URL for it. Proposed Solution: Update the link to point at and mention in the text that this is archived from the original. Page to Update: Additional Information: To edit via GitHub web interface: /kind bug /priority backlog /language en /triage accepted /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: In the section of the Operator pattern concept page there is a link to CoreOS' original article about the Operator pattern. Update the link to point at and mention in the text that this is archived from the original. To edit via GitHub web interface: /priority backlog /language en /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
I would like to take this one. This will be my first time contributing to repo, so I might take a while.
/assign
Fixed in /close
Closing this issue. <detailsIn response to : Fixed in /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
Code change:
{{< feature-state for_k8s_version="v1.19" state="stable" >}} <del> A CertificateSigningRequest (CSR) resource is used to request that a certificate be signed </del> <ins> A [CertificateSigningRequest](/docs/reference/kubernetes-api/authentication-resources/certificate-signing-request-v1/) (CSR) resource is used to request that a certificate be signed </ins> by a denoted signer, after which the request may be approved or denied before finally being signed.

Related discussion:
text: 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. --In the document , it would be helpful to link to the . Why is this needed I was studying for the CKA exam, and was practicing only using the pages to search for info about CertificateSigningRequests. The doc came up readily, but the was not so easily discoverable via a search using only the search interface. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/triage accepted
Code change:
* Block device mapping * Memory as the storage medium (for example, `emptyDir.medium` set to `Memory`) * File system features like uid/gid; per-user Linux filesystem permissions <del> * Setting [secret permissions with DefaultMode](/docs/concepts/configuration/secret/#secret-files-permissions) (due to UID/GID dependency) </del> <ins> * Setting [secret permissions with DefaultMode](/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys) (due to UID/GID dependency) </ins> * NFS based storage/volume support * Expanding the mounted volume (resizefs)

Related discussion:
text: This is a Bug Report <!--Required Information--Problem: The link for under in is incorrect. It is redirecting to the instead of that it should redirect to the . As given in the , the (line 195) shows the heading is changed to from . Proposed Solution: should redirect to the instead of Page to Update:
/language en /sig docs /sig storage
I would like to work on it. /assign
/triage accepted A fixup/clarification is welcome.
/assign
The issue is fixed here:
Code change:
[community_youtube_name] other = "YouTube" <ins> [cve_id] other = "CVE ID" [cve_issue_url] other = "CVE GitHub Issue URL" [cve_json_external_url] other = "external_url" [cve_json_id] other = "id" [cve_json_summary] other = "概要" [cve_json_url] other = "url" [cve_summary] other = "问题描述" [cve_table] other = "Kubernetes CVE 列表" [cve_url] other = "CVE URL" </ins> [deprecation_title] <del> other = "您正在查看 Kubernetes 版本的文档：" </del> <ins> other = "你正在查看的文档所针对的是 Kubernetes 版本：" </ins> [deprecation_warning] <del> other = " 版本的文档已不再维护。您现在看到的版本来自于一份静态的快照。如需查阅最新文档，请点击" </del> <ins> other = " 版本的文档已不再维护。你现在看到的版本来自于一份静态的快照。如需查阅最新文档，请点击" </ins> [deprecation_file_warning] other = "已过时"

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign
Code change:
``` Serviços possuem endereço IP dedicado e são disponibilizados para o contêiner via DNS, <del> se possuírem [DNS addon](https://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/) habilitado. </del> <ins> se possuírem [DNS addon](https://releases.k8s.io/{{< param "fullversion" >}}/cluster/addons/dns/) habilitado. </ins>

Related discussion:
text: This is a Bug Report Problem: Regarding , I found the similar broken links on other pages. English pages have already been fixed. ref: pt pages also need to be fixed. Proposed Solution: Fixes broken links including {{< param "githubbranch" }} to master. In the case of link to , fixes to {{< param "fullversion" }}. ref:
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
/assign