jiebi/CodeConvo huggingface dataset:
Change:
type will be deleted when its namespace is deleted and access to that resource type is controlled by authorization checks on the namespace scope. <ins> Note: core resources use `/api` instead of `/apis` and omit the GROUP path segment. Examples: * `/api/v1/namespaces` * `/api/v1/pods` * `/api/v1/namespaces/my-namespace/pods` * `/apis/apps/v1/deployments` * `/apis/apps/v1/namespaces/my-namespace/deployments` * `/apis/apps/v1/namespaces/my-namespace/deployments/my-deployment` </ins> You can also access collections of resources (for example: listing all Nodes). The following paths are used to retrieve collections and resources:

Discussion:
While reading Events to learn how to construct api urls I found that the instructions here do not cover how paths for core resources are constructed, mainly that they start with instead of . It hints at this with the example but it should be directly stated to be more clear. after rereading my original post let me me more clear. Core resources start with /api all other resources start with /apis I am asking for this destinction to be made more clear in the docs.
/wg api-expression /language en /triage accepted /priority backlog
/assign
after rereading my original post let me me more clear. Core resources start with /api all other resources start with /apis I am asking for this destinction to be made more clear in the docs.
would you be willing to edit the original description that you wrote for the issue, to include that clarification?
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
Change:
content_type: tutorial weight: 10 --- <!-- <del> --- </del> title: Exposing an External IP Address to Access an Application in a Cluster content_type: tutorial weight: 10 <del> --- </del> --> <!-- overview -->

Discussion:
This is a Bug Report Chinese page contentzhdocstutorialsstateless-applicationexpose-external-ip- outdated <!-- 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 contentzhdocstutorialsstateless-applicationexpose-external-ip- is different with English version page. Proposed Solution: Update Chinese page Page to Update: contentzhdocstutorialsstateless-applicationexpose-external-ip- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
/remove-lifecycle rotten
/assign
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: volume-test spec: containers: - name: container-test image: busybox:1.28 volumeMounts: - name: all-in-one mountPath: "/projected-volume" readOnly: true volumes: - name: all-in-one projected: sources: - secret: name: mysecret items: - key: username path: my-group/my-username - secret: name: mysecret2 items: - key: password path: my-group/my-password mode: 511 </ins>

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments /triage accepted /kind feature /language es /sig docs
Hi Rodolfo, I will take it!
/assign
algún avance al respecto?
disculpa. Lo terminaré hoy, gracias por recordarmenlo Victor.
Change:
* [Validate IPv4/IPv6 dual-stack](/docs/tasks/network/validate-dual-stack) networking * Read about [Dual-stack](/docs/concepts/services-networking/dual-stack/) cluster networking <del> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta2/) </del> <ins> * Learn more about the kubeadm [configuration format](/docs/reference/config-api/kubeadm-config.v1beta3/) </ins>

