jiebi/CodeConvo huggingface dataset:
Change:
[examples_heading] other = "उदाहरण" <ins> [feature_state] other = "फ़ीचर स्थिति:" </ins> [feedback_heading] other = "प्रतिक्रिया"

Discussion:
Updated with new strings from Didn't remove any strings from , even if they're missing from
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
/language hi
Completed.
Change:
as a bearer token.  See [above](#putting-a-bearer-token-in-a-request) for how the token is included in a request. <del> ![Kubernetes OpenID Connect Flow](/images/docs/admin/k8s_oidc_login.svg) </del> <ins> {{< mermaid >}} sequenceDiagram participant user as User participant idp as Identity Provider participant kube as Kubectl participant api as API Server user ->> idp: 1. Login to IdP activate idp idp -->> user: 2. Provide access_token,<br>id_token, and refresh_token deactivate idp activate user user ->> kube: 3. Call Kubectl<br>with --token being the id_token<br>OR add tokens to .kube/config deactivate user activate kube kube ->> api: 4. Authorization: Bearer... deactivate kube activate api api ->> api: 5. Is JWT signature valid? api ->> api: 6. Has the JWT expired?(iat+exp) api ->> api: 7. user authorized? api -->> kube: 8. Authorized: Perform<br>action and return result deactivate api activate kube kube --x user: 9. Return result deactivate kube {{< /mermaid >}} </ins> 1.  Login to your identity provider 2.  Your identity provider will provide you with an `access_token`, `id_token` and a `refresh_token`

Discussion:
This is a Feature Request What would you like to be Replace the sequence diagram on with the one by . This is the follow-up of . Why is this needed There are several pros to use mermaid to draw the sequence diagram: mermaid format is more readable easy to modify better styling Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/assign
/kind cleanup /language en /triage accepted /priority backlog
Change:
.resources { width: 100%; <del> margin-top; 5%; </del> <ins> margin-top: 5%; </ins> margin-bottom: 3%; float: left; }

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: (Despite the PR has been merged, it seems that the error still exists. So opening an issue here. ) From the PR : [As-is] ! ! [To-be] ! ! Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--CC /area web-development
/triage accepted
Hello Thanks for reporting this issue. May i kindly know some more details to reproduce the issue. 1) Browser & Version ? 2) Resolution of your display ? I'm trying to reproduce it on wide viewport !
Hello Here is the info of my env: Windows 10 Enterprise 20H2 Google Chrome 97.0.4692.99 (64bit) Monitor resolution: 3840 1600 Chrome window size: [1868 1592] ! [1868 1592] [3767 1600] ! [3767 * 1600]
I can replicate this with Chromium and with Firefox.
/priority backlog
Thanks for the information. Please can you assign this issue to me.
try this Prow command: /assign ravikiranr26 (reply in a comment with that command on a line by itself)
/assign ravikiranr26
Change:
release in order to get access to the packages of the desired Kubernetes minor version. <del> {{< tabs name="k8s_install_versions" >}} </del> <ins> {{< tabs name="k8s_upgrade_versions" >}} </ins> {{% tab name="Ubuntu, Debian or HypriotOS" %}} 1. Open the file that defines the Kubernetes `apt` repository using a text editor of your choice:

Discussion:
In the "" section of the "" document, the steps for switching CentOS/RHEL/Fedora are the same as those for Ubuntu/Debian. There should be specific steps for RHEL based distributions. Suggest the following: Open the file that defines the Kubernetes apt repository using a text editor of your choice: nano You should see a single line with the URL that contains your current Kubernetes minor version. For example, if you're using v1.27, you should see this: Change the version in the URL to the next available minor release, for example: Save the file and exit your text editor. Continue following the relevant upgrade instructions.
Page reported in issue: /language en /sig docs
I see that the content is present in the file but isn't displaying correctly within the tab layout on the page. /kind bug /priority backlog /triage accepted
I'll try to investigate this issue and see if I can offer assistance. /assign
Change:
release in order to get access to the packages of the desired Kubernetes minor version. <del> {{< tabs name="k8s_install_versions" >}} </del> <ins> {{< tabs name="k8s_upgrade_versions" >}} </ins> {{% tab name="Ubuntu, Debian or HypriotOS" %}} 1. Open the file that defines the Kubernetes `apt` repository using a text editor of your choice:

