jiebi/CodeConvo huggingface dataset:
Change:
- bsalamat title: Assigning Pods to Nodes content_template: templates/concept <del> weight: 30 </del> <ins> weight: 50 </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 write a new concept page: (or possibly ) If the does not work as the page overview, consider tweaking the glossary entry so that it does. Then use a Hugo shortcode. Why is this needed ConfigMap is a core object type for Kubernetes; as such, it needs documenting properly. Comments Consider using as an example for page structure. It's better to put Task-style documentation in task pages such as and then hyperlink to those from the Concept page. Also see: /docs/user-guide/configmap need more details on ConfigMap updates Actionable user-guide/configmap does not document self-updating It's unclear what happens when ConfigMap is changed Need doc on using ConfigMap updates Wanted: ConfigMap Rollout Options Doc
/language en /sig apps
/priority important-longterm
This is worth prioritizing /priority important-soon
/remove-priority important-longterm
/project Doc Sprints
/assign
/unassign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
Still worth documenting /remove-lifecycle stale
/reopen let's collaborate on this!
Change:
You can [download Kubernetes](/releases/download/) to deploy a Kubernetes cluster on a local machine, into the cloud, or for your own datacenter. <ins> Several [Kubernetes components](/docs/concepts/overview/components/) such as `kube-apiserver` or `kube-proxy` can also be deployed as [container images](/releases/download/#container-images) within the cluster. It is **recommended** to run Kubernetes components as container images wherever that is possible, and to have Kubernetes manage those components. Components that run containers - notably, the kubelet - can't be included in this category. </ins> If you don't want to manage a Kubernetes cluster yourself, you could pick a managed service, including [certified platforms](/docs/setup/production-environment/turnkey-solutions/). There are also other standardized and custom solutions across a wide range of cloud and

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 Tell readers where they can find container images for components of Kubernetes. Why is this needed It's possible to run components of Kubernetes using containers; in fact, as a project we recommend this. However if you try to find where those images are using a search engine and plausible search queries, you don't find that information. Comments Relevant to and to /sig release
/triage accepted
Extra credit: update to link to the new text.
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]:
/remove-lifecycle rotten
is somewhat relevant.
/assign
Change:
<li><i>ClusterIP</i> (default) - Exposes the Service on an internal IP in the cluster. This type makes the Service only reachable from within the cluster.</li> <li><i>NodePort</i> - Exposes the Service on the same port of each selected Node in the cluster using NAT. Makes a Service accessible from outside the cluster using <code>&lt;NodeIP&gt;:&lt;NodePort&gt;</code>. Superset of ClusterIP.</li> <li><i>LoadBalancer</i> - Creates an external load balancer in the current cloud (if supported) and assigns a fixed, external IP to the Service. Superset of NodePort.</li> <del> <li><i>ExternalName</i> - Exposes the Service using an arbitrary name (specified by <code>externalName</code> in the spec) by returning a CNAME record with the name. No proxy is used. This type requires v1.7 or higher of <code>kube-dns</code>.</li> </del> <ins> <li><i>ExternalName</i> - Maps the Service to the contents of the <code>externalName</code> field (e.g. `foo.bar.example.com`), by returning a <code>CNAME</code> record with its value. No proxying of any kind is set up. This type requires v1.7 or higher of <code>kube-dns</code>, or CoreDNS version 0.0.8 or higher.</li> </ins> </ul> <p>More information about the different types of Services can be found in the <a href="/docs/tutorials/services/source-ip/">Using Source IP</a> tutorial. Also see <a href="/docs/concepts/services-networking/connect-applications-service">Connecting Applications with Services</a>.</p> <p>Additionally, note that there are some use cases with Services that involve not defining <code>selector</code> in the spec. A Service created without <code>selector</code> will also not create the corresponding Endpoints object. This allows users to manually map a Service to specific endpoints. Another possibility why there may be no selector is you are strictly using <code>type: ExternalName</code>.</p>

