jiebi/CodeConvo huggingface dataset:
Change:
### Beta level <ins> - **ephemeralContainers** ([]<a href="{{< ref "../workload-resources/pod-v1#EphemeralContainer" >}}">EphemeralContainer</a>) *Patch strategy: merge on key `name`* List of ephemeral containers run in this pod. Ephemeral containers may be run in an existing pod to perform user-initiated actions such as debugging. This list cannot be specified when creating a pod, and it cannot be modified by updating the pod spec. In order to add an ephemeral container to an existing pod, use the pod's ephemeralcontainers subresource. This field is beta-level and available on clusters that haven't disabled the EphemeralContainers feature gate. </ins> - **preemptionPolicy** (string) PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.

Discussion:
This is a Bug Report <!--Required Information--Problem: Setting for ephemeral containers is allowed as of Kubernetes 1.22, but it's still showing up as a "not allowed" field here: Proposed Solution: This page looks to be autogenerated based on the API definition, but I'm not sure how it's detecting not allowed fields. If it's automatic we'll correct the metadata or if it's curated then just reclassify the field in docs. Page to Update:
/assign
The fix is likely to happen within
is autogenerated. I don't think received field updates for v1.22
Track the update of the documentation as an issue in this repository. /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]:
Looks like this is still happening, and also is showing up under the alpha heading even though its description says (correctly) that it's beta. This dropped off my radar, but I'll take a look at it in the next few days. /remove-lifecycle stale
/priority critical-urgent
/remove-priority critical-urgent /priority important-soon /sig security you're welcome to make a case for raising it back to critical. What would be the motivation there?
Hi I don't wish to make that case. I was just trying to assign a priority according to guidance and . The documentation is wrong for a core feature, which seems like a "fix it now" rather than "fix it in the next release" priority. The priority isn't important to me, though. Happy for it to be whatever you think is best.
This repo uses continuous deployment (we don't wait for a release for fixes). Anyway, yes, it looks important.
Change:
1. Загрузите последнюю версию с помощью команды: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/`curl -LS https://dl.k8s.io/release/stable.txt`/bin/linux/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" >}} для Linux будет выглядеть следующим образом: ``` <del> curl -LO https://storage.googleapis.com/kubernetes-release/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/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:
#### Указание версии Kubernetes <del> Вы можете указать используемую версию Kubernetes в Minikube, добавив параметр `--kubernetes-version` в команду `minikube start`. Например, чтобы запустить Minikube из-под версии {{< param "fullversion" >}}, вам нужно выполнить следующую команду: </del> <ins> Вы можете указать используемую версию Kubernetes в Minikube, добавив параметр `--kubernetes-version` в команду `minikube start`. Например, чтобы запустить Minikube из-под версии {{< skew currentPatchVersion >}}, вам нужно выполнить следующую команду: </ins> ```shell <del> minikube start --kubernetes-version {{< param "fullversion" >}} </del> <ins> minikube start --kubernetes-version {{< skew currentPatchVersion >}} </ins> ``` #### Указание драйвера виртуальной машины

Discussion:
Problem: Based on , I have created this issue/task to help update the [ru] language documentation. Proposed Solution: Page to Update: In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 33: Например, для установки версии {{< param "fullversion" }} на Linux введите: 36: {{< param "fullversion" }}/bin/linux/amd64/kubectl 110: Например, для установки версии {{< param "fullversion" }} на macOS введите: 113: {{< param "fullversion" }}/bin/darwin/amd64/kubectl 175: 1. Загрузите последний релиз {{< param "fullversion" }} по этой ссылке. 180: {{< param "fullversion" }} In the branch, I found: Results for "fullversion" in "k8s-website/content/ru" /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/concepts/containers/container- 44: DNS, если включен . /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/setup/learning- 222: чтобы запустить Minikube из-под версии {{< param "fullversion" }}, вам нужно выполнить следующую команду: 225: minikube start --kubernetes-version {{< param "fullversion" }} /home/rdlugyhe/kubernetes/k8s-website/content/ru/docs/tasks/tools/install- 36: Например, команда загрузки версии {{< param "fullversion" }} для Linux будет выглядеть следующим образом 39: curl -LO {{< param "fullversion" }}/bin/linux/amd64/kubectl 116: Например, команда загрузки версии {{< param "fullversion" }} для macOS будет выглядеть следующим образом 119: curl -LO {{< param "fullversion" }}/bin/darwin/amd64/kubectl 183: 1.

Загрузите последнюю версию {{< param "fullversion" }} по этой ссылкеe
Change:
## `README.md`'s स्थानीयकरण कुबरनेट्स प्रलेखन <del> आप पर हिंदी स्थानीयकरण के maintainers तक पहुँच सकते हैं: </del> <ins> आप हिंदी स्थानीयकरण के मैन्टेनरों तक पहुँच सकते हैं: * Anubhav Vardhan ([Slack](https://kubernetes.slack.com/archives/D0261C0A3R8), [Twitter](https://twitter.com/anubha_v_ardhan), [GitHub](https://github.com/anubha-v-ardhan)) * Divya Mohan ([Slack](https://kubernetes.slack.com/archives/D027R7BE804), [Twitter](https://twitter.com/Divya_Mohan02), [GitHub](https://github.com/divya-mohan0209)) </ins> * Yashu Mittal ([Twitter](https://twitter.com/mittalyashu77), [GitHub](https://github.com/mittalyashu)) * [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-hi) ## स्थानीय रूप से डॉकर का उपयोग करके साइट चलाना

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: All the current maintainers of Hindi localization are not mentioned in README- isn't grammatically correct. Proposed Solution: Add and with appropriate links to -Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language hi
Can I work on this?
Sure, Here are the links to be Slack: Twitter: GitHub: Slack: Twitter: /assign
/triage accepted
/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 : /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
Hey I'm working on this right now
Sorry but is already assigned to fix this. We would love to see more contributions from you.
/unassign
Change:
## Creating a new namespace <ins> {{< note >}} Avoid creating namespace with prefix `kube-`, since it is reserved for Kubernetes system namespaces. {{< /note >}} </ins> 1. Create a new YAML file called `my-namespace.yaml` with the contents: ```yaml

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 Update to document that namespaces starting are reserved. Why is this needed According to all namespaces with names that start with are reserved. Comments /kind feature /language en /sig architecture /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update to document that namespaces starting are reserved. According to all namespaces with names that start with are reserved. /kind feature /language en /sig architecture /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
/assign me
GitHub didn't allow me to assign the following users: me. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign me </details
/assign
Change:
<ins> --- title: ミラーPod id: mirror-pod date: 2019-08-06 short_description: > kubelet上のstatic Podを追跡するAPIサーバー内のオブジェクトです。 aka: tags: - fundamental --- kubeletが{{< glossary_tooltip text="static Pod" term_id="static-pod" >}}を代表するために使用する{{< glossary_tooltip text="Pod" term_id="pod" >}}オブジェクトです。 <!--more--> kubeletが設定の中にstatic Podを発見すると、static Podに対応するPodオブジェクトをKubernetes APIサーバー上に自動的に作成しようとします。つまり、APIサーバーからはPodが見えていますが、制御まではできないということです。 (たとえば、ミラーPodを削除しても、kubeletデーモンが対応するPodの実行を停止することはありません。) </ins>

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
Change:
```shell openssl genrsa -out myuser.key 2048 <del> openssl req -new -key myuser.key -out myuser.csr </del> <ins> openssl req -new -key myuser.key -out myuser.csr -subj "/CN=myuser" </ins> ``` ### Create a CertificateSigningRequest {#create-certificatessigningrequest}

Discussion:
I guess this needs to be appended here After following instructions I am unable to authenticate to the cluster if is missing.
I think the author of that reference page expected that you would use the OpenSSL tool interactively, and that's why you can read: If your configuration for OpenSSL doesn't prompt you for a common name, the advice won't work as expected. We could change this page to use a different tool - not - that is perhaps easier to explain consistently. /sig auth /language en
Just by appending would make this reference a working copy/paste step-by-step guide.
Should we do this as the first step so the docs are correct? Then we could explore the option of a different tool as per WDYT?
/triage accepted
I won't comment on that - SIG Auth or SIG Security are the best people to explain and confirm what the right fix is here, from a technical perspective. If you know it does fix this then sure, feel free to open a PR.
I will open a PR for it. /assign
Fixed it here:
or anyone from you, could you please take a look at the PR: corresponding to this issue? Thanks
Change:
<!-- image source: https://docs.google.com/drawings/d/1k2YdJgNTtNfW7_A8moIIkij-DmVgEhNrn3y2OODwqQQ/view --> <del> {{< figure src="/docs/concepts/extend-kubernetes/extension-points.svg" </del> <ins> {{< figure src="/docs/concepts/extend-kubernetes/extension-points.png" </ins> alt="用符号表示的七个编号的 Kubernetes 扩展点" class="diagram-large" caption="Kubernetes 扩展点" >}}

Discussion:
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
Please raise the issue in English language so that it can be easy to understand in community.
/language zh Issue Translation is Currently this After this page select , the text in the flow chart is not .
/triage needs-information Even with a translation, I don't understand if this is a bug report, a support query, or a feature request.
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page It is a bug, on zh-cn page , the text in the flowchart should be Chinese instead of Korean.
Re-titling can only be requested by trusted users, like repository collaborators. <detailsIn response to : /retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page , the text in the flowchart should be Chinese instead of Korean. 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
/retitle [zh] Bug - the text in the flowchart should be Chinese on Extending Kubernetes page
/assign
Change:
the threshold values respectively. {{< /note >}} <ins> The `imagefs` is an optional filesystem that container runtimes use to store container images and container writable layers. </ins> ## Start a kubelet process configured via the config file {{< note >}}

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: As we know that, in eviction hard thresholds, when we change the default value of any one of the four parameters (memory.available, nodefs.available, imagefs.available, nodefs.inodesFree), then the value of other parameters will be set to 0. Although this is an expected behaviour but I think it's not a good motivation for user to change only the one parameter as given in this . As setting other parameters to 0 is not a good scenario. Proposed Solution: Is there any good case by setting the other parameters to 0 or we should change the example to motivate users to change all parameters 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 en
/retitle Enhance and add more evictionHard thresholds in example yaml to encourage holistic parameter changes
/remove-kind bug /kind feature
/assign
Change:
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: > 为 Kubernetes 开源代码库开发并贡献代码的人。

Discussion:
This is a Bug Report I have fixed the same issue in English docs, same issue is followed by the other localization team. has one broken issue which needs to fix. ! Refer my merged PR of english docs. /assign
/triage accepted
Change:
この時点で、オブジェクトはKubernetesAPIに表示されなくなります。 フォアグラウンドカスケード削除中に、オーナーの削除をブロックする依存関係は、`ownerReference.blockOwnerDeletion=true`フィールドを持つ依存関係のみです。 <del> 詳細については、[フォアグラウンドカスケード削除の使用](/docs/tasks/administer-cluster/use-cascading-deletion/#use-foreground-cascading-deletion)を参照してください。 </del> <ins> 詳細については、[フォアグラウンドカスケード削除の使用](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#use-foreground-cascading-deletion)を参照してください。 </ins> ### バックグラウンドカスケード削除 {#background-deletion} バックグラウンドカスケード削除では、Kubernetes APIサーバーがオーナーオブジェクトをすぐに削除し、コントローラーがバックグラウンドで依存オブジェクトをクリーンアップします。 デフォルトでは、フォアグラウンド削除を手動で使用するか、依存オブジェクトを孤立させることを選択しない限り、Kubernetesはバックグラウンドカスケード削除を使用します。 <del> 詳細については、[バックグラウンドカスケード削除の使用](/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)を参照してください。 </del> <ins> 詳細については、[バックグラウンドカスケード削除の使用](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#use-background-cascading-deletion)を参照してください。 </ins> ### 孤立した依存関係 Kubernetesがオーナーオブジェクトを削除すると、残された依存関係は*orphan*オブジェクトと呼ばれます。 <del> デフォルトでは、Kubernetesは依存関係オブジェクトを削除します。この動作をオーバーライドする方法については、[オーナーオブジェクトと孤立した依存関係の削除](/docs/tasks/administer-cluster/use-cascading-deletion/#set-orphan-deletion-policy)を参照してください。 </del> <ins> デフォルトでは、Kubernetesは依存関係オブジェクトを削除します。この動作をオーバーライドする方法については、[オーナーオブジェクトの削除と従属オブジェクトの孤立](/ja/docs/tasks/administer-cluster/use-cascading-deletion/#set-orphan-deletion-policy)を参照してください。 </ins> ## 未使用のコンテナとイメージのガベージコレクション {#containers-images}

Discussion:
This is a Feature Request What would you like to be Translate tasks/administer-cluster/use-cascading-deletion/ into Japanese. Why is this needed This page has not been translated. 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:
<!-- Fetch release_binaries.json from kubernetes-sigs/downloadkubernetes to render in table --> <del> {{ $response := getJSON "https://raw.githubusercontent.com/kubernetes-sigs/downloadkubernetes/master/dist/release_binaries.json" }} </del> <ins> {{- $url := "https://raw.githubusercontent.com/kubernetes-sigs/downloadkubernetes/master/dist/release_binaries.json" }} {{- $response := "" }} {{- with resources.GetRemote $url -}} {{- if .Err -}} {{- $message := printf "Failed to retrieve release binaries data: %s" .Err -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- else -}} {{- $response = .Content | transform.Unmarshal }} {{- end -}} {{- else -}} {{ $message := printf "Unable to fetch release binaries data from the specified URL: %q" $url -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- end -}} <!-- Continue processing only if release binaries JSON is available, accommodating for offline builds. --> {{ if ne $response nil }} </ins> {{ $currentVersion := site.Params.version }} {{ $Binaries := slice }}

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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign
Change:
admission controller. To get started with `cosigned` here are a few helpful resources: <del> * [Installation](https://github.com/sigstore/helm-charts/tree/main/charts/cosigned) </del> <ins> * [Installation](https://github.com/sigstore/cosign#installation) </ins> * [Configuration Options](https://github.com/sigstore/cosign/tree/main/config)

Discussion:
The and link in the section are broken.
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 don't know if the issue is open or not, but I would like to work in it.
Looks like installation of cosign has moved from to
/assign
What about Configuration link?
Hi Instead of Configuration we can add Detailed usage of cosign there -