jiebi/CodeConvo huggingface dataset:
Change:
* [Introduction to Kubernetes (edX)](https://www.edx.org/course/introduction-kubernetes-linuxfoundationx-lfs158x#) <del> * [Hello Minikube](/docs/tutorials/hello-minikube/) </del> <ins> * [Hello Minikube](/es/docs/tutorials/hello-minikube/) </ins> ## Configuración

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:
/docs/admin/etcd_upgrade/     /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301 /docs/admin/extensible-admission-controllers.md     /docs/reference/access-authn-authz/extensible-admission-controllers/ 301 /docs/admin/garbage-collection/     /docs/concepts/cluster-administration/kubelet-garbage-collection/ 301 <del> /docs/admin/ha-master-gce/     /docs/tasks/administer-cluster/highly-available-master/ 301 /docs/admin/ha-master-gce.md/     /docs/tasks/administer-cluster/highly-available-master/ 301 </del> <ins> /docs/admin/ha-master-gce/     /docs/setup/production-environment/#production-control-plane 301 /docs/admin/ha-master-gce.md/     /docs/setup/production-environment/#production-control-plane 301 </ins> /docs/admin/high-availability/      /docs/setup/production-environment/tools/kubeadm/high-availability/   301 /docs/admin/kubelet-authentication-authorization/     /docs/reference/command-line-tools-reference/kubelet-authentication-authorization/ 301 /docs/admin/kubelet-tls-bootstrapping/     /docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/ 301

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 , and scripts are mentioned. But according to 's , And the in (where the and scripts exist) says that Proposed Solution: ~Update to not mention and scripts.~ Delete and redirect it to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/language en
/kind cleanup /triage accepted
/sig cluster-lifecycle (ish)
/reopen The page still mentions those scripts.
Reopened this issue. <detailsIn response to : /reopen 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 think it would probably be best to instead drop all reference to them, we have if we need to document details to upstream contributors, previously we did not and sort of did double-duty IMHO
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]:
Let's delete and redirect it to /lifecycle frozen do you agree with that approach? If so, please update the issue description to highlight it as a plan.
→ Yes! → Done!
/assign
Thanks all.
Change:
<p>If the user provides a configuration types that is not expected for the action you are performing, kubeadm will ignore those types and print a warning.</p> <h2>Kubeadm init configuration types</h2> <del> <p>When executing kubeadm init with the `--config“ option, the following configuration types could be used: </del> <ins> <p>When executing kubeadm init with the <code>--config</code> option, the following configuration types could be used: </ins> InitConfiguration, ClusterConfiguration, KubeProxyConfiguration, KubeletConfiguration, but only one between InitConfiguration and ClusterConfiguration is mandatory.</p> <pre style="background-color:#fff"><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta4<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>InitConfiguration<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">bootstrapTokens</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb"></span>...<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">nodeRegistration</span>:<span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#bbb">	</span>...<span style="color:#bbb"> </span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb"></span>...<span style="color:#bbb"> </ins> </span></pre><p>The InitConfiguration type should be used to configure runtime settings, that in case of kubeadm init are the configuration of the bootstrap token and all the setting which are specific to the node where kubeadm is executed, including:</p>

Discussion:
The indentation of the example configuration is messy. !
/kind bug /language en page:
Also Consider to remove the exist in the same page under . Note: This page is automatically generated, you are not allowed to directly change the documentation page.
/retitle Messy indentation on kubeadm config reference page
/priority backlog We'd prioritize other improvements over this one. /triage accepted
/assign This is because the Golang source code contains TAB characters instead of SPACEs as a convention, and those TABs are messing up the YAML snippet. I'll work on this.
PR sent for website. PR sent for the generator.
Change:
This is achievable with the usage of the `endPort` field, as the following example: <del> ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: multi-port-egress namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Egress egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 32000 endPort: 32768 ``` </del> <ins> {{< codenew file="service/networking/networkpolicy-multiport-egress.yaml" >}} </ins> The above rule allows any Pod with label `role=db` on the namespace `default` to communicate with any IP within the range `10.0.0.0/24` over TCP, provided that the target port is between the range 32000 and 32768. The following restrictions apply when using this field: * The `endPort` field must be equal to or greater than the `port` field. * `endPort` can only be defined if `port` is also defined. * Both ports must be numeric.

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:
<ins> flowchart TD A(创建策略n实例) -->|命名空间添加注解n以验证签名| B(创建 Pod) B --> C{策略评估} C --> |合格| D[fa:fa-check 允许] C --> |失败| E[fa:fa-xmark 不允许] D --> |需要时| F[镜像拉取] </ins>

