jiebi/CodeConvo huggingface dataset:
Code change:
## {{% heading "prerequisites" %}} <del> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. </del> <ins> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v{{< skew latestVersion >}} client can communicate with v{{< skew prevMinorVersion >}}, v{{< skew latestVersion >}}, and v{{< skew nextMinorVersion >}} control planes. </ins> Using the latest version of kubectl helps avoid unforeseen issues. ## Install kubectl on Linux

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: There are a couple of issues with existing wording: “master” should be read “control plane” versions aren't current. Proposed Solution: Replace that text with: Page to Update: Additional Information: /language en /kind bug /wg naming
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
/help If you're picking this up and want to be extra neat, replace those specific version numbers with shortcodes that automatically fill in based on the current release; for example:
This request has been marked as needing help from a contributor. 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 : /help </details
/assign
Code change:
title: Picking the Right Solution --- <del> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to rack of </del> <ins> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to a rack of </ins> bare metal servers. The effort required to set up a cluster varies from running a single command to crafting your own customized cluster. Use this guide to choose a solution that fits your needs.

Related discussion:
text: <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:
Code change:
} body.cid-community #videos { <del> width: 100vw; </del> <ins> width: 100%; </ins> max-width: initial; padding: 0.5em 5vw 5% 5vw; /* fallback in case calc() fails */ background-color: #eeeeee;

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: Proposed Solution: Page to Update: /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
During my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.
/area web-development
I tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.
I see, In that case I'll try to find anymore pages that might be having the same issue.
Similar issue is present in case study
Code change:
<div class="row"> <div class="col-md-8"> <p> <del> For your first Deployment, you'll use a Node.js application packaged in a Docker container. (If you didn't already try creating a Node.js application and deploying it using a container, you can do that first by following the instructions from the <a href="/docs/tutorials/hello-minikube/">Hello Minikube tutorial</a>). </del> <ins> For your first Deployment, you'll use a hello-node application packaged in a Docker container that uses NGINX to echo back all the requests. (If you didn't already try creating a hello-node application and deploying it using a container, you can do that first by following the instructions from the <a href="/docs/tutorials/hello-minikube/">Hello Minikube tutorial</a>). </ins> <p> <p>Now that you know what Deployments are, let's go to the online tutorial and deploy our first app!</p>

