jiebi/CodeConvo huggingface dataset:
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: redirects to Proposed Solution: Remove the alias from the Portuguese blog page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /priority critical-urgent /kind bug /area blog I think a side effect of would be to make this kind of mixup less likely.
/triage accepted

Discussion:
title: "Atualizado: Perguntas frequentes (FAQ) sobre a remoção do Dockershim" date: 2022-02-17 slug: dockershim-faq <del> aliases: [ '/dockershim' ] </del> --- **Esta é uma atualização do artigo original [FAQ sobre a depreciação do Dockershim](/blog/2020/12/02/dockershim-faq/),
Change:
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 ja/docs/concepts/scheduling-eviction/kube- to fix the weight and some links. Why is this needed The weight value has changed on the current English page. One of the links on this page does not work. Update to other links. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/retitle [ja] Update /ja/docs/concepts/scheduling-eviction/kube- to fix the weight and some links /triage accepted

Discussion:
--- title: Kubernetesのスケジューラー content_type: concept <del> weight: 60 </del> <ins> weight: 10 </ins> --- <!-- overview -->

* [Podトポロジーの分散制約](/docs/concepts/workloads/pods/pod-topology-spread-constraints/)を参照してください。 * kube-schedulerの[リファレンスドキュメント](/docs/reference/command-line-tools-reference/kube-scheduler/)を参照してください。 * [複数のスケジューラーの設定](/docs/tasks/administer-cluster/configure-multiple-schedulers/)について学んでください。 <del> * [トポロジーの管理ポリシー](/docs/tasks/administer-cluster/topology-manager/)について学んでください。 * [Podのオーバーヘッド](/docs/concepts/scheduling-eviction/pod-overhead/)について学んでください。 </del> <ins> * [トポロジーの管理ポリシー](/ja/docs/tasks/administer-cluster/topology-manager/)について学んでください。 * [Podのオーバーヘッド](/ja/docs/concepts/scheduling-eviction/pod-overhead/)について学んでください。 </ins> * ボリュームを使用するPodのスケジューリングについて以下で学んでください。 * [Volume Topology Support](/docs/concepts/storage/storage-classes/#volume-binding-mode) <del> * [ストレージ容量の追跡](/ja//ja/docs/concepts/storage/storage-capacity/) </del> <ins> * [ストレージ容量の追跡](/ja/docs/concepts/storage/storage-capacity/) </ins> * [Node-specific Volume Limits](/docs/concepts/storage/storage-limits/)
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: doesn't mention the feature gate , but it should do. Proposed Solution: Update documentation for migration from in-tree Azure File driver. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig storage /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
/assign

Discussion:
must be installed on the cluster and the `CSIMigration` and `CSIMigrationAzureDisk` features must be enabled. <ins> #### azureDisk CSI migration complete {{< feature-state for_k8s_version="v1.21" state="alpha" >}} To disable the `azureDisk` storage plugin from being loaded by the controller manager and the kubelet, set the `InTreePluginAzureDiskUnregister` flag to `true`. </ins> ### azureFile {#azurefile} The `azureFile` volume type mounts a Microsoft Azure File volume (SMB 2.1 and 3.0)

Azure File CSI driver does not support using same volume with different fsgroups, if Azurefile CSI migration is enabled, using same volume with different fsgroups won't be supported at all. <ins> #### azureFile CSI migration complete {{< feature-state for_k8s_version="v1.21" state="alpha" >}} To disable the `azureFile` storage plugin from being loaded by the controller manager and the kubelet, set the `InTreePluginAzureFileUnregister` flag to `true`. </ins> ### cephfs A `cephfs` volume allows an existing CephFS volume to be
Change:
While evaluating , it was suggested that we should make a stronger statement about migrating from dockershim on the page. The current wording is: Perhaps it could be more along the lines of:
/language en /triage accepted
Hi, I would like to work on this issue. Thanks. /assign
I have one question: The PR for this issue should target the branch or the branch?
Good question. I think clarity is a good thing right now. So my personal preference is .

Discussion:
<!-- body --> <del> If you use Docker via dockershim as your container runtime, the Kubernetes project recommends that you migrate to an alternative container runtime. </del> <ins> Dockershim will be removed from Kubernetes following the release of v1.24. If you use Docker via dockershim as your container runtime, and wish to upgrade to v1.24, it is recommended that you either migrate to another runtime or find an alternative means to obtain Docker Engine support. </ins> If you're not sure whether you are using Docker, [find out what container runtime is used on a node](/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/).
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: I use the /website/edit/main/content/en/examples/application/mysql/mysql- to deploy mysql cluster,and get error when the mysql-1 clone-mysql container starting to get backup file: I think it is the reason why datadir is not specified Proposed Solution: then I change mysql- as It works fine and success create other pod Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:v1.18.8--<!--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
/assign

Discussion:
# Apply this config only on the primary. [mysqld] log-bin <ins> datadir=/var/lib/mysql/mysql </ins> replica.cnf: | # Apply this config only on replicas. [mysqld] super-read-only <ins> datadir=/var/lib/mysql/mysql </ins>
Change:
There is a bug: ,%E4%BA%86%E8%A7%A3%E5%9E%83%E5%9C%BE%E6%94%B6%E9%9B%86.,-%E5%8F%8D%E9%A6%88 This hyperlink is 404, it should be ""
/assign
/triage accepted
The issue was solved by PR . If there is any problem, please give feedback again. /close
Closing this issue. <detailsIn response to : The issue was solved by PR . If there is any problem, please give feedback again. /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
<!--overview--> <!-- <del> This page shows you how to specify the type of [cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> This page shows you how to specify the type of [cascading deletion](/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> to use in your cluster during {{<glossary_tooltip text="garbage collection" term_id="garbage-collection">}}. --> 本页面向你展示如何设置在你的集群执行{{<glossary_tooltip text="垃圾收集" term_id="garbage-collection">}} <del> 时要使用的[级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#cascading-deletion) </del> <ins> 时要使用的[级联删除](/zh/docs/concepts/architecture/garbage-collection/#cascading-deletion) </ins> 类型。 ## {{% heading "prerequisites" %}}

<!-- ## Use foreground cascading deletion {#use-foreground-cascading-deletion} <del> By default, Kubernetes uses [background cascading deletion](/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> By default, Kubernetes uses [background cascading deletion](/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> to delete dependents of an object. You can switch to foreground cascading deletion using either `kubectl` or the Kubernetes API, depending on the Kubernetes version your cluster runs. {{<version-check>}} --> ## 使用前台级联删除    {#use-foreground-cascading-deletion} <del> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/workloads/controllers/garbage-collection/#background-deletion) </del> <ins> 默认情况下，Kubernetes 使用[后台级联删除](/zh/docs/concepts/architecture/garbage-collection/#background-deletion) </ins> 以删除依赖某对象的其他对象。取决于你的集群所运行的 Kubernetes 版本， 你可以使用 `kubectl` 或者 Kubernetes API 来切换到前台级联删除。 {{<version-check>}}

输出中包含 `foregroundDeletion` {{<glossary_tooltip text="finalizer" term_id="finalizer">}}， 类似这样： <del> ```none </del> <ins> ``` </ins> "kind": "Deployment", "apiVersion": "apps/v1", "metadata": {

--> * 了解 Kubernetes 中的[属主与依赖](/zh/docs/concepts/overview/working-with-objects/owners-dependents/) * 了解 Kubernetes [finalizers](/zh/docs/concepts/overview/working-with-objects/finalizers/) <del> * 了解[垃圾收集](/zh/docs/concepts/workloads/controllers/garbage-collection/). </del> <ins> * 了解[垃圾收集](/zh/docs/concepts/architecture/garbage-collection/). </ins>
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: Running the command fails with the following error: What I did: I ran the following commands: The current directory is mounted into . In the container, these files appear as owned by root (group nobody). I think, this may be a consequence of this CVE-2022-  What else I tried: Adding to the Dockerfile doesn't have an effect. Adding to the environment in the container didn't have an effect. (Found ). Running the command as root works. Proposed Solution: I don't know what the best solution would be. Maybe just wait until is updated for alpine? <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi. What OS are you running Docker on
I can replicate this with a recent image (local checksum: )
/triage accepted /priority important-longterm Thanks for reporting this
I think adding to the would be a reasonable fix, so long as it's done the right way.
I got it working by: the mount point of the docs directory OR using a different working directory for the user. (Otherwise the gets overwritten by the mounted ). an additional after we set the user and working directory.

Discussion:
FROM golang:1.16-alpine RUN apk add --no-cache  <ins> runuser  </ins> git  openssh-client  rsync  npm &&  npm install -D autoprefixer postcss-cli <del> RUN mkdir -p /usr/local/src &&  cd /usr/local/src &&  </del> <ins> RUN mkdir -p /var/hugo &&  </ins> addgroup -Sg 1000 hugo &&  <del> adduser -Sg hugo -u 1000 -h /src hugo </del> <ins> adduser -Sg hugo -u 1000 -h /var/hugo hugo &&  chown -R hugo: /var/hugo &&  runuser -u hugo -- git config --global --add safe.directory /src </ins> COPY --from=0 /go/bin/hugo /usr/local/bin/hugo
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 following sentence is not complete: As this guide explains using the cgroupfs driver with kubeadm is not recommended. What would you like to be : More information needs to be after "explains", or rephrase it from scratch. 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
/language en /sig cluster-lifecycle
do you mean that the sentence: As this guide explains using the cgroupfs driver with kubeadm is not recommended. should link to one of the earlier paragraphs on the same page (same guide)? The page explains that the systemd driver is recommended for kubeadm based setups instead of the cgroupfs driver, because kubeadm manages the kubelet as a systemd service. if you have a particular change in mind, please send a PR for review.
technically, as per the overall page context, the sentence: As this guide explains using the cgroupfs driver with kubeadm is not recommended. can be deleted entirely... the section is providing an alternative after the main point has been made earlier - i.e. "cgroupfs driver = not recommended".

Discussion:
## Using the `cgroupfs` driver <del> As this guide explains using the `cgroupfs` driver with kubeadm is not recommended. To continue using `cgroupfs` and to prevent `kubeadm upgrade` from modifying the </del> <ins> To use `cgroupfs` and to prevent `kubeadm upgrade` from modifying the </ins> `KubeletConfiguration` cgroup driver on existing setups, you must be explicit about its value. This applies to a case where you do not wish future versions of kubeadm to apply the `systemd` driver by default.
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: I followed the section "Running the website locally using Hugo" in README of this repo, but I met an error. With Ubuntu 18.04 desktop amd64 the latest commit of this repo () Docsy whose version is the same as of (docsy @ ) npm version: 6.14.15 node version: v14.18.1 go version go1.17.3 linux/amd64 hugo v0.96.0-+extended linux/amd64 BuildDate=2022-03-26T09:15:58Z VendorInfo=mage Docker Client/Server: 20.10.11 [How to reproduce] Proposed Solution:
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
The version of Hugo that we support is as declared in : 0.87.0 Try using Hugo 0.87.0 Pull requests to adopt a newer Hugo version are welcome.
Following comment, I confirmed that this error does not occur with Hugo 0.87.0. After doing some testing, it seems that the field is accessible with Hugo 0.87.0, but not with Hugo 0.96.0 (and maybe with some other versions too). (I tried to find Hugo changelog that says field of is deprecated in what Hugo version, but I could not find.) Suggested solution: Instead of field, if we use , I checked locally that it seems working. [] How I checked: In page (http://localhost:1313/docs/concepts/workloads/controllers/cron-jobs/#what-s-next), the link goes to http://localhost:1313/docs/reference/kubernetes-api/workload-resources/cron-job-v1/ , for these cases: (As-is) , with Hugo 0.87.0 (To-be) , with Hugo 0.87.0 (To-be) , with Hugo 0.96.0 /area web-development
/assign

Discussion:
{{ $textArg := .Get "text" }} {{ $page := site.GetPage "page" (printf "%s/%s" $base $pageArg) }} {{ $metadata := $page.Params.api_metadata }} <del> <a href="{{ $page.URL }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a> </del>  No newline at end of file <ins> <a href="{{ $page.RelPermalink }}{{if $anchorArg}}#{{ $anchorArg }}{{end}}">{{if $textArg}}{{ $textArg }}{{else if $anchorArg}}{{ $anchorArg }}{{else}}{{ $metadata.kind }}{{end}}</a> </ins>  No newline at end of file
Change:
Hello, It's not clear what the meaning of restricted warnings and restricted audit or any combination of them. It seems that you attempt to design in a way that you want to make things more complicated. The aim of your design seems that nobody should be able to understand clearly and one should spend a lot of time for understanding the basics. You can create very complex systems but at the end you will see that nobody uses them. We have seen such attempts in the past from big vendors and after a lot of marketing and spending millions of dollars, those big guys failed miserably. Can someone explain the meaning of all those and possibly more combinations? enforce: baseline, audit: baseline, warn: baseline enforce: baseline, audit: restricted, warn: baseline enforce: baseline, audit: restricted, warn: restricted enforce: restricted, audit: baseline, warn: baseline enforce: restricted, audit: restricted, warn: baseline enforce: restricted, audit: restricted, warn: restricted enforce: privileged, audit: baseline, warn: baseline enforce: privileged, audit: privileged, warn: baseline enforce: privileged, audit: privileged, warn: privileged enforce: baseline, audit: restricted, warn: privileged ... ... ...
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
The first sentence in this page is Although this introduction is accurate, we could add more text to avoid the risk of a reader skipping past it and then feeling confused. For example, we could name the three Pod Security Standards and make each of those names a link to the relevant part of ; we could also repeat the table from the top of do you think adding more text to the introduction would help here? /language en
We could also link to in the introduction; I think we should.

Discussion:
min-kubernetes-server-version: v1.22 --- <del> Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). </del> <ins> Namespaces can be labeled to enforce the [Pod Security Standards](/docs/concepts/security/pod-security-standards). The three policies [privileged](/docs/concepts/security/pod-security-standards/#privileged), [baseline](/docs/concepts/security/pod-security-standards/#baseline) and [restricted](https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted) broadly cover the security spectrum and are implemented by the [Pod Security](/docs/concepts/security/pod-security-admission/) {{< glossary_tooltip text="admission controller" term_id="admission-controller" >}}. </ins> ## {{% heading "prerequisites" %}}
Change:
This is a Feature Request What would you like to be Update README- Why is this needed has been updated after translated Comments /language ja
/triage accepted

Discussion:
このリポジトリには、[KubernetesのWebサイトとドキュメント](https://kubernetes.io/)をビルドするために必要な全アセットが格納されています。貢献に興味を持っていただきありがとうございます！ <ins> - [ドキュメントに貢献する](#contributing-to-the-docs) - [翻訳された`README.md`一覧](#localization-readmemds) </ins> # リポジトリの使い方 Hugo(Extended version)を使用してWebサイトをローカルで実行することも、コンテナランタイムで実行することもできます。コンテナランタイムを使用することを強くお勧めします。これにより、本番Webサイトとのデプロイメントの一貫性が得られます。

これで、Hugoのサーバーが1313番ポートを使って開始します。お使いのブラウザにて http://localhost:1313 にアクセスしてください。リポジトリ内のソースファイルに変更を加えると、HugoがWebサイトの内容を更新してブラウザに反映します。 <ins> ## API reference pagesをビルドする `content/en/docs/reference/kubernetes-api`に配置されているAPIリファレンスページは<https://github.com/kubernetes-sigs/reference-docs/tree/master/gen-resourcesdocs>を使ってSwagger仕様書からビルドされています。 新しいKubernetesリリースのためにリファレンスページをアップデートするには、次の手順を実行します: 1. `api-ref-generator`サブモジュールをプルする: ```bash git submodule update --init --recursive --depth 1 ``` 2. Swagger仕様書を更新する: ```bash curl 'https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json' > api-ref-assets/api/swagger.json ``` 3. 新しいリリースの変更を反映するため、`api-ref-assets/config/`で`toc.yaml`と`fields.yaml`を適用する。 4. 次に、ページをビルドする: ```bash make api-reference ``` コンテナイメージからサイトを作成・サーブする事でローカルで結果をテストすることができます: ```bash make container-image make container-serve ``` APIリファレンスを見るために、ブラウザで<http://localhost:1313/docs/reference/kubernetes-api/>を開いてください。 5. 新しいコントラクトのすべての変更が設定ファイル`toc.yaml`と`fields.yaml`に反映されたら、新しく生成されたAPIリファレンスページとともにPull Requestを作成します。 </ins> ## トラブルシューティング ### error: failed to transform resource: TOCSS: failed to transform "scss/main.scss" (text/x-scss): this feature is not available in your current Hugo version

- [Slack](https://kubernetes.slack.com/messages/kubernetes-docs-ja) - [メーリングリスト](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) <del> ## ドキュメントに貢献する </del> <ins> ## ドキュメントに貢献する {#contributing-to-the-docs} </ins> GitHubの画面右上にある**Fork**ボタンをクリックすると、お使いのGitHubアカウントに紐付いた本リポジトリのコピーが作成され、このコピーのことを*フォーク*と呼びます。フォークリポジトリの中ではお好きなように変更を加えていただいて構いません。加えた変更をこのリポジトリに追加したい任意のタイミングにて、フォークリポジトリからPull Reqeustを作成してください。

* [ドキュメントのスタイルガイド](https://kubernetes.io/docs/contribute/style/style-guide/) * [Kubernetesドキュメントの翻訳方法](https://kubernetes.io/docs/contribute/localization/) <del> ## 翻訳された`README.md`一覧 </del> <ins> ### New Contributor Ambassadors コントリビュートする時に何か助けが必要なら、[New Contributor Ambassadors](https://kubernetes.io/docs/contribute/advanced/#serve-as-a-new-contributor-ambassador)に聞いてみると良いでしょう。彼らはSIG Docsのapproverで、最初の数回のPull Requestを通して新しいコントリビューターを指導し助けることを責務としています。New Contributors Ambassadorsにコンタクトするには、[Kubernetes Slack](https://slack.k8s.io)が最適な場所です。現在のSIG DocsのNew Contributor Ambassadorは次の通りです: | 名前                       | Slack                      | GitHub                     | | -------------------------- | -------------------------- | -------------------------- | | Arsh Sharma                | @arsh                      | @RinkiyaKeDad              | ## 翻訳された`README.md`一覧 {#localization-readmemds} </ins> | Language  | Language | |---|---|