jiebi/CodeConvo huggingface dataset:
Change:
log retrievals), and can accept and serve those resources in different representations for convenience or efficiency. <del> Kubernetes supports efficient change notifications on resources via *watches*. </del> <ins> Kubernetes supports efficient change notifications on resources via _watches_: {{< glossary_definition prepend="in the Kubernetes API, watch is" term_id="watch" length="short" >}} </ins> Kubernetes also provides consistent list operations so that API clients can effectively cache, track, and synchronize the state of resources.

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 the to include an explanation of “watch”. Why is this needed The watch verb (and actually watchcollection as well) is K8s-specific jargon. We should help readers understand it. Comments Extra credit for also using the new term in existing pages, using a . /kind feature /wg api-expression
/assign
/priority backlog /triage accepted
Hi PR: for this issue. PTAL
I'm happy for any reviewer (for English) to take a look there.
Change:
<ins> ## `LoggingConfiguration`     {#LoggingConfiguration} **Appears in:** - [KubeletConfiguration](#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) LoggingConfiguration contains logging options Refer [Logs Options](https://github.com/kubernetes/component-base/blob/master/logs/options.go) for more information. <table class="table"> <thead><tr><th width="30%">Field</th><th>Description</th></tr></thead> <tbody> <tr><td><code>format</code> <B>[Required]</B><br/> <code>string</code> </td> <td> Format Flag specifies the structure of log messages. default value of format is `text`</td> </tr> <tr><td><code>sanitization</code> <B>[Required]</B><br/> <code>bool</code> </td> <td> [Experimental] When enabled prevents logging of fields tagged as sensitive (passwords, keys, tokens). Runtime log sanitization may introduce significant computation overhead and therefore should not be enabled in production.`)</td> </tr> </tbody> </table> </ins> ## `KubeletConfiguration`     {#kubelet-config-k8s-io-v1beta1-KubeletConfiguration}

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:
| `MemoryPressure` | `True` 表示节点存在内存压力，即节点内存可用量低，否则为 `False` | | `PIDPressure` | `True` 表示节点存在进程压力，即节点上进程过多；否则为 `False` | | `NetworkUnavailable` | `True` 表示节点网络配置不正确；否则为 `False` | <ins> {{< /table >}} </ins> <!-- If you use command-line tools to print details of a cordoned Node, the Condition includes

Discussion:
The Chinese version of the chapter introducing the concept of misses the explanation of the info field compared to the English version. Please check it.
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
this is fixed here
Change:
* [Running ZooKeeper, A CP Distributed System](/docs/tutorials/stateful-application/zookeeper/) <del> ## Clusters * [AppArmor](/docs/tutorials/clusters/apparmor/) * [seccomp](/docs/tutorials/clusters/seccomp/) </del> ## Services * [Using Source IP](/docs/tutorials/services/source-ip/)

Discussion:
This is a Feature Request What would you like to be Post-merge of , move the tutorials under into Merge clusters section into security section here: Why is this needed Issue description is a slight modification from original request in the comment Comments /hold for /cc /sig docs security
this might be a good first issue for new contributors in sig-security-docs /triage accepted
Hi, I would like to work on this issue. /assign
/kind cleanup
Hi , I a query: moving the tutorials from the cluster sub-directory into the security sub-directory, the cluster sub-directory will only have its file so do I need to do something regarding it ( file)? Thanks
Whenever you are free can you please help me with the above mentioned query. Thanks
Change:
`cluster-info`    | `kubectl cluster-info [flags]` | Display endpoint information about the master and services in the cluster. `completion`    | `kubectl completion SHELL [options]` | Output shell completion code for the specified shell (bash or zsh). `config`        | `kubectl config SUBCOMMAND [flags]` | Modifies kubeconfig files. See the individual subcommands for details. <del> --> `apply`            | `kubectl apply -f FILENAME [flags]`| 从文件或 stdin 对资源应用配置更改。 `attach`        | `kubectl attach POD -c CONTAINER [-i] [-t] [flags]` | 挂接到正在运行的容器，查看输出流或与容器（stdin）交互。 `auth`    | `kubectl auth [flags] [options]` | 检查授权。 `autoscale`    | <code>kubectl autoscale (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] [flags]</code> | 自动扩缩由副本控制器管理的一组 pod。 `certificate`    | `kubectl certificate SUBCOMMAND [options]` | 修改证书资源。 `cluster-info`    | `kubectl cluster-info [flags]` | 显示有关集群中主服务器和服务的端口信息。 `completion`    | `kubectl completion SHELL [options]` | 为指定的 Shell（Bash 或 Zsh）输出 Shell 补齐代码。 `config`        | `kubectl config SUBCOMMAND [flags]` | 修改 kubeconfig 文件。有关详细信息，请参阅各个子命令。 <!-- </del> `convert`    | `kubectl convert -f FILENAME [options]` | Convert config files between different API versions. Both YAML and JSON formats are accepted. Note - requires `kubectl-convert` plugin to be installed. `cordon`    | `kubectl cordon NODE [options]` | Mark node as unschedulable. `cp`    | `kubectl cp <file-spec-src> <file-spec-dest> [options]` | Copy files and directories to and from containers.