Related discussion:
text: The below sentence is there towards the end of this page: (If you didn't already try creating a application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial). But the "Hello Minkube" tutorial link has nothing about creating any application or deploying it.
This is indeed a documentation bug. The v1.4 echoserver uses NGINX without Good spot, /kind bug /language en /triage accepted /priority backlog
/assign
Code change:
{{% capture whatsnext %}} <del> - [Learn about how to use `kubectl` for application introspection and debugging.](/docs/tasks/debug-application-cluster/debug-application-introspection/) - [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/) </del> <ins> - Learn about [how to use `kubectl` for application introspection and debugging](/docs/tasks/debug-application-cluster/debug-application-introspection/). - See [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/). </ins> {{% /capture %}}

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 143, the backquote is placed at wrong position. The flag works with any operation that accepts the flag such as: Line 456~457, it needs to change hugo code for the consistency with other documents Proposed Solution: Line 143: The flag works with any operation that accepts the flag such as: etc. Line 456~457: Learn about . See . 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:
{{% /tab %}} {{% tab name="URL copy and paste" %}} <del> If you don't want minikube to open a web browser for you, run the dashboard command with the </del> <ins> If you don't want minikube to open a web browser for you, run the `dashboard` subcommand with the </ins> `--url` flag. `minikube` outputs a URL that you can open in the browser you prefer. Open a **new** terminal, and run:

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: The page has a broken link / anchor named "Open Dashboard with URL" in the Dashboard section. The markdown anchor named #open-dashboard-with-url cannot be resolved. Proposed Solution: This link / anchor needs to be fixed, however I am not able to understand what section it referred to in the first place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /sig docs
Page related to the issue:
I think the URL should be replaced with
Let's wait for the opinions of other members regarding the same.
I would to like to work on this issue is the triage gets accepted.
Thanks. I checked further. Please check . Here you will find the section for the "Open Dashboard with URL". It seems this section was removed in later versions of this page, but the anchor/link was not removed.
The anchor for "Open Dashboard with URL," , is now obsolete as we've integrated this content into tab layout (Launch a browser, URL copy and paste) on the.
Pull request has been submitted quite some time ago to handle this issue, and it's awaiting review and approval for merging.
Indeed. Once is approved, it will address this issue. I do not see anyone actively working on this PR since many days. has volunteered to help. please take a look at There are some suggestions from in the PR already.
/triage accepted
Code change:
{{% /capture %}} <ins> ## インストールの確認 ハイパーバイザーとMinikube両方のインストール成功を確認するため、以下のコマンドをローカルKubernetesクラスターを起動するために実行してください: {{< note >}} `minikube start`で`--vm-driver`の設定をするため、次の`<driver_name>`の部分では、インストールしたハイパーバイザーの名前を小文字で入力してください。`--vm-driver`値のすべてのリストは、[specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver)で確認できます。 {{< /note >}} ```shell minikube start --vm-driver=<driver_name> ``` `minikube start`が完了した場合、次のコマンドを実行してクラスターの状態を確認します。 ```shell minikube status ``` クラスターが起動していると、`minikube status`の出力はこのようになります。 ``` host: Running kubelet: Running apiserver: Running kubeconfig: Configured ``` 選択したハイパーバイザーでMinikubeが動作しているか確認した後は、そのままMinikubeを使い続けることもできます。また、クラスターを停止することもできます。クラスターを停止するためには、次を実行してください。 ```shell minikube stop ``` </ins> ## ローカル状態のクリーンアップ {#cleanup-local-state} もし以前に　Minikubeをインストールしていたら、以下のコマンドを実行します。

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 Update tasks/tools/install- to follow v1.17 of the original (Englist) text. Why is this needed content/ja/docs/tasks/tools/install- is outdated. Comments /language ja /good-first-issue File to update Original https://v1- diff between translated and v1.17 Note Currently, we use branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
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 tasks/tools/install- to follow v1.17 of the original (Englist) text. content/ja/docs/tasks/tools/install- is outdated. /language ja /good-first-issue Currently, we use branch. Please open a PR targeting the branch. 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
/close
Closing this issue. <detailsIn response to : /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
Code change:
<ins> --- title: Node Affinityを利用してPodをノードに割り当てる min-kubernetes-server-version: v1.10 content_type: task weight: 120 --- <!-- overview --> このページでは、Node Affinityを利用して、PodをKubernetesクラスター内の特定のノードに割り当てる方法を説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- steps --> ## ノードにラベルを追加する 1. クラスター内のノードを一覧表示して、ラベルを確認します。 ```shell kubectl get nodes --show-labels ``` 出力は次のようになります。 ```shell NAME      STATUS    ROLES    AGE     VERSION        LABELS worker0   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker0 worker1   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker1 worker2   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker2 ``` 1. ノードを選択して、ラベルを追加します。 ```shell kubectl label nodes <your-node-name> disktype=ssd ``` ここで、`<your-node-name>`は選択したノードの名前で置換します。 1. 選択したノードに`disktype=ssd`ラベルがあることを確認します。 ```shell kubectl get nodes --show-labels ``` 出力は次のようになります。 ``` NAME      STATUS    ROLES    AGE     VERSION        LABELS worker0   Ready     <none>   1d      v1.13.0        ...,disktype=ssd,kubernetes.io/hostname=worker0 worker1   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker1 worker2   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker2 ``` この出力を見ると、`worker0`ノードに`disktype=ssd`というラベルが追加されたことがわかります。 ## required node affinityを使用してPodをスケジューリングする 以下に示すマニフェストには、`requiredDuringSchedulingIgnoredDuringExecution`に`disktype: ssd`というnode affinityを使用したPodが書かれています。このように書くと、Podは`disktype=ssd`というラベルを持つノードにだけスケジューリングされるようになります。 {{< codenew file="pods/pod-nginx-required-affinity.yaml" >}} 1. マニフェストを適用して、選択したノード上にスケジューリングされるPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/pod-nginx-required-affinity.yaml ``` 1. Podが選択したノード上で実行されていることを確認します。 ```shell kubectl get pods --output=wide ``` 出力は次のようになります。 ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` ## preferred node affinityを使用してPodをスケジューリングする 以下に示すマニフェストには、`preferredDuringSchedulingIgnoredDuringExecution`に`disktype: ssd`というnode affinityを使用したPodが書かれています。このように書くと、Podは`disktype=ssd`というラベルを持つノードに優先的にスケジューリングされるようになります。 {{< codenew file="pods/pod-nginx-preferred-affinity.yaml" >}} 1. マニフェストを適用して、選択したノード上にスケジューリングされるPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/pod-nginx-preferred-affinity.yaml ``` 1. Podが選択したノード上で実行されていることを確認します。 ```shell kubectl get pods --output=wide ``` 出力は次のようになります。 ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` ## {{% heading "whatsnext" %}} [Node Affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)についてさらに学ぶ。 </ins>

Related discussion:
text: 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
Code change:
## {{% heading "prerequisites" %}} <del> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. </del> <ins> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v{{< skew latestVersion >}} client can communicate with v{{< skew prevMinorVersion >}}, v{{< skew latestVersion >}}, and v{{< skew nextMinorVersion >}} control planes. </ins> Using the latest version of kubectl helps avoid unforeseen issues. ## Install kubectl on Windows

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: There are a couple of issues with existing wording: “master” should be read “control plane” versions aren't current. Proposed Solution: Replace that text with: Page to Update: Additional Information: /language en /kind bug /wg naming
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
/help If you're picking this up and want to be extra neat, replace those specific version numbers with shortcodes that automatically fill in based on the current release; for example:
This request has been marked as needing help from a contributor. 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 : /help </details
/assign
Code change:
RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)" ARCH="amd64" cd $DOWNLOAD_DIR <del> sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </del> <ins> sudo curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </ins> sudo chmod +x {kubeadm,kubelet,kubectl} RELEASE_VERSION="v0.4.0"

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: 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.
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: k8s.gcr.io/busybox command: [ "/bin/sh", "-c", "env" ] env: - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: name: special-config key: special.how - name: LOG_LEVEL valueFrom: configMapKeyRef: name: env-config key: log_level restartPolicy: Never </ins>

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 Translate tasks/configure-pod-container/configure-pod-configmap/ into Japanese. Why is this needed This page has not been translated. Comments /language ja
/assign
/close
Closing this issue. <detailsIn response to : /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
Code change:
401: Unauthorized <del> 404: Not Found (if the `CheckpointContainer` feature gate is disabled) </del> <ins> 404: Not Found (if the `ContainerCheckpoint` feature gate is disabled) </ins> 404: Not Found (if the specified `namespace`, `pod` or `container` cannot be found)

