jiebi/CodeConvo huggingface dataset:
Change:
所生成的 ConfigMap 和 Secret 都会包含内容哈希值后缀。 这是为了确保内容发生变化时，所生成的是新的 ConfigMap 或 Secret。 要禁止自动添加后缀的行为，用户可以使用 `generatorOptions`。 <del> 除此以外，为生成的 ConfigMap 和 Secret 指定贯穿性选项也是可能的。 </del> <ins> 除此以外，为生成的 ConfigMap 和 Secret 指定贯穿性选项也是可以的。 </ins> ```shell cat <<EOF >./kustomization.yaml

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:
As mentioned above, you use the `kubectl cluster-info` command to retrieve the service's proxy URL. To create proxy URLs that include service endpoints, suffixes, and parameters, you append to the service's proxy URL: `http://`*`kubernetes_master_address`*`/api/v1/namespaces/`*`namespace_name`*`/services/`*`service_name[:port_name]`*`/proxy` <del> If you haven't specified a name for your port, you don't have to specify *port_name* in the URL. </del> <ins> If you haven't specified a name for your port, you don't have to specify *port_name* in the URL. You can also use the port number in place of the *port_name* for both named and unnamed ports. </ins> By default, the API server proxies to your service using http. To use https, prefix the service name with `https:`: `http://`*`kubernetes_master_address`*`/api/v1/namespaces/`*`namespace_name`*`/services/`*`https:service_name:[port_name]`*`/proxy`

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. --The is lacking clarity that both the port name or port number can be used when proxying to a service. The documentation should mention the field represented by can either be the name of a port in a service or the port number of a service for both forms and . Why is this needed The apiserver proxy endpoint supports using either a to locate the service to proxy to. The alternative form of using the port number could be useful if migrating from an unnamed/default service port to a named service port. Example: The following api server request could be used to proxy either form of the following service object since it references the port number, . If the query was constructed as , only the unnamed port would return a result. Conversely, if was used in the query only the named port would return a result. default/unnamed: named: Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/kind cleanup
/triage accepted
/priority backlog
Change:
### containerd <del> This section contains the necessary steps to use `containerd` as CRI runtime. </del> <ins> This section contains the necessary steps to use containerd as CRI runtime. </ins> Use the following commands to install Containerd on your system:

Discussion:
The current installation instructions for installing the third party Kubernetes Apt repository on Debian/Ubuntu, goes against best security practice. Currently the signing keys are to . The keychain should be downloaded to (file name to match the name used in ) using or (not as this is deprecated and will be last available in Debian 11 and Ubuntu 22.04) and referred to in as such Page to Update: References:
i read the linked pages and this change seems valid. thank you for bringing this up. would you help us by sending a PR for that? /sig cluster-lifecycle
/priority important-longterm /kind cleanup
/triage accepted
Please see
/sig cli
Change:
- テナントは、Secretを各NamespaceのimagePullSecretsへ追加する 複数のレジストリへのアクセスが必要な場合、それぞれのレジストリ毎にひとつのSecretを作成する事ができます。 <del> Kubeletは複数の`imagePullSecrets`を単一の仮想的な`.docker/config.json`にマージします。 </del> ## {{% heading "whatsnext" %}} <del> * [OCI Image Manifest Specification](https://github.com/opencontainers/image-spec/blob/master/manifest.md)を読みます。 </del> <ins> * [OCI Image Manifest Specification](https://github.com/opencontainers/image-spec/blob/master/manifest.md)を読む * [コンテナのガベージコレクション](/ja/docs/concepts/architecture/garbage-collection/#container-image-garbage-collection)について学ぶ * [pulling an Image from a Private Registry](/docs/tasks/configure-pod-container/pull-image-private-registry)について学ぶ </ins>

