jiebi/CodeConvo huggingface dataset:
Change:
## Updating the pod's resources <del> Let's say the CPU requirements have increased, and 0.8 CPU is now desired. This is typically determined, and may be programmatically applied, by an entity such as </del> <ins> Let's say the CPU requirements have increased, and 0.8 CPU is now desired. This may be specified manually, or determined and programmatically applied by an entity such as </ins> [VerticalPodAutoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) (VPA). {{< note >}}

Discussion:
Not able to find which alpha feature gates for
/kind feature /triage accepted // +featureGate=InPlacePodVerticalScaling // +optional ResizePolicy []ContainerResizePolicy This field is controlled by the feature gate . It looks like we need to add a feature gate description. Does anyone want to help? /help
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 /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
There is a blog under review. I do concur that some docs are needed for such an important feature.
We should mention within didn't cover this detail.
InPlacePodVerticalScaling in also missing in
Fix coming in
Hi , as I am unable see the changes can I add it to the page?
The feature gate issue has been fixed but the feature description needs some more formal documentation. Please feel free to provide some inputs.
sure so we need to add the featureGate thing? here
It is not limited to the feature gate. It is about the feature. We are supposed to provide some brief introduction to this feature. Currently we have some texts on it, but those texts are provided as a blog (see ). Some of the blogs could have been part of the docs task page ().
thanks for clarifying
Note that this is the same issue as
Change:
[certified platforms](/docs/setup/production-environment/turnkey-solutions/). There are also other standardized and custom solutions across a wide range of cloud and bare metal environments. <del> -->。 </del> <ins> --> </ins> 可以[下载 Kubernetes](/releases/download/)，在本地机器、云或你自己的数据中心上部署 Kubernetes 集群。 如果你不想自己管理 Kubernetes 集群，则可以选择托管服务，包括[经过认证的平台](/zh/docs/setup/production-environment/turnkey-solutions/)。 在各种云和裸机环境中，还有其他标准化和定制的解决方案。

