jiebi/CodeConvo huggingface dataset:
Code change:
For further documentation refer to the authorization.v1beta1 API objects and [webhook.go](https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/staging/src/k8s.io/apiserver/plugin/pkg/authorizer/webhook/webhook.go).

Related discussion:
text: 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: Documentation - description is not fully inline with current version. Current text: "Non-resource paths include: /api, /apis, /metrics, /resetMetrics, /logs, /debug, /healthz, /swagger-ui/, /swaggerapi/, /ui, and /version." The following non-resource don't seem to exist anymore: '/resetMetrics', '/swagger-ui' ( swagger 1.2 was deprecated and functionality seems it was already removed), '/swaggerapi'. The non-resource path '/ui' would need more checking, but it seems is part only of some tests. Proposed Solution: Description should be updated accordingly. For example, the text could be updated as: "Non-resource paths include: /api, /apis, /metrics, /logs, /debug, /healthz, /livez, /openapi/v2, /readyz and /version." Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--{ "gitVersion": "v1.18.2", "gitCommit": "" } <!--Additional Information:--
/assign
/priority important-longterm /language en
/kind bug
Code change:
* `apiserver_flowcontrol_dispatched_requests_total` is a counter vector (cumulative since server start) of requests that began <del> executing, broken down by the labels `flowSchema` (indicating the one that matched the request) and `priorityLevel` (indicating the </del> <ins> executing, broken down by the labels `flow_schema` (indicating the one that matched the request) and `priority_level` (indicating the </ins> one to which the request was assigned). * `apiserver_current_inqueue_requests` is a gauge vector of recent

Related discussion:
text: Keep the doc consistent with
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
Code change:
kubectl create secret docker-registry secret-tiger-docker  --docker-username=tiger  --docker-password=pass113  <del> --docker-email=tiger@acme.com </del> <ins> --docker-email=tiger@acme.com  --docker-server=my-registry.example:5000 </ins> ``` このコマンドは、`kubernetes.io/dockerconfigjson`型のSecretを作成します。

Related discussion:
text: 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. --About Some corrections need to be made. Why is this needed JSON in .dockerconfigjson dump is strange. Lack of options for kubectl command. And some more correction is needed. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja
/assign
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten because the related PR is under reviewing /triage accepted
Code change:
--> [HostAliases](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#hostalias-v1-core) 是一个包含主机名和 IP 地址的可选列表，配置后将被注入到 Pod 内的 hosts 文件中。 <del> 该选项仅适用于没有配置 hostNetwork 的 Pod. </del> <ins> 该选项仅适用于没有配置 hostNetwork 的 Pod。 </ins>

Related discussion:
text: Hello, I noticed some punctuation errors on page /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
Code change:
release in order to get access to the packages of the desired Kubernetes minor version. <del> {{< tabs name="k8s_install_versions" >}} </del> <ins> {{< tabs name="k8s_upgrade_versions" >}} </ins> {{% tab name="Ubuntu, Debian or HypriotOS" %}} 1. Open the file that defines the Kubernetes `apt` repository using a text editor of your choice:

Related discussion:
text: : "Switching to another Kubernetes package repository" and particularly the one for CentOS/REHL shows commands for Debian based system, not REHL based rpm
I'm not seeing this. Can you point out where there are deb commands for RHEL? !
Excuse me it is for old versions: https://v1- https://v1- https://v1- !
I'm also not able to see this for Old version?? !
/retitle Broken tab layout on "Changing The Kubernetes Package Repository" page in older doc versions /kind bug
The problem stems from the existence of two tab layouts on this page having the same name "k8sinstallversions". This issue has been resolved in the branch. To address this issue in old docs versions, we'll need to backport and apply the fix to each corresponding old branch (release-1.25, release-1.26, release-1.27, release-1.28). Considering that the older versions of the documentation are no longer actively maintained, there's a question of whether it's worth investing efforts into fixing this issue.
I don't think it much important!
I'd support a backport. One of the things we do want people to learn to do with older Kubernetes versions is: to upgrade them! /triage accepted /priority backlog
I can try to help with this. /assign
I think the backporting is done which resolves this issue
If it is ok we can close this issue
The fixes have been back-ported to the older release branches. Closing this as completed. /close
Closing this issue. <detailsIn response to : The fixes have been back-ported to the older release branches. Closing this as completed. 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
Code change:
1. Validate the binary (optional) <del> Download the kubectl checksum file: </del> <ins> Download the `kubectl` checksum file: </ins> ```powershell curl -LO "https://dl.k8s.io/{{< param "fullversion" >}}/bin/windows/amd64/kubectl.exe.sha256" ``` <del> Validate the kubectl binary against the checksum file: </del> <ins> Validate the `kubectl` binary against the checksum file: </ins> - Using Command Prompt to manually compare `CertUtil`'s output to the checksum file downloaded:

Related discussion:
text: 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: In , the step No. 3 is talking about the location of binary, but actually in this section ("Install plugin") we should care about the location of binary, not of binary. Proposed Solution: In : And optionally, wrap these words with backquotes in : : kubectl L47: kubectl L62: kubectl L159: kubectl-convert L165: kubectl-convert (L180: kubectl-convert) - Already suggested above. Page to Update: )-,Append%20or%20prepend%20the%20kubectl%20binary%20folder%20to%20your%20PATH%20environment%20variable.,-Verify%20plugin%20is <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en
/triage accepted
/assign
Code change:
the YAML: `192.0.2.42:9376` (TCP). {{< note >}} <del> The Kubernetes API server does not allow proxying to endpoints that are not mapped to pods. Actions such as `kubectl proxy <service-name>` where the service has no selector will fail due to this constraint. This prevents the Kubernetes API server from being used as a proxy to endpoints the caller may not be authorized to access. </del> <ins> The Kubernetes API server does not allow proxying to endpoints that are not mapped to pods. Actions such as `kubectl proxy <service-name>` where the service has no selector will fail due to this constraint. This prevents the Kubernetes API server from being used as a proxy to endpoints the caller may not be authorized to access. </ins> {{< /note >}} An ExternalName Service is a special case of Service that does not have

Related discussion:
text: 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: marks the userspace kube-proxy as deprecated. This was missed from the v1.23 docs updates and . Proposed Solution: Mark the kube-proxy in userspace mode as deprecated. Page to Update: <!--Additional Information:--/sig network /language en /priority important-longterm
/lifecycle frozen /triage accepted
/assign
Code change:
/usr/local/bin/kubectl-foo /usr/local/bin/kubectl-bar ``` <del> ``` </del> <ins> ```shell </ins> # this command can also warn us about plugins that are # not executable, or that are overshadowed by other # plugins, for example

Related discussion:
text: 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: line 35~39, there are extra spaces(more than 4 spaces) in front of shell box. line 427~430, it should be a shell box. So, we need shell code. line 445~451, it should be a shell box. So, we need shell code. Proposed Solution: [1] : Specifies the . Resource types are case-insensitive and you can specify the singular, plural, or abbreviated forms. For example, the following commands produce the same output: [2] [3] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/assign
Code change:
アルファリリースでは、静的にプロビジョニングされたボリュームのみがサポートされます。管理者は、rawブロックデバイスを使用する場合、これらの値を考慮するように注意する必要があります。 {{< /note >}} <del> ## ボリュームのスナップショットとスナップショットからのボリュームの復元のサポート </del> <ins> ## ボリュームのスナップショットとスナップショットからのボリュームの復元のサポート {#volume-snapshot-and-restore-volume-from-snapshot-support} </ins> {{< feature-state for_k8s_version="v1.17" state="beta" >}}

Related discussion:
text: 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 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
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
/triage accepted
Code change:
```json { <del> "auths": { "https://index.docker.io/v1/": { "username": "tiger", "password": "pass113", "email": "tiger@acme.com", "auth": "dGlnZXI6cGFzczExMw==" } } </del> <ins> "apiVersion": "v1", "data": { ".dockerconfigjson": "eyJhdXRocyI6eyJteS1yZWdpc3RyeTo1MDAwIjp7InVzZXJuYW1lIjoidGlnZXIiLCJwYXNzd29yZCI6InBhc3MxMTMiLCJlbWFpbCI6InRpZ2VyQGFjbWUuY29tIiwiYXV0aCI6ImRHbG5aWEk2Y0dGemN6RXhNdz09In19fQ==" }, "kind": "Secret", "metadata": { "creationTimestamp": "2021-07-01T07:30:59Z", "name": "secret-tiger-docker", "namespace": "default", "resourceVersion": "566718", "uid": "e15c1d7b-9071-4100-8681-f3a7a2ce89ca" }, "type": "kubernetes.io/dockerconfigjson" </ins> } ``` ### Basic authentication Secret

Related discussion:
text: 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. --About Some corrections need to be made. Why is this needed JSON in .dockerconfigjson dump is strange. Lack of options for kubectl command. And some more correction is needed. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja
/assign
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
/remove-lifecycle rotten because the related PR is under reviewing /triage accepted
Code change:
* `apiserver_flowcontrol_request_execution_seconds` is a histogram vector of how long requests took to actually execute, broken down by <del> the labels `flowSchema` (indicating which one matched the request) and `priorityLevel` (indicating the one to which the request was </del> <ins> the labels `flow_schema` (indicating which one matched the request) and `priority_level` (indicating the one to which the request was </ins> assigned). ### Debug endpoints

Related discussion:
text: Keep the doc consistent with
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
Code change:
[blog_post_show_more] other = "Show More Posts..." <ins> [banner_acknowledgement] other = "Hide this notice" </ins> [caution] other = "Caution:"

Related discussion:
text: This is a Feature Request The red banner introduced with is too intrusive. Most Kubernetes users don't actually care about this deadline, and there is no way to dismiss it. What would you like to be A simple "dismiss" button that sets a cookie to hide the banner in any future visit, like other websites do. Why is this needed I'd argue that most users of the website just want to read the documentation, they aren't going to submit images to that registry, so the warning isn't useful. Comments This could be reused for future banners.
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 Add way to dismiss banners in the K8s website We would implement this for all banners, not just red ones.
/area web-development
oh boy! are you in for a ride!!
xref: also, here's how i deal with papercuts on the web -
Which all banners are you referring to? I'd be willing to take this up.
There's a banner displayed now, it looks like this: ! Imagine if you could click to acknowledge that you'd read it and didn't want to see it again for a fortnight. (separately: does feel relevant - ruled out taking action as they don't plan to push a container image there, which I think reveals a misunderstanding. I think it's worth repeating banners every couple of weeks in case it helps a message to land better).
Which ...To clarify for anyone reading: This banner applies to pulling / downloading container images from the Kubernetes project, this banner is aimed at users, not Kubernetes developers. Nobody can push directly to either of these hosts and the change isn't related to pushing / submitting images.
Thanks and for the explanation! I'll take this up and try to resolve this. /assign
are you working on this issue? I would like to help if you want. Do let me know.
Yes, I'm working on this still, mostly it's completed already, but thanks for the offer!
Code change:
[blog_post_show_more] other = "Show More Posts..." <ins> [banner_acknowledgement] other = "Hide this notice" </ins> [caution] other = "Caution:"

Related discussion:
text: The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues 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 as fresh with Close this issue with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
As XDRAGON2002 seems is evaded, could you please proceed?
/remove-lifecycle stale
I'll help with this, it seems like a good feature
/sig docs
Code change:
There are a few options for tuning DNS horizontal autoscaling. Which option to use depends on different conditions. <del> ### Option 1: Scale down the dns-autoscaler deployment to 0 replicas </del> <ins> ### Option 1: Scale down the kube-dns-autoscaler deployment to 0 replicas </ins> This option works for all situations. Enter this command: ```shell <del> kubectl scale deployment --replicas=0 dns-autoscaler --namespace=kube-system </del> <ins> kubectl scale deployment --replicas=0 kube-dns-autoscaler --namespace=kube-system </ins> ``` The output is: <del> deployment.apps/dns-autoscaler scaled </del> <ins> deployment.apps/kube-dns-autoscaler scaled </ins> Verify that the replica count is zero:

Related discussion:
text: dns-horizontal- kube-dns-autoscaler dns-autoscaler 2
/language zh
please describe the issue in English
page related to the issue:
/triage needs-information
Translate to English: The kube-dns-autoscaler used in dns-horizontal- and the dns-autoscaler used in subsequent commands are confused and out of sync. It seems that the English version also has this problem. /triage accepted /kind bug /retitle Inconsistent name in the DNS horizontal autoscaling example
/language en
/assign
Code change:
- [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を作成してください。

Related discussion:
text: 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
Code change:
## References <del> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build-tools/kube-dns/README.md) </del> <ins> - [Docs for the DNS cluster addon](http://releases.k8s.io/{{page.githubbranch}}/build/kube-dns/README.md) </ins> ## What's next - [Autoscaling the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/).

Related discussion:
text: This is a Bug Report Problem: includes dead link to at the bottom of the page
I guess it is here -
Code change:
* [ドキュメントのスタイルガイド](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 | |---|---|

Related discussion:
text: 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