Discussion:
I will localize the blog: . To avoid any conflict, this issue is opened. /language zh /assign
/triage accepted
Change:
schedules: - release: 1.23 releaseDate: 2021-12-07 <del> next: 1.23.3 cherryPickDeadline: 2022-01-24 targetDate: 2022-01-25 </del> <ins> next: 1.23.4 cherryPickDeadline: 2022-02-11 targetDate: 2022-02-16 </ins> endOfLifeDate: 2023-02-28 previousPatches: <ins> - release: 1.23.3 cherryPickDeadLine: 2022-01-24 targetDate: 2022-01-25 note: "Out-of-Bound Release https://groups.google.com/u/2/a/kubernetes.io/g/dev/c/Xl1sm-CItaY" </ins> - release: 1.23.2 cherryPickDeadline: 2022-01-14 targetDate: 2022-01-19

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 ~is~ soon will be an out of band v1.23.3 release - see - and the releases page should mention it. Proposed Solution: Update the releases page to mention v1.23.3 To change that, edit the data within Pages to Update: <!--Optional Information (remove the comment tags around information you would like to include)--Kubernetes Version: v1.23.3 Additional Information: /sig release /priority important-soon
/remove-kind bug
Related to
Hi, I would like to work on this issue. /assign
/area release-eng
/triage accepted
now is out of date as v1.23.3 is live - see
Change:
* `periodSeconds`: Probeが実行される頻度(秒数)。デフォルトは10秒。最小値は1。 * `timeoutSeconds`: Probeがタイムアウトになるまでの秒数。デフォルトは1秒。最小値は1。 * `successThreshold`: 一度Probeが失敗した後、次のProbeが成功したとみなされるための最小連続成功数。 <del> デフォルトは1。Liveness Probeには1を設定する必要があります。最小値は1。 </del> <ins> デフォルトは1。Liveness ProbeおよびStartup Probeには1を設定する必要があります。最小値は1。 </ins> * `failureThreshold`: Probeが失敗した場合、Kubernetesは`failureThreshold`に設定した回数までProbeを試行します。 Liveness Probeにおいて、試行回数に到達することはコンテナを再起動することを意味します。 Readiness Probeの場合は、Podが準備できていない状態として通知されます。デフォルトは3。最小値は1。

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 description that startupProbe successThreshold must be 1. Why is this needed The limitation has already been mentioned in the English page. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --I checked startupProbe successThreshold must be 1. /language ja
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:
the kubelets to tell individual containers to use the DNS Service's IP to resolve DNS names. <del> ### What things get DNS names? </del> Every Service defined in the cluster (including the DNS server itself) is <del> assigned a DNS name.  By default, a client Pod's DNS search list will include the Pod's own namespace and the cluster's default domain.  This is best illustrated by example: </del> <ins> assigned a DNS name. By default, a client Pod's DNS search list includes the Pod's own namespace and the cluster's default domain. ### Namespaces of Services A DNS query may return different results based on the namespace of the pod making it. DNS queries that don't specify a namespace are limited to the pod's namespace. Access services in other namespaces by specifying it in the DNS query. For example, consider a pod in a `test` namespace. A `data` service is in the `prod` namespace. A query for `data` returns no results, because it uses the pod's `test` namespace. A query for `data.prod` returns the intended result, because it specifies the namespace. DNS queries may be expanded using the pod's `/etc/resolv.conf`. Kubelet sets this file for each pod. For example, a query for just `data` may be expanded to `data.test.cluster.local`. The values of the `search` option are used to expand queries. To learn more about DNS queries, see [the `resolv.conf` manual page.](https://www.man7.org/linux/man-pages/man5/resolv.conf.5.html) ``` nameserver 10.32.0.10 search <namespace>.svc.cluster.local svc.cluster.local cluster.local options ndots:5 ``` In summary, a pod in the _test_ namespace can successfully resolve either `data.prod` or `data.prod.cluster.local`. ### DNS Records What objects get DNS records? </ins> <del> Assume a Service named `foo` in the Kubernetes namespace `bar`. A Pod running in namespace `bar` can look up this service by querying a DNS service for `foo`. A Pod running in namespace `quux` can look up this service by doing a DNS query for `foo.bar`. </del> <ins> 1. Services 2. Pods </ins> <del> The following sections detail the supported record types and layout that is </del> <ins> The following sections detail the supported DNS record types and layout that is </ins> supported.  Any other layout or names or queries that happen to work are considered implementation details and are subject to change without warning. For more up-to-date specification, see

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: the guidance on DNS resolution for services between namespaces is confusing users. Proposed Solution: add additional info on the troubleshooting pages, add a table to the services concept page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
/triage accepted /kind cleanup
/sig network
Change:
Kubernetes is often used to support workloads designed with microservice architecture. By design, microservices aim to follow the UNIX philosophy of "Do One Thing And Do It Well". Each microservice has a bounded context and a clear interface. In other words, you can expect the microservice clients to send relatively regular requests and the microservice to present a relatively regular behavior as a response to these requests. Consequently, a microservice architecture is an excellent candidate for security-behavior monitoring. <del> {{< figure src="Microservices.png" alt="Image showing why microservices are well suited for security-behavior monitoring" class="diagram-large" caption="Figure 2. Microservices are well suited for security-behavior monitoring" >}} </del> <ins> {{< figure src="security_behavior_figure_2.svg" alt="Image showing why microservices are well suited for security-behavior monitoring" class="diagram-large" caption="Figure 2. Microservices are well suited for security-behavior monitoring" >}} </ins> The diagram above clarifies how dividing a monolithic service to a set of microservices improves our ability to perform security-behavior monitoring and control. In a monolithic service approach, different client requests are intertwined, resulting in a diminished ability to identify irregular client behaviors. Without prior knowledge, an observer of the intertwined client requests will find it hard to distinguish between types of requests and their related characteristics. Further, internal client requests are not exposed to the observer. Lastly, the aggregated behavior of the monolithic service is a compound of the many different internal behaviors of its components, making it hard to identify irregular service behavior.

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: The image files in need to be converted to an SVG. Currently, they are PNG. The originals are PPT files that can be found at Earlier attempts to convert them to SVG resulted in poor-quality images. Proposed Solution: If anyone has the tools and expertise to convert the PNG/PPT to high-quality SVG that will look the same as the PNGs, we welcome the help. Page to Update: <!--Optional Information (remove the comment tags around the information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign If anyone gets to this first: great!
hey! looking to contribute to this project !..can I?
/triage accepted
I've made progress on this and hope to send in a PR later this week.
Change:
<!-- overview --> <del> {{< feature-state for_k8s_version="v1.14" state="beta" >}} </del> <ins> {{< feature-state for_k8s_version="v1.20" state="stable" >}} </ins> このページではRuntimeClassリソースと、runtimeセクションのメカニズムについて説明します。

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:
- Each container has access to the keys through a volume mounted at `/etc/nginx/ssl`. This is setup *before* the nginx server is started. --> <ins> 关于 nginx-secure-app 清单，值得注意的几点如下： </ins> <del> 关于 nginx-secure-app manifest 值得注意的点如下： - 它在相同的文件中包含了 Deployment 和 Service 的规格 - [Nginx 服务器](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/examples/https-nginx/default.conf) 处理 80 端口上的 http 流量，以及 443  端口上的 https 流量，Nginx Service 暴露了这两个端口。 - 每个容器访问挂载在 /etc/nginx/ssl 卷上的秘钥。这需要在 Nginx server 启动之前安装好。 </del> <ins> - 它在相同的文件中包含了 Deployment 和 Service 的规约 - [nginx 服务器](https://github.com/kubernetes/kubernetes/tree/{{< param "githubbranch" >}}/staging/https-nginx/default.conf) 处理 80 端口上的 HTTP 流量，以及 443  端口上的 HTTPS 流量，Nginx Service 暴露了这两个端口。 - 每个容器访问挂载在 /etc/nginx/ssl 卷上的秘钥。这需要在 Nginx 服务器启动之前安装好。 </ins> ```shell kubectl delete deployments,svc my-nginx; kubectl create -f ./nginx-secure-app.yaml

Discussion:
Nginx https 404
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Hi It sounds like you wanted to provide feedback about a web page. Which web page was that? /triage needs-information
Change:
<ins> --- title: Eviction id: eviction date: 2021-05-08 full_link: /docs/concepts/scheduling-eviction/ short_description: > Process of terminating one or more Pods on Nodes aka: tags: - operation --- Eviction is the process of terminating one or more Pods on Nodes. <!--more--> There are two kinds of eviction: * [Node-pressure eviction](/docs/concepts/scheduling-eviction/node-pressure-eviction/) * [API-initiated eviction](/docs/concepts/scheduling-eviction/api-eviction/) </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 Add an entry to the Kubernetes glossary, “Eviction”. Explain how Kubernetes uses this term. There are two flavors of eviction: node-initiated eviction, and API-initiated eviction. The detailed glossary entry should mention both and hyperlink to more detailed articles on these. Why is this needed “eviction” is Kubernetes jargon; readers may well come across the term without recognising it. We have entries for the specific flavors but not an overall entry for the general term. Comments Also see issue /kind feature /language en /priority backlog
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
Related pages: Scheduling, Preemption and Eviction Node-pressure Eviction API-initiated Eviction
/assign
Change:
<div id="frameHolder"> <script src="https://cdnjs.cloudflare.com/ajax/libs/iframe-resizer/4.3.9/iframeResizer.min.js"></script> {{ if ( .Get "category" ) }} <del> <iframe id="iframe-landscape" src="https://landscape.cncf.io/embed/embed.html?key={{ .Get "category" }}&headers=false&style=shadowed&size=md&bg-color=%23d95e00&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> </del> <ins> <iframe id="iframe-landscape" src="https://landscape.cncf.io/embed/embed.html?key={{ .Get "category" }}&headers=false&style=shadowed&size=md&bg-color=%233371e3&fg-color=%23ffffff&iframe-resizer=true" style="width: 1px; min-width: 100%; min-height: 100px; border: 0;"></iframe> </ins> <script> iFrameResize({ }, '#iframe-landscape'); </script>

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: uses the wrong background color(s); it's but should be (Kubernetes blue). I think the orange color was copied from by mistake. Proposed Solution: Revise the shortcode. Consider making the color be set once and then reused (“”). Page to Update: You would see the change on We should use blue backgrounds whether or not an announcement banner is showing. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: PR updated the shortcode. /area web-development /triage accepted /priority backlog If fixing this, consider also moving the iframe scroll-margin-top fix to be more general. See and
this is a nit against PR but fixing it isn't at all urgent.
/lifecycle frozen We should fix this eventually.
I would like to help with this. /assign
/assign