jiebi/CodeConvo huggingface dataset:
Change:
* Read the [Container](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#container-v1-core) API reference * Read the [ResourceRequirements](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#resourcerequirements-v1-core) API reference * Read about [project quotas](https://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/xfs-quotas.html) in XFS <del> * Read more about the [kube-scheduler Policy reference (v1)](/docs/reference/config-api/kube-scheduler-policy-config.v1/) </del> <ins> * Read more about the [kube-scheduler configuration reference (v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/) </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: The scheduler policy API was completely removed in 1.23. Proposed Solution: Revise concepts/configuration/manage-resources- to remove references to the scheduler policy API; Revise or even remove which is meaningless; Remove the kube-scheduler-policy- file from config API. Page to Update: See above. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Related:
/sig scheduling /language en
/triage accepted
Change:
} } <ins> .td-search { header > .header-filler { height: $hero-padding-top; background-color: black; } } </ins> // Docs specific #editPageButton {

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: Navbar prevents search input field from being clicked on Can reproduce on Firefox, Chrome on latest builds Proposed Solution: Remove navbar from search page Page to Update: !
is not supposed to look like that screenshot /kind bug /priority critical-urgent /area web-development Thanks for reporting this.
/triage accepted
/retitle Navbar prevents search inputfield from being clicked
Actually /retitle Search page rendering incorrectly
Change:
apply multiple fixes in between pausing and resuming without triggering unnecessary rollouts. * For example, with a Deployment that was created: Get the Deployment details: ```shell kubectl get deploy

Discussion:
suggests: Do changes, then The output is equivalent to the previous run of . I do not see, how this output can confirm, that the Deployment was updated.
Welcome and thanks for contributing your first issue here! This sentence does seem confusing to me. I will improve it. /triage accepted /kind bug /assign
/sig apps
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]:
The Kubernetes project currently lacks enough active 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 Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle rotten [1]:
Change:
- perithompson title:    Security For Windows Nodes content_type: concept <del> weight: 75 </del> <ins> weight: 40 </ins> --- <!-- overview -->

Discussion:
This is a Feature Request What would you like to be A section in the Kubernetes documentation to provide users with best practice guidelines and references to Kubernetes projects and solutions for multi-tenancy. This can be a new section in . Why is this needed Kubernetes is commonly used by multiple teams and to run multiple applications. The has been chartered with defining multi-tenancy models for Kubernetes and making these easy to consume for end users. The group has produced multiple projects like , , and and published blog posts on and the projects (, ). The HNC and Virtual Cluster projects have “graduated” from the working group and are now managed under SIG-auth and SIG-cluster-lifecycle. However, multi-tenancy remains a confusing and complex topic for Kubernetes users, especially beginners. Having a section on multi-tenancy in the Kubernetes documentation, with links to projects, would be helpful to all users. Comments If this seems like a good idea, the Multi-Tenancy WG can take the lead to propose a draft document. cc:
Happy for multitenancy WG to take this forward - also, that WG is welcome to triage this as accepted. Please also explore whether you can put new content within three of the existing sections: and, that way, avoid adding a new section to the concept list - we already have quite a few. of course, it's also fine to add new Task or Reference pages that cover multi-tenancy aspects.
/language en
/triage accepted
See also
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
/wg multi-tenancy
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /wg multi-tenancy 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
/wg multitenancy
Change:
| Session affinity | Ensures that connections from a particular client are passed to the same Pod each time. | Windows Server 2022 | Set `service.spec.sessionAffinity` to "ClientIP" | | Direct Server Return (DSR) | Load balancing mode where the IP address fixups and the LBNAT occurs at the container vSwitch port directly; service traffic arrives with the source IP set as the originating pod IP. | Windows Server 2019 | Set the following flags in kube-proxy: `--feature-gates="WinDSR=true" --enable-dsr=true` | | Preserve-Destination | Skips DNAT of service traffic, thereby preserving the virtual IP of the target service in packets reaching the backend Pod. Also disables node-node forwarding. | Windows Server, version 1903 | Set `"preserve-destination": "true"` in service annotations and enable DSR in kube-proxy. | <del> | IPv4/IPv6 dual-stack networking | Native IPv4-to-IPv4 in parallel with IPv6-to-IPv6 communications to, from, and within a cluster | Windows Server 2019 | See [IPv4/IPv6 dual-stack](#ipv4ipv6-dual-stack) | </del> <ins> | IPv4/IPv6 dual-stack networking | Native IPv4-to-IPv4 in parallel with IPv6-to-IPv6 communications to, from, and within a cluster | Windows Server 2019 | See [IPv4/IPv6 dual-stack](/docs/concepts/services-networking/dual-stack/#windows-support) | </ins> | Client IP preservation | Ensures that source IP of incoming ingress traffic gets preserved. Also disables node-node forwarding. |  Windows Server 2019  | Set `service.spec.externalTrafficPolicy` to "Local" and enable DSR in kube-proxy | {{< /table >}}

Discussion:
This is a Bug Report Problem: The link for under the in is wrong. It is redirected to the instead of that it should redirect to the Proposed Solution: IPv4/IPv6 dual stack should redirect to the instead to the Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/sig network /sig docs
I would like to work on it /assign
/language en
This issue is resolved here
/triage accepted
Change:
{{< note >}} Para descargar una versión específica, reemplace la parte de `$(curl -L -s https://dl.k8s.io/release/stable.txt)` del comando con la versión específica. <del> Por ejemplo, para descargar la versión {{< param "fullversion" >}} en Linux, escriba: </del> <ins> Por ejemplo, para descargar la versión {{< skew currentPatchVersion >}} en Linux, escriba: </ins> ```bash <del> curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl </del> <ins> curl -LO https://dl.k8s.io/release/v{{< skew currentPatchVersion >}}/bin/linux/amd64/kubectl </ins> ``` {{< /note >}}

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 param is deprecated. Proposed Solution: Replace the shortcode (Spanish pages), for example with or something close. <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--Part of /language es
/triage accepted /area localization /priority backlog
Change:
You can define _exemptions_ from pod security enforcement in order allow the creation of pods that would have otherwise been prohibited due to the policy associated with a given namespace. Exemptions can be statically configured in the <del> [Admission Controller configuration](#configuring-the-admission-controller). </del> <ins> [Admission Controller configuration](/docs/tasks/configure-pod-container/enforce-standards-admission-controller/#configure-the-admission-controller). </ins> Exemptions must be explicitly enumerated. Requests meeting exemption criteria are _ignored_ by the Admission Controller (all `enforce`, `audit` and `warn` behaviors are skipped). Exemption dimensions include:

Discussion:
There's a broken link on this page pointing to: It's in the first paragraph under:
I'm seeing the same. Looks like it should probably link over to: . Does that make sense to you as well?
Yeah I think that's probably what the original author intended
/sig security auth /kind bug /triage accepted /language en
Change:
</td> <td> <p><code>tlsBootstrapToken</code> is a token used for TLS bootstrapping. <del> If <code>bootstrapToken</code> is set, this field is defaulted to <code>.bootstrapToken.token</code>, but can be overridden. If <code>file</code> is set, this field <strong>must be set</strong> in case the KubeConfigFile does not </del> <ins> If <code>bootstrapToken</code> is set, this field is defaulted to <code>.bootstrapToken.token</code>, but can be overridden. If <code>file</code> is set, this field <strong>must be set</strong> in case the KubeConfigFile does not </ins> contain any other authentication information.</p> </td> </tr>

Discussion:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: while cleaning up mentions of the legacy "master" taint in kubeadm docs: saw the following: it seems the generated reference API docs for kubeadm still include the "master" taint. Proposed Solution: cleanup mentions of the old taint from kubeadm's API reference docs at perhaps these need to be synced with: for dev-1.25 and main at k/website we removed the old taint from there before 1.24 was released. 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
/sig cluster-lifecycle /priority important-soon /kind cleanup
cc
Change:
Your deployments are running in Kubernetes. <del> 4.  Access your application. </del> <ins> 3.  Access your application. </ins> If you're already using `minikube` for your development process:

Discussion:
Hi, This command does not exist for kompose I'm using version 1.22 and there is no such command.
This looks like a report for The fix I recommend is to remove the list item, currently numbered 2 in the rendered page, that starts /language en /good-first-issue /kind bug /triage accepted /priority backlog Thanks
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 : This looks like a report for Run the kompose up command to deploy to Kubernetes directly, or skip to the next step instead to generate a file to use with kubectl. /good-first-issue /kind bug /triage accepted /priority backlog 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
+1 to remove the list item, I would like to work on it. /assign
If you have time, this task page could use some cleanup of the markup.
Change:
gate defaults to enabled in Kubernetes v1.24, which means that users can specify any custom resource as the data source of a PVC. <del> An [earlier blog article](/blog/2021/08/30-volume-populators-redesigned/) detailed how the </del> <ins> An [earlier blog article](/blog/2021/08/30/volume-populators-redesigned/) detailed how the </ins> volume populators feature works. In short, a cluster administrator can install a CRD and associated populator controller in the cluster, and any user who can create instances of the CR can create pre-populated volumes by taking advantage of the populator.

Discussion:
<!-- 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: Link of in gives 404 Proposed Solution: Update link to Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/kind documentation /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: Link of in gives 404 Proposed Solution: Page to Update: <!--Kubernetes Version:--/kind documentation /good-first-issue </details
useful to open PR. /language en
I have created a PR for this issue.
Thanks for PR. Kindly assign this issue to yourself and update PR description as
/assign
/triage accepted
/area blog
Change:
{{< glossary_definition term_id="kube-controller-manager" length="all" >}} <del> Some types of these controllers are: </del> <ins> There are many different types of controllers. Some examples of them are: </ins> * Node controller: Responsible for noticing and responding when nodes go down. * Job controller: Watches for Job objects that represent one-off tasks, then creates

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --I think adding some expressions to indicate controller manager runs many controllers explicitly, moreover indicate the actual amount of controllers in document page is useful for beginner. Why is this needed When I communicated with some k8s beginners, they think controller-manager only run 4 controllers refered to the document. Actually controller manager has run nearly 40 controllers currently, and the amount will increase in the future in predict. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
Its difficult to mention all the controllers in the document as some examples of the controllers that run within the kube-controller-manager process. There are additional controllers for different aspects of the Kubernetes cluster.
/language en Rather we can say there are more controllers that run within the kube-controller-manager. With few more examples
/triage accepted /priority backlog Don't add more examples. Instead, reword to make it clearer that the 4 examples listed are selected from a much larger set.
Expression in is puzzled too
There I would make changes. Swap: remove “replication controller” out, using “statefulset controller” as its replacement remove “endpoints controller” out, using “endpointslice controller” as its replacement
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available .

If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I'd like to work on this
/assign
/assign
Hey has assigned this issue already. You can find another issue that you can work on.
Change:
## Install the Weave Net addon <del> Follow the [Integrating Kubernetes via the Addon](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/) guide. </del> <ins> Follow the [Integrating Kubernetes via the Addon](https://github.com/weaveworks/weave/blob/master/site/kubernetes/kube-addon.md#-installation) guide. </ins> The Weave Net addon for Kubernetes comes with a <del> [Network Policy Controller](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#npc) </del> <ins> [Network Policy Controller](https://github.com/weaveworks/weave/blob/master/site/kubernetes/kube-addon.md#network-policy) </ins> that automatically monitors Kubernetes for any NetworkPolicy annotations on all namespaces and configures `iptables` rules to allow or block traffic as directed by the policies.

Discussion:
The following links for Weave Net are no longer viable, and should either be updated (e.g. pointing to the GitHub repo where it is now maintained, , which again, admittedly needs to be updated, but puts the onus on the project itself), or the page should be completely removed: Google link-to-highlight: ,by%20the%20policies. This issue resembles
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
Submitted PR with fix for review and merge. Can also remove page and associated links if this is regarded as a type of technical debt.
Page mentioned in the issue: /language en /kind bug
Change:
<li data-target="#myCarousel" data-slide-to="3"></li> </ol> <div class="carousel-inner" role="listbox"> <del> <div class="item active"> </del> <ins> <div class="item carousel-item active"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates1.svg" > </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates2.svg"> </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates3.svg"> </div> <del> <div class="item"> </del> <ins> <div class="item carousel-item"> </ins> <img src="/docs/tutorials/kubernetes-basics/public/images/module_06_rollingupdates4.svg"> </div> </div>

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 carousel is not working Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh
It seems the class of carousel images changed /assign