Discussion:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed 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
Change:
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"`

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 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
Change:
## Upcoming Release Webinar <del> Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 a.m. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](https://community.cncf.io/events/details/cncf-cncf-online-programs-presents-cncf-live-webinar-kubernetes-v128-release/) on the CNCF Online Programs site. </del> <ins> Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 A.M. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the [event page](https://community.cncf.io/events/) on the CNCF Online Programs site. </ins> ## Get Involved

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 release blog has this section: Join members of the Kubernetes v1.28 release team on Friday, September 14, 2023, at 10 a.m. PDT to learn about the major features of this release, as well as deprecations and removals to help plan for upgrades. For more information and registration, visit the on the CNCF Online Programs site. This currently has a broken link to the event page. Proposed Solution: Once the event is live on CNCF we should fix this in the blog or at least remove the link until then. Page to Update: /cc
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
Thanks confirmed it is broken talking with CNCF now regarding it. Will do a PR to remove for now
/assign
Change:
強制削除が実行されると、API serverは、Podが実行されていたNode上でPodが停止されたというkubeletからの確認を待ちません。API内のPodは直ちに削除されるため、新しいPodを同じ名前で作成できるようになります。Node上では、すぐに終了するように設定されるPodは、強制終了される前にわずかな猶予期間が与えられます。 <ins> {{< caution >}} 即時削除では、実行中のリソースの終了を待ちません。 リソースはクラスタ上で無期限に実行し続ける可能性があります。 {{< /caution >}} </ins> StatefulSetのPodについては、[StatefulSetからPodを削除するためのタスクのドキュメント](/ja/docs/tasks/run-application/force-delete-stateful-set-pod/)を参照してください。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/workloads/pods/pod- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/workloads/pods/pod- is outdated. For example, there is no description of PodHasNetwork(alpha feature). Comments /language ja /assign
/triage accepted
Change:
<ins> --- title: Container Runtime Interface (CRI) content_type: concept weight: 60 --- <!-- overview --> _CRI_ es una interfaz de plugin que permite que kubelet use una amplia variedad de container runtimes, sin necesidad de volver a compilar los componentes del clúster. Necesitas un _{{<glossary_tooltip text="container runtime" term_id="container-runtime">}}_ ejecutándose en cada Nodo en tu clúster, de manera que {{<glossary_tooltip text="kubelet" term_id="kubelet">}} pueda iniciar los {{<glossary_tooltip text="Pods" term_id="pod">}} y sus contenedores. {{<glossary_definition prepend="Container Runtime Interface (CRI) es" term_id="container-runtime-interface" length="all">}} <!-- body --> ## API {#api} {{< feature-state for_k8s_version="v1.23" state="stable" >}} Kubelet actúa como un cliente cuando se conecta al _runtime_ del contenedor a través de gRPC. El _runtime_ y los _endpoints_ del servicio de imágenes deben estar disponibles en el _runtime_ del contenedor, que se puede configurar por separado dentro del kubelet usando `--image-service-endpoint` [banderas de línea de comando](/docs/reference/command-line-tools-reference/kubelet). Para Kubernetes v{{< skew currentVersion >}}, kubelet prefiere usar CRI `v1`. Si el _runtime_ del contenedor no es compatible con `v1` del CRI, kubelet intenta negociar cualquier versión compatible anterior. El kubelet v{{< skew currentVersion >}} también puede negociar CRI `v1alpha2`, pero esta versión se considera obsoleta. Si el kubelet no puede negociar una versión CRI soportada, el kubelet se da por vencido y no se registra como un nodo. ## Actualizando Al actualizar Kubernetes, el kubelet intenta seleccionar automáticamente la última versión de CRI al reiniciar el componente. Si eso falla, entonces la alternativa se llevará a cabo como se mencionó anteriormente. Si se requirió una rellamada de gRPC porque el _runtime_ del contenedor se ha actualizado, entonces el _runtime_ del contenedor también debe soportar la versión seleccionada inicialmente o se espera que la rellamada falle. Esto requiere un reinicio del kubelet. ## {{% heading "whatsnext" %}} - Más información sobre CRI [definición de protocolo](https://github.com/kubernetes/cri-api/blob/c75ef5b/pkg/apis/runtime/v1/api.proto) </ins>

Discussion:
This is a Feature Request What would you like to be Localize to Spanish Why is this needed Comments
/triage accepted
/language es
/kind feature
/assign
/assign
Change:
{{< note >}} Para fazer o download de uma versão específica, substitua a parte `$(curl -L -s https://dl.k8s.io/release/stable.txt)` do comando pela versão específica. <del> Por exemplo, para fazer download da versão {{< param "fullversion" >}} no Linux, digite: </del> <ins> Por exemplo, para fazer download da versão {{< skew currentPatchVersion >}} no Linux, digite: </ins> ```bash <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` {{< /note >}}

Discussion:
Parent issue: Replace the deprecated shortcode with the shortcode in the Brazilian Portuguese localized docs. /assign /triage accepted /language pt
Change:
この場合、なにも操作する必要はありません。 {{< note >}} <del> Homebrewでインストールしたbash-completion v2は`BASH_COMPLETION_COMPAT_DIR`ディレクトリ内のすべてのファイルをsourceするため、後者の2つの方法が機能します。 </del> <ins> Homebrewでインストールしたbash-completion v2は`BASH_COMPLETION_COMPAT_DIR`ディレクトリ内のすべてのファイルを読み込むため、後者の2つの方法が機能します。 </ins> {{< /note >}} どの場合でも、シェルをリロードしたあとに、kubectlの自動補完が機能するはずです。

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. --Update Why is this needed Reflect the following feedback on this file, too. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/area localization /triage accepted
Change:
labels: k8s-app: kube-dns-autoscaler kubernetes.io/cluster-service: "true" <del> addonmanager.kubernetes.io/mode: Reconcile </del> spec: selector: matchLabels:

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: mentions an annotation prefix that is deprecated / not actually official. Proposed Solution: Remove all mention of annotations from that page. Page to Update: and specifically Additional Information: This is a follow-up to /language en
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 Remove labels from ”Autoscale the DNS Service in a Cluster”
/assign
Change:
il ajoute une étiquette, `statefulset.kubernetes.io/pod-name`, renseignée avec le nom du Pod. Cette étiquette vous permet d'attacher un Service à un Pod spécifique du StatefulSet. <del> ## Garanties de déploiment et de mise à l'échelle </del> <ins> ## Garanties de déploiement et de mise à l'échelle </ins> * Pour un StatefulSet avec N réplicas, lorsque les Pods sont déployés, ils sont créés de manière séquentielle, dans l'ordre {0..N-1}. * Lorsque les Pods sont supprimés, ils sont terminés dans l'ordre inverse, {N-1..0}.