Discussion:
: "Switching to another Kubernetes package repository" and particularly the one for CentOS/REHL shows commands for Debian based system, not REHL based rpm
I'm not seeing this. Can you point out where there are deb commands for RHEL? !
Excuse me it is for old versions: https://v1- https://v1- https://v1- !
I'm also not able to see this for Old version?? !
/retitle Broken tab layout on "Changing The Kubernetes Package Repository" page in older doc versions /kind bug
The problem stems from the existence of two tab layouts on this page having the same name "k8sinstallversions". This issue has been resolved in the branch. To address this issue in old docs versions, we'll need to backport and apply the fix to each corresponding old branch (release-1.25, release-1.26, release-1.27, release-1.28). Considering that the older versions of the documentation are no longer actively maintained, there's a question of whether it's worth investing efforts into fixing this issue.
I don't think it much important!
I'd support a backport. One of the things we do want people to learn to do with older Kubernetes versions is: to upgrade them! /triage accepted /priority backlog
I can try to help with this. /assign
I think the backporting is done which resolves this issue
If it is ok we can close this issue
The fixes have been back-ported to the older release branches. Closing this as completed. /close
Closing this issue. <detailsIn response to : The fixes have been back-ported to the older release branches. Closing this as completed. 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
Change:
## {{% heading "whatsnext" %}} <del> Learn more about [Labels and Selectors](/docs/concepts/overview/working-with-objects/labels/). </del> <ins> - Learn more about [Labels and Selectors](/docs/concepts/overview/working-with-objects/labels/). - Find [Well-known labels, Annotations and Taints](/docs/reference/labels-annotations-taints/) </ins>

Discussion:
This page should probably link to resources for defining standard annotations. Especially the thinks mentioned as examples. That would unify it a bit (for example contact address). Maybe link to
Page related to issue: /language en
/retitle Signpost from "Annotations" to "Well-Known Labels, Annotations and Taints" reference page
We can enhance the section by including a link to the reference page, as well as any other relevant pages. This will be beneficial in guiding readers to explore those additional pages.
/kind feature /triage accepted /priority backlog
please i will want to work in this! /assign
i have riased pull request please review.
Change:
- name: about title: ドキュメントについて description: このWebサイトには、Kubernetesの最新バージョンと過去4世代のドキュメントが含まれています。 <ins> button: "利用可能なバージョンを見る" button_path: "/docs/home/supported-doc-versions" </ins> ---

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. --Add button for "" in Why is this needed Because it exists in en() but not in ja( ). Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /assign
/retitle [ja] Add button in /area localization /triage accepted
Change:
Kubernetes imposes on them. | Built-in Type                         | Usage                                   | <del> | ------------------------------------- | --------------------------------------- | | `Opaque`                              | arbitrary user-defined data             | </del> <ins> | ------------------------------------- |---------------------------------------- | | `Opaque`                              | arbitrary user-defined data            | </ins> | `kubernetes.io/service-account-token` | ServiceAccount token                    | | `kubernetes.io/dockercfg`             | serialized `~/.dockercfg` file          | | `kubernetes.io/dockerconfigjson`      | serialized `~/.docker/config.json` file |