Discussion:
In this document () service type External name is explained as follows: ExternalName - Exposes the Service using an arbitrary name (specified by externalName in the spec) by returning a CNAME record with the name. No proxy is used. This type requires v1.7 or higher of kube-dns. This is misleading. The correct explanation could be (from ) as follows: ExternalName: Maps the Service to the contents of the externalName field (e.g. ), by returning a CNAME record with its value. No proxying of any kind is set up. This type requires v1.7 or higher of kube-dns, or coreDNS version 0.0.8 or higher.
/sig network /kind cleanup /triage accepted
Thanks - that's worth fixing /priority backlog
/assign
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Change:
border: 5px solid white; } <ins> body.cid-training #get-certified .col-nav { flex-flow: column nowrap; justify-content: space-between; } body.cid-training #get-certified .col-nav > * { flex-grow: 0; flex-shrink: 0; flex-basis: auto; } body.cid-training #get-certified .col-nav > br { flex-grow: 1; display: block; min-height: 2em; } body.cid-training #get-certified .col-nav a.button { flex: initial; width: auto; margin-left: auto; margin-right: auto; } </ins> @media only screen and (max-width: 840px) { <del> section.call-to-action .main-section .cta-image.cta-image-before, section.call-to-action .main-section .cta-image.cta-image-after { order: 0; } section.call-to-action .main-section .cta-image > img { </del> <ins> body.cid-training   section.call-to-action .main-section .cta-image > img { </ins> margin: 0; } <del> section.call-to-action .main-section .cta-image > img { </del> <ins> body.cid-training   section.call-to-action .main-section .cta-image > img { </ins> width: 7rem; } <del> section.call-to-action .main-section > div.call-to-action > div { </del> <ins> body.cid-training section.call-to-action .main-section > div.call-to-action > div { </ins> padding: 0 2rem 0 2rem; } <del> section.call-to-action .main-section .cta-text { flex: 2 0 75vw; max-width: initial; padding: 5vw 0 0 0; } </del> } /*  GO FULL WIDTH AT LESS THAN 480 PIXELS */ @media only screen and (max-width: 480px) { <del> .col { margin: 1% 0 1% 0%;} .col-container { flex-direction: column; } </del> <ins> body.cid-training .col { margin: 1% 0 1% 0%;} body.cid-training .col-container { flex-direction: column; } body.cid-training #logo-cks { order: initial; } </ins> } @media only screen and (max-width: 650px) { <del> .col-nav { </del> <ins> body.cid-training .col-nav { </ins> display: block; width: 100%; } <del> .col-container { flex-direction: column; } </del> <ins> body.cid-training .col-container { flex-direction: column; } </ins> } <del> .button{ </del> <ins> body.cid-training .button { </ins> max-width: 100%; box-sizing: border-box; margin: 1em 0;

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 Update to mention the new Kubernetes Security Specialist Certification Why is this needed There is a Kubernetes Security Specialist Certification, coming in November 2020. Comments /kind feature /language en
/priority important-soon
let's collaborate to put everything in place to make this into a Good First Issue.
Design-wise, it's much easier to place 2 certification logos than 3. do you have any thoughts on how to adjust things design-wise to incorporate the 3rd certification?
/sig security
/triage accepted
/cc
Change:
allocates resources for a pod based on its `requests`, and restricts the pod's resource usage based on the `limits` specified in the pod's containers. <ins> Changing the resource allocation for a running Pod requires the `InPlacePodVerticalScaling` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. The alternative is to delete the Pod and let the [workload controller](/docs/concepts/workloads/controllers/) make a replacement Pod that has a different resource requirement. </ins> For in-place resize of pod resources: - Container's resource `requests` and `limits` are _mutable_ for CPU and memory resources.

Discussion:
Not able to find which alpha feature gates for
/kind feature /triage accepted // +featureGate=InPlacePodVerticalScaling // +optional ResizePolicy []ContainerResizePolicy This field is controlled by the feature gate . It looks like we need to add a feature gate description. Does anyone want to help? /help
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 : /kind feature /triage accepted /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
There is a blog under review. I do concur that some docs are needed for such an important feature.
We should mention within didn't cover this detail.
InPlacePodVerticalScaling in also missing in
Fix coming in
Hi , as I am unable see the changes can I add it to the page?
The feature gate issue has been fixed but the feature description needs some more formal documentation. Please feel free to provide some inputs.
sure so we need to add the featureGate thing? here
It is not limited to the feature gate. It is about the feature. We are supposed to provide some brief introduction to this feature. Currently we have some texts on it, but those texts are provided as a blog (see ). Some of the blogs could have been part of the docs task page ().
thanks for clarifying
Note that this is the same issue as
Change:
title: "弃用 Dockershim 的常见问题" date: 2020-12-02 slug: dockershim-faq <del> aliases: [ '/dockershim' ] </del> <ins> aliases: [ '/zh/dockershim' ] </ins> --- <!-- layout: blog

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 link at the top of the homepage () seems to currently redirect to I assume this is the same issue as Proposed Solution: Remove the /dockershim alias from the ZH blog page. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
Same symptoms, different PR. /triage accepted Thanks. /priority important-soon
/assign
Change:
To enable the rolling update feature of a DaemonSet, you must set its `.spec.updateStrategy.type` to `RollingUpdate`. <del> You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/concepts/workloads/controllers/deployment/#max-unavailable) </del> <ins> You may want to set [`.spec.updateStrategy.rollingUpdate.maxUnavailable`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) </ins> (default to 1), <del> [`.spec.minReadySeconds`](/docs/concepts/workloads/controllers/deployment/#min-ready-seconds) (default to 0) and </del> <ins> [`.spec.minReadySeconds`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (default to 0) and </ins> [`.spec.updateStrategy.rollingUpdate.maxSurge`](/docs/reference/kubernetes-api/workload-resources/daemon-set-v1/#DaemonSetSpec) (a beta feature and defaults to 0) as well.

