jiebi/CodeConvo huggingface dataset:
Change:
cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes <del> baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch </del> <ins> baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-$basearch </ins> enabled=1 gpgcheck=1 repo_gpgcheck=1

Discussion:
This is a Bug Report Problem: The getting started guide doesn't work on CentOS 7.7.1908. The section Installing kubeadm, kubelet and kubectl contains an error in this line: Whereas is not defined. Proposed Solution: Replace with Page to Update:
Ah I'm wrong /remove-kind bug /remove-good-first-issue /remove-priority important-longterm /triage support
What's the error on CentOS 7.7.1908 YUM usually lets you use and other built-in variables in a repository configuration.
/remove-good-first-issue
/remove-help
The error is: As it seems is evaluated to "" BTW, returns empty as well.
Hmm. Try this: What's the output?
Loaded plugins: fastestmirror {'arch': 'ia32e', 'basearch': 'x86_64', 'contentdir': 'centos', 'infra': 'stock', 'releasever': '7', 'uuid': '-e4c7-4444-9d2f-'}
Looks like is set in YUM. The problem is that the page instructs the reader to use a “here document” to edit the YUM configuration. /remove-triage support /kind bug /sig cluster-lifecycle /priority important-soon thanks for clarifying.
Change:
Name (CN), also known as a Fully Qualified Domain Name (FQDN) for `https-example.foo.com`. --> 在 Ingress 中引用此 Secret 将会告诉 Ingress 控制器使用 TLS 加密从客户端到负载均衡器的通道。 <del> 你需要确保创建的 TLS Secret 创建自包含 `sslexample.foo.com` 的公用名称（CN）的证书。 </del> <ins> 你需要确保创建的 TLS Secret 创建自包含 `https-example.foo.com` 的公用名称（CN）的证书。 </ins> 这里的公共名称也被称为全限定域名（FQDN）。 {{< note >}}

Discussion:
The host in the yaml is https- But the host in the document is
/language zh
/triage accepted /kind bug /assign
Change:
<p>Next, we’ll do a <code>curl</code> to the exposed IP address and port. Execute the command multiple times:</p> <p><code><b>curl http://"$(minikube ip):$NODE_PORT"</b></b></b></code></p> <p>We hit a different Pod with every request. This demonstrates that the load-balancing is working.</p> <ins> {{< note >}}<p>If you're running minikube with Docker Desktop as the container driver, a minikube tunnel is needed. This is because containers inside Docker Desktop are isolated from your host computer.<br> <p>In a separate terminal window, execute:<br> <code><b>minikube service kubernetes-bootcamp --url</b></code></p> <p>The output looks like this: <pre><b>http://127.0.0.1:51082<br>!  Because you are using a Docker driver on darwin, the terminal needs to be open to run it.</b></pre></p> <p>Then use the given URL to access the app:<br> <code><b>curl 127.0.0.1:51082</b></code></p> {{< /note >}} </ins> </div> </div>

