jiebi/CodeConvo huggingface dataset:
Code change:
| `app.kubernetes.io/managed-by`      | The tool being used to manage the operation of an application | `helm` | string | | `app.kubernetes.io/created-by`      | The controller/user who created this resource | `controller-manager` | string | <del> To illustrate these labels in action, consider the following StatefulSet object: </del> <ins> To illustrate these labels in action, consider the following {{< glossary_tooltip text="StatefulSet" term_id="statefulset" >}} object: </ins> ```yaml <ins> # This is an excerpt </ins> apiVersion: apps/v1 kind: StatefulSet metadata:

Related discussion:
text: The concept of the has not been introduced at this point yet, but is used at multiple locations on this page. It would make sense to briefly explain what that is and link to a page that covers that topic.
/triage accepted /language en /help I would use a here. We should also mention that StatefulSet is just an example. Related, the example manifest is incomplete. We should add a comment in YAML to make it clear that this is an excerpt.
This request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /triage accepted /language en /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I would like to fix this /assign
I think is already defined .
My idea is to reference that definition into (see PR )
Code change:
gcloud components install kubectl ``` <del> Do check that the version is sufficiently up-to-date using `kubectl version`. </del> <ins> Check that the version is sufficiently up-to-date using `kubectl version`. </ins> <del> ## Install with brew </del> <ins> ## Install with Homebrew on macOS </ins> <del> If you are on MacOS and using brew, you can install with: </del> <ins> If you are on macOS and using [Homebrew](https://brew.sh/) package manager, you can install with: </ins> ```shell brew install kubectl

Related discussion:
text: This is a... [x] Bug Report Problem: There is no directory in the tar bundle. Example: Proposed Solution: Recommend people to execute in the bundle? Page to Update:
Code change:
body.cid-community #gallery { display: flex; <del> max-width: 100vw; </del> <ins> max-width: 100%; </ins> gap: 0.75rem; justify-content: center; margin-left: auto;

Related discussion:
text: 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: /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
During my browsing of the docs on a mobile device, I came across a similar situation on another page, specifically in the . It seems this issue might be widespread and could be affecting multiple pages, not limited to just the community page. Perhaps we could explore identifying a CSS fix that enhances the rendering of pages with wider elements. This way, we can efficiently resolve the problem and improve the overall user experience.
/area web-development
I tried making some changes on the source, A simple overflow - x in the right places seems to solve the problem. ! However, I'd often come across such problems when the scaling isn't managed properly. I'm sure there are better ways to get this problem fixed.
I see, In that case I'll try to find anymore pages that might be having the same issue.
Similar issue is present in case study
Code change:
| Golang marker | OpenAPI extension | Accepted values | Description | Introduced in | |---|---|---|---|---| <del> | `//+listType` | `x-kubernetes-list-type` | `atomic`/`set`/`map` | Applicable to lists. `atomic` and `set` apply to lists with scalar elements only. `map` applies to lists of nested types only. If configured as `atomic`, the entire list is replaced during merge; a single manager manages the list as a whole at any one time. If `granular`, different managers can manage entries separately. | 1.16          | </del> <ins> | `//+listType` | `x-kubernetes-list-type` | `atomic`/`set`/`map` | Applicable to lists. `atomic` and `set` apply to lists with scalar elements only. `map` applies to lists of nested types only. If configured as `atomic`, the entire list is replaced during merge; a single manager manages the list as a whole at any one time. If `set` or `map`, different managers can manage entries separately. | 1.16          | </ins> | `//+listMapKey` | `x-kubernetes-list-map-keys` | Slice of map keys that uniquely identify entries for example `["port", "protocol"]` | Only applicable when `+listType=map`. A slice of strings whose values in combination must uniquely identify list entries. While there can be multiple keys, `listMapKey` is singular because keys need to be specified individually in the Go type. | 1.16 | | `//+mapType` | `x-kubernetes-map-type` | `atomic`/`granular` | Applicable to maps. `atomic` means that the map can only be entirely replaced by a single manager. `granular` means that the map supports separate managers updating individual fields. | 1.17 | | `//+structType` | `x-kubernetes-map-type` | `atomic`/`granular` | Applicable to structs; otherwise same usage and OpenAPI annotation as `//+mapType`.| 1.17 |

Related discussion:
text: In the section, the annotation documentation gives possible values of //, but the description describes and . There's a more-detailed behaviour description in which might be useful to draw from.
Good point, let me send a quick fix.
/triage accepted
/kind cleanup /language en
Code change:
title: "Overview" weight: 20 description: Get a high-level outline of Kubernetes and the components it is built from. <ins> sitemap: priority: 0.9 </ins> ---