Discussion:
In , the para says that But after I click the page, I find no and I can only see . I also try in my env, the updateStrategy` does not. error: error validating "dep-": error validating data: ValidationError(): unknown field "updateStrategy" in ; if you choose to ignore these errors, turn validation off with --validate=false Is this document outdated? I can make a fix if it is.
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 Both DaemonSet and Deployment use these 3 fields, linking to the deployment creates some confusion or misleading. I think we could link and to , same as refer to this similar issue for more info: see the reference api for
/good-first-issue
/remove-good-first-issue We only add that label for issues that have a barrier to entry that is zero or close to it. I'd expect to see at least: a link to the page that needs fixing a language label on the issue clear advice on the route to a fix / no concerns that there might be different options and the person working on it must choose /language en
Thanks, for this information. Actually, I forgot to mention the page in my comment, This is the page we have to update:
Yeah. I agree the new link will be better.
/assign
Change:
$ kubectl config view ``` <del> Many of the [examples](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/) provide an introduction to using kubectl and complete documentation is found in the [kubectl manual](/docs/user-guide/kubectl/index). </del> <ins> Many of the [examples](/docs/user-guide/kubectl-cheatsheet) provide an introduction to using kubectl and complete documentation is found in the [kubectl manual](/docs/user-guide/kubectl-overview). </ins> ### Directly accessing the REST API

Discussion:
The URL can not access at the doc use the Go client library, and create a client using the rest.InClusterConfig() and kubernetes.NewForConfig()functions. They handle locating and authenticating to the apiserver. I think we should change this URL to
I can help fix it
This is fixed now and can be closed.
Change:
- [`pod-security.kubernetes.io/audit-violations`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-audit-violations) - [`pod-security.kubernetes.io/enforce-policy`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-enforce-policy) - [`pod-security.kubernetes.io/exempt`](/docs/reference/labels-annotations-taints/audit-annotations/#pod-security-kubernetes-io-exempt) <ins> - [`validation.policy.admission.k8s.io/validation_failure`](/docs/reference/labels-annotations-taints/audit-annotations/#validation-policy-admission-k8s-io-validation-failure) </ins> See more details on [Audit Annotations](/docs/reference/labels-annotations-taints/audit-annotations/). ## kubeadm

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: documents the audit annotation ; however, it is missing from (which is the formal document we use to record registrations). Proposed Solution: Update to mention the ValidatingAdmissionPolicy audit annotation. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig api-machinery /language en /priority backlog /triage accepted /help
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 : This is a Bug Report <!-- See for guidance on writing an actionable issue description. --Problem: documents the audit annotation ; however, it is missing from (which is the formal document we use to record registrations). Update to mention the ValidatingAdmissionPolicy audit annotation. <!--Kubernetes Version:--/sig api-machinery /language en /priority backlog /triage accepted /help </details
hey ,please review my change , I am trying to solve this
/assign
Fix merged as part of /close
Closing this issue. <detailsIn response to : Fix merged as part of 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:
</form> </div> <div id="content-desktop"></div> <del> {{ end }} </del> <ins> {{ end -}} </ins> <nav class="collapse td-sidebar-nav{{ if .Site.Params.ui.sidebar_menu_foldable }} foldable-nav{{ end }}" id="td-section-nav"> <!-- {{ if  (gt (len .Site.Home.Translations) 0) }} <div class="nav-item dropdown d-block d-lg-none">

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: I saw by accident very big page files on Kubernetes documentation. For example is lines long and the lines 286- are taken for the sidebar menu containing a lot of whitespace (do right-mouse and "view page source"). Proposed Solution: I reported the issue already with Docsy: and proposed a pull request. But this will not be enough. Somebody has to update too. 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
/assign
The hugo Docsy theme side issue is resolved and closed: When will somebody review and implement pull request ? You can do this separate from a Docsy theme update at It is only about (huge) whitespace reduction, not a functional change. But k8s website users will benefit in user experience.
Change:
- Start or help with a [localization](/docs/contribute/localization/). --> <del> ## 下一步 </del> <ins> ## 下一步 {#next-teps} </ins> - 学习在仓库的[本地克隆中工作](/zh/docs/contribute/new-content/open-a-pr/#fork-the-repo)。 - 为[发行版的特性](/zh/docs/contribute/new-content/new-features/)编写文档。

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: Chinese page is different with English version page. Proposed Solution: Update Chinese page Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language zh /assign
thanks reviews and approvement from xichengliudui, tengqm and idealhack
Change:
If you have already created the cluster you must adapt it by doing the following: - Find and edit the `kubelet-config-{{< skew latestVersion >}}` ConfigMap in the `kube-system` namespace. <del> In that ConfigMap, the `config` key has a </del> <ins> In that ConfigMap, the `kubelet` key has a </ins> [KubeletConfiguration](/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration) document as its value. Edit the KubeletConfiguration document to set `serverTLSBootstrap: true`. - On each node, add the `serverTLSBootstrap: true` field in `/var/lib/kubelet/config.yaml`

Discussion:
Hi, In this document, In this section It is mentioned that in order to make the metrics-server works probably, you have to edit the ConfigMap as shown But in a kubeadm deployed cluster, there is no key in the ConfigMap .. There is this: Which you can not edit as described in the document. The metrics-server is not working due to this issue..
thanks for the report. the key should be renamed from to in PRs welcome. /triage accepted /sig cluster-lifecycle /kind bug
/help
This request has been marked as needing help from a contributor. 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 : /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