jiebi/CodeConvo huggingface dataset:
Change:
1. Download the latest release with the command: ```bash <del> curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert </del> <ins> curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert" </ins> ``` 1. Validate the binary (optional)

Discussion:
I was following the instructions on . When I download the kubectl convert plugin, it gives me this error. !
Hi The URL used by you is wrong. In your URL you put a backslash in two places one is after $ and the second after see below: Correct one is:
For me, there seems no backslashes in the command, ! but when I copy that and paste, the backslashes appear. ! (Copied in Windows 10 x64, Chrome 97.0.4692.71, pasted to the Oracle Virtualbox VM, Ubuntu 18.04 desktop x64, bundled Terminal app) In that page, replacing to might resolve the problem. ! (This one causes no problem.) /kind bug /triage accepted
Hi when I do copy and paste it, the backslash does not appear in the command.
Maybe automatically adds backslashes.. I am using , and I guess that is using too. ( Is this correct? ) And It seems that you are using other than , Is this correct? If these are correct, then I guess that replacing to will cause no problem on , , and so on.
Hi yes, I am using the bash, maybe it is with zsh. I tried this command and it is also working, so we can replace the command with
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Yup, I am using zsh as well
/assign
GitHub didn't allow me to assign the following users: championshuttler.

Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
Change:
cosign verify-blob "$BINARY" --signature "$BINARY".sig --certificate "$BINARY".cert ``` <ins> cosign v1.9.0 is required to be able to use the `--certificate` flag. Please use `--cert` for older versions of cosign. </ins> {{< note >}} To learn more about keyless signing, please refer to [Keyless Signatures](https://github.com/sigstore/cosign/blob/main/KEYLESS.md#keyless-signatures).

Discussion:
The right command line for usage should be: So with instead of the actual which is an unrecognized option, at least in version 1.6.0.
/retitle Wrong command in “Verify Signed Kubernetes Artifacts” task /language en
It appears that the cosign version has updated this parameter to --certificate But for compatibility with previous versions, both and can be used. So the document just uses the newer version of the command. related issue: related PR: code
Today, if you follow the instructions (and so you download 1.6.0), you get an error, so it might be useful to fix this anyway.
Perhaps, the version of needs to be indicated in the docs? For more advice.
Yes, maybe that would fix the problem as well.
I agree having the cosign version mentioned in the docs will help us to prevent such issues in the future.
/triage accepted
Page to update:
Can we also mention the note about cosign, something like this: if we are using cosign version v1.9.0+ we should use the parameter instead of the
/assign
Change:
4. Katacoda environment only: Type `30000`, and then click **Display Port**. {{< note >}} <del> The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. </del> <ins> The `dashboard` command enables the dashboard add-on and opens the proxy in the default web browser. You can create Kubernetes resources on the dashboard such as Deployment and Service. </ins> If you are running in an environment as root, see [Open Dashboard with URL](#open-dashboard-with-url). <del> To stop the proxy, run `Ctrl+C` to exit the process. The dashboard remains running. </del> <ins> By default, the dashboard is only accessible from within the internal Kubernetes virtual network. The `dashboard` command creates a temporary proxy to make the dashboard accessible from outside the Kubernetes virtual network. To stop the proxy, run `Ctrl+C` to exit the process. After the command exits, the dashboard remains running in Kubernetes cluster. You can run the `dashboard` command again to create another proxy to access the dashboard. </ins> {{< /note >}} ## Open Dashboard with URL

Discussion:
Nope, when you press Ctrl+C after running the dashboard stops working.
Thanks for the first issue here! By saying "when you press Ctrl+C after running minikube dashboard the dashboard stops working", do you mean the web browser cannot access the dashboard page after Ctrl+C? This is the expected behavior. After the proxy is stopped, the current web browser session stops working. But the dashboard server is still running in the background, you can open another proxy connection to access it again. I can try to improve the doc if the original sentence confuses new learners.
Hello, From a user perspective the dashboard is unusable after Ctrl+C and if you start it again it’s on a different port so it looks very mich like it’s stopped. The real question is why starting the dashboard should block the CLI like this. I’d say the behaviour is unnecessarily confusing for beginners and the documentation compounds this.
Let me improve the doc to clarify this. /triage accepted /kind feature
/assign
Change:
/docs/reference/glossary/maintainer/    /docs/reference/glossary/approver/ 301 <ins> /docs/reference/kubectl/kubectl-cmds/     /docs/reference/generated/kubectl/kubectl-commands/ 301! </ins> /docs/reference/kubectl/kubectl/kubectl_*.md    /docs/reference/generated/kubectl/kubectl-commands#:splat 301 /docs/reference/scheduling/profiles/    /docs/reference/scheduling/config/#profiles 301

Discussion:
A page just to provide a link another page? My be you are planning more links on this page. If not this page it self can point to target page.
Hi in this there is another link reference to kubectl commands refrence , so far i am understanding is that you want to replace reference Link for kubectl command to be in this ?
To fix this, edit  so that it redirects to /good-first-issue /language en
/triage accepted
/retitle No page content for
/assign
hi could you help to review the PR? Thanks
~reviewers~ approvers for the English localization (who are mainly volunteers) pick up that task on a . I can take a look though.
/remove-good-first-issue
/assign
I the redirect () but it doesn't seem to be working on the deploy preview or locally. Any advice would be appreciated:
Change:
<ins> apiVersion: v1 kind: Pod metadata: name: envvars-multiple-secrets spec: containers: - name: envars-test-container image: nginx env: - name: BACKEND_USERNAME valueFrom: secretKeyRef: name: backend-user key: backend-username - name: DB_USERNAME valueFrom: secretKeyRef: name: db-user key: db-username </ins>

Discussion:
Translate into Japanese. This page has not been translated. /language ja /assign
/triage accepted
Change:
- Put object descriptions in annotations, to allow better introspection. <ins> {{< note >}} There is a breaking change introduced in the [YAML 1.2](https://yaml.org/spec/1.2.0/#id2602744) boolean values specification with respect to [YAML 1.1](https://yaml.org/spec/1.1/#id864510). This is a known [issue](https://github.com/kubernetes/kubernetes/issues/34146) in Kubernetes. YAML 1.2 only recognizes **true** and **false** as valid booleans, while YAML 1.1 also accepts **yes**, **no**, **on**, and  **off** as booleans. However, Kubernetes uses YAML [parsers](https://github.com/kubernetes/kubernetes/issues/34146#issuecomment-252692024) that are mostly compatible with YAML 1.1, which means that using **yes** or **no** instead of **true** or **false** in a YAML manifest may cause unexpected errors or behaviors. To avoid this issue, it is recommended to always use **true** or **false** for boolean values in YAML manifests, and to quote any strings that may be confused with booleans, such as **"yes"** or **"no"**. Besides booleans, there are additional specifications changes between YAML versions. Please refer to the [YAML Specification Changes](https://spec.yaml.io/main/spec/1.2.2/ext/changes) documentation for a comprehensive list. {{< /note >}} </ins> ## "Naked" Pods versus ReplicaSets, Deployments, and Jobs {#naked-pods-vs-replicasets-deployments-and-jobs} - Don't use naked Pods (that is, Pods not bound to a [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) or

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 describes a bug in Kubernetes where YAML 1.2 documents are not parsed (Kubernetes does not have good support for YAML 1.1), but then also Kubernetes does incorrectly parse completely valid YAML 1.1 the way that the specification defines. Why is this needed The bug makes it hard for some people, using conformant libraries, to make YAML documents that Kubernetes accepts. We should document the bug so that readers are aware of the shortcomings here. Comments /wg api-expression /language en /priority backlog
/triage accepted
i can help you because I'm new to it so if i can tag along i will be able to learn a lot
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]:
/remove-lifecycle stale
would you add this as a warning note in ?
/assign
Change:
Creation and deletion of namespaces are described in the [Admin Guide documentation for namespaces](/docs/admin/namespaces). <ins> {{< note >}} Avoid creating namespace with prefix `kube-`, since it is reserved for Kubernetes system namespaces. {{< /note >}} </ins> ### Viewing namespaces You can list the current namespaces in a cluster using:

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update to document that namespaces starting are reserved. Why is this needed According to all namespaces with names that start with are reserved. Comments /kind feature /language en /sig architecture /good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update to document that namespaces starting are reserved. According to all namespaces with names that start with are reserved. /kind feature /language en /sig architecture /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign me
GitHub didn't allow me to assign the following users: me. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign me </details
/assign
Change:
<hr> <del> - **resource** (string), 必选 </del> <ins> - **resource** (string)，必选 </ins> <!-- Required: resource to select --> 必选：选择的资源

Discussion:
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
/retitle Punctuation errors on /remove-kind feature /kind bug
Change:
* Configure `kubectl` to communicate with your Kubernetes API server. For instructions, see the documentation for your cloud provider. ## {{% heading "objectives" %}} * Run five instances of a Hello World application. * Create a Service object that exposes an external IP address. * Use the Service object to access the running application. <!-- lessoncontent --> ## Creating a service for an application running in five pods

Discussion:
This is a Bug Report There are some commands in the tutorial that are missing code formatting. This is a request to update those commands and remove any extra lines in the page. <!--Required Information--Problem: The tutorial has commands that are not formatted as code. For example, kubectl get deployments hello-world Add code formatting: Proposed Solution: Identify the commands that are missing code formatting. Add the code formatting to the commands. Clean up any extra lines in the page. Page to Update: This is a good issue for a first time contributor. If you need more information, feel free to ask in this issue. It is a good idea to build your changes locally.
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted /language en Thanks - another good spot
Is this PR currently being worked on?
it seems already formatted, right?
I don't see any issues with the page as well, and it looks like it was last modified July 27, 2020 at 4:18. Are we missing something?
Let me look. I'd like a first time contributor to work on this issue.
The page renders correctly, however, it would be helpful to clean up the formatting of the page such as extra lines and spaces. Also, the page should use code blocks around any commands (instead of indentation). Let me know if you need more information. Thanks!
i'm a first timer in kubernetes. But i saw nothing wrong in formatting code nor indentation. Only i think there is missing some instruction in creating apps. Should be better to follow Just my 2cent. wdyt?
/assign
Change:
the [security context](/docs/tasks/configure-pod-container/security-context/) of the container spec. This is useful for containers that want to use operating system administrative capabilities such as manipulating the network stack or accessing hardware devices. Processes within a privileged container get almost the same privileges that are available to processes outside a container. --> <del> ## 容器的特权模式     {#rivileged-mode-for-containers} </del> <ins> ## 容器的特权模式     {#privileged-mode-for-containers} </ins> Pod 中的任何容器都可以使用容器规约中的 [安全性上下文](/zh/docs/tasks/configure-pod-container/security-context/)中的

Discussion:
Hi, the header url of Privileged mode for containers in Chinese version doc misses a . Best regards.
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
/kind bug /language zh
/assign /retitle [zh] Wrong custom heading ID in zh/docs/concepts/workloads/pods
Change:
* [Node Metrics Data](/docs/reference/instrumentation/node-metrics). <del> * [CRI Pod & Container Metrics](/docs/reference/instrumentation/cri-pod-container-metrics). </del>  No newline at end of file <ins> * [CRI Pod & Container Metrics](/docs/reference/instrumentation/cri-pod-container-metrics). </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: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Proposed Solution: Add more links into (look at the left nav to see which ones they are) Page to Update: /language en /priority backlog /good-first-issue /triage accepted :information_source: have you already worked on an issue? Please save this for a contributor who has not.
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: does not link in the page content to every item that we can find (on a desktop browser) in the left-hand navigation for that section. Add more links into (look at the left nav to see which ones they are) /good-first-issue /triage accepted 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
I want to work on this. /assign
Pr to fix this issue
Change:
<!-- Now create the secrets using the file: --> <del> 现在使用文件创建 secrets： </del> <ins> 现在使用文件创建 Secrets： </ins> ```shell kubectl apply -f nginxsecrets.yaml