Related discussion:
text: Feature Gate ChecpointContainer is unrecognized by kubelet. I've tried to set up a new 1.25 cluster with kubeadm with kubelet config And it fails with I've also tried to set up another cluster without this feature gate and enable it after, and it goes the same. Kubelet is started and checkpoint api is accessible. To reproduce try to install a new cluster with kubeadm v1.25.0 and use next kubelet config Or try to enable this feature gate on already installed 1.25.0 cluster No response <details</details<detailsBare Metal </details<details</details<detailskubeadm 1.25.0 </details<detailscontainerd </details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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 feature gate name is according to
/sig node
/kind documentation
doesn't list a feature gate for kubelets. has a feature gate named . I'm guessing that this is a docs bug and is incorrect (possibly other docs pages too).
Thank you Yep, using as feature gate name resolves the issue. So this is a doc bug.
/retitle Feature gate misnamed in docs
/transfer website
This issue is now and should fix it. /language en /triage accepted
/sig docs
/priority backlog
Code change:
<!--more--> <del> kubeadmを使用して、コントロールプレーンとワーカーノード{{< glossary_tooltip text="ワーカーノード" term_id="node" >}}コンポーネントの両方をインストールできます。 </del> <ins> kubeadmを使用して、コントロールプレーンと{{< glossary_tooltip text="ワーカーノード" term_id="node" >}}コンポーネントの両方をインストールできます。 </ins>

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: There is typo in Following is the text with a typo. kubeadm Proposed Solution: fix "" to "" Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Page link for reported issue: Markdown of glossary entry reported to have issue: /language ja
/area localization
/assign
/triage accepted
Code change:
The list of phases can be obtained with the <code>kubeadm init --help</code> command. The flag &quot;--skip-phases&quot; takes precedence over this field.</p> --> <del> <p><code>skipPhases</code> 是命令执行过程中药略过的阶段（Phases）。 </del> <ins> <p><code>skipPhases</code> 是命令执行过程中要略过的阶段（Phases）。 </ins> 通过执行命令 <code>kubeadm init --help</code> 可以获得阶段的列表。 参数标志 &quot;--skip-phases&quot; 优先于此字段的设置。</p> </td>

Related discussion:
text: skipPhases Phases skipPhases Phases
/triage accepted /kind bug PRs welcomed.
/language zh
/assign