Related discussion:
text: 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 Kubernetes website generates a sitemap. Let's highlight specific pages using priority weighting: (and any localization that copies the priority weight) (and any localization that copies the priority weight) (and any localization that copies the priority weight) Why is this needed: Making this change helps search engines understand what pages the Kubernetes project sees as important. Comments /kind feature
Code change:
id: statefulset name: StatefulSet full-link: /docs/concepts/workloads/controllers/statefulset/ <del> aka: - PetSet </del> related: - deployment - pod

Related discussion:
text: This is a... [ ] Feature Request [x] Bug Report Problem: There is a link missing that was supposed to be in section Differences between alpha PetSets and beta StatefulSets under it in the second point StatefulSet guards against split brain which ends with following text TODO: Link to doc about fencing. Change it and add the link that is required. Proposed Solution: Add link which is missing Page to Update:
PetSet has long been replaced by StatefuSet and StatefulSet has been GA'ed in 1.9. So we are going to remove this page to avoid further confusion.
Code change:
If you want to use minikube again to learn more about Kubernetes, you don't need to delete it. <ins> ## Conclusion This page covered the basic aspects to get a minikube cluster up and running. You are now ready to deploy applications. </ins> ## {{% heading "whatsnext" %}}

Related discussion:
text: The basic tutorial starts at , which leads to , which leads to Since one does not know what is exactly meant with in the second site, one does also the deploy step. Because it's not clearly said "" or so. Then you go back to the second site, to read all through, only to do create/expose again (with little extras), only to go back to the first site and do create/expose again. Back to the first site on step 2, pretty much at the beginning it says: But I did it already 2 times in the current tutorial flow. Now I have 3 deployments, still in the basics deployment tutorial. Its like, there are 3 tutorials to do, which are the same, but also not the same. Instead of leading the user back and forth, I suggest to do one single sufficient tutorial.
Page related to issue: /language en
/retitle Consolidate and streamline Kubernetes basics tutorials to avoid redundancy and confusion
/sig docs
the three tutorial have different purpose. What I understood the purpose of having these as three.: Yes, Its leading to back and forth of the users but I think First link showing the general functionality of the cluster's component. It Should have the link To and then link will be helpful for readers to traverse. This sequence is lacking in the page. Thats the reason why i thing its taking user back and forth several times .
There was a previous attempt at de-duplicating, but it probably has to be done again - after the removal of the Katacoda tutorials, which were using a hosted setup of to run through the tutorials "inline" with the docs
I'll change the title to frame this as a bug. /retitle Multiple, similar Kubernetes basics tutorials that cause confusion /kind bug /triage accepted /priority important-longterm
/lifecycle frozen
Yes You are right! +1
/assign
I will start working on this.
Code change:
`Pending`   | The Pod has been accepted by the Kubernetes cluster, but one or more of the containers has not been set up and made ready to run. This includes time a Pod spends waiting to be scheduled as well as the time spent downloading container images over the network. `Running`   | The Pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting. `Succeeded` | All containers in the Pod have terminated in success, and will not be restarted. <del> `Failed`    | All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system. </del> <ins> `Failed`    | All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system, and is not set for automatic restarting. </ins> `Unknown`   | For some reason the state of the Pod could not be obtained. This phase typically occurs due to an error in communicating with the node where the Pod should be running. {{< note >}}

Related discussion:
text: This is a Bug Report Problem: An explanation in the Pod phase section is misleading. A pod doesn't have a state until it is configured not to be restarted. If the is not set, the pod will still be in the state. Proposed Solution: All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system, and will not be restarted. Page to Update: Kubernetes Version: v1.30.1 I'll be happy to work on it if it's accepted.
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
/sig node
so long as you're confident your understanding is correct, you don't need anyone to tell you it's OK to start work. Kubernetes is open source.
That’s true, thanks. /assign
Code change:
/docs/reference/generated/kube-scheduler/     /docs/reference/command-line-tools-reference/kube-scheduler/ 301 /docs/reference/generated/kubectl/kubectl-options/     /docs/reference/kubectl/kubectl/ 301 /docs/reference/generated/kubectl/kubectl/     /docs/reference/generated/kubectl/kubectl-commands/ 301 <del> /docs/reference/generated/kubectl/kubectl/kubectl_*.md    /docs/reference/generated/kubectl/kubectl-commands#:splat 301 </del> <ins> /docs/reference/generated/kubectl/kubectl/kubectl_*    /docs/reference/generated/kubectl/kubectl-commands#:splat 301 </ins> /docs/reference/glossary/maintainer/    /docs/reference/glossary/approver/ 301 /docs/reference/kubectl/kubectl-cmds/     /docs/reference/generated/kubectl/kubectl-commands/ 301! <del> /docs/reference/kubectl/kubectl/kubectl_*.md    /docs/reference/generated/kubectl/kubectl-commands#:splat 301 </del> <ins> /docs/reference/kubectl/kubectl/kubectl_*    /docs/reference/generated/kubectl/kubectl-commands#:splat 301 </ins> /docs/reference/scheduling/profiles/    /docs/reference/scheduling/config/#profiles 301 /docs/reference/generated/kubernetes-api/v1.15/    https://v1-15.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.15/  301