Discussion:
The following step does not work: Now we can test that the app is exposed outside of the cluster using curl, the IP address of the Node and the externally exposed port: Steps are in the following places: (Load Balancing section) (Create a new Service section) Per the Minikube requires that Services of type NodePort be exposed with . Recommend adding a step to run this Minikube command in a separate terminal instance, copy the URL from this command, and curl that URL.
It depends on the minikube driver, but you are right that the step is required if using Docker Desktop (without an IP)
/retitle Explain extra step for exposing Services locally on minikube If some minikube drivers need it, we should mention that. /kind bug /language en /priority backlog /triage accepted
/assign
should we repeat the instructions shown in the existing or just add a link to said document? I think I read somewhere that we should avoid repeating documentation. Or should we rewrite the minikube commands to align them to the tutorial? Thanks!
These tutorials are outdated, as far as I know. Nothing for me here, seems to be documented:
Any of those is fine. I do not have an opinion on which is best.
Help with a fix is very welcome. If you'd like to help but aren't sure how: please ask in #sig-docs on the Kubernetes Slack workspace. If you're not already a member of that workspace, you can visit for an invitation.
/assign
A very nice note has already been in the live documentation as can be seen here. I will create a PR to add a similar note to This should be sufficient in my opinion.
Change:
body.cid-training section.call-to-action .main-section > div.call-to-action > div { padding: 0 2rem 0 2rem; } <ins> body.cid-training section.call-to-action .main-section > div.call-to-action div.cta-image { padding: 0 2rem 0 2rem; /* Change display to CSS Grid layout with 2 columns that autofill */ display: grid; grid-template-columns: repeat(auto-fill, minmax(50%, 1fr)); } /* Make the CTA text fill 100% of the viewport */ body.cid-training section.call-to-action .main-section > div.call-to-action > div.cta-text { width: 100%; } /* Resize the div that contains the images so that the images wrap 2 at a time and have no margin issues */ body.cid-training section.call-to-action .main-section > div.call-to-action { width: 60%; margin: auto; padding-top: 20px; } </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 The narrow (square grid) and wide (single row) logo layouts for are fine, however there is an intermediate state that we'd like to cut out. See for an animation showing the issue Why is this needed It's odd to show the logos in a 3:1 split. Two even rows would look better. Comments The fix for this should be Sass / CSS changes only. /area web-development Follows on from
/kind cleanup
I'm interested to see how this works. I spent a good hour fiddling with flexboxes and now I cascadingly hate stylesheets
Flexbox was handy when we had 3 items. Now we have a different challenge. The way I'd do it is with CSS grid, and assign items to specific grid columns and rows using media queries (default to a single row; use a square for narrow viewports only). If we wanted to not use a media query here then I think we'd have to change the HTML to add helper elements, and I'm not so keen on that.
/remove-kind feature
/assign
Also /triage accepted
Change:
<del> {{ getJSON .Site.Params.cveFeedBucket | jsonify }} </del> <ins> {{- $url := .Site.Params.cveFeedBucket -}} {{- with resources.GetRemote $url -}} {{- if .Err -}} {{- $message := printf "Failed to retrieve CVE data: %s" .Err -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- else -}} {{- .Content | transform.Unmarshal | jsonify -}} {{- end -}} {{- else -}} {{- $message := printf "Unable to fetch CVE data from the specified URL: %q" $url -}} {{- if eq hugo.Environment "production" -}} {{- errorf $message -}} {{- else -}} {{- warnf $message -}} {{- end -}} {{- end -}} </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 Migrate to instead of Hugo's Why is this needed Upstream Hugo has deprecated , which we use. We should aim to migrate to use ; see Comments We may need to upgrade to a newer Hugo as part of this work, or related to it. /area web-development /lifecycle frozen
/triage accepted /priority backlog
Let me see if I can assist with this. Edit: Proposed fix in /assign
Change:
* Поддержка CNI (Container Network Interface) * Ingress <del> ## Установке </del> <ins> ## Установка </ins> Посмотрите страницу [Установка Minikube](/ru/docs/tasks/tools/install-minikube/).

Discussion:
There is a grammatical error, should be "УстановкА
/language ru page is Thanks for reporting this
You are welcome) But, the page, where i found it is here:
Thanks for clarifying
/assign
/triage accepted
Change:
<ins> var http = require('http'); var handleRequest = function(request, response) { console.log('Received request for URL: ' + request.url); response.writeHead(200); response.end('Hello World!'); }; var www = http.createServer(handleRequest); www.listen(8080); </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: is a missing page; however, is part of the for a localization. Proposed Solution: Localize “Hello Minikube” into Spanish Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language es /kind bug
/assign
Change:
lsb_dist="$(echo ${lsb_dist} | tr '[:upper:]' '[:lower:]')" case "${lsb_dist}" in <del> amzn|centos|debian|ubuntu) </del> <ins> amzn|centos|debian|ubuntu|fedora) </ins> ;; *) <del> echo "Error: We currently only support ubuntu|debian|amzn|centos." </del> <ins> echo "Error: We currently only support ubuntu|debian|amzn|centos|fedora." </ins> exit 1 ;; esac

