jiebi/CodeConvo huggingface dataset:
Change:
- architecture - operation --- <del> Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud. </del> <ins> Cloud Controller Manager is a Kubernetes component that embeds cloud-specific control logic. </ins> <!--more--> <del> Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code. </del> <ins> Originally part of the kube-controller-manager, the cloud-controller-manager is responsible to decoupling the interoperability logic between Kubernetes and the underlying cloud infrastructure, enabling cloud providers to release features at a different pace compared to the main project. </ins>

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: is out of date; it talks about Kubernetes releases v1.6 and v1.8 Proposed Solution: At a minimum, remove the reference to releases v1.6 and v1.8 from the glossary entry. It's OK to revise further as well. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /kind cleanup /help /language en /priority important-longterm Also see issue
I'll work on that! /remove-help /assign
Change:
### 必須のフィールド <del> 他の全てのKubernetesの設定と同様に、DaemonSetは`apiVersion`、`kind`と`metadata`フィールドが必須となります。設定ファイルの活用法に関する一般的な情報は、[ステートレスアプリケーションの稼働](/ja/docs/tasks/run-application/run-stateless-application-deployment/)、[コンテナの設定](/ja/docs/tasks/)、[kubectlを用いたオブジェクトの管理](/ja/docs/concepts/overview/working-with-objects/object-management/)といったドキュメントを参照ください。 </del> <ins> 他の全てのKubernetesの設定と同様に、DaemonSetは`apiVersion`、`kind`と`metadata`フィールドが必須となります。設定ファイルの活用法に関する一般的な情報は、[ステートレスアプリケーションの稼働](/ja/docs/tasks/run-application/run-stateless-application-deployment/)、[kubectlを用いたオブジェクトの管理](/ja/docs/concepts/overview/working-with-objects/object-management/)といったドキュメントを参照ください。 </ins> DaemonSetオブジェクトの名前は、有効な [DNSサブドメイン名](/ja/docs/concepts/overview/working-with-objects/names#dns-subdomain-names)である必要があります。

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. --Updated Japanese translation for the file. Why is this needed There are several updates in and therefore this page is outdated. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja
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
Change:
<ins> apiVersion: apps/v1 kind: Deployment metadata: name: mongo labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: selector: matchLabels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend replicas: 1 template: metadata: labels: app.kubernetes.io/name: mongo app.kubernetes.io/component: backend spec: containers: - name: mongo image: mongo:4.2 args: - --bind_ip - 0.0.0.0 resources: requests: cpu: 100m memory: 100Mi ports: - containerPort: 27017 </ins>

Discussion:
In the section of There is no file with the specified URL, and the output of running this command is:
In PR the is deleted, which is used in the 'Creating MongoDB deployment and service' page. /kind bug
/triage accepted /retitle Example missing from Use Port Forwarding to Access Applications in a Cluster
/assign will add these yaml's
Fix it here
Change:
Kubernetes progressively rolls out changes to your application or its configuration, while monitoring application health to ensure it doesn't kill all your instances at the same time. If something goes wrong, Kubernetes will rollback the change for you. Take advantage of a growing ecosystem of deployment solutions. content_type: concept <del> weight: 30 </del> <ins> weight: 10 </ins> --- <!-- overview -->

Discussion:
This is an enhancement 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 Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. It is also OK to replace this page with a hand-written overview that achieves the same effect. Why is this needed ReplicationController is deprecated. Comments You can make this change by editing the attribute in the of pages inside . /language en /priority backlog /good-first-issue /kind cleanup
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 an enhancement Request <!-- See for guidance on writing an actionable issue description. --Change to list Deployment and ReplicaSet early (Deployment first), with ReplicationController at or near the end of the list. ReplicationController is deprecated. You can make this change by editing the attribute in the of pages inside . /priority backlog /good-first-issue /kind cleanup 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
Just the order of list needs to be changed to list Deployments and then ReplicaSet early and ReplicationController at the end in the , right?
(and to anyone else) you can make the minimal change you described, or you can consider further tidying. Either approach is valid; if you like, there is a spectrum of thoroughness in how you deal with this.
Oh, I've fixed the link to front matter; it should be to
Hey folks, I can take care of it if OK with that.
Sure you can go ahead!
Thanks! /assign
Change:
## Run and expose php-apache server <del> To demonstrate a HorizontalPodAutoscaler, you will first make a custom container image that uses the `php-apache` image from Docker Hub as its starting point. The `Dockerfile` is ready-made for you, and has the following content: ```dockerfile FROM php:5-apache COPY index.php /var/www/html/index.php RUN chmod a+rx index.php ``` This code defines a simple `index.php` page that performs some CPU intensive computations, in order to simulate load in your cluster. ```php <?php $x = 0.0001; for ($i = 0; $i <= 1000000; $i++) { $x += sqrt($x); } echo "OK!"; ?> ``` Once you have made that container image, start a Deployment that runs a container using the image you made, and expose it as a {{< glossary_tooltip term_id="service">}} </del> <ins> To demonstrate a HorizontalPodAutoscaler, you will first start a Deployment that runs a container using the `hpa-example` image, and expose it as a {{< glossary_tooltip term_id="service">}} </ins> using the following manifest: {{< codenew file="application/php-apache.yaml" >}}