Discussion:
Umbrella issue: contains multiple "use cases" for Secrets. However, many of these are mini-tasks. In this issue, I'd like to discuss each of these use cases at a high level to see which we can remove, which we can trim, and which we can move to a new or existing task page. That way, the "Use cases section could even be a bulleted list with links to relevant tasks. Use case: As container environment variables Recommendation: Delete Justification: the goal is achieved in . This also isn't a use case, it's a way to use a secret. Use case: Pod with SSH keys Recommendation: Delete content, keep use case as bullet Justification: the steps add no value beyond the existing task to . Use case: Pods with prod / test credentials Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page. Use case: dotfiles in a secret volume Recommendation: Remove steps and keep as bullet point with additional info about why it would be useful. Use case: Secret visible to one container in a Pod Recommendation: Move content to a new or existing task Justification: The content is complex enough that it can be its own task, either as part of or a new task page with actual steps to achieve more than just "secret visible to one container". Perhaps including RBAC steps. If you're interested, review each use case and leave a comment for each agreeing, disagreeing, or providing a different approach to each use case. After we've discussed and settled on an action for these use cases, we can start the actual work! /sig docs /cc
/assign
I think the "Use case: As container environment variables" can be removed as the goal is achieved in too.
Yeah agreed, although I'm separately removing that section and linking it to our existing task page as part of
Let's shift "Use case: Pods with prod/test credentials" and "Use case: secret visible to one container in a Pod" to and attach the link in the use case section as bullet notes.
/triage accepted
Imo the prod/test thing might not even need to move - it can live as an example in the concept but the task steps seem quite basic now that I think about it. Just referencing two Secrets in two different Pods...
Change:
an illustrative collection of numbers of elephants. See https://play.golang.org/p/Gi0PLgVHiUg , which computes this table. <del> {{< table caption="Example Shuffle Sharding Configurations" >}} |HandSize|     Queues|	1 elephant|		4 elephants|		16 elephants| |--------|-----------|------------|----------------|--------------------| |      12|         32|	4.428838398950118e-09|	0.11431348830099144|	0.9935089607656024| |      10|         32|	1.550093439632541e-08|	0.0626479840223545|	0.9753101519027554| |      10|         64|	6.601827268370426e-12|	0.00045571320990370776|	0.49999929150089345| |       9|         64|	3.6310049976037345e-11|	0.00045501212304112273|	0.4282314876454858| |       8|         64|	2.25929199850899e-10|	0.0004886697053040446|	0.35935114681123076| |       8|        128|	6.994461389026097e-13|	3.4055790161620863e-06|	0.02746173137155063| |       7|        128|	1.0579122850901972e-11|	6.960839379258192e-06|	0.02406157386340147| |       7|        256|	7.597695465552631e-14|	6.728547142019406e-08|	0.0006709661542533682| |       6|        256|	2.7134626662687968e-12|	2.9516464018476436e-07|	0.0008895654642000348| |       6|        512|	4.116062922897309e-14|	4.982983350480894e-09|	2.26025764343413e-05| |       6|       1024|	6.337324016514285e-16|	8.09060164312957e-11|	4.517408062903668e-07| </del> <ins> {{< table caption = "Example Shuffle Sharding Configurations" >}} HandSize | Queues | 1 elephant | 4 elephants | 16 elephants |----------|-----------|------------|----------------|--------------------| | 12 | 32 | 4.428838398950118e-09 | 0.11431348830099144 | 0.9935089607656024 | | 10 | 32 | 1.550093439632541e-08 | 0.0626479840223545 | 0.9753101519027554 | | 10 | 64 | 6.601827268370426e-12 | 0.00045571320990370776 | 0.49999929150089345 | | 9 | 64 | 3.6310049976037345e-11 | 0.00045501212304112273 | 0.4282314876454858 | | 8 | 64 | 2.25929199850899e-10 | 0.0004886697053040446 | 0.35935114681123076 | | 8 | 128 | 6.994461389026097e-13 | 3.4055790161620863e-06 | 0.02746173137155063 | | 7 | 128 | 1.0579122850901972e-11 | 6.960839379258192e-06 | 0.02406157386340147 | | 7 | 256 | 7.597695465552631e-14 | 6.728547142019406e-08 | 0.0006709661542533682 | | 6 | 256 | 2.7134626662687968e-12 | 2.9516464018476436e-07 | 0.0008895654642000348 | | 6 | 512 | 4.116062922897309e-14 | 4.982983350480894e-09 | 2.26025764343413e-05 | | 6 | 1024 | 6.337324016514285e-16 | 8.09060164312957e-11 | 4.517408062903668e-07 | {{< /table >}} </ins> ### FlowSchema

