jiebi/CodeConvo huggingface dataset:
Change:
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

Discussion:
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:
Change:
Hello team. Recently I noticed that this page: shows wrong command. Instead of it should be I believe the fix should go into this file Please review. Thank you
/assign
- -- -- -- -- -- -- -Also see this:
should this issue and its corresponding PR be closed?
closed his prior PR, and opened . IMO it would be good to keep this issue open until the error in K8s Docs has been resolved. /kind bug
Okay
/triage accepted
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]:
Should the PR be opened in Kuberenetes/website?
/remove-lifecycle stale

Discussion:
<p>Create a TLS secret from the given public/private key pair.</p> <p> The public/private key pair must exist beforehand. The public key certificate must be .PEM encoded and match the given private key.</p> <h3 id="usage">Usage</h3> <del> <p><code>$ kubectl create tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]</code></p> </del> <ins> <p><code>$ kubectl create secret tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]</code></p> </ins> <h3 id="flags">Flags</h3> <table> <thead>
Change:
This is a Bug Report <!--Required Information--The FEATURE STATE for and is mentioned under which is wrong, As per mention in the the correct Feature state for is . Proposed Solution: Update the Feature State of Serving and Terminating from to . Page to Update: <!--Additional Information:--EndpointSliceTerminatingCondition: Enables EndpointSlice and condition fields.
/assign
Fixed it here:
/language en /triage accepted

Discussion:
#### Serving <del> {{< feature-state for_k8s_version="v1.20" state="alpha" >}} </del> <ins> {{< feature-state for_k8s_version="v1.22" state="beta" >}} </ins> `serving` is identical to the `ready` condition, except it does not account for terminating states. Consumers of the EndpointSlice API should check this condition if they care about pod readiness while

#### Terminating <del> {{< feature-state for_k8s_version="v1.20" state="alpha" >}} </del> <ins> {{< feature-state for_k8s_version="v1.22" state="beta" >}} </ins> `Terminating` is a condition that indicates whether an endpoint is terminating. For pods, this is any pod that has a deletion timestamp set.
Change:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the texts Code Contributor to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the texts to and not to this . /assign /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
duplicate triage this issue will fix it
Hey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /triage accepted /good-first-issue /assign amolmote
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 : Hey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /good-first-issue /assign amolmote 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
Oh, I just noticed that already assign themselves on this issue. Since it's been a bit more than two months, please tell amolmote if you are still working on this one or if it's okay that they take over.

Discussion:
title: Code Contributor id: code-contributor date: 2018-04-12 <del> full_link: /docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > A person who develops and contributes code to the Kubernetes open source codebase.
Change:
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 to LimitRanger design document in is broken. F) T) Proposed Solution: fix link in doc 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
/language ja /assign

Discussion:
## {{% heading "whatsnext" %}} <del> より詳しい情報は、[LimitRangerの設計ドキュメント](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md)を参照してください。 </del> <ins> より詳しい情報は、[LimitRangerの設計ドキュメント](https://git.k8s.io/design-proposals-archive/resource-management/admission_control_limit_range.md)を参照してください。 </ins> 制限の使用例については、以下のページを読んでください。
Change:
This is a Bug Report Hi Team, Hope you're all doing well. Problem: When raising a PR for kubernetes/website, the guiding text is as follows - The URL listed, sadly, gives a 404. Proposed Solution: Either we fix the target url or update to an alternative location. Thoughts? Best Regards James Spurin
The URL works. Fixes welcome.
/triage accepted
I would like to work on this issue. Thanks. /assign

Discussion:
PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: <del> https://kubernetes.io/docs/contribute/suggest-improvements/ </del> <ins> https://kubernetes.io/docs/contribute/suggesting-improvements/ </ins> Use the default base branch, “main”, if you're documenting existing features in the English localization.
Change:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Storage Policy Based Management for dynamic provisioning of volumes to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text Storage Policy Based Management for dynamic provisioning of volumes to and not to this . /assign /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
/triage accepted