Discussion:
If we are using as our custom image, why do the documentation starts by telling the user to build an image from Dockerfile provided and the code?
Page:
/retitle HorizontalPodAutoscaler walkthrough page recommends unnecessary container image build /kind bug /language en /triage accepted Thanks for reporting this.
I could take this up /assign
Change:
Edit the yaml files in `/_data/` for the Guides, Reference, Samples, or Support areas. <ins> You may have to exit and `jekyll clean` before restarting the `jekyll serve` to get changes to files in `/_data/` to show up. </ins> ### Add Images Put the new image in `/images/docs/` if it's for the documentation, and just `/images/` if it's for the website.

Discussion:
[X] Feature Request Problem: When upstream master removed an API that the docs tests check, all travis builds started failing. The immediate issue is fixed in two ways, with : changed the API checks that failed changed the upstream version from master to latest stable release This is an excellent interim solution, but we need to do a few more things to ensure that such breaks don't happen again. Proposed Solution: document for docs release meister that when release is cut, tests should be updated to run against the latest release versiondocument for docs release meister or shadow or other that we should check for any API changes that could break the tests. We can check the release notes manually for now, and devise an automated solution if the manual approach proves inadequate or someone wants to get clever. (Note that checking the API refdocs is not a reliable solution here. example: the 1.10 refdocs are wrong for exactly the offending API in the test break.) Page to Update:
Thank you for this--I'll take it on for my playbook update in
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
Change:
kind: Service metadata: name: my-service <ins> labels: app: MyApp </ins> spec: selector: app: MyApp ports: - protocol: TCP port: 80 <del> targetPort: 9376 </del>  No newline at end of file

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
/triage accepted
Change:
your backups using a well reviewed backup and encryption solution, and consider using full disk encryption where possible. <del> Kubernetes supports optional [encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) for information in the Kubernetes API. </del> <ins> Kubernetes supports optional [encryption at rest](/docs/tasks/administer-cluster/encrypt-data/) for information in the Kubernetes API. </ins> This lets you ensure that when Kubernetes stores data for objects (for example, `Secret` or `ConfigMap` objects), the API server writes an encrypted representation of the object. That encryption means that even someone who has access to etcd backup data is unable

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. --We have two pages with similar aims: We should ensure that the advice in the two documents is aligned, and also make sure that the two documents link to each other. Why is this needed It's a bad idea to document multiple ways to make sure that your cluster is secure, unless those are well aligned. Comments /sig security /sig docs /language en
Relevant to
Regarding this: We can use a reference section/note/what's next section in the end of stating: -
/triage accepted
Hey I would like to work on this.
/assign
Change:
Print the live configuration using `kubectl get`: ```shell <del> kubectl get -f http://k8s.io/docs/concepts/tools/kubectl/simple_deployment.yaml -o yaml </del> <ins> kubectl get -f http://k8s.io/docs/tutorials/object-management-kubectl/simple_deployment.yaml -o yaml </ins> ``` The output shows that the `kubectl.kubernetes.io/last-applied-configuration` annotation