Discussion:
Nginx https 404
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
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
<ins> --- title: "Kubeadm" weight: 10 no_list: true content_type: concept card: name: reference weight: 40 --- <img src="https://raw.githubusercontent.com/kubernetes/kubeadm/master/logos/stacked/color/kubeadm-stacked-color.png" align="right" width="150px">kubeadmは、`kubeadm init`や`kubeadm join`などのコマンドを提供するツールで、Kubernetesクラスターを構築する上でのベストプラクティスを反映した「近道」を提供するものとして開発されました。 kubeadmは実用最小限のクラスターをセットアップするための処理を実行します。設計上、kubeadmはブートストラップのみを行い、マシンのプロビジョニングは行いません。同様に、Kubernetesダッシュボード、モニタリングソリューション、クラウド向けのアドオンなど、あれば便利でもなくても支障のない各種アドオンのインストールも範囲外です。 その代わりに、高度な特定用途向けのツールはkubeadmをベースに構築されることが期待されています。理想的には、すべてのデプロイのベースとしてkubeadmを使用することで、適合テストに通るクラスターを簡単に作れるようになります。 ## インストール方法 kubeadmをインストールするには、[インストールガイド](/ja/docs/setup/production-environment/tools/kubeadm/install-kubeadm)を参照してください。 ## {{% heading "whatsnext" %}} * [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init)を使用して、Kubernetesのコントロールプレーンノードをブートストラップする * [kubeadm join](/docs/reference/setup-tools/kubeadm/kubeadm-join)を使用して、Kubernetesのワーカーノードをブートストラップし、クラスターに参加させる * [kubeadm upgrade](/docs/reference/setup-tools/kubeadm/kubeadm-upgrade)で、Kubernetesクラスターを新しいバージョンにアップグレードする * [kubeadm config](/docs/reference/setup-tools/kubeadm/kubeadm-config)を使用して、kubeadm v1.7.x以前で初期化されたクラスターを、`kubeadm upgrade`を利用できるように設定する * [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token)で、`kubeadm join`のためのトークンを管理する * [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset)を使用して、`kubeadm init`または`kubeadm join`でホストに行われた変更を元に戻す * [kubeadm version](/docs/reference/setup-tools/kubeadm/kubeadm-version)で、kubeadmのバージョンを表示する * [kubeadm alpha](/docs/reference/setup-tools/kubeadm/kubeadm-alpha)で、コミュニティからのフィードバックを集めるために有効にされた各種機能を試用する </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
Change:
cat ./kubectl-whoami ``` 次の例では、下記の内容を含んだ`kubectl-whoami`が既に作成済であることを前提としています。 <del> The next few examples assume that you already made `kubectl-whoami` have the following contents: </del> ```shell #!/bin/bash