Discussion:
In there is initial check for but then it is not put in checks. I mean there are checks like but then in consecutive code there are things like following where is not mentioned.
Change:
# ... ``` <del> これは、Kubeletに対してPodを稼働させるためのRuntimeClassを使うように指示します。もし設定されたRuntimeClassが存在しない場合や、CRIが対応するハンドラーを実行できない場合、そのPodは`Failed`という[フェーズ](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)になります。 エラーメッセージに関しては対応する[イベント](/docs/tasks/debug-application-cluster/debug-application-introspection/)を参照して下さい。 </del> <ins> これは、kubeletに対してPodを稼働させるためのRuntimeClassを使うように指示します。もし設定されたRuntimeClassが存在しない場合や、CRIが対応するハンドラーを実行できない場合、そのPodは`Failed`という[フェーズ](/ja/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase)になります。 エラーメッセージに関しては対応する[イベント](/docs/tasks/debug/debug-application/debug-running-pod/)を参照して下さい。 </ins> もし`runtimeClassName`が指定されていない場合、デフォルトのRuntimeHandlerが使用され、これはRuntimeClassの機能が無効であるときのふるまいと同じものとなります。 <del> ### CRIの設定 </del> <ins> ### CRIの設定 {#cri-configuration} </ins> CRIランタイムのセットアップに関するさらなる詳細は、[CRIのインストール](/docs/setup/cri/)を参照してください。 <del> #### dockershim Kubernetesのビルトインのdockershim CRIは、ランタイムハンドラーをサポートしていません。 </del> #### {{< glossary_tooltip term_id="containerd" >}} ランタイムハンドラーは、`/etc/containerd/config.toml`にあるcontainerdの設定ファイルにより設定されます。

Discussion:
This is a Feature Request What would you like to be We need to update content/ja/docs/concepts/containers/runtime- according to the English text, because it is outdated. Why is this needed content/ja/docs/concepts/containers/runtime- is outdated. Comments /language ja /assign
/triage accepted
Change:
* [CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie) enables Kubernetes to seamlessly connect to a choice of CNI plugins, such as Calico, Canal, Flannel, Romana, or Weave. * [Contiv](https://contiv.github.io) provides configurable networking (native L3 using BGP, overlay using vxlan, classic L2, and Cisco-SDN/ACI) for various use cases and a rich policy framework. Contiv project is fully [open sourced](https://github.com/contiv). The [installer](https://github.com/contiv/install) provides both kubeadm and non-kubeadm based installation options. * [Contrail](https://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/), based on [Tungsten Fabric](https://tungsten.io), is an open source, multi-cloud network virtualization and policy management platform. Contrail and Tungsten Fabric are integrated with orchestration systems such as Kubernetes, OpenShift, OpenStack and Mesos, and provide isolation modes for virtual machines, containers/pods and bare metal workloads. <del> * [Flannel](https://github.com/coreos/flannel/blob/master/Documentation/kubernetes.md) is an overlay network provider that can be used with Kubernetes. </del> <ins> * [Flannel](https://github.com/flannel-io/flannel#deploying-flannel-manually) is an overlay network provider that can be used with Kubernetes. </ins> * [Knitter](https://github.com/ZTE/Knitter/) is a plugin to support multiple network interfaces in a Kubernetes pod. * [Multus](https://github.com/Intel-Corp/multus-cni) is a Multi plugin for multiple network support in Kubernetes to support all CNI plugins (e.g. Calico, Cilium, Contiv, Flannel), in addition to SRIOV, DPDK, OVS-DPDK and VPP based workloads in Kubernetes. * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/) is a networking provider for Kubernetes based on [OVN (Open Virtual Network)](https://github.com/ovn-org/ovn/), a virtual networking implementation that came out of the Open vSwitch (OVS) project. OVN-Kubernetes provides an overlay based networking implementation for Kubernetes, including an OVS based implementation of load balancing and network policy.

Discussion:
In kubernetes documentation page: There is an obsolete link to addon Flannel - (v1.15-16) The latest documentation is in main README -- (v1.17+)
/retitle Installing Addons has outdated link to Flannel network plugin /kind cleanup /language en /triage accepted /good-first-issue I agree with the fix that suggests
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 : /retitle Installing Addons has outdated link to Flannel network plugin /kind cleanup /language en /triage accepted /good-first-issue </details
/assign
Change:
<del> apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 </del> <ins> apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2 </ins> kind: Deployment metadata: name: nginx-deployment

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] --- [ ] Feature Request [x ] Bug Report Problem: Deployment yaml file: mysql- api version does not fit 1.9 version: apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1 kind: Deployment Proposed Solution: change apiVersion to: apps/v1 Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: 9 ! <!--Additional Information:--
Change:
of the cluster administrator. In the Service spec, `externalIPs` can be specified along with any of the `ServiceTypes`. <del> In the example below, "`my-service`" can be accessed by clients on "`80.11.12.10:80`" (`externalIP:port`) </del> <ins> In the example below, "`my-service`" can be accessed by clients on "`198.51.100.32:80`" (`externalIP:port`) </ins> ```yaml apiVersion: v1

Discussion:
The yaml has the definition of: externalIPs: 198.51.100.32 But the docs above say: "my-service" can be accessed by clients on "80.11.12.10:80" (externalIP:port) Should it not be: "my-service" can be accessed by clients on "198.51.100.32:80" (externalIP:port)
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 , can you please explain some more ? which document page are you referring to and how can we replicate or get this error/bug?
The title is not explanatory of the issue. I'd suggest changing title to explain in brief what issue you are facing/refering to.
I think he's talking about this page:
PR only modified the data in YAML but did not modify the above description. Is a change to this description missing?
/retitle The description of Service External IPs does not match the YAML example
You are right
Thank you, I will try to use a better title next time
That could be my bug. Sorry about that.
Open PR to fix this issue.
Change:
FROM golang:1.16-alpine RUN apk add --no-cache  <ins> runuser  </ins> git  openssh-client  rsync  npm &&  npm install -D autoprefixer postcss-cli <del> RUN mkdir -p /usr/local/src &&  cd /usr/local/src &&  </del> <ins> RUN mkdir -p /var/hugo &&  </ins> addgroup -Sg 1000 hugo &&  <del> adduser -Sg hugo -u 1000 -h /src hugo </del> <ins> adduser -Sg hugo -u 1000 -h /var/hugo hugo &&  chown -R hugo: /var/hugo &&  runuser -u hugo -- git config --global --add safe.directory /src </ins> COPY --from=0 /go/bin/hugo /usr/local/bin/hugo

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: Running the command fails with the following error: What I did: I ran the following commands: The current directory is mounted into . In the container, these files appear as owned by root (group nobody). I think, this may be a consequence of this CVE-2022-  What else I tried: Adding to the Dockerfile doesn't have an effect. Adding to the environment in the container didn't have an effect. (Found ). Running the command as root works. Proposed Solution: I don't know what the best solution would be. Maybe just wait until is updated for alpine? <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Hi. What OS are you running Docker on
I can replicate this with a recent image (local checksum: )
/triage accepted /priority important-longterm Thanks for reporting this
I think adding to the would be a reasonable fix, so long as it's done the right way.
I got it working by: the mount point of the docs directory OR using a different working directory for the user. (Otherwise the gets overwritten by the mounted ). an additional after we set the user and working directory.
Change:
Events: Type    Reason            Age   From                   Message ----    ------            ----  ----                   ------- <del> Normal  SuccessfulCreate  117s  replicaset-controller  Created pod: frontend-wtsmm Normal  SuccessfulCreate  116s  replicaset-controller  Created pod: frontend-b2zdv Normal  SuccessfulCreate  116s  replicaset-controller  Created pod: frontend-vcmts </del> <ins> Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-gbgfx Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-rwz57 Normal  SuccessfulCreate  13s   replicaset-controller  Created pod: frontend-wkl7w </ins> ``` And lastly you can check for the Pods brought up:

Discussion:
Hi Currently we obsrved that following image is not availble
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 /sig docs
can you please provide the page link of the issue?
HI Kubernetes/Website PFA link
/retitle Container image is not available for /kind bug
This looks similar to issue we already have I think it is a duplicate. /triage duplicate
Thanks for raising this! However, closing this request as it closely mirrors the original issue. Feel free to continue the discussion on the original issue. /close not-planned
Closing this issue, marking it as "Not Planned". <detailsIn response to : Thanks for raising this! 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:
## Changelog since v1.20.0 <del> # Release notes for v1.21.0-rc.0 [Documentation](https://docs.k8s.io/docs/home) # Changelog since v1.20.0 </del> ## What's New (Major Themes) ### Deprecation of PodSecurityPolicy

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: There exist bugs in . [Part number 1] [Part number 2] Proposed Solution: [Part number 1] [Part number 2] Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/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
[As-is] [To-be]
Hello . Note: The release notes are auto-generated. What do you think about logging an issue with the release team (release notes)?
Hi Following your advice, I posted an on . Thank you!
release notes team here. yes this was autogenerated but we had to make manual fix to k/k (ref: ) a few days after the official release went out. i think it's the right move to fix it here as well
Change:
<hr> <del> - **kind** (string), 必需 </del> <ins> - **kind** (string)，必需 </ins> Kind 是被引用的资源的类型 <del> - **name** (string), 必需 </del> <ins> - **name** (string)，必需 </ins> Name 是被引用的资源的名称

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