Discussion:
HTML breaks on this page: Related to Hugo version upgrade in
After investigating, it appears that the table is breaking partly because the caption shortcode was . The originating PR was by That said, even refactoring the table for whitespace doesn't fix the error; only removing the shortcode does. I'll open a PR for others to experiment. UPDATE: Works fine.
Change:
在开始本教程之前，你应该熟悉以下 Kubernetes 的概念： <del> * [Pods](/zh/docs/user-guide/pods/single-container/) </del> <ins> * [Pods](/zh/docs/concepts/workloads/pods/) </ins> * [Cluster DNS](/zh/docs/concepts/services-networking/dns-pod-service/) * [Headless Services](/zh/docs/concepts/services-networking/service/#headless-services) * [PersistentVolumes](/zh/docs/concepts/storage/persistent-volumes/)

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: ! ! Proposed Solution: Page to Update: <!--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
/language zh
/kind bug
/assign
Change:
Type for HostPath Volume Defaults to "" More info: https://kubernetes.io/docs/concepts/storage/volumes#hostpath <del> ### Persistent volumes {#Persistent volumes} </del> <ins> ### Persistent volumes {#Persistent-volumes} </ins> - **awsElasticBlockStore** (AWSElasticBlockStoreVolumeSource)

Discussion:
This is a Bug Report The issue is outlined in:
/triage accepted
/kind cleanup
Hi Thanks for opening a PR to fix this issue! /assign
Change:
<ins> --- title: ドキュメントコンテンツガイド linktitle: コンテンツガイド content_type: concept weight: 10 --- <!-- overview --> このページでは、Kubernetesのドキュメント上のコンテンツのガイドラインを説明します。 許可されるコンテンツに関して疑問がある場合は、[Kubernetes Slack](https://slack.k8s.io/)の#sig-docsチャンネルに参加して質問してください！ Kubernetes Slackには、<https://slack.k8s.io/> から参加登録ができます。 Kubernetesドキュメントの新しいコンテンツの作成に関する情報については、[スタイルガイド](/docs/contribute/style/style-guide)に従ってください。 <!-- body --> ## 概要 ドキュメントを含むKubernetesのウェブサイトのソースは、[kubernetes/website](https://github.com/kubernetes/website)リポジトリに置かれています。 Kubernetesの主要なドキュメントは`kubernetes/website/content/<language_code>/docs`フォルダに置かれており、これらは[Kubernetesプロジェクト](https://github.com/kubernetes/kubernetes)を対象としています。 ## 許可されるコンテンツ Kubernetesのドキュメントにサードパーティーのコンテンツを掲載することが許されるのは、次の場合のみです。 - コンテンツがKubernetesプロジェクト内のソフトウェアのドキュメントとなる場合 - コンテンツがプロジェクト外のソフトウェアのドキュメントとなるが、Kubernetesを機能させるために必要である場合 - コンテンツがkubernetes.ioの正規のコンテンツであるか、他の場所の正規のコンテンツへのリンクである場合 ### サードパーティーのコンテンツ Kubernetesのドキュメントには、Kubernetesプロジェクト([kubernetes](https://github.com/kubernetes)および[kubernetes-sigs](https://github.com/kubernetes-sigs) GitHub organizationsに存在するプロジェクト)の適用例が含まれています。 Kubernetesプロジェクト内のアクティブなコンテンツへのリンクは常に許可されます。 Kubernetesを機能させるためには、一部サードパーティーのコンテンツが必要です。たとえば、コンテナランタイム(containerd、CRI-O、Docker)、[ネットワークポリシー](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)(CNI plugin)、[Ingressコントローラー](/ja/docs/concepts/services-networking/ingress-controllers/)、[ロギング](/docs/concepts/cluster-administration/logging/)などです。 ドキュメント内で、Kubernetesプロジェクト外のサードパーティーのオープンソースソフトウェア(OSS)にリンクすることができるのは、Kubernetesを機能させるために必要な場合のみです。 ### 情報源が重複するコンテンツ 可能な限り、Kubernetesのドキュメントは正規の情報源にリンクするようにし、情報源が重複してしまうようなホスティングは行いません。 情報源が重複したコンテンツは、メンテナンスするために2倍の労力(あるいはそれ以上！)が必要になり、より早く情報が古くなってしまいます。 {{< note >}} あなたがKubernetesのプロジェクトのメンテナーであり、ドキュメントのホスティングに関して手助けが必要なときは、[Kubernetes Slackの#sig-docs](https://kubernetes.slack.com/messages/C1J0BPD2M/)で教えてください。 {{< /note >}} ### その他の情報 許可されるコンテンツに関して疑問がある場合は、[Kubernetes Slack](https://slack.k8s.io/)の#sig-docsチャンネルに参加して質問してください！ ## {{% heading "whatsnext" %}} * [スタイルガイド](/docs/contribute/style/style-guide)を読む </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
/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
Change:
... ``` <del> contains two elements in the `from` array, and allows connections from Pods in the local Namespace with the label `role=client`, *or* from any Pod in any namespace with the label `user=alice`. </del> <ins> It contains two elements in the `from` array, and allows connections from Pods in the local Namespace with the label `role=client`, *or* from any Pod in any namespace with the label `user=alice`. </ins> When in doubt, use `kubectl describe` to see how Kubernetes has interpreted the policy. <a name="behavior-of-ipblock-selectors"></a> <del> __ipBlock__: This selects particular IP CIDR ranges to allow as ingress sources or egress destinations. These should be cluster-external IPs, since Pod IPs are ephemeral and unpredictable. </del> <ins> **ipBlock**: This selects particular IP CIDR ranges to allow as ingress sources or egress destinations. These should be cluster-external IPs, since Pod IPs are ephemeral and unpredictable. </ins> Cluster ingress and egress mechanisms often require rewriting the source or destination IP of packets. In cases where this happens, it is not defined whether this happens before or

Discussion:
I spent one hour to do one sample exercice about network policy because of your wrong configuration !!! +++++++++++++++++++++ policyTypes: # should remove space in the 2nd & 3rd line Ingress Egress ++++++++++++++++++++++ egress: to: ipBlock: cidr: 10.0.0.0/24 ports: # "-" is missing before ports protocol: TCP port: 5978
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
/retitle Invalid manifest in Network Policies page Thanks for reporting the bug /kind bug /language en Please paste in the entire invalid manifest (surround it by <tt`</ttif you can) so we know which part of the page is wrong. We could guess, but it's easier if you're explicit about this
/triage accepted /assign
Change:
spec: containers: - name: follower <del> image: gcr.io/google_samples/gb-redis-follower:v2 </del> <ins> image: us-docker.pkg.dev/google-samples/containers/gke/gb-redis-follower:v2 </ins> resources: requests: cpu: 100m

Discussion:
cannot pull frontend container, it shows ImagePullBackOff !
Page reported in issue: /language zh
/retitle [zh] Deprecated image causes failures in "Deploying PHP Guestbook with Redis" tutorial
/kind bug
/triage accepted /assign
Change:
## 업그레이드할 버전 결정 <del> 1.  최신의 안정 버전인 1.18을 찾는다. </del> <ins> 최신의 안정 버전인 1.18을 찾는다. </ins> <del> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </ins> apt update apt-cache madison kubeadm # 목록에서 최신 버전 1.18을 찾는다 # 1.18.x-00과 같아야 한다. 여기서 x는 최신 패치이다. <del> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </ins> yum list --showduplicates kubeadm --disableexcludes=kubernetes # 목록에서 최신 버전 1.18을 찾는다 # 1.18.x-0과 같아야 한다. 여기서 x는 최신 패치이다. <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> ## 컨트롤 플레인 노드 업그레이드 ### 첫 번째 컨트롤 플레인 노드 업그레이드 <del> 1.  첫 번째 컨트롤 플레인 노드에서 kubeadm을 업그레이드한다. </del> <ins> -  첫 번째 컨트롤 플레인 노드에서 kubeadm을 업그레이드한다. </ins> <del> {{< tabs name="k8s_install_kubeadm_first_cp" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </del> <ins> {{< tabs name="k8s_install_kubeadm_first_cp" >}} {{% tab name="Ubuntu, Debian 또는 HypriotOS" %}} </ins> # 1.18.x-00에서 x를 최신 패치 버전으로 바꾼다. apt-mark unhold kubeadm &&  apt-get update && apt-get install -y kubeadm=1.18.x-00 &&  apt-mark hold kubeadm <ins> - </ins> # apt-get 버전 1.1부터 다음 방법을 사용할 수도 있다 apt-get update &&  apt-get install -y --allow-change-held-packages kubeadm=1.18.x-00 <del> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </del> <ins> {{% /tab %}} {{% tab name="CentOS, RHEL 또는 Fedora" %}} </ins> # 1.18.x-0에서 x를 최신 패치 버전으로 바꾼다. yum install -y kubeadm-1.18.x-0 --disableexcludes=kubernetes <del> {{% /tab %}} {{< /tabs >}} </del> <ins> {{% /tab %}} {{< /tabs >}} </ins> <del> 1.  다운로드하려는 버전이 잘 받아졌는지 확인한다. </del> <ins> -  다운로드하려는 버전이 잘 받아졌는지 확인한다. </ins> ```shell kubeadm version ``` <del> 1.  컨트롤 플레인 노드를 드레인(drain)한다. </del> <ins> -  컨트롤 플레인 노드를 드레인(drain)한다. </ins> ```shell # <cp-node-name>을 컨트롤 플레인 노드 이름으로 바꾼다. kubectl drain <cp-node-name> --ignore-daemonsets ``` <del> 1.  컨트롤 플레인 노드에서 다음을 실행한다. </del> <ins> -  컨트롤 플레인 노드에서 다음을 실행한다. </ins> ```shell sudo kubeadm upgrade plan

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 .