Discussion:
Typo in frensh Statefulset documentation: Garanties de déploiment et de mise à l'échelle -Garanties de déploiement et de mise à l'échelle
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
/kind bug /language fr
/assign
Change:
1. Загрузите последнюю версию: ``` <del> curl -LO "https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/darwin/amd64/kubectl" </del> <ins> curl -LO "https://dl.k8s.io/release/$(curl -LS https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl" </ins> ``` <del> Чтобы загрузить определенную версию, вставьте в фрагмент команды `$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)` нужную версию. </del> <ins> Чтобы загрузить определенную версию, вставьте в фрагмент команды `$(curl -LS https://dl.k8s.io/release/stable.txt)` нужную версию. </ins> Например, команда загрузки версии {{< param "fullversion" >}} для macOS будет выглядеть следующим образом: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/darwin/amd64/kubectl </ins> ``` 2. Сделайте двоичный файл kubectl исполняемым:

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: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--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
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.
Change:
kube-proxy | kube-proxy | Kubelet | Kubelet | Kubernetes | 쿠버네티스 | <ins> Kube-router | Kube-router | </ins> label | 레이블 | lifecycle | 라이프사이클 | Linux | 리눅스 |

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. --There are several CNI plugins that need to be translated into Korean to be to . English --- --- Calico Cilium Flannel Kube-router Romana Weave-net Weaveworks 'Weave Net' . Why is this needed This is for standardization of terminology when document is localized. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --Page to update: - /language ko
/assign
Change:
where: <del> * `<your-registry-server>` is your Private Docker Registry FQDN. (https://index.docker.io/v1/ for DockerHub) </del> <ins> * `<your-registry-server>` is your Private Docker Registry FQDN. Use `https://index.docker.io/v2/` for DockerHub. </ins> * `<your-name>` is your Docker username. * `<your-pword>` is your Docker password. * `<your-email>` is your Docker email.

Discussion:
This link "" appears to be broken in the line: " <your-registry-serveris your Private Docker Registry FQDN. ( for DockerHub) "
According to , the V1 API has been deprecated.
/triage accepted /assign
Change:
### オブジェクトリストのソート <del> ターミナルウィンドウで、オブジェクトをソートされたリストに出力するには、サポートされている`kubectl`コマンドに`--sort-by`フラグを追加します。`--sort-by`フラグで任意の数値フィールドや文字列フィールドを指定することで、オブジェクトをソートします。フィールドの指定には、[jsonpath](/docs/reference/kubectl/jsonpath/)式を使用します。 </del> <ins> ターミナルウィンドウで、オブジェクトをソートされたリストに出力するには、サポートされている`kubectl`コマンドに`--sort-by`フラグを追加します。`--sort-by`フラグで任意の数値フィールドや文字列フィールドを指定することで、オブジェクトをソートします。フィールドの指定には、[jsonpath](/ja/docs/reference/kubectl/jsonpath/)式を使用します。 </ins> #### 構文

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. --Translate reference/kubectl/jsonpath/ into Japanese. Why is this needed This page has not been translated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/triage accepted
Change:
<ins> ## `ClientConnectionConfiguration`     {#ClientConnectionConfiguration} **Appears in:** - [KubeProxyConfiguration](#kubeproxy-config-k8s-io-v1alpha1-KubeProxyConfiguration) ClientConnectionConfiguration contains details for constructing a client. <table class="table"> <thead><tr><th width="30%">Field</th><th>Description</th></tr></thead> <tbody> <tr><td><code>kubeconfig</code> <B>[Required]</B><br/> <code>string</code> </td> <td> kubeconfig is the path to a KubeConfig file.</td> </tr> <tr><td><code>acceptContentTypes</code> <B>[Required]</B><br/> <code>string</code> </td> <td> acceptContentTypes defines the Accept header sent by clients when connecting to a server, overriding the default value of 'application/json'. This field will control all connections to the server used by a particular client.</td> </tr> <tr><td><code>contentType</code> <B>[Required]</B><br/> <code>string</code> </td> <td> contentType is the content type used when sending data to the server from this client.</td> </tr> <tr><td><code>qps</code> <B>[Required]</B><br/> <code>float32</code> </td> <td> qps controls the number of queries per second allowed for this connection.</td> </tr> <tr><td><code>burst</code> <B>[Required]</B><br/> <code>int32</code> </td> <td> burst allows extra queries to accumulate when a client is exceeding its rate.</td> </tr> </tbody> </table> </ins>

Discussion:
links to in the table, but does not exist. Probably it should be linked to another page?
/triage accepted /kind bug /assign