Related discussion:
text: To do tests, you should changes on  file, a PR, and the redirection rules on the deploy preview: https://deploy-preview-xxxxx--kubernetes-io-main- And regarding your research, I suggest to make changes like these: and test on the deploy preview of the PR you will post. I did some searching and found these: content/en/blog/posts/2016-08-00-Kubernetes-Namespaces-Use-Cases- content/en/blog/posts/2016-12-00-Statefulset-Run-Scale-Stateful-Applications-In-
I have made the PR. Let me know if I have to do some more changes or anything
Code change:
--> ### 仅在某些节点上运行 Pod <del> 如果指定了 `.spec.template.spec.nodeSelector`，DaemonSet Controller 将在能够与 [Node Selector](/zh/docs/concepts/scheduling-eviction/assign-pod-node/) 匹配的节点上创建 Pod。类似这种情况，可以指定 `.spec.template.spec.affinity`，然后 DaemonSet Controller 将在能够与 [node Affinity](/zh/docs/concepts/scheduling-eviction/assign-pod-node/) 匹配的节点上创建 Pod。 </del> <ins> 如果指定了 `.spec.template.spec.nodeSelector`，DaemonSet 控制器将在能够与 [Node 选择算符](/zh/docs/concepts/scheduling-eviction/assign-pod-node/) 匹配的节点上创建 Pod。 类似这种情况，可以指定 `.spec.template.spec.affinity`，之后 DaemonSet 控制器 将在能够与[节点亲和性](/zh/docs/concepts/scheduling-eviction/assign-pod-node/) 匹配的节点上创建 Pod。 </ins> 如果根本就没有指定，则 DaemonSet Controller 将在所有节点上创建 Pod。 <!--

Related discussion:
text: “ DaemonSet spec.template.“ “”“”
Mind propose a fix?
/triage accepted
/language zh (I presume)
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh (I presume) 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
yes,this is chinese languge,“”change to“”
/assign
Code change:
sudo mv ./kubectl /usr/local/bin/kubectl ``` <del> ## Extract kubectl from Release .tar.gz or Compiled Source If you downloaded a pre-compiled [release](https://github.com/kubernetes/kubernetes/releases), kubectl will be under `platforms/<os>/<arch>` from the tar bundle. If you compiled Kubernetes from source, kubectl should be either under `_output/local/bin/<os>/<arch>` or `_output/dockerized/bin/<os>/<arch>`. Copy or move kubectl into a directory already in your PATH (e.g. `/usr/local/bin`). For example: ```shell # OS X sudo cp platforms/darwin/amd64/kubectl /usr/local/bin/kubectl # Linux sudo cp platforms/linux/amd64/kubectl /usr/local/bin/kubectl ``` Next make it executable with the following command: ```shell sudo chmod +x /usr/local/bin/kubectl ``` The kubectl binary doesn't have to be installed to be executable, but the rest of the walkthrough will assume that it's in your PATH. If you prefer not to copy kubectl, you need to ensure it is in your path: ```shell # OS X export PATH=<path/to/kubernetes-directory>/platforms/darwin/amd64:$PATH # Linux export PATH=<path/to/kubernetes-directory>/platforms/linux/amd64:$PATH ``` </del> ## Download as part of the Google Cloud SDK kubectl can be installed as part of the Google Cloud SDK:

Related discussion:
text: This is a... [x] Bug Report Problem: There is no directory in the tar bundle. Example: Proposed Solution: Recommend people to execute in the bundle? Page to Update:
Code change:
<ins> apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: k8s.gcr.io/busybox command: [ "/bin/sh", "-c", "env" ] env: # 環境変数を定義します - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: # SPECIAL_LEVEL_KEYに割り当てる値をConfigMapが保持します name: special-config # 値に紐付けるキーを指定します key: special.how restartPolicy: Never </ins>

