jiebi/CodeConvo huggingface dataset:
Change:
`expose`        | <code>kubectl expose (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [--port=port] [--protocol=TCP&#124;UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags]</code> | Expose a replication controller, service, or pod as a new Kubernetes service. `get`        | <code>kubectl get (-f FILENAME &#124; TYPE [NAME &#124; /NAME &#124; -l label]) [--watch] [--sort-by=FIELD] [[-o &#124; --output]=OUTPUT_FORMAT] [flags]</code> | List one or more resources. `kustomize`    | `kubectl kustomize <dir> [flags] [options]` | List a set of API resources generated from instructions in a kustomization.yaml file. The argument must be the path to the directory containing the file, or a git repository URL with a path suffix specifying same with respect to the repository root. <del> --> `drain`    | `kubectl drain NODE [options]` | 腾空节点以准备维护。 `edit`        | <code>kubectl edit (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [flags]</code> | 使用默认编辑器编辑和更新服务器上一个或多个资源的定义。 `exec`        | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | 对 Pod 中的容器执行命令。 `explain`    | `kubectl explain  [--recursive=false] [flags]` | 获取多种资源的文档。例如 Pod、Node、Service 等。 `expose`        | <code>kubectl expose (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) [--port=port] [--protocol=TCP&#124;UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags]</code> | 将副本控制器、服务或 Pod 作为新的 Kubernetes 服务暴露。 `get`        | <code>kubectl get (-f FILENAME &#124; TYPE [NAME &#124; /NAME &#124; -l label]) [--watch] [--sort-by=FIELD] [[-o &#124; --output]=OUTPUT_FORMAT] [flags]</code> | 列出一个或多个资源。 `kustomize`    | <code>kubectl kustomize <dir> [flags] [options]` </code> | 列出从 kustomization.yaml 文件中的指令生成的一组 API 资源。参数必须是包含文件的目录的路径，或者是 git 存储库 URL，其路径后缀相对于存储库根目录指定了相同的路径。 <!-- </del> `label`        | <code>kubectl label (-f FILENAME &#124; TYPE NAME &#124; TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags]</code> | Add or update the labels of one or more resources. `logs`        | `kubectl logs POD [-c CONTAINER] [--follow] [flags]` | Print the logs for a container in a pod. `options`    | `kubectl options` | List of global command-line options, which apply to all commands.

Discussion:
web
/retitle [zh-cn] Fix table formatting errors on the kubectl page
/triage accepted
Change:
[omit](#load-balancer-nodeport-allocation) assigning a node port, provided that the cloud provider implementation supports this. <ins> Some cloud providers allow you to specify the `loadBalancerIP`. In those cases, the load-balancer is created with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not specified, the loadBalancer is set up with an ephemeral IP address. If you specify a `loadBalancerIP` but your cloud provider does not support the feature, the `loadbalancerIP` field that you set is ignored. </ins> {{< note >}} <del> On **Azure**, if you want to use a user-specified public type `loadBalancerIP`, you first need to create a static type public IP address resource. This public IP address resource should be in the same resource group of the other automatically created resources of the cluster. For example, `MC_myResourceGroup_myAKSCluster_eastus`. Specify the assigned IP address as loadBalancerIP. Ensure that you have updated the `securityGroupName` in the cloud provider configuration file. For information about troubleshooting `CreatingLoadBalancerFailed` permission issues see, [Use a static IP address with the Azure Kubernetes Service (AKS) load balancer](https://docs.microsoft.com/en-us/azure/aks/static-ip) or [CreatingLoadBalancerFailed on AKS cluster with advanced networking](https://github.com/Azure/AKS/issues/357). </del> <ins> The`.spec.loadBalancerIP` field for a Service was deprecated in Kubernetes v1.24. This field was under-specified and its meaning varies across implementations. It also cannot support dual-stack networking. This field may be removed in a future API version. If you're integrating with a provider that supports specifying the load balancer IP address(es) for a Service via a (provider specific) annotation, you should switch to doing that. If you are writing code for a load balancer integration with Kubernetes, avoid using this field. You can integrate with [Gateway](https://gateway-api.sigs.k8s.io/) rather than Service, or you can define your own (provider specific) annotations on the Service that specify the equivalent detail. </ins> {{< /note >}}

Discussion:
This is a Bug Report Problem: As per , the has been deprecated since 1.24 but the docs does not mention about the deprecation - Proposed Solution: should mention the deprecation at least. Page to Update:
/triage accepted
Hi , the triage has been accepted and if you want to contribute the change you can assign it to yourself . If not, please let us know here, I'll be happy to add this
Thank you. Please go ahead
Great . Thanks /assign
/sig apps /sig network /sig docs
Continuing the discussion for change: One way we can apply this change is by adding a note: But should we give an example of the annotations ?
Hi , Raised a PR for the Note:
Change:
* Etcd's official [documentation](https://etcd.io/docs/). * Several [container runtimes](/docs/setup/production-environment/container-runtimes/) in Kubernetes. * Integrating with cloud providers using [cloud-controller-manager](/docs/concepts/architecture/cloud-controller/). <del> * [kubectl](/docs/reference/generated/kubectl/kubectl-commands) commands. </del> <ins> * [kubectl](/docs/reference/generated/kubectl/kubectl-commands) commands. </ins>  No newline at end of file

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. --I think adding some expressions to indicate controller manager runs many controllers explicitly, moreover indicate the actual amount of controllers in document page is useful for beginner. Why is this needed When I communicated with some k8s beginners, they think controller-manager only run 4 controllers refered to the document. Actually controller manager has run nearly 40 controllers currently, and the amount will increase in the future in predict. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
Its difficult to mention all the controllers in the document as some examples of the controllers that run within the kube-controller-manager process. There are additional controllers for different aspects of the Kubernetes cluster.
/language en Rather we can say there are more controllers that run within the kube-controller-manager. With few more examples
/triage accepted /priority backlog Don't add more examples. Instead, reword to make it clearer that the 4 examples listed are selected from a much larger set.
Expression in is puzzled too
There I would make changes. Swap: remove “replication controller” out, using “statefulset controller” as its replacement remove “endpoints controller” out, using “endpointslice controller” as its replacement
/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
I'd like to work on this
/assign
/assign
Hey has assigned this issue already. You can find another issue that you can work on.
Change:
- ahg-g title: Resource Bin Packing for Extended Resources content_template: templates/concept <del> weight: 10 </del> <ins> weight: 50 </ins> --- {{% capture overview %}}

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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
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
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!
Change:
## What is a Pod? {{< note >}} <del> While Kubernetes supports more {{< glossary_tooltip text="container runtimes" term_id="container-runtime" >}} than just Docker, [Docker](https://www.docker.com/) is the most commonly known runtime, and it helps to describe Pods using some terminology from Docker. </del> <ins> You need to install a [container runtime](/docs/setup/production-environment/container-runtimes/) into each node in the cluster so that Pods can run there. </ins> {{< /note >}} The shared context of a Pod is a set of Linux namespaces, cgroups, and

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: implies that Kubernetes has Docker Engine support. In fact, Docker Engine only works with Kubernetes if you either: connect Kubernetes to the containerd that makes Docker Engine work use an adapter such as Proposed Solution: Pick an option: the sentence: a bigger revision to the concept page (check if there is already work under way) Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en
Hi is this work fine or if you like to add something
/triage accepted
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
Change:
# Apply this config only on the primary. [mysqld] log-bin <ins> datadir=/var/lib/mysql/mysql </ins> replica.cnf: | # Apply this config only on replicas. [mysqld] super-read-only <ins> datadir=/var/lib/mysql/mysql </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: I use the /website/edit/main/content/en/examples/application/mysql/mysql- to deploy mysql cluster,and get error when the mysql-1 clone-mysql container starting to get backup file: I think it is the reason why datadir is not specified Proposed Solution: then I change mysql- as It works fine and success create other pod Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:v1.18.8--<!--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
/language en
/assign
Change:
</script> <body> <div id="frameHolder"> <del> <iframe id="landscape" frameBorder="0" scrolling="no" style="width: 1px; min-width: 100%" src=""></iframe> <script src="https://cdnjs.cloudflare.com/ajax/libs/iframe-resizer/3.6.0/iframeResizer.js"></script> <script> document.addEventListener('DOMContentLoaded', function() { iFrameResize({ log:true, messageCallback         : function(messageData){ // Callback fn when message is received if (messageData.message.type === 'showModal') { document.querySelector('body').style.overflow = 'hidden'; } if (messageData.message.type === 'hideModal') { document.querySelector('body').style.overflow = 'auto'; } }, }, '#landscape'); }); </script> </del> <ins> <iframe id="landscape" title="CNCF Landscape" frameBorder="0" scrolling="no" style="width: 1px; min-width: 100%" src=""></iframe> <script src="https://landscape.cncf.io/iframeResizer.js"></script> </ins> </div> </body> </main>

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: Missing partners in You can see to find the different. Proposed Solution: Update Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh /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:
echo 'complete -F __start_kubectl k' >>~/.bash_profile ``` <del> - If you installed kubectl with Homebrew (as explained [above](#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything. </del> <ins> - If you installed kubectl with Homebrew (as explained [here](/docs/tasks/tools/install-kubectl-macos/#install-with-homebrew-on-macos)), then the kubectl completion script should already be in `/usr/local/etc/bash_completion.d/kubectl`. In that case, you don't need to do anything. </ins> {{< note >}} The Homebrew installation of bash-completion v2 sources all the files in the `BASH_COMPLETION_COMPAT_DIR` directory, that's why the latter two methods work. {{< /note >}} <del> In any case, after reloading your shell, kubectl completion should be working. </del>  No newline at end of file <ins> In any case, after reloading your shell, kubectl completion should be working. </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: In , the link  is broken. Proposed Solution: Update link to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/kind bug /priority backlog /language en
/triage accepted
Change:
title: Code Contributor id: code-contributor date: 2018-04-12 <del> full_link: /docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > A person who develops and contributes code to the Kubernetes open source codebase.

Discussion:
This is a Bug Report I have fixed the same issue in English docs, same issue is followed by the other localization team. has one broken issue which needs to fix. ! Refer my merged PR of english docs. /assign
/triage accepted
Change:
## アドオンの有効化 <del> Minikubeはビルトインの{{< glossary_tooltip text="アドオン" term_id="addons" >}}があり、有効化、無効化、あるいはローカルのKubernetes環境に公開することができます。 </del> <ins> minikubeはビルトインの{{< glossary_tooltip text="アドオン" term_id="addons" >}}があり、有効化、無効化、あるいはローカルのKubernetes環境に公開することができます。 </ins> 1. サポートされているアドオンをリストアップします:

Discussion:
This is a Feature Request In the documentation available in , as well as in the link, the term is written as . I'd like to suggest updating it to to align with the and . <!-- 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 occurrences of to . Why is this needed Using the incorrect casing can be misleading, especially for newcomers. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
/assign
/language ja
/triage accepted
Change:
<tbody> <tr> <del> <td colspan="2">--azure-container-registry-config string</td> </del> <ins> <td colspan="2">--add_dir_header</td> </ins> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the file containing Azure container registry configuration information.</p></td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true, adds the file directory to the header of the log messages</p></td> </ins> </tr> <tr> <del> <td colspan="2">--bind-address string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0</td> </del> <ins> <td colspan="2">--alsologtostderr</td> </ins> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The IP address for the proxy server to serve on (set to '0.0.0.0' for all IPv4 interfaces and '::' for all IPv6 interfaces). This parameter is ignored if a config file is specified by --config.</p></td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>log to standard error as well as files</p></td> </ins> </tr> <tr> <del> <td colspan="2">--bind-address-hard-fail</td> </del> <ins> <td colspan="2">--bind-address string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 0.0.0.0</td> </ins> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true kube-proxy will treat failure to bind to a port as fatal and exit</p></td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The IP address for the proxy server to serve on (set to '0.0.0.0' for all IPv4 interfaces and '::' for all IPv6 interfaces). This parameter is ignored if a config file is specified by --config.</p></td> </ins> </tr> <tr> <del> <td colspan="2">--boot-id-file string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/proc/sys/kernel/random/boot_id"</td> </del> <ins> <td colspan="2">--bind-address-hard-fail</td> </ins> </tr> <tr> <del> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Comma-separated list of files to check for boot-id. Use the first one that exists.</p></td> </del> <ins> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true kube-proxy will treat failure to bind to a port as fatal and exit</p></td> </ins> </tr> <tr>

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: ! xref: Has references to some CLI arguments that are not valid for . Seem to be side effect of changes went into Proposed Solution: Remove the invalid flags from the documentation in Page to Update:
/language en /triage accepted
/assign
/assign
Thanks for taking care of this :)
Change:
#### Dockerの設定を利用してSecretを作成する。 <ins> レジストリへの認証のためにユーザー名、レジストリのパスワード、クライアントのメールアドレス、およびそのホスト名を知っている必要があります。 </ins> 適切な大文字の値を置き換えて、次のコマンドを実行します。 ```shell

Discussion:
This is a Feature Request What would you like to be We need to update according to the English text, because it is outdated. Why is this needed is outdated. Comments /language ja /assign
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Change:
<ins> --- title: "Jobの実行" description: 並列処理を使用してJobを実行します。 weight: 50 --- </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
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
Change:
each of them. Unlabeled namespaces should only indicate that they've yet to be evaluated. In the scenario that all workloads in all namespaces have the same security requirements, <del> we provide an [example](/docs/concepts/security/pod-security-admission/#applying-to-all-namespaces) </del> <ins> we provide an [example](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels/#applying-to-all-namespaces) </ins> that illustrates how the PodSecurity labels can be applied in bulk. ### Embrace the principle of least privilege

Discussion:
Problem: The text on should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text example to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on should point to these Check the page for the problem. It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the text example to and not to this . /assign /language en 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