Discussion:
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: 404 on Proposed Solution: Update location of Page to Update:
Change:
It is populated when adding `--record` to a `kubectl` command that may change an object. <ins> ## kubernetes.io/description {#description} Example: `kubernetes.io/description: "Description of K8s object."` Used on: All Objects This annotation is used for describing specific behaviour of given object. </ins> ## controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost} Example: `controller.kubernetes.io/pod-deletion-cost=10`

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: Kubernetes an annotation, , that is not registered or documented. Proposed Solution: Register and document this annotation. Page to Update: Also consider whether to mention that annotation in Additional Information: /sig auth /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
I would like to work on this.
/assign
Change:
<div class="layout" id="top"> <del> <main class="content katacoda-content"> <div class="row"> <div class="col-md-12"> <p> Um pod é a unidade de execução básica de um aplicativo Kubernetes. Cada pod representa uma parte de uma carga de trabalho em execução no cluster. <a href="/docs/concepts/workloads/pods/"> Saiba mais sobre pods</a>. </p> </div> </div> <br> <div class="katacoda"> <div class="katacoda__alert"> Para interagir com o Terminal, use a versão desktop/tablet </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/7" data-katacoda-color="326de6" data-katacoda-secondary="273d6d" data-katacoda-hideintro="false" data-katacoda-prompt="Terminal para treinamento do Kubernetes" style="height: 600px;"> </div> </div> <div class="row"> <div class="col-md-12"> <a class="btn btn-lg btn-success" href="/pt/docs/tutorials/kubernetes-basics/explore/explore-intro/" role="button">Continue para o Módulo 3<span class="btn__next">›</span></a> </div> </div> </del> <ins> <main class="content"> <div> <h2 class="katacoda-gone"> Conteúdo indisponível </h2> <p> O tutorial interativo de como implantar um aplicativo no seu cluster não está disponível. Para mais informações, veja o <a href="https://kubernetes.io/pt-br/blog/2023/02/14/kubernetes-katacoda-tutorials-stop-from-2023-03-31/"> anúncio de encerramento do Katacoda</a>. </p> </div> </ins> </main> </div>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug
Change:
{{- with $currentStage -}} <!-- Display feature state information  --> <del> <div class="my-2 feature-state-notice feature-{{ .stage }}" title="{{ printf "%s %s" (T "feature_state_feature_gate_tooltip") $feature_gate_name }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]</code> </div> </del> <ins> <div class="my-2 feature-state-notice feature-{{ .stage }}" title="{{ printf "%s %s" (T "feature_state_feature_gate_tooltip") $feature_gate_name }}"> <b>{{ T "feature_state" }}</b> <code>{{T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]</code> </div> </ins> {{- $featureGateFound = true -}} {{- end -}}