Discussion:
says: the “configuration format” is a hyperlink to , it shall instead point to (beta2 → beta3) says: where “NodeRegistrationOptions” is a hyperlink to . It shall instead point to (beta2 → beta3) says: where “configuration file” is a hypelink to . It shall instead point to (beta2 → beta3) says: where “API referenc” is a hyperlink to It shall instead point to .
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
/sig cluster-lifecycle /remove-kind bug /kind cleanup
/language en
Change:
--> 通过创建与[公共顶级域名](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) 同名的名字空间，这些名字空间中的服务可以拥有与公共 DNS 记录重叠的、较短的 DNS 名称。 <del> 所有名字空间中的负载在执行 DNS 查找时，如果查找的名称没有 [尾部句点](https://datatracker.ietf.org/doc/html/rfc1034#page-8)， </del> <ins> 所有名字空间中的负载在执行 DNS 查找时， 如果查找的名称没有[尾部句点](https://datatracker.ietf.org/doc/html/rfc1034#page-8)， </ins> 就会被重定向到这些服务上，因此呈现出比公共 DNS 更高的优先序。 <!--

Discussion:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace
Change:
--- title: 使用 Minikube 安装 Kubernetes <ins> weight: 30 </ins> content_type: concept --- <!--

Discussion:
This is a Bug Report Problem: is missing in Chinese version. Proposed Solution: Add content/zh/docs/setup/learning- Page to Update: content/zh/docs/setup/learning- content/zh/docs/setup/learning-
/language zh /assign
Change:
Install CNI plugins (required for most pod network): ```bash <del> CNI_PLUGINS_VERSION="v1.1.1" </del> <ins> CNI_PLUGINS_VERSION="v1.2.0" </ins> ARCH="amd64" DEST="/opt/cni/bin" sudo mkdir -p "$DEST"

Discussion:
This is a Bug Report Problem: The versions of the cri-tools and cni-plugins dependencies was updated in packages, but not in the documentation: Proposed Solution: Update the versions, to match what is in the deb/rpm packages. Currently they are not pinned, but installs the latest: Compared with the deb installation: Page to Update: Kubernetes Version: 27.0 <!--Additional Information:--Related:
/sig cluster-lifecycle /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 : /sig cluster-lifecycle /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
/triage accepted /priority backlog
/assign
/unassign
Change:
<!-- body --> <del> ## コンテナイメージ </del> <ins> ## コンテナイメージ {#container-images} </ins> [コンテナイメージ](/docs/concepts/containers/images/)はすぐに実行可能なソフトウェアパッケージで、アプリケーションの実行に必要なものをすべて含んています。コードと必要なランタイム、アプリケーションとシステムのライブラリ、そして必須な設定項目のデフォルト値を含みます。 設計上、コンテナは不変で、既に実行中のコンテナのコードを変更することはできません。コンテナ化されたアプリケーションがあり変更したい場合は、変更を含んだ新しいイメージをビルドし、コンテナを再作成して、更新されたイメージから起動する必要があります。

Discussion:
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
/triage accepted
Change:
TODO: Test and explain how to use additional non-K8s secrets with an existing service account. TODO explain: <del> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </del>  No newline at end of file <ins> - The token goes to: "/var/run/secrets/kubernetes.io/serviceaccount/$WHATFILENAME" </ins>

Discussion:
I wish /docs/admin/cluster-components/dns/ page existed It's linked from
Change:
--> ### 设置贯穿性字段  {#setting-cross-cutting-fields} <del> 在项目中未所有 Kubernetes 对象设置贯穿性字段是一种常见操作。 </del> <ins> 在项目中为所有 Kubernetes 对象设置贯穿性字段是一种常见操作。 </ins> 贯穿性字段的一些使用场景如下： * 为所有资源设置相同的名字空间

Discussion:
There are some Chinese typo issues in , which should be corrected. For example: <img width="705" alt="image" src="https://user-"The "" should be "“. And, <img width="572" alt="image" src="https://user-"The "“ is wrong and should be "". As I have read the full article, I am planing to submit a PR.
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
Change:
### ローカルのエフェメラルストレージの要求と制限設定 <del> ローカルのエフェメラルストレージを管理するためには_ephemeral-storage_パラメーターを利用することができます。 </del> <ins> ローカルのエフェメラルストレージを管理するためには _ephemeral-storage_ パラメーターを利用することができます。 </ins> Podの各コンテナは、次の1つ以上を指定できます。 * `spec.containers[].resources.limits.ephemeral-storage` * `spec.containers[].resources.requests.ephemeral-storage`

Discussion:
ref: ! [x] [x] [x] [ ] content/ja/docs/concepts/configuration/manage-resources- [ ] [x] content/ja/docs/concepts/configuration/pod-priority- [x] [x] [ ] content/ja/docs/concepts/containers/runtime- [x] content/ja/docs/concepts/overview/kubernetes- [x] content/ja/docs/concepts/extend-kubernetes/api-extension/custom- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with-objects/common- [x] content/ja/docs/concepts/overview/working-with-objects/field- [x] content/ja/docs/concepts/overview/working-with- [x] content/ja/docs/concepts/overview/working-with- [ ] content/ja/docs/concepts/scheduling-eviction/assign-pod- [ ] content/ja/docs/concepts/scheduling-eviction/kube- [x] content/ja/docs/concepts/scheduling-eviction/taint-and- [x] [x] content/ja/docs/concepts/security/pod-security- [x] content/ja/docs/concepts/services- [x] content/ja/docs/concepts/storage/persistent- [x] [x] content/ja/docs/concepts/workloads/controllers/cron- [x] [x] [x] [x] content/ja/docs/concepts/workloads/pods/pod- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/reference/access-authn- [x] content/ja/docs/setup/production-environment/tools/kubeadm/create-cluster- [x] content/ja/docs/setup/production-environment/tools/kubeadm/troubleshooting- [ ] content/ja/docs/tasks/access-application-cluster/web-ui- [x] content/ja/docs/tasks/debug-application-cluster/get-shell-running- [x] content/ja/docs/tasks/run-application/horizontal-pod-autoscale- [x] content/ja/docs/tasks/run-application/run-single-instance-stateful- [x] content/ja/docs/tutorials/stateful-application/basic-stateful- [x] content/ja/docs/tutorials/stateful- (grep) /language ja
/triage accepted
/assign
/kind bug
I'm facing same issue lol :smiley: Feel free to mention me for review if create PRs for this.
Change:
## インフラストラクチャ * [KubeVirt](https://kubevirt.io/user-guide/#/installation/installation)は仮想マシンをKubernetes上で実行するためのアドオンです。通常、ベアメタルのクラスタで実行します。 <ins> * [node problem detector](https://github.com/kubernetes/node-problem-detector)はLinuxノード上で動作し、システムの問題を[Event](/docs/reference/kubernetes-api/cluster-resources/event-v1/)または[ノードのCondition](/ja/docs/concepts/architecture/nodes/#condition)として報告します。 </ins> ## レガシーなアドオン

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 file might be outdated. en: Under "Networking and Network Policy" section, the entry "Contiv" exists. ja: The entry "Contiv" does not exist. Proposed Solution: Update . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ja
/triage accepted
/assign
I'd like to create a PR for this issue. Please comment if you are working on this issue.
sorry, I have not started to work this issue. please do that.
Thanks for your reply. I'll do it. /assign
Change:
* 为控制面[加密通信中的数据](/zh/docs/tasks/tls/managing-tls-in-a-cluster/) * [加密静止状态的数据](/zh/docs/tasks/administer-cluster/encrypt-data/) * [Kubernetes 中的 Secret](/zh/docs/concepts/configuration/secret/) <ins> * [运行时类](/zh/docs/concepts/containers/runtime-class) </ins>

Discussion:
! Chinese page link can not open
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/language zh
/assign
/kind bug
Change:
* [kube-apiserver configuration (v1)](/docs/reference/config-api/apiserver-config.v1/) <ins> * [kube-apiserver encryption (v1)](/docs/reference/config-api/apiserver-encryption.v1/) </ins> * [kubelet configuration (v1alpha1)](/docs/reference/config-api/kubelet-config.v1alpha1/) and [kubelet configuration (v1beta1)](/docs/reference/config-api/kubelet-config.v1beta1/) * [kube-scheduler configuration (v1beta2)](/docs/reference/config-api/kube-scheduler-config.v1beta2/) and

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 Within add a new generated page that documents the format for an encryption configuration. Update to hyperlink to that new reference Why is this needed Within , there is a configuration format for the API server, EncryptionConfiguration. At the moment that format is not documented in Readers may want to look up what that format covers. Comments /sig api-machinery /sig auth /kind feature /language en
/triage accepted
/assign This file is already generated in the generator. All we need to do is to copy it to the website repo.
Change:
$ kubectl create -f https://k8s.io/docs/tasks/administer-cluster/namespace-dev.json ``` <ins> Save the following contents into file [`namespace-prod.json`](/docs/admin/namespaces/namespace-prod.json) which describes a production namespace: {% include code.html language="json" file="namespace-prod.json" ghlink="/docs/tasks/administer-cluster/namespace-prod.json" %} </ins> And then let's create the production namespace using kubectl. ```shell

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [x ] Feature Request [ ] Bug Report Problem: Add the steps to get back out of the kubectl context after running the commands Proposed Solution: point out that the .kube folder has a config file that holds the info Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. Prevent issues from auto-closing with an comment. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/remove-lifecycle stale /assign
Change:
{{< note >}} एक विशिष्ट संस्करण डाउनलोड करने के लिए, कमांड के इस हिस्से `$(curl -L -s https://dl.k8s.io/release/stable.txt)` को विशिष्ट संस्करण से बदलें। <del> उदाहरण के लिए, Intel macOS पर {{< param "fullversion" >}} संस्करण डाउनलोड करने के लिए, टाइप करें: </del> <ins> उदाहरण के लिए, Intel macOS पर {{< skew currentPatchVersion >}} संस्करण डाउनलोड करने के लिए, टाइप करें: </ins> ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/amd64/kubectl" </ins> ``` और Apple Silicon macOS के लिए, टाइप करें: ```bash <del> curl -LO "https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/arm64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/darwin/arm64/kubectl" </ins> ``` {{< /note >}}

Discussion:
Parent issue: Substitute the outdated shortcode with the new shortcode in the Hindi language documentation. /assign /triage accepted /language hi
PR has been raised to address this issue.
Change:
.button { display: inline-block; border-radius: 6px; <del> padding: 0 20px; line-height: 40px; </del> <ins> padding: 6px 20px; line-height: 1.3rem; </ins> color: white; background-color: $blue; text-decoration: none;

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 space between lines in button is too wide, causing ugly labels especially when the window is not wide or in localized pages which use more characters for the button text (i.e. ). The new docsy theme narrows this page width so it tends to happen more. Proposed Solution: The current stylesheet specifies 0px as vertical padding and set 40px as line-height. The problem can be fixed by specifying a reasonable vertical padding and less line-height. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--I've written a code to fix this problem. I'll send a PR to fix this problem. /assign
/kind cleanup
Change:
* The [deprecation policy](/docs/reference/using-api/deprecation-policy/) for Kubernetes explains the project's approach to removing features and components.

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: link At 435 line: See [Support Device Monitoring]() for more details. from link At 479 line: - : Enable service to route traffic based upon the Node topology of the cluster. See [ServiceTopology]() for more details. Proposed Solution: with correct link from link /docs/concepts/services-networking/service-topology/ Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Change:
<!-- This page covers how to customize the components that kubeadm deploys. For control plane components <del> you can use flags in the `ClusteConfiguration` structure or patches per-node. For the kubelet </del> <ins> you can use flags in the `ClusterConfiguration` structure or patches per-node. For the kubelet </ins> and kube-proxy you can use `KubeletConfiguration` and `KubeProxyConfiguration`, accordingly. All of these options are possible via the kubeadm configuration API. For more details on each field in the configuration you can navigate to our <del> [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). </del> <ins> [API reference pages](/docs/reference/config-api/kubeadm-config.v1beta3/). </ins> --> 本页面介绍了如何自定义 kubeadm 部署的组件。 <del> 你可以使用 `ClusteConfiguration` 结构中定义的参数，或者在每个节点上应用补丁来定制控制平面组件。 </del> <ins> 你可以使用 `ClusterConfiguration` 结构中定义的参数，或者在每个节点上应用补丁来定制控制平面组件。 </ins> 你可以使用 `KubeletConfiguration` 和 `KubeProxyConfiguration` 结构分别定制 kubelet 和 kube-proxy 组件。 所有这些选项都可以通过 kubeadm 配置 API 实现。

Discussion:
!
/language zh /triage accepted
/kind bug
/assign
/retitle [zh] typo in kubeadm API
Change:
Pod runs a Container based on the provided Docker image. ```shell <del> kubectl create deployment hello-node --image=registry.k8s.io/echoserver:1.4 </del> <ins> kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080 </ins> ``` 2. View the Deployment:

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. --I decided to try to learn a bit of Kubernetes on my new M1 Mac. It all worked except for the command, as that image does not support ARM. A bit of Googling and a visit to StackOverflow fixed it for me, but it would be better if that information was in the core guide. For others following in my footsteps, I have created a pull request with the ARM image info. Why is this needed ARM-based devices are becoming increasingly popular dev platforms, especially for early prototyping and learning. A Getting Started guide that worked on these hosts would be preferable to one which doesn't. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I will link this Issue to my pull request. I realize the version number, not just the repo and name, are different from the existing image. However, being on an ARM device, I have no way of testing the original image, so I didn't change it.
I agree, it would be nice that the "getting started" guide is working on both platforms or at least propose an alternative image for ARM. Feel free to link this issue from the PR you made and thanks for taking the time! /triage accepted /priority backlog /language en
Oops, I had a typo in the pull request link. Linked.