Discussion:
!
/triage accepted Would you like propose a fix?
/language zh
/kind bug (right?)
Please delete this symbol. !
I have already apply a pull request.
Change:
You might need to restart `containerd` as well once you've updated the config file: `systemctl restart containerd`. <del> Please note, that it is a best practice for kubelet to declare the matching `pod-infra-container-image`. If not configured, kubelet may attempt to garbage collect the `pause` image. There is ongoing work in [containerd to pin the pause image](https://github.com/containerd/containerd/issues/6352) and not require this setting on kubelet any longer. </del> ### CRI-O This section contains the necessary steps to install CRI-O as a container runtime.

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: On the production environment page, under the container runtimes section, there is a reference to from containerd as ongoing work. Proposed Solution: I think the reference should be removed or updated to this Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /triage accepted /priority backlog /help
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 /priority backlog 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 will try to help with this. /assign
Change:
In order to use the Kubernetes Volume Snapshot feature, you must ensure the following components have been deployed on your Kubernetes cluster: <del> - [Kubernetes Volume Snapshot CRDs](https://github.com/kubernetes-csi/external-snapshotter/tree/master/config/crd) </del> <ins> - [Kubernetes Volume Snapshot CRDs](https://github.com/kubernetes-csi/external-snapshotter/tree/53469c21962339229dd150cbba50c34359acec73/config/crd) </ins> - [Volume snapshot controller](https://github.com/kubernetes-csi/external-snapshotter/tree/master/pkg/common-controller) - CSI Driver supporting Kubernetes volume snapshot beta

Discussion:
Links are broken on this page:
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
/retitle Broken link in article /language en /area blog
/assign
will you please test the fix @ https://deploy-preview---kubernetes-io-master-
Change:
<!-- At this point you can reach the nginx server from any node. --> <del> 这时可以从任何节点访问到 Nginx server。 </del> <ins> 这时，你可以从任何节点访问到 Nginx 服务器。 </ins> ```shell kubectl get pods -o yaml | grep -i podip

Discussion:
Nginx https 404
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
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
`cluster-info`    | `kubectl cluster-info [flags]` | Display endpoint information about the master and services in the cluster. `completion`    | `kubectl completion SHELL [options]` | Output shell completion code for the specified shell (bash or zsh). `config`        | `kubectl config SUBCOMMAND [flags]` | Modifies kubeconfig files. See the individual subcommands for details. <del> `convert`    | `kubectl convert -f FILENAME [options]` | Convert config files between different API versions. Both YAML and JSON formats are accepted. </del> <ins> `convert`    | `kubectl convert -f FILENAME [options]` | Convert config files between different API versions. Both YAML and JSON formats are accepted. Note - requires `kubectl-convert` plugin to be installed. </ins> `cordon`    | `kubectl cordon NODE [options]` | Mark node as unschedulable. `cp`    | `kubectl cp <file-spec-src> <file-spec-dest> [options]` | Copy files and directories to and from containers. `create`        | `kubectl create -f FILENAME [flags]` | Create one or more resources from a file or stdin.

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: kubectl-convert is now a plugin and does not come bundled with kubectl, but the still lists convert as a operation Proposed Solution: Remove the reference of convert from operations 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 cli
We could also leave it in the table but mark that it depends on an in-tree plugin that you must already have installed onto your client.
/language en
/retitle kubectl command reference page lists “kubectl convert” (which is provided by a plugin)
Sure. I will create a PR for this
Change:
| `rolebindings` | | rbac.authorization.k8s.io | true | RoleBinding | | `roles` | | rbac.authorization.k8s.io | true | Role | | `priorityclasses` | `pc` | scheduling.k8s.io | false | PriorityClass | <del> | `storageclasses` | `sc` | storage.k8s.io |  false | StorageClass | </del> <ins> | `csidrivers` | | storage.k8s.io | false | CSIDriver | | `csinodes` | | storage.k8s.io | false | CSINode | | `storageclasses` | `sc` | storage.k8s.io | false | StorageClass | </ins> | `volumeattachments` | | storage.k8s.io | false | VolumeAttachment | --> | 资源名 | 缩写名 | API 分组 | 按命名空间 | 资源类型 | |---|---|---|---|---| <ins> | `bindings` | | | true | Binding | </ins> | `componentstatuses` | `cs` | | false | ComponentStatus | | `configmaps` | `cm` | | true | ConfigMap | | `endpoints` | `ep` | | true | Endpoints | <ins> | `events` | `ev` | | true | Event | </ins> | `limitranges` | `limits` | | true | LimitRange | | `namespaces` | `ns` | | false | Namespace | | `nodes` | `no` | | false | Node |

Discussion:
This is a Bug Report Problem: The resource type list on is about v1.13.3 which is too old. We are not obliged to keep the list updated on every release, but having the list updated to a supported version is still desireable. Proposed Solution: Update the list to reflect what we have today. Page to Update:
ref:
/assign
fixed. /close
Closing this issue. <detailsIn response to : fixed. /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:
and does things like starting pods and containers. * `kubectl`: the command line util to talk to your cluster. <del> kubeadm **will not** install or manage `kubelet` or `kubectl` for you, so you will need to ensure they match the version of the Kubernetes control plane you want kubeadm to install for you. If you do not, there is a risk of a version skew occurring that can lead to unexpected, buggy behaviour. However, _one_ minor version skew between the kubelet and the control plane is supported, but the kubelet version may never exceed the API server version. For example, kubelets running 1.7.0 should be fully compatible with a 1.8.0 API server, but not vice versa. For information about installing `kubectl`, see [Install and set up kubectl](/docs/tasks/tools/). </del> --> ## 安装 kubeadm、kubelet 和 kubectl

Discussion:
(kubeadm) []
/triage accepted /kind bug /assign /language zh
Change:
__Important: You must have your own Ceph server running with the share exported before you can use it__ <del> See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/cephfs/) for more details. </del> <ins> See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/volumes/cephfs/) for more details. </ins> ### gitRepo

Discussion:
Cites looking at a cephfs example, that promptly 404's once clicked
It appears this should actually point to: not
Change:
Whether you are submitting JSON data or YAML data, use `application/apply-patch+yaml` as the `Content-Type` header value. <del> All JSON documents are valid YAML. </del> <ins> All JSON documents are valid YAML. However, Kubernetes has a bug where it uses a YAML parser that does not fully implement the YAML specification. Some JSON escapes may not be recognized. </ins> {{< /note >}} The serialization is the same as for Kubernetes objects, with the exception that

Discussion:
Hello there! In the , the statement is made that: While this is correct, it's misleading in context because go-yaml has an regarding compatibility with the spec. While I understand this is particularly nitpicky, I think it's worth documenting this case because: issue was raised more than two years ago. are open that have been pending to resolve this for years. are major languages and libraries where the default options generate valid JSON/YAML that run into this case (e.g., PHP). The escape sequence is explicitly listed in , near the top of page 9, as being an allowed escape sequence. I'd argue that this section should either: Explicitly call out the incompatibility; or Soften the language to some thing like "Most JSON documents are accepted as YAML by Kubernetes." At least in softening the language, people may be encouraged to explore the possibility that it's not their code that's broken, but instead an issue with the YAML that kubernetes accepts and attempt to find workarounds instead of spending an embarrassing amount of time looking in the wrong place like I just did. Thank you for your time! Adam
Page reported in issue: /language en
/retitle Improve "Server-Side Apply" page to address JSON/YAML compatibility with go-yaml
/kind feature We can document the bug in Kubernetes. I'd prefer to make it clear that it's a bug, rather than document the bug as our expected behavior.
/wg api-expression /priority backlog /triage accepted
/assign
Change:
<ins> --- title: 对象 id: object date: 2020-10-12 full_link: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects short_description: > Kubernetes 系统中的实体, 代表了集群的部分状态。 aka: tags: - fundamental --- <!-- --- title: Object id: object date: 2020-10-12 full_link: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects short_description: > A entity in the Kubernetes system, representing part of the state of your cluster. aka: tags: - fundamental --- --> <!-- An entity in the Kubernetes system. The Kubernetes API uses these entities to represent the state of your cluster. --> Kubernetes 系统中的实体。Kubernetes API 用这些实体表示集群的状态。 <!--more--> <!-- A Kubernetes object is typically a “record of intent”—once you create the object, the Kubernetes {{< glossary_tooltip text="control plane" term_id="control-plane" >}} works constantly to ensure that the item it represents actually exists. By creating an object, you're effectively telling the Kubernetes system what you want that part of your cluster's workload to look like; this is your cluster's desired state. --> Kubernetes 对象通常是一个“目标记录”-一旦你创建了一个对象，Kubernetes {{< glossary_tooltip text="控制平面" term_id="control-plane" >}} 不断工作，以确保它代表的项目确实存在。 创建一个对象相当于告知 Kubernetes 系统：你期望这部分集群负载看起来像什么；这也就是你集群的期望状态。 </ins>  No newline at end of file

Discussion:
translate into Chinese
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 /language zh
Change:
<ins> --- title: containerd id: containerd date: 2019-05-14 full_link: https://containerd.io/docs/ short_description: > シンプルさ、堅牢性、移植性を重視したコンテナランタイムです。 aka: tags: - tool --- シンプルさ、堅牢性、移植性を重視したコンテナランタイムです。 <!--more--> containerdはLinuxやWindows上でデーモンとして実行される{{< glossary_tooltip text="コンテナ" term_id="container" >}}ランタイムです。containerdはコンテナイメージの取得や保存、コンテナの実行、ネットワークアクセスの提供などを行います。 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document:
/area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. 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 : /area localization /language ja /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
/triage accepted
The label cannot be applied. Only GitHub organization members can add the label. <detailsIn response to : /triage accepted </details
/assign
Raised PR in
Hi Thank you for interesting in SIG-docs ja subproject !! This is a Japanese localization Project, but It looks that you live in India and you are fluent Hindi / English. So, Participating in Hindi projects is helpful for k/website :) you can search issues from this query result thank you
I checked , but it looks that this translation is made by google translation (or any other auto-translation tools). We cannot accept the pr like this. Thank you
/unassign Shubhdeep02
I sincerely apologize for the problems occurred due to me , and thanks for your support.
Thank you for understanding Your motivation is really excellent for the kubernetes community, so I believe that you will be able to make valuable contributions!! Please don't hesitate to contact us if there's anything you need support with. Thank you :)
/triage accepted
/assign
PRPR
Change:
* [Emissary-Ingress](https://www.getambassador.io/products/api-gateway) API Gateway is an [Envoy](https://www.envoyproxy.io)-based ingress controller. * [EnRoute](https://getenroute.io/) is an [Envoy](https://www.envoyproxy.io) based API gateway that can run as an ingress controller. <del> * [Easegress IngressController](https://github.com/megaease/easegress/blob/main/doc/reference/ingresscontroller.md) is an [Easegress](https://megaease.com/easegress/) based API gateway that can run as an ingress controller. </del> <ins> * [Easegress IngressController](https://megaease.com/docs/easegress/04.cloud-native/4.1.kubernetes-ingress-controller/) is an [Easegress](https://megaease.com/easegress/) based API gateway that can run as an ingress controller. </ins> * F5 BIG-IP [Container Ingress Services for Kubernetes](https://clouddocs.f5.com/containers/latest/userguide/kubernetes/) lets you use an Ingress to configure F5 BIG-IP virtual servers. * [FortiADC Ingress Controller](https://docs.fortinet.com/document/fortiadc/7.0.0/fortiadc-ingress-controller/742835/fortiadc-ingress-controller-overview) support the Kubernetes Ingress resources and allows you to manage FortiADC objects from 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: The under in docs redirects to this link: which shows the message that 'This document has been moved to' this link: Proposed Solution: Update link of from to 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
I would like to work on this. /assign /language en /sig network /sig docs
I'd link to which seems to be the relevant documentation.
Hi this link looks more relevant to me. Thank you for sharing this. I will update this link in the documentation.
Change:
This repository contains the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute! - [Contributing to the docs](#contributing-to-the-docs) <del> - [Localization READMEs](#localization-readmemds) </del> <ins> - [Localization READMEs](#localization-readmes) </ins> ## Using this repository

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: <img width="470" alt="image" src="" quick navigation link is broken Proposed Solution: It looks like it's due to a small typo. <img width="391" alt="image" src=""Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en Yes its a typo mistake
Let's first the issue have the label triage accepted, then only work on this!!
/triage accepted /priority backlog
Change:
{{ block "deprecated" . }} {{ partial "deprecation-warning.html" . }} {{ end }} <del> {{ if or ( .HasShortcode "kat-button" ) ( .HasShortcode "katacoda-tutorial" ) }} {{ block "katacoda-removal" . }} {{ partial "katacoda-removal.html" . }} {{ end }} {{ end }} </del> {{ block "main" . }}{{ end }} {{- if .HasShortcode "thirdparty-content" -}} {{ block "thirdparty-disclaimer" . }}

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: We a banner: Given the latest updates from O'Reilly, that banner may not be accurate and the service (albeit possibly degraded?) is expected to survive beyond June 15th 2022. Example page: Relevant to issue
we could remove the banner and wait till June 15. If a new update came then we can update it?
I'm OK with removing the banner.
/assign
/triage accepted