Related discussion:
text: 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 Translate tasks/configure-pod-container/configure-pod-configmap/ 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
Code change:
{{< /table >}} {{< note >}} <del> <!-- Generators other than `run-pod/v1` are deprecated. -->不推荐使用 `run-pod/v1` 以外的其他生成器。 </del> <ins> <!--Generators other than `run-pod/v1` are deprecated.--> 不推荐使用 `run-pod/v1` 以外的其他生成器. </ins> {{< /note >}} <!--

Related discussion:
text: there is an useless "" character on
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
Code change:
[previous_patches] other = "Poprawki:" <ins> [release_date_after] other = ")" [release_date_before] other = "(wydano: " # See https://gohugo.io/functions/format/#gos-layout-string # Use a suitable format for your locale [release_date_format] other = "2006-01-02" [release_cherry_pick_deadline] other = "Termin poprawek Cherry Pick" # Deprecated. Planned for removal in a future release. # Use [release_full_details_initial_text] instead. [release_complete] other = "Pełny" [release_end_of_life_date] other = "Termin End Of Life" # Replace [release_complete] with [release_full_details_initial_text] [release_full_details_initial_text] other = "Pełny" [release_information_navbar] other = "Informacje o wydaniu" [release_minor_version] other = "Podwersja (Minor)" [release_info_next_patch] other = "Następne wydanie zawierające poprawki to **%s**." # Localization note: You can use Markdown here. # The three placeholders (in order) are: #   Kubernetes minor version #   maintenance mode date #   end of life date # # Keep this order. It is OK to use more than one sentence, and it's also OK to change the # tense of the text so long as the meaning is clear. [release_info_eol] other = "**%s** od **%s** wchodzi w tryb minimalnego utrzymania (maintenance mode), a całkowity koniec wsparcia to **%s**." [release_note] other = "Uwagi" [release_schedule] other = "Harmonogram" [release_target_date] other = "Planowany termin" [release_changelog] other = "Rejestr zmian" </ins> [seealso_heading] other = "Zobacz też"

Related discussion:
text: What would you like to be This issue is a follow-up task from displays some English text: ! To replace this text with localized strings, you can update with from . Specifically, these:
/language pl
/sig docs
/triage accepted
Code change:
{{< codenew file="service/networking/network-policy-default-deny-egress.yaml" >}} This ensures that even pods that aren't selected by any other NetworkPolicy will not be allowed egress traffic. This policy does not <del> change the default ingress isolation behavior. </del> <ins> change the ingress isolation behavior of any pod. </ins> <del> ### Default allow all egress traffic </del> <ins> ### Allow all egress traffic </ins> <del> If you want to allow all traffic from all pods in a namespace (even if policies are added that cause some pods to be treated as "isolated"), you can create a policy that explicitly allows all egress traffic in that namespace. </del> <ins> If you want to allow all connections from all pods in a namespace, you can create a policy that explicitly allows all outgoing connections from pods in that namespace. </ins> {{< codenew file="service/networking/network-policy-allow-all-egress.yaml" >}} <ins> With this policy in place, no additional policy or policies can cause any outgoing connection from those pods to be denied.  This policy has no effect on isolation for ingress to any pod. </ins> ### Default deny all ingress and all egress traffic You can create a "default" policy for a namespace which prevents all ingress AND egress traffic by creating the following NetworkPolicy in that namespace.

Related discussion:
text: As discussed in the sig-networking mailing list (), has not been fully updated since the introduction of egress filtering.
/sig network /sig docs /kind bug (it's a bug because the doc should already have been updated) /language en /triage accepted
/priority backlog
Code change:
```shell $ export SERVICE_IP=$(kubectl get service nginx-service -o go-template={% raw %}{{.spec.clusterIP}}{% endraw %}) <del> $ export SERVICE_PORT=$(kubectl get service nginx-service -o go-template={% raw %}{{(index .spec.ports 0).port}}{% endraw %}) </del> <ins> $ export SERVICE_PORT=$(kubectl get service nginx-service -o go-template='{% raw %}{{(index .spec.ports 0).port}}{% endraw %}') </ins> $ curl http://${SERVICE_IP}:${SERVICE_PORT} ```

Related discussion:
text: Below command has a syntax error Add a single quotation or double quotation for the template part can make it work. PR will be sent later.