Discussion:
This is a Bug Report <!--Required Information--Problem: Documentation layout issue in page under IngressClass scope Namespaced section, see following screenshot: <img width="912" alt="image" src=""Proposed Solution: I would like to create a PR to fix it, the solution is to remove and outside of template Page to Update: Documentation layout issue in Ingress.
Change:
<del> ## `ResourceChangeDetectionStrategy`     {#kubelet-config-k8s-io-v1beta1-ResourceChangeDetectionStrategy} (Alias of `string`) **Appears in:** - [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) ResourceChangeDetectionStrategy denotes a mode in which internal managers (secret, configmap) are discovering object changes. ## `LoggingConfiguration`     {#LoggingConfiguration} </del> <ins> ## `MemoryReservation`     {#kubelet-config-k8s-io-v1beta1-MemoryReservation} </ins>

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: Visiting provides inaccurate default values for shutdownGracePeriod (30s rather than 0s) and shutdownGracePeriodCriticalPods (10s rather than 0s). Proposed Solution: Correct the documentation to match the actual default values. Page to Update:
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 would like to take up this ticket.
Change:
レビューを始める前に、以下のことを心に留めてください。 <del> - [CNCFの行動規範](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)を読み、いかなる時にも行動規範にしたがって行動するようにする。 </del> <ins> - [CNCFの行動規範](https://github.com/cncf/foundation/blob/main/code-of-conduct.md)を読み、いかなる時にも行動規範にしたがって行動するようにする。 </ins> - 礼儀正しく、思いやりを持ち、助け合う気持ちを持つ。 - 変更点だけでなく、PRのポジティブな側面についてもコメントする。 - 相手の気持ちに共感して、自分のレビューが相手にどのように受け取られるのかをよく意識する。 - 相手の善意を前提として、疑問点を明確にする質問をする。 <del> - 経験を積んだコントリビューターの場合、コンテンツに大幅な変更が必要な新規のコントリビューターとペアを組んで作業に取り組むことを考える。 </del> <ins> - 経験を積んだコントリビューターの場合、コンテンツに大幅な変更が必要な作業を行う新規のコントリビューターとペアを組んで取り組むことを考える。 </ins> ## レビューのプロセス <del> 一般に、コンテンツや文体に対するプルリクエストは、英語でレビューを行います。 </del> <ins> 一般に、コンテンツや文体に対するプルリクエストは、英語でレビューを行います。図1は、レビュープロセスについて手順の概要を示しています。 各ステップの詳細は次のとおりです。 **(訳注:SIG Docs jaでは、日本語でも対応しています。日本語の翻訳に対するレビューは、日本語でも構いません。ただし、プルリクエストの作成者や他のコントリビューターが必ずしも日本語を理解できるとは限りませんので、注意して発言してください。)** <!-- See https://github.com/kubernetes/website/issues/28808 for live-editor URL to this figure --> <!-- You can also cut/paste the mermaid code into the live editor at https://mermaid-js.github.io/mermaid-live-editor to play around with it --> {{< mermaid >}} flowchart LR subgraph fourth[レビューの開始] direction TB S[ ] -.- M[コメントを追加] --> N[変更の確認] N --> O[Commentを選択] end subgraph third[PRの選択] direction TB T[ ] -.- J[説明とコメントを読む]--> K[Netlifyプレビューで<br>変更点を表示] end A[オープン状態の<br>PR一覧を確認]--> B[オープン状態のPRを<br>ラベルで絞り込む] B --> third --> fourth classDef grey fill:#dddddd,stroke:#ffffff,stroke-width:px,color:#000000, font-size:15px; classDef white fill:#ffffff,stroke:#000,stroke-width:px,color:#000,font-weight:bold classDef spacewhite fill:#ffffff,stroke:#fff,stroke-width:0px,color:#000 class A,B,J,K,M,N,O grey class S,T spacewhite class third,fourth white {{</ mermaid >}} 図1. レビュープロセスの手順 </ins> 1.  [https://github.com/kubernetes/website/pulls](https://github.com/kubernetes/website/pulls)に移動します。Kubernetesのウェブサイトとドキュメントに対するopen状態のプルリクエスト一覧が表示されます。 2.  open状態のPRに、以下に示すラベルを1つ以上使って絞り込みます。 <del> - `cncf-cla: yes` (推奨): CLAにサインしていないコントリビューターが提出したPRはマージできません。詳しい情報は、[CLAの署名](/docs/contribute/new-content/overview/#sign-the-cla)を読んでください。 </del> <ins> - `cncf-cla: yes` (推奨): CLAにサインしていないコントリビューターが提出したPRはマージできません。詳しい情報は、[CLAの署名](/docs/contribute/new-content/#sign-the-cla)を読んでください。 </ins> - `language/en` (推奨): 英語のPRだけに絞り込みます。 - `size/<size>`: 特定の大きさのPRだけに絞り込みます。レビューを始めたばかりの人は、小さなPRから始めてください。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/architecture/garbage- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/architecture/garbage- is outdated. It contains important information for contributors. Comments /language ja /assign
/triage accepted
Change:
<div class="layout" id="top"> <del> <main class="content katacoda-content"> <br> <div class="katacoda"> <div class="katacoda__alert"> Para interagir com o Terminal, por favor, use a versão para desktop ou table. </div> <div class="katacoda__box" id="inline-terminal-1"  data-katacoda-id="kubernetes-bootcamp/4" data-katacoda-color="326de6" data-katacoda-secondary="273d6d" data-katacoda-hideintro="false" data-katacoda-prompt="Kubernetes Bootcamp Terminal" style="height: 600px;"> </div> </div> <div class="row"> <div class="col-md-12"> <a class="btn btn-lg btn-success" href="/pt/docs/tutorials/kubernetes-basics/expose/expose-intro/" role="button">Continue para o Módulo 4<span class="btn__next">›</span></a> </div> </div> </del> <ins> <main class="content"> <div> <h2 class="katacoda-gone"> Conteúdo indisponível </h2> <p> O tutorial interativo de como explorar seu aplicativo não está disponível. Para mais informações, veja o <a href="https://kubernetes.io/pt-br/blog/2023/02/14/kubernetes-katacoda-tutorials-stop-from-2023-03-31/"> anúncio de encerramento do Katacoda</a>. </p> </div> </ins> </main> </div>

Discussion:
The terminal to use the interactive tutorials is using Katacoda, however, it was purchased by O'Reilly and is outside the domain that the terminal is using to run.
Hi You can ask support queries in channels.
Page related to issue: /language pt
/retitle [pt-br] Remove the obsolete online interactive tutorial from the page
For anyone willing to assist on this, please refer to PR for information regarding the implementation of similar changes carried out on the main website (i.e. English pages).
/good-first-isssue
/triage accepted /assign
/retitle [pt-br] Obsolete online interactive tutorial in the Using Minikube to Create a Cluster page /kind bug