Discussion:
persistent volume (virtual disk) is being created. The virtual disk is distributed across the Virtual SAN datastore to meet the requirements. <del> You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html) </del> <ins> You can see [Storage Policy Based Management for dynamic provisioning of volumes](https://github.com/vmware-archive/vsphere-storage-for-kubernetes/blob/fa4c8b8ad46a85b6555d715dd9d27ff69839df53/documentation/policy-based-mgmt.md) </ins> for more details on how to use storage policies for persistent volumes management.
Change:
Please update page, it should be instead of
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

Discussion:
The Dashboard UI is not deployed by default. To deploy it, run the following command: ``` <del> kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.5.0/aio/deploy/recommended.yaml </del> <ins> kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.6.1/aio/deploy/recommended.yaml </ins> ``` ## Accessing the Dashboard UI
Change:
markdown <img width="681" alt="WX20220809- src="https://user-"
page: /triage accepted /assign
namespace

Discussion:
<!-- In Kubernetes, _namespaces_ provides a mechanism for isolating groups of resources within a single cluster. Names of resources need to be unique within a namespace, but not across namespaces. Namespace-based scoping is applicable only for namespaced objects _(e.g. Deployments, Services, etc)_ and not for cluster-wide objects _(e.g. StorageClass, Nodes, PersistentVolumes, etc)_. --> <del> 在 Kubernetes 中，**名字空间（Namespace）**提供一种机制，将同一集群中的资源划分为相互隔离的组。 </del> <ins> 在 Kubernetes 中，**名字空间（Namespace）** 提供一种机制，将同一集群中的资源划分为相互隔离的组。 </ins> 同一名字空间内的资源名称要唯一，但跨名字空间时没有这个要求。 名字空间作用域仅针对带有名字空间的对象，例如 Deployment、Service 等， 这种作用域对集群访问的对象不适用，例如 StorageClass、Node、PersistentVolume 等。

--> 通过创建与[公共顶级域名](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 更高的优先序。 <!--

TLDs](https://data.iana.org/TLD/tlds-alpha-by-domain.txt). --> 为了缓解这类问题，需要将创建名字空间的权限授予可信的用户。 <del> 如果需要，你可以额外部署第三方的安全控制机制，例如以 [准入 Webhook](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/) </del> <ins> 如果需要，你可以额外部署第三方的安全控制机制， 例如以[准入 Webhook](/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/) </ins> 的形式，阻止用户创建与公共 [TLD](https://data.iana.org/TLD/tlds-alpha-by-domain.txt) 同名的名字空间。 {{< /warning >}}

persistentVolumes, are not in any namespace. --> 大多数 kubernetes 资源（例如 Pod、Service、副本控制器等）都位于某些名字空间中。 <del> 但是名字空间资源本身并不在名字空间中。而且底层资源，例如 [节点](/zh-cn/docs/concepts/architecture/nodes/)和持久化卷不属于任何名字空间。 </del> <ins> 但是名字空间资源本身并不在名字空间中。而且底层资源， 例如[节点](/zh-cn/docs/concepts/architecture/nodes/)和持久化卷不属于任何名字空间。 </ins> <!-- To see which Kubernetes resources are and aren't in a namespace:

--> Kubernetes 控制面会为所有名字空间设置一个不可变更的 {{< glossary_tooltip text="标签" term_id="label" >}} <del> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/) 被启用。标签的值是名字空间的名称。 </del> <ins> `kubernetes.io/metadata.name`，只要 `NamespaceDefaultLabelName` 这一[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)被启用。 标签的值是名字空间的名称。 </ins> ## {{% heading "whatsnext" %}}
Change:
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 cluster autoscaler uses an annotation, . However, we don't list that annotation in Well-Known Labels, Annotations and Taints. Proposed Solution: Update Well-Known Labels, Annotations and Taints to mention the Pod annotation and why you might use it. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
/triage accepted /sig autoscaling
/assign

Discussion:
One of the [recommended labels](/docs/concepts/overview/working-with-objects/common-labels/#labels). <ins> ### cluster-autoscaler.kubernetes.io/safe-to-evict Example: `cluster-autoscaler.kubernetes.io/safe-to-evict: "true"` Used on: Pod When this annotation is set to `"true"`, the cluster autoscaler is allowed to evict a Pod even if other rules would normally prevent that. The cluster autoscaler never evicts Pods that have this annotation explicitly set to `"false"`; you could set that on an important Pod that you want to keep running. If this annotation is not set then the cluster autoscaler follows its Pod-level behavior. </ins> ### kubernetes.io/arch Example: `kubernetes.io/arch: "amd64"`
Change:
Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text StorageClass for GCE PD to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text StorageClass for GCE PD to and not to this . /assign /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
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

Discussion:
#### Manually provisioning a Regional PD PersistentVolume Dynamic provisioning is possible using a <del> [StorageClass for GCE PD](/docs/concepts/storage/storage-classes/#gce). </del> <ins> [StorageClass for GCE PD](/docs/concepts/storage/storage-classes/#gce-pd). </ins> Before creating a PersistentVolume, you must create the persistent disk: ```shell
Change:
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 cluster autoscaler uses an annotation, . However, we don't list that annotation in Well-Known Labels, Annotations and Taints. Proposed Solution: Update Well-Known Labels, Annotations and Taints to mention the Pod annotation and why you might use it. We could mention that you typically set this annotation in the Pod template within a DaemonSet and that you don't set that annotation on the DaemonSet itself. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
I would like to work on this. /assign /sig autoscaling
Fixed it here:
/triage accepted

Discussion:
This annotation is used to set [Pod Deletion Cost](/docs/concepts/workloads/controllers/replicaset/#pod-deletion-cost) which allows users to influence ReplicaSet downscaling order. The annotation parses into an `int32` type. <ins> ### cluster-autoscaler.kubernetes.io/enable-ds-eviction Example: `cluster-autoscaler.kubernetes.io/enable-ds-eviction: "true"` Used on: Pod This annotation controls whether a DaemonSet pod should be evicted by a ClusterAutoscaler. This annotation needs to be specified on DaemonSet pods in a DaemonSet manifest. When this annotation is set to `"true"`, the ClusterAutoscaler is allowed to evict a DaemonSet Pod, even if other rules would normally prevent that. To disallow the ClusterAutoscaler from evicting DaemonSet pods, you can set this annotation to `"false"` for important DaemonSet pods. If this annotation is not set, then the Cluster Autoscaler follows its overall behaviour (i.e evict the DaemonSets based on its configuration). {{< note >}} This annotation only impacts DaemonSet pods. {{< /note >}} </ins> ### kubernetes.io/ingress-bandwidth {{< note >}}
Change:
Hi,I am interested to translate the "cluster-resources/lease-" page. There is a description that has not been translated. I will modify this file. /language zh
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

Discussion:
import: "k8s.io/api/coordination/v1" kind: "Lease" content_type: "api_reference" <del> description: "Lease defines a lease concept." </del> <ins> description: "Lease 定义了租约的概念。" </ins> title: "Lease" weight: 5 ---
Change:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/container- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/container- is outdated. Comments /language ja /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

Discussion:
Podの名前と名前空間は[downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/)を通じて環境変数として利用可能です。 Pod定義からのユーザー定義の環境変数もコンテナで利用できます。 <del> Dockerイメージで静的に指定されている環境変数も同様です。 </del> <ins> コンテナイメージで静的に指定されている環境変数も同様です。 </ins> ### クラスター情報 コンテナの作成時に実行されていたすべてのサービスのリストは、環境変数として使用できます。 <del> これらの環境変数はDockerリンクの構文と一致します。 </del> <ins> このリストは、新しいコンテナのPodおよびKubernetesコントロールプレーンサービスと同じ名前空間のサービスに制限されます。 </ins> *bar* という名前のコンテナに対応する *foo* という名前のサービスの場合、以下の変数が定義されています。
Change:
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: When somebody configures shell completion for , the instructions explain how to turn that on for your current session. However, that advice only works if the reader picked the approach in the “User” tab. If someone picked the “System” tab, the advice does not help them update their current session. Proposed Solution: Change that page to advise the user to run Some other change that also helps the user, regardless of which approach they took. Page to Update: Additional Information: Prompted by /language en /priority backlog
/triage accepted
/assign

Discussion:
{{< /note >}} Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. <del> To enable bash autocompletion in current session of shell, source the ~/.bashrc file: </del> <ins> To enable bash autocompletion in current session of shell, run `exec bash`: </ins> ```bash <del> source ~/.bashrc </del> <ins> exec bash </ins> ```