Discussion:
This is a Bug Report <!--Required Information--Problem: There are both a raw untranslated sentence and its translated sentence. Proposed Solution: remove this raw sentence Page to Update:
/assign
/triage accepted
Change:
locality, inter-workload interference, and so on. --> 在做调度决定时需要考虑的因素包括：单独和整体的资源请求、硬件/软件/策略限制、 <del> 亲和以及反亲和要求、数据局域性、负载间的干扰等等。 </del> <ins> 亲和以及反亲和要求、数据局部性、负载间的干扰等等。 </ins> <!-- ## Scheduling with kube-scheduler {#kube-scheduler-implementation}

Discussion:
originalFactors that need to be taken into account for scheduling decisions include individual and collective resource requirements, hardware / software / policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference, and so on. translation// "data locality" should translate to "", not "".
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 zh
translates it as "". Generally speaking, in computer terminology, we translate this as "". Does this page need to be changed Request for advice
“”“”“”“”
PR
Change:
<ins> apiVersion: v1 kind: Service metadata: name: my-service labels: app: MyApp spec: ipFamilyPolicy: PreferDualStack ipFamilies: - IPv6 - IPv4 selector: app: MyApp ports: - protocol: TCP port: 80 </ins>

Discussion:
This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign
/triage accepted