Discussion:
web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted
Change:
response to a successful request is a hello message: ```none <del> Hello Kubernetes! </del> <ins> Hello, world! Version: 2.0.0 Hostname: hello-world-cdd4458f4-m47c8 </ins> ``` ## Using a service configuration file

Discussion:
After running the kubectl apply command at , "kubectl get all" shows it is having "ImagePullBackOff" error When I do a describe it says the image is too old and need to be updated According to this link , the image was created back in 2016. Can we either update all the sample images to use manifest version 2 or find another image that works out of the box?
Related issue:
We shoudl fix this i think. sftim Any idea how we could resolve to help with tutorial working again?
Sample yaml reported in the issue: /language en
It seems that the image may have been removed by Google. We can either update the sample with image's new location (will need some searching), similar to what we’ve done for other tutorials (example ), or find a suitable alternative image to use.
I'd love to help out if appropriate, it appears to be a good first issue but I am not sure.
Would be good to fix this issue with the tutorial. /priority backlog /triage accepted
/kind bug
Change:
Used on: Node <del> Kubernetes automatically enables the `ServiceNodeExclusion` feature gate on the clusters it creates. With this feature gate enabled on a cluster, you can add labels to particular worker nodes to exclude them from the list of backend servers. </del> <ins> You can add labels to particular worker nodes to exclude them from the list of backend servers used by external load balancers. </ins> The following command can be used to exclude a worker node from the list of backend servers in a backend set:

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: mentions a feature gate; however, Kubernetes v1.23 onwards don't have such a feature gate. This is in connection with a label, . Proposed Solution: Drop the mention of the feature gate. Reword the description of that label accordingly. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /kind bug /priority backlog
/triage accepted
I would to like to work on this issue. /assign
/sig docs
The issue is fixed .
Change:
``` <!-- <del> Use `CTRL-C` to terminate to kubectl. </del> <ins> Use `CTRL-C` to terminate kubectl. </ins> You cannot drain the third node because evicting `zk-2` would violate `zk-budget`. However, the node will remain cordoned.

Discussion:
Numbers in the following list may be not up to date. Please run again before working on each of them.
/language zh /triage accepted /help
This request has been marked as needing help from a contributor. 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 : /language zh /triage accepted /help 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:
version: "v1.9" githubbranch: "v1.9.0" docsbranch: "release-1.9" <del> url: https://kubernetes.io/docs/home/ </del> <ins> url: https://kubernetes.io </ins> - fullversion: "v1.8.4" version: "v1.8" githubbranch: "v1.8.4" docsbranch: "release-1.8" <del> url: https://v1-8.docs.kubernetes.io/docs/home/ </del> <ins> url: https://v1-8.docs.kubernetes.io </ins> - fullversion: "v1.7.6" version: "v1.7" githubbranch: "v1.7.6" docsbranch: "release-1.7" <del> url: https://v1-7.docs.kubernetes.io/docs/home/ </del> <ins> url: https://v1-7.docs.kubernetes.io </ins> - fullversion: "v1.6.8" version: "v1.6" githubbranch: "v1.6.8" docsbranch: "release-1.6" <del> url: https://v1-6.docs.kubernetes.io/docs/home/ </del> <ins> url: https://v1-6.docs.kubernetes.io </ins> - fullversion: "v1.5.7" version: "v1.5" githubbranch: "v1.5.7" docsbranch: "release-1.5" <del> url: https://v1-5.docs.kubernetes.io/docs/ </del> <ins> url: https://v1-5.docs.kubernetes.io </ins> deprecated: false currentUrl: https://kubernetes.io/docs/home/ nextUrl: http://kubernetes-io-vnext-staging.netlify.com/

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] --- [x] Feature Request [ ] Bug Report Problem: When switching to a different version of the docs, I get redirected to the root of the doc tree. Proposed Solution: Would be nice to redirect users to an equivalent page in the previous version of docs. Easy way to get started would be to just support pages that haven't moved or been refactored. Could get fancier after that.
Also related (found while I was reproducing this), the drop-down mechanism that allows version changing doesn't render correctly on safari (mobile or laptop) so that you can't choose the older versions, and the same happens in Chrome (IOS) - you see part of 1.8, but the rest of the list is cut off. See embedded screenshot (from Chrome IOS) !
I've attempted to implement a solution to this in . This part works by default This part requires setting data on the page as to where to send the person.
This issue is still present on the current version of the website.
not sure if we should reopen this issue or file a new one as a bug report but this no longer works. from what I can tell during the migration to hugo the header file was removed
Change:
<!-- <p><em>Scaling</em> is accomplished by changing the number of replicas in a Deployment</p> <del> <p> <b> NOTE </b> If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section </a>, you may need to start from <a href="/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">creating a cluster</a> as the services may have been deleted </p> </del> <ins> <p>If you are trying this after <a href="/docs/tutorials/kubernetes-basics/expose/expose-intro/">the previous section</a>, you may have deleted the Service exposing the Deployment. In that case, please expose the Deployment again using the following command:</p><p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080</b></code></p> </ins> --> <p><b>扩缩</b> 是通过改变 Deployment 中的副本数量来实现的。</p> <del> <p> <b> 注意 </b> 如果你是在 <a href="/zh-cn/docs/tutorials/kubernetes-basics/expose/expose-intro/">上一节</a> 之后尝试此操作, 你可能需要从 <a href="/zh-cn/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/">创建一个集群</a> 开始， 因为 Service 可能已被删除。</p> </del> <ins> {{< note >}} <p>如果你是在 <a href="/zh-cn/docs/tutorials/kubernetes-basics/expose/expose-intro/">上一节</a> 之后尝试此操作, 那么你可能已经删除了公开 Deployment 的 Service。在这种情况下，请使用以下命令再次公开 Deployment：</p> <p><code><b>kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080</b></code></p> {{< /note >}} </ins> </div> <div class="col-md-4"> <div class="content__box content__box_lined">

Discussion:
Chinese document display in raw html format. <img width="868" alt="image" src=""
/language zh
/kind bug
Related page: /retitle [zh] Displays Raw Html data in tutorials page
/sig docs /triage accepted /priority backlog
As per original site, this part should look something like this - !
/assign
Change:
1. Apply the frontend Deployment from the `frontend-deployment.yaml` file: <ins> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml --> </ins> ```shell kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-deployment.yaml ``` <del> <!--- for local testing of the content via relative file path kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml --> </del> 1. Query the list of Pods to verify that the three frontend replicas are running: ```shell

Discussion:
4 ordered lists have wrong indexes. For example, the number below should be 3. ! Page to update: /language en /kind cleanup
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:
You can renew your certificates manually at any time with the `kubeadm certs renew` command. <del> This command performs the renewal using CA (or front-proxy-CA) certificate and key stored in `/etc/kubernetes/pki`. </del> <ins> This command performs the renewal using CA (or front-proxy-CA) certificate and key stored in `/etc/kubernetes/pki`. </ins> After running the command you should restart the control plane Pods. This is required since dynamic certificate reload is currently not supported for all components and certificates. [Static Pods](/docs/tasks/configure-pod-container/static-pod/) are managed by the local kubelet and not by the API Server, thus kubectl cannot be used to delete and restart them. <del> To restart a static Pod you can temporarily remove its manifest file from `/etc/kubernetes/manifests/` </del> <ins> To restart a static Pod you can temporarily remove its manifest file from `/etc/kubernetes/manifests/` </ins> and wait for 20 seconds (see the `fileCheckFrequency` value in [KubeletConfiguration struct](/docs/reference/config-api/kubelet-config.v1beta1/). The kubelet will terminate the Pod if it's no longer in the manifest directory. You can then move the file back and after another `fileCheckFrequency` period, the kubelet will recreate

Discussion:
The command only has Cobra (CLI) documentation and there are no pointers on what fields are relevant in the configuration passed with --config to it: Add a minimal example + config for the command usage on this page: /sig cluster-lifecycle /kind feature xref
/triage accepted
/language en
Change:
Create a directory named `config-exercise`. In your `config-exercise` directory, create a file named `config-demo` with this content: <del> ```shell </del> <ins> ```yaml </ins> apiVersion: v1 kind: Config preferences: {}

Discussion:
Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
The 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]:
Thanks for reporting, I can open a PR to fix this! /remove-lifecycle stale /assign
Change:
image again: ```shell <del> kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"gcr.io/google_containers/nginx-slim:0.8"}]' </del> <ins> kubectl patch statefulset web --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"registry.k8s.io/nginx-slim:0.8"}]' </ins> ``` ``` statefulset.apps/web patched

Discussion:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.
Change:
prefer responding with the same apiVersion they were sent. --> <p> <del> CredentialProviderRequest 包括 kubelet 需要进行身份验证的镜像。 </del> <ins> CredentialProviderRequest 包含 kubelet 需要进行身份验证的镜像。 </ins> Kubelet 会通过标准输入将此请求对象传递给插件。一般来说，插件倾向于用它们所收到的相同的 apiVersion 来响应。 </p>

Discussion:
Translate Chinese version for reference/config-api/kubelet- Comments /language zh /assign
/triage accepted
I think this issue can be included in next time.
Change:
used in this tutorial. Follow the necessary steps, based on your environment, storage configuration, and provisioning method, to ensure that all storage is reclaimed. <del> {{< /note >}} </del>  No newline at end of file <ins> {{< /note >}} </ins>

Discussion:
I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).
Ubuntu is getting a big rewrite as well.
Change:
`delete`        | <code>kubectl delete (-f FILENAME &#124; TYPE [NAME &#124; /NAME &#124; -l label &#124; --all]) [flags]</code> | Delete resources either from a file, stdin, or specifying label selectors, names, resource selectors, or resources. `describe`    | <code>kubectl describe (-f FILENAME &#124; TYPE [NAME_PREFIX &#124; /NAME &#124; -l label]) [flags]</code> | Display the detailed state of one or more resources. `diff`        | `kubectl diff -f FILENAME [flags]`| Diff file or stdin against live configuration. <del> --> `convert`    | `kubectl convert -f FILENAME [options]` | 在不同的 API 版本之间转换配置文件。配置文件可以是 YAML 或 JSON 格式。注意 - 需要安装 `kubectl-convert` 插件。 `cordon`    | `kubectl cordon NODE [options]` | 将节点标记为不可调度。 `cp`    | `kubectl cp <file-spec-src> <file-spec-dest> [options]` | 从容器复制文件、目录或将文件、目录复制到容器。 `create`        | `kubectl create -f FILENAME [flags]` | 从文件或 stdin 创建一个或多个资源。 `delete`        |  <code>kubectl delete (-f FILENAME &#124; TYPE [NAME &#124; /NAME &#124; -l label &#124; --all]) [flags]</code> |  基于文件、标准输入或通过指定标签选择器、名称、资源选择器或资源本身，删除资源。 `describe`    | <code>kubectl describe (-f FILENAME &#124; TYPE [NAME_PREFIX &#124; /NAME &#124; -l label]) [flags]</code> | 显示一个或多个资源的详细状态。 `diff`        | `kubectl diff -f FILENAME [flags]`| 在当前起作用的配置和文件或标准输之间作对比 (**BETA**) <!-- </del> `drain`    | `kubectl drain NODE [options]` | Drain node in preparation for maintenance. `edit`        | <code>kubectl edit (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [flags]</code> | Edit and update the definition of one or more resources on the server by using the default editor. `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | Execute a command against a container in a pod.

Discussion:
web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted
Change:
이 명령은 클러스터를 업그레이드할 수 있는지를 확인하고, 업그레이드할 수 있는 버전을 가져온다. <del> {{< note >}} 또한 `kubeadm upgrade` 는 이 노드에서 관리하는 인증서를 자동으로 갱신한다. 인증서 갱신을 하지 않으려면 `--certificate-renewal=false` 플래그를 사용할 수 있다. 자세한 내용은 [인증서 관리 가이드](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs)를 참고한다. {{</ note >}} </del> <ins> {{< note >}} 또한 `kubeadm upgrade` 는 이 노드에서 관리하는 인증서를 자동으로 갱신한다. 인증서 갱신을 하지 않으려면 `--certificate-renewal=false` 플래그를 사용할 수 있다. 자세한 내용은 [인증서 관리 가이드](/docs/tasks/administer-cluster/kubeadm/kubeadm-certs)를 참고한다. {{</ note >}} </ins> <del> 1.  업그레이드할 버전을 선택하고, 적절한 명령을 실행한다. 예를 들면 다음과 같다. </del> <ins> -  업그레이드할 버전을 선택하고, 적절한 명령을 실행한다. 예를 들면 다음과 같다. </ins> ```shell # 이 업그레이드를 위해 선택한 패치 버전으로 x를 바꾼다.

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: Broken layout on "kubeadm " ! Proposed Solution: Check and apply upstream changes. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language ko
/assign
/unassign This issue already has been assigned to .