Question: It's possible to configure `kubeadm join` with a configuration file instead of command line flags, and some more advanced features may only be available as configuration file options. This file is passed using the `--config` flag and it must <del> contain a `JoinConfiguration` structure. </del> <ins> contain a `JoinConfiguration` structure. Mixing `--config` with others flags may not be allowed in some cases. </ins> <del> To print the default values of `JoinConfiguration` run the following command: </del> <ins> The default configuration can be printed out using the [kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. </ins> <del> ```shell kubeadm config print join-defaults ``` </del> <ins> If your configuration is not using the latest version it is **recommended** that you migrate using the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. </ins> <del> For details on individual fields in `JoinConfiguration` see [the godoc](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#JoinConfiguration). </del> <ins> For more information on the fields and usage of the configuration you can navigate to our API reference page and pick a version from [the list](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#pkg-subdirectories). </ins> ## {{% heading "whatsnext" %}}

It is very difficult to find any links to the . This is a huge roadblock to new users trying to do anything custom with kubeadm. As a new user, I don't expect to have to read about to find information about configuring the tool. To someone who is unfamiliar with the project, that seems like more advanced documentation than I should need, and therefore not somewhere I would expect to find basic config file documentation. I also was able to find the long before I found the more user-friendly documentation, which made it seem like that was the only documentation that exists. I would expect a link to those docs to be available on the kubeadm-config page, as well as where config files are mentioned in the kubeadm-init and kubeadm-join pages.
/language en
it seems you have missed these two sections: and for these commands the kubeadm API is actually the most important for. linking the command line reference page to the API makes sense. but instead of linking to a particular version of the API we should link to: and let users navigate to a particular API version. this is done with the idea that can also migrate v1beta1 -v1beta2. PRs welcome. thanks /sig cluster-lifecycle /priority backlog /help wanted
. I will keep most of the discussion over there for now.
/remove-help /assign /lifecycle-active sending a PR with:


Question: <ins> --- layout: blog title: '在 Ingress-NGINX v1.2.0 中提高安全标准' date: 2022-04-28 slug: ingress-nginx-1-2-0 --- <!-- layout: blog title: 'Increasing the security bar in Ingress-NGINX v1.2.0' date: 2022-04-28 slug: ingress-nginx-1-2-0 --> <!-- **Authors:** Ricardo Katz (VMware), James Strong (Chainguard) --> **作者：** Ricardo Katz (VMware), James Strong (Chainguard) <!-- The [Ingress](/docs/concepts/services-networking/ingress/) may be one of the most targeted components of Kubernetes. An Ingress typically defines an HTTP reverse proxy, exposed to the Internet, containing multiple websites, and with some privileged access to Kubernetes API (such as to read Secrets relating to TLS certificates and their private keys). --> [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) 可能是 Kubernetes 最容易受攻击的组件之一。 Ingress 通常定义一个 HTTP 反向代理，暴露在互联网上，包含多个网站，并具有对 Kubernetes API 的一些特权访问（例如读取与 TLS 证书及其私钥相关的 Secret）。 <!-- While it is a risky component in your architecture, it is still the most popular way to properly expose your services. --> 虽然它是架构中的一个风险组件，但它仍然是正常公开服务的最流行方式。 <!-- Ingress-NGINX has been part of security assessments that figured out we have a big problem: we don't do all proper sanitization before turning the configuration into an `nginx.conf` file, which may lead to information disclosure risks. --> Ingress-NGINX 一直是安全评估的重头戏，这类评估会发现我们有着很大的问题： 在将配置转换为 `nginx.conf` 文件之前，我们没有进行所有适当的清理，这可能会导致信息泄露风险。 <!-- While we understand this risk and the real need to fix this, it's not an easy process to do, so we took another approach to reduce (but not remove!) this risk in the current (v1.2.0) release. --> 虽然我们了解此风险以及解决此问题的真正需求，但这并不是一个容易的过程， 因此我们在当前(v1.2.0)版本中采取了另一种方法来减少（但不是消除！）这种风险。 <!-- ## Meet Ingress NGINX v1.2.0 and the chrooted NGINX process --> ## 了解 Ingress NGINX v1.2.0 和 chrooted NGINX 进程 <!-- One of the main challenges is that Ingress-NGINX runs the web proxy server (NGINX) alongside the Ingress controller (the component that has access to Kubernetes API that and that creates the `nginx.conf` file). --> 主要挑战之一是 Ingress-NGINX 运行着 Web 代理服务器（NGINX），并与 Ingress 控制器一起运行 （后者是一个可以访问 Kubernetes API 并创建 `nginx.conf` 的组件）。 <!-- So, NGINX does have the same access to the filesystem of the controller (and Kubernetes service account token, and other configurations from the container). While splitting those components is our end goal, the project needed a fast response; that lead us to the idea of using `chroot()`. --> 因此，NGINX 对控制器的文件系统（和 Kubernetes 服务帐户令牌，以及容器中的其他配置）具有相同的访问权限。 虽然拆分这些组件是我们的最终目标，但该项目需要快速响应；这让我们想到了使用 `chroot()`。 <!-- Let's take a look into what an Ingress-NGINX container looked like before this change: --> 让我们看一下 Ingress-NGINX 容器在此更改之前的样子： ![Ingress NGINX pre chroot](ingress-pre-chroot.png) <!-- As we can see, the same container (not the Pod, the container!) that provides HTTP Proxy is the one that watches Ingress objects and writes the Container Volume --> 正如我们所见，用来提供 HTTP Proxy 的容器（不是 Pod，是容器！）也是是监视 Ingress 对象并将数据写入容器卷的容器。 <!-- Now, meet the new architecture: --> 现在，见识一下新架构： ![Ingress NGINX post chroot](ingress-post-chroot.png) <!-- What does all of this mean? A basic summary is: that we are isolating the NGINX service as a container inside the controller container. --> 这一切意味着什么？一个基本的总结是：我们将 NGINX 服务隔离为控制器容器内的容器。 <!-- While this is not strictly true, to understand what was done here, it's good to understand how Linux containers (and underlying mechanisms such as kernel namespaces) work. You can read about cgroups in the Kubernetes glossary: [`cgroup`](https://kubernetes.io/docs/reference/glossary/?fundamental=true#term-cgroup) and learn more about cgroups interact with namespaces in the NGINX project article [What Are Namespaces and cgroups, and How Do They Work?](https://www.nginx.com/blog/what-are-namespaces-cgroups-how-do-they-work/). (As you read that, bear in mind that Linux kernel namespaces are a different thing from [Kubernetes namespaces](/docs/concepts/overview/working-with-objects/namespaces/)). --> 虽然这并不完全正确，但要了解这里所做的事情，最好了解 Linux 容器（以及内核命名空间等底层机制）是如何工作的。 你可以在 Kubernetes 词汇表中阅读有关 cgroup 的信息：[`cgroup`](/zh-cn/docs/reference/glossary/?fundamental=true#term-cgroup)， 并在 NGINX 项目文章[什么是命名空间和 cgroup，以及它们如何工作？](https://www.nginx.com/blog/what-are-namespaces-cgroups-how-do-they-work/) 中了解有关 cgroup 与命名空间交互的更多信息。（当你阅读时，请记住 Linux 内核命名空间与 [Kubernetes 命名空间](/zh-cn/docs/concepts/overview/working-with-objects/namespaces/)不同）。 <!-- ## Skip the talk, what do I need to use this new approach? --> ## 跳过谈话，我需要什么才能使用这种新方法？ <!-- While this increases the security, we made this feature an opt-in in this release so you can have time to make the right adjustments in your environment(s). This new feature is only available from release v1.2.0 of the Ingress-NGINX controller. --> 虽然这增加了安全性，但我们在这个版本中把这个功能作为一个选项，这样你就可以有时间在你的环境中做出正确的调整。 此新功能仅在 Ingress-NGINX 控制器的 v1.2.0 版本中可用。 <!-- There are two required changes in your deployments to use this feature: * Append the suffix "-chroot" to the container image name. For example: `gcr.io/k8s-staging-ingress-nginx/controller-chroot:v1.2.0` * In your Pod template for the Ingress controller, find where you add the capability `NET_BIND_SERVICE` and add the capability `SYS_CHROOT`. After you edit the manifest, you'll see a snippet like: --> 要使用这个功能，在你的部署中有两个必要的改变： * 将后缀 "-chroot" 添加到容器镜像名称中。例如：`gcr.io/k8s-staging-ingress-nginx/controller-chroot:v1.2.0` * 在你的 Ingress 控制器的 Pod 模板中，找到添加 `NET_BIND_SERVICE` 权能的位置并添加 `SYS_CHROOT` 权能。 编辑清单后，你将看到如下代码段： ```yaml capabilities: drop: - ALL add: - NET_BIND_SERVICE - SYS_CHROOT ``` <!-- If you deploy the controller using the official Helm chart then change the following setting in `values.yaml`: --> 如果你使用官方 Helm Chart 部署控制器，则在 `values.yaml` 中更改以下设置： ```yaml controller: image: chroot: true ``` <!-- Ingress controllers are normally set up cluster-wide (the IngressClass API is cluster scoped). If you manage the Ingress-NGINX controller but you're not the overall cluster operator, then check with your cluster admin about whether you can use the `SYS_CHROOT` capability, **before** you enable it in your deployment. --> Ingress 控制器通常部署在集群作用域（IngressClass API 是集群作用域的）。 如果你管理 Ingress-NGINX 控制器但你不是整个集群的操作员， 请在部署中启用它**之前**与集群管理员确认你是否可以使用 `SYS_CHROOT` 功能。 <!-- ## OK, but how does this increase the security of my Ingress controller? Take the following configuration snippet and imagine, for some reason it was added to your `nginx.conf`: --> ## 好吧，但这如何能提高我的 Ingress 控制器的安全性呢？ 以下面的配置片段为例，想象一下，由于某种原因，它被添加到你的 `nginx.conf` 中： ``` location /randomthing/ { alias /; autoindex on; } ``` <!-- If you deploy this configuration, someone can call `http://website.example/randomthing` and get some listing (and access) to the whole filesystem of the Ingress controller. Now, can you spot the difference between chrooted and non chrooted Nginx on the listings below? --> 如果你部署了这种配置，有人可以调用 `http://website.example/randomthing` 并获取对 Ingress 控制器的整个文件系统的一些列表（和访问权限）。 现在，你能在下面的列表中发现 chroot 处理过和未经 chroot 处理过的 Nginx 之间的区别吗？ | 不额外调用 `chroot()`             | 额外调用 `chroot()` | |----------------------------|--------| | `bin`                      | `bin`  | | `dev`                      | `dev`  | | `etc`                      | `etc`  | | `home`                     |        | | `lib`                      | `lib`  | | `media`                    |        | | `mnt`                      |        | | `opt`                      | `opt`  | | `proc`                     | `proc` | | `root`                     |        | | `run`                      | `run`  | | `sbin`                     |        | | `srv`                      |        | | `sys`                      |        | | `tmp`                      | `tmp`  | | `usr`                      | `usr`  | | `var`                      | `var`  | | `dbg`                      |        | | `nginx-ingress-controller` |        | | `wait-shutdown`            |        | <!-- The one in left side is not chrooted. So NGINX has full access to the filesystem. The one in right side is chrooted, so a new filesystem with only the required files to make NGINX work is created. --> 左侧的那个没有 chroot 处理。所以 NGINX 可以完全访问文件系统。右侧的那个经过 chroot 处理， 因此创建了一个新文件系统，其中只有使 NGINX 工作所需的文件。 <!-- ## What about other security improvements in this release? --> ## 此版本中的其他安全改进如何？ <!-- We know that the new `chroot()` mechanism helps address some portion of the risk, but still, someone can try to inject commands to read, for example, the `nginx.conf` file and extract sensitive information. --> 我们知道新的 `chroot()` 机制有助于解决部分风险，但仍然有人可以尝试注入命令来读取，例如 `nginx.conf` 文件并提取敏感信息。 <!-- So, another change in this release (this is opt-out!) is the _deep inspector_. We know that some directives or regular expressions may be dangerous to NGINX, so the deep inspector checks all fields from an Ingress object (during its reconciliation, and also with a [validating admission webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)) to verify if any fields contains these dangerous directives. --> 所以，这个版本的另一个变化（可选择取消）是 **深度探测（Deep Inspector）**。 我们知道某些指令或正则表达式可能对 NGINX 造成危险，因此深度探测器会检查 Ingress 对象中的所有字段 （在其协调期间，并且还使用[验证准入 webhook](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)) 验证是否有任何字段包含这些危险指令。 <!-- The ingress controller already does this for annotations, and our goal is to move this existing validation to happen inside deep inspection as part of a future release. --> Ingress 控制器已经通过注解做了这个工作，我们的目标是把现有的验证转移到深度探测中，作为未来版本的一部分。 <!-- You can take a look into the existing rules in [https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go](https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go). --> 你可以在 [https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go](https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go) 中查看现有规则。 <!-- Due to the nature of inspecting and matching all strings within relevant Ingress objects, this new feature may consume a bit more CPU. You can disable it by running the ingress controller with the command line argument `--deep-inspect=false`. --> 由于检查和匹配相关 Ingress 对象中的所有字符串的性质，此新功能可能会消耗更多 CPU。 你可以通过使用命令行参数 `--deep-inspect=false` 运行 Ingress 控制器来禁用它。 <!-- ## What's next? This is not our final goal. Our final goal is to split the control plane and the data plane processes. In fact, doing so will help us also achieve a [Gateway](https://gateway-api.sigs.k8s.io/) API implementation, as we may have a different controller as soon as it "knows" what to provide to the data plane (we need some help here!!) --> ## 下一步是什么? 这不是我们的最终目标。我们的最终目标是拆分控制平面和数据平面进程。 事实上，这样做也将帮助我们实现 [Gateway](https://gateway-api.sigs.k8s.io/) API 实现， 因为一旦它“知道”要提供什么，我们可能会有不同的控制器 数据平面（我们需要一些帮助！！） <!-- Some other projects in Kubernetes already take this approach (like [KPNG](https://github.com/kubernetes-sigs/kpng), the proposed replacement for `kube-proxy`), and we plan to align with them and get the same experience for Ingress-NGINX. --> Kubernetes 中的其他一些项目已经采用了这种方法（如 [KPNG](https://github.com/kubernetes-sigs/kpng)， 建议替换 `kube-proxy`），我们计划与他们保持一致，并为 Ingress-NGINX 获得相同的体验。 <!-- ## Further reading If you want to take a look into how chrooting was done in Ingress NGINX, take a look into [https://github.com/kubernetes/ingress-nginx/pull/8337](https://github.com/kubernetes/ingress-nginx/pull/8337) The release v1.2.0 containing all the changes can be found at [https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0) --> ## 延伸阅读 如果你想了解如何在 Ingress NGINX 中完成 chrooting，请查看 [https://github.com/kubernetes/ingress-nginx/pull/8337](https://github.com/kubernetes/ingress-nginx/pull/8337)。 包含所有更改的版本 v1.2.0 可以在以下位置找到 [https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0) </ins>

This is a Feature Report Problem: misssing Chinese translation docs: content/en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX Proposed Solution: add Chinese translation docs in website Kubernetes Blog Comments /language zh /assign
English page:
/triage accepted


Question: cpu: 100m memory: 100Mi ports: <del> - containerPort: 80 </del>  No newline at end of file <ins> - containerPort: 80 </ins>

The yaml file in "Creating the Guestbook Frontend Deployment" uses an image no more available ( ) I solved the issue by using Here is the working version I used!
Hey Can you share us a pic of the solved issue here?
/kind bug
/triage accepted
/assign


Question: cpu: 100m memory: 100Mi ports: <del> - containerPort: 80 </del>  No newline at end of file <ins> - containerPort: 80 </ins>

The image file download for the frontend- is currently failing. I fixed by changing it to: image: us-
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
This looks similar to issue(s) and I think it is a duplicate. /triage duplicate
Fixes are welcome; please visit to discuss and track that work.
Closing this issue, resolved by PR
/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


Question: <ins> --- title: Tutorials main_menu: true weight: 60 content_template: templates/concept --- {{% capture overview %}} Questa sezione della documentazione di Kubernetes contiene i tutorials. Un tutorial mostra come raggiungere un obiettivo più complesso di un singolo [task](/docs/tasks/). Solitamente un tutorial ha diverse sezioni, ognuna delle quali consiste in una sequenza di più task. Prima di procedere con vari tutorial, raccomandiamo di aggiungere il [Glossario](/docs/reference/glossary/) ai tuoi bookmark per riferimenti successivi. {{% /capture %}} {{% capture body %}} ## Per cominciare * [Kubernetes Basics](/docs/tutorials/kubernetes-basics/) è un approfondito tutorial che aiuta a capire cosa è Kubernetes e che permette di testare in modo interattivo alcune semplici funzionalità di Kubernetes. * [Introduction to Kubernetes (edX)](https://www.edx.org/course/introduction-kubernetes-linuxfoundationx-lfs158x#) * [Hello Minikube](/docs/tutorials/hello-minikube/) ## Configurazione * [Configurare Redis utilizzando una ConfigMap](/docs/tutorials/configuration/configure-redis-using-configmap/) ## Stateless Applications * [Esporre un External IP Address per permettere l'accesso alle applicazioni nel Cluster](/docs/tutorials/stateless-application/expose-external-ip-address/) * [Esempio: Rilasciare l'applicazione PHP Guestbook con Redis](/docs/tutorials/stateless-application/guestbook/) ## Stateful Applications * [StatefulSet Basics](/docs/tutorials/stateful-application/basic-stateful-set/) * [Esempio: WordPress e MySQL con i PersistentVolumes](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/) * [Esempio: Rilasciare Cassandra con i StatefulSets](/docs/tutorials/stateful-application/cassandra/) * [Eseguire ZooKeeper, un sistema distribuito CP](/docs/tutorials/stateful-application/zookeeper/) ## CI/CD Pipelines * [Set Up a CI/CD Pipeline with Kubernetes Part 1: Overview](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/5/set-cicd-pipeline-kubernetes-part-1-overview) * [Set Up a CI/CD Pipeline with a Jenkins Pod in Kubernetes (Part 2)](https://www.linux.com/blog/learn/chapter/Intro-to-Kubernetes/2017/6/set-cicd-pipeline-jenkins-pod-kubernetes-part-2) * [Run and Scale a Distributed Crossword Puzzle App with CI/CD on Kubernetes (Part 3)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/run-and-scale-distributed-crossword-puzzle-app-cicd-kubernetes-part-3) * [Set Up CI/CD for a Distributed Crossword Puzzle App on Kubernetes (Part 4)](https://www.linux.com/blog/learn/chapter/intro-to-kubernetes/2017/6/set-cicd-distributed-crossword-puzzle-app-kubernetes-part-4) ## Clusters * [AppArmor](/docs/tutorials/clusters/apparmor/) ## Servizi * [Utilizzare Source IP](/docs/tutorials/services/source-ip/) {{% /capture %}} {{% capture whatsnext %}} Se sei interessato a scrivere un tutorial, vedi [Utilizzare i Page Templates](/docs/home/contribute/page-templates/) per informazioni su come creare una tutorial page e sul tutorial template. {{% /capture %}} </ins>

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 Italian Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language it
/kind bug
/assign /lifecycle active


Question: <ins> apiVersion: apps/v1 kind: Deployment metadata: name: patch-demo spec: replicas: 2 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: patch-demo-ctr image: nginx tolerations: - effect: NoSchedule key: dedicated value: test-team </ins>

This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs /area localization
/assign
/unassign


Question: * One or more machines running one of: - Ubuntu 16.04+ - Debian 9+ <del> - CentOS 7 - Red Hat Enterprise Linux (RHEL) 7 </del> <ins> - CentOS 7+ - Red Hat Enterprise Linux (RHEL) 7+ </ins> - Fedora 25+ - HypriotOS v1.0.1+ - Flatcar Container Linux (tested with 2512.3.0)

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 site '' does not list RHEL 8 or CentOS 8 as a supported os. Only RHEL 7 / CentOS 7 is listed. Both os versions released over a year ago and Google provides a lot of guides for how to install Kubernetes on CentOS 8. Please a) add RHEL 8 / CentOS 8 to the list of supported platforms or b) if there is a reason for this, explain it on the website. Why is this needed It is confusing when only an old os version ist supported without any further explanation. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --
it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /sig cluster-lifecycle /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 : it's a matter of users testing and confirming these distros work fine. if you have tested them feel free to send a pull request to update. /help </details
/triage accepted
/kind feature /retitle Document kubeadm for RHEL 8
I had a look at it and sent in a pull request for this. Add forward compatibility in RHEL / CentOS to the list of supported platforms.
/assign


Question:
 --- title: Actualiza Objetos del API en su sitio (in Place) usando kubectl patch description:  Usa kubectl patch para actualizar objetos del API de kubernetes sin reemplazarlos. Usa strategic merge patch o JSON merge patch. content_type: task weight: 50 ---  Esta tarea muestra cómo utilizar `kubectl patch` para actualizar un objeto del API sin reemplazarlo. Los ejercicios de esta tarea demuestran el uso de "strategic merge patch" y "JSON merge patch" ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}  ## Usa strategic merge patch para actualizar un Deployment Aquí está el archivo de configuración para un Deployment con dos réplicas. Cada réplica es un Pod que tiene un contenedor: {{% code_sample file="application/deployment-patch.yaml" %}} Crea el Deployment: ```shell kubectl apply -f https://k8s.io/examples/application/deployment-patch.yaml ``` Revisa los Pods asociados con tu Deployment: ```shell kubectl get pods ``` El resultado muestra que el Deployment tiene dos Pods. El `1/1` indica que cada Pod tiene un contenedor: ``` NAME                        READY     STATUS    RESTARTS   AGE patch-demo-28633765-670qr   1/1       Running   0          23s patch-demo-28633765-j5qs3   1/1       Running   0          23s ``` Toma nota de los nombres de los Pods que se están ejecutando. Verás que estos Pods son terminados y reemplazados posteriormente. En este punto cada Pod tiene un contenedor que ejecuta una imagen de nginx. Ahora supón que quieres que cada Pod tenga dos contenedores: uno que ejecute nginx y otro que ejecute redis. Crea un archivo llamado `patch-file.yaml` con el siguiente contenido: ```yaml spec: template: spec: containers: - name: patch-demo-ctr-2 image: redis ``` Modifica tu Deployment usando Patch: ```shell kubectl patch deployment patch-demo --patch-file patch-file.yaml ``` Revisa el Deployment modificado: ```shell kubectl get deployment patch-demo --output yaml ``` El resultado muestra que el PodSpec del Deployment tiene dos contenedores: ```yaml containers: - image: redis imagePullPolicy: Always name: patch-demo-ctr-2 ... - image: nginx imagePullPolicy: Always name: patch-demo-ctr ... ``` Revisa los Pods asociados con tu Deployment modificado: ```shell kubectl get pods ``` El resultado muestra que los Pods tienen un nombre distinto a los que se estaban ejecutando anteriormente. El Deployment terminó los Pods viejos y creo dos nuevos que cumplen con la especificación actualizada del Deployment. El `2/2` indica que cada Pod tiene dos contenedores: ``` NAME                          READY     STATUS    RESTARTS   AGE patch-demo-1081991389-2wrn5   2/2       Running   0          1m patch-demo-1081991389-jmg7b   2/2       Running   0          1m ``` Un vistazo más de cerca a uno de los Pods del patch-demo: ```shell kubectl get pod <your-pod-name> --output yaml ``` El resultado muestra que el Pod tienen dos contenedores: uno ejecutando nginx y otro redis: ``` containers: - image: redis ... - image: nginx ... ``` ### Notas acerca de strategic merge patch El patch que hiciste en el ejercicio anterior se llama *strategic merge patch*. Toma en cuenta que el path no reemplazó la lista `containers`. Sino que agregó un contenedor nuevo a la lista. En otras palabras, la lista en el patch fue agregada a la lista ya existente. Esto no es lo que pasa siempre que se utiliza strategic merge patch en una lista. En algunos casos la lista existente podría ser reemplazada en lugar de unir ambas. Con strategic merge patch, la lista existente puede ser reemplazada o unida con la nueva dependiendo de la estrategia de patch. La estrategia de patch se especifica en el valor de la clave `patchStrategy`en un campo tag del código fuente de Kubernetes. Por ejemplo el campo `Containers` de la struct `PodSpec` tiene un valor de `merge` en su clave `patchStrategy`: ```go type PodSpec struct { ... Containers []Container `json:"containers" patchStrategy:"merge" patchMergeKey:"name" ...` ... } ``` También puedes consultar la estrategia de patch en [OpenApi spec](https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json): ```yaml "io.k8s.api.core.v1.PodSpec": { ..., "containers": { "description": "List of containers belonging to the pod.  ...." }, "x-kubernetes-patch-merge-key": "name", "x-kubernetes-patch-strategy": "merge" } ```  Y puedes consultar la estrategia de patch en la [Documentación del API Kubernetes](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core). Crea un archivo llamado `patch-file-tolerations.yaml` que tenga el siguiente contenido: ```yaml spec: template: spec: tolerations: - effect: NoSchedule key: disktype value: ssd ``` Modifica tu Deployment utilizando Patch: ```shell kubectl patch deployment patch-demo --patch-file patch-file-tolerations.yaml ``` Revisa el Deployment modificado: ```shell kubectl get deployment patch-demo --output yaml ``` El resultado muestra que el PodsSpec del Deployment tiene solo un Toleration: ```yaml tolerations: - effect: NoSchedule key: disktype value: ssd ``` Toma en cuenta que la lista de `tolerations` en el PodSpec fue reemplazada, no unida. Esto es porque el campo de Tolerations del PodSpec no tiene una clave `patchStrategy` en su campo de tag. por lo tanto strategic merge patch utiliza la estrategia de patch por defecto, la cual es `replace`. ```go type PodSpec struct { ... Tolerations []Toleration `json:"tolerations,omitempty" protobuf:"bytes,22,opt,name=tolerations"` ... } ``` ## Usa JSON merge patch para actualizar un Deployment Un strategic merge patch es distinto a un [JSON merge patch](https://tools.ietf.org/html/rfc7386). Con JSON merge patch, si quieres actualizar una lista tienes que especificar la lista nueva en su totalidad y reemplazar la lista existente con la lista nueva. El comando `kubectl patch` tiene un parámetro `type` que acepta los siguientes valores:

Valor del parámetro	tipo de unión

json	JSON Patch, RFC 6902

merge	JSON Merge Patch, RFC 7386

strategic	Strategic merge patch

 Para una comparación entre JSON patch y JSON merge patch, revisa [JSON Patch y JSON Merge Patch](https://erosb.github.io/post/json-patch-vs-merge-patch/). El valor predeterminado para el parámetro `type` es  `strategic`. Entonces en el ejercicio anterior hiciste un strategic merge patch. A continuación haz un JSON merge path en el mismo Deployment. Crea un archivo llamado `patch-file-2.yaml` que tenga el siguiente contenido: ```yaml spec: template: spec: containers: - name: patch-demo-ctr-3 image: gcr.io/google-samples/node-hello:1.0 ``` En el comando patch configura el valor de `type` como `merge` ```shell kubectl patch deployment patch-demo --type merge --patch-file patch-file-2.yaml ``` Revisa el Deployment modificado: ```shell kubectl get deployment patch-demo --output yaml ``` La lista `containers` que especificaste en el patch solo tiene un contenedor. el resultado muestra que tu lista con un contenedor reemplazó a la lista `containers` preexistente. ```yaml spec: containers: - image: gcr.io/google-samples/node-hello:1.0 ... name: patch-demo-ctr-3 ``` Revisa los Pods en ejecución: ```shell kubectl get pods ``` En el resultado se puede ver que los Pods existentes fueron terminados y se crearon Pods nuevos. El `1/1` indica que cada Pod nuevo esta ejecutando un solo contenedor. ```shell NAME                          READY     STATUS    RESTARTS   AGE patch-demo-1307768864-69308   1/1       Running   0          1m patch-demo-1307768864-c86dc   1/1       Running   0          1m ``` ## Usa strategic merge patch para actualizar un Deployment utilizando la estrategia retainKeys Aquí esta el archivo de configuración para un Deployment que usa la estrategia `RollingUpdate`: {{% code_sample file="application/deployment-retainkeys.yaml" %}} Crea el Deployment: ```shell kubectl apply -f https://k8s.io/examples/application/deployment-retainkeys.yaml ``` En este punto, el Deployment es creado y está usando la estrategia `RollingUpdate`. Crea un archivo llamado `patch-file-no-retainkeys.yaml` con el siguiente contenido: ```yaml spec: strategy: type: Recreate ``` Modifica tu Deployment: ```shell kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-no-retainkeys.yaml ``` En el resultado se puede ver que no es posible definir el `type` como `Recreate` cuando hay un value definido para `spec.strategy.rollingUpdate`: ``` The Deployment "retainkeys-demo" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate' ``` La forma para quitar el valor para `spec.strategy.rollingUpdate` al momento de cambiar el valor `type` es usar la estrategia `retainKeys` para el strategic merge. Crea otro archivo llamado `patch-file-retainkeys.yaml` con el siguiente contenido: ```yaml spec: strategy: $retainKeys: - type type: Recreate ``` Con este Patch definimos que solo queremos conservar la clave `type` del objeto `strategy`. Por lo tanto la clave `rollingUpdate` será eliminada durante la operación de modificación. Modifica tu Deployment de nuevo con este nuevo Patch: ```shell kubectl patch deployment retainkeys-demo --type strategic --patch-file patch-file-retainkeys.yaml ``` Revisa el contenido del Deployment: ```shell kubectl get deployment retainkeys-demo --output yaml ``` El resultado muestra que el objeto `strategy` en el Deployment ya no contiene la clave `rollingUpdate`: ```yaml spec: strategy: type: Recreate template: ``` ### Notas acerca de strategic merge patch utilizando la estrategia retainKeys La modificación realizada en el ejercicio anterior tiene el nombre de *strategic merge patch con estrategia retainKeys*. Este método introduce una nueva directiva `$retainKeys` que tiene las siguientes estrategias: - Contiene una lista de strings. - Todos los campos que necesiten ser preservados deben estar presentes en la lista `$retainKeys`. - Todos los campos que estén presentes serán combinados con el objeto existente. - Todos los campos faltantes serán removidos o vaciados al momento de la modificación. - Todos los campos en la lista `$retainKeys` deberán ser un superconjunto o idéntico a los campos presentes en el Patch. La estrategia `retainKeys` no funciona para todos los objetos. Solo funciona cuando el valor de la key `patchStrategy`en el campo tag de el código fuente de Kubernetes contenga `retainKeys`. Por ejemplo, el campo `Strategy` del struct `DeploymentSpec` tiene un valor de `retainKeys` en su tag `patchStrategy` ```go type DeploymentSpec struct { ... // +patchStrategy=retainKeys Strategy DeploymentStrategy `json:"strategy,omitempty" patchStrategy:"retainKeys" ...` ... } ``` También puedes revisar la estrategia `retainKeys` en la especificación de [OpenApi](https://raw.githubusercontent.com/kubernetes/kubernetes/master/api/openapi-spec/swagger.json): ```yaml "io.k8s.api.apps.v1.DeploymentSpec": { ..., "strategy": { "$ref": "#/definitions/io.k8s.api.apps.v1.DeploymentStrategy", "description": "The deployment strategy to use to replace existing pods with new ones.", "x-kubernetes-patch-strategy": "retainKeys" }, .... } ```  Además puedes revisar la estrategia `retainKeys` en la [documentación del API de k8s](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#deploymentspec-v1-apps). ### Formas alternativas del comando kubectl patch El comando `kubectl patch` toma como entrada un archivo en formato YAML o JSON desde el sistema de archivos o la línea de comandos. Crea un archivo llamado `patch-file.json` que contenga lo siguiente: ```json { "spec": { "template": { "spec": { "containers": [ { "name": "patch-demo-ctr-2", "image": "redis" } ] } } } } ``` Los siguientes comandos son equivalentes: ```shell kubectl patch deployment patch-demo --patch-file patch-file.yaml kubectl patch deployment patch-demo --patch 'spec:n template:n  spec:n   containers:n   - name: patch-demo-ctr-2n     image: redis' kubectl patch deployment patch-demo --patch-file patch-file.json kubectl patch deployment patch-demo --patch '{"spec": {"template": {"spec": {"containers": [{"name": "patch-demo-ctr-2","image": "redis"}]}}}}' ``` ### Actualiza la cantidad de réplicas de un objeto utilizando `kubectl patch` con `--subresource` {#scale-kubectl-patch} {{< feature-state for_k8s_version="v1.24" state="alpha" >}} La bandera `--subresource=[subresource-name]` es utilizada con comandos de kubectl como get, patch y replace para obtener y actualizar los subrecursos `status` y `scale` de los recursos (aplicable para las versiones de kubectl de v1.24 en adelante). Esta bandera se utiliza con todos los recursos del API (incluidos en k8s o CRs) que tengan los subrecursos `status` o `scale`. Deployment es un ejemplo de un objeto con estos subrecursos. A continuación se muestra un ejemplo de un Deployment con dos réplicas: {{% code_sample file="application/deployment.yaml" %}} Crea el Deployment: ```shell kubectl apply -f https://k8s.io/examples/application/deployment.yaml ``` Revisa los Pods asociados al Deployment ```shell kubectl get pods -l app=nginx ``` En el resultado se puede observar que el Deployment tiene dos Pods: ``` NAME                                READY   STATUS    RESTARTS   AGE nginx-deployment-7fb96c846b-22567   1/1     Running   0          47s nginx-deployment-7fb96c846b-mlgns   1/1     Running   0          47s ``` Ahora modifica el Deployment utilizando Patch con la bandera `--subresource=[subresource-name]`: ```shell kubectl patch deployment nginx-deployment --subresource='scale' --type='merge' -p '{"spec":{"replicas":3}}' ``` El resultado es : ```shell scale.autoscaling/nginx-deployment patched ``` Revisa los Pods asociados al Deployment modificado: ```shell kubectl get pods -l app=nginx ``` En el resultado se puede apreciar que se ha creado un Pod nuevo. Ahora tienes 3 Pods en ejecución. ``` NAME                                READY   STATUS    RESTARTS   AGE nginx-deployment-7fb96c846b-22567   1/1     Running   0          107s nginx-deployment-7fb96c846b-lxfr2   1/1     Running   0          14s nginx-deployment-7fb96c846b-mlgns   1/1     Running   0          107s ``` Revisa el Deployment modificado ```shell kubectl get deployment nginx-deployment -o yaml ``` ```yaml ... spec: replicas: 3 ... status: ... availableReplicas: 3 readyReplicas: 3 replicas: 3 ``` {{< note >}} Si ejecutas `kubectl patch` y especificas la bandera `--subresource` para un recurso que no soporte un subrecurso en particular, el servidor del API regresará un error 404 Not Found. {{< /note >}} ## Resumen En este ejercicio utilizaste `kubectl patch` para cambiar la configuración en ejecución de un objeto de tipo Deployment. No hubo cambios al archivo de configuración que se utilizó originalmente para crear el Deployment. Otros comandos utilizados para actualizar objetos del API incluyen: [kubectl annotate](/docs/reference/generated/kubectl/kubectl-commands/#annotate), [kubectl edit](/docs/reference/generated/kubectl/kubectl-commands/#edit), [kubectl replace](/docs/reference/generated/kubectl/kubectl-commands/#replace), [kubectl scale](/docs/reference/generated/kubectl/kubectl-commands/#scale), y [kubectl apply](/docs/reference/generated/kubectl/kubectl-commands/#apply). {{< note >}} Strategic merge patch no tiene soporte para Custom Resources (CRs). {{< /note >}} ## {{% heading "whatsnext" %}} * [Manejo de Objetos de Kubernetes](/docs/concepts/overview/working-with-objects/object-management/) * [Manejo de Objetos de Kubernetes usando comandos imperativos](/docs/tasks/manage-kubernetes-objects/imperative-command/) * [Manejo Imperativo de Objetos de Kubernetes usando archivos de configuración](/docs/tasks/manage-kubernetes-objects/imperative-config/) * [Manejo Declarativo de Objetos de Kubernetes usando archivos de configuración](/docs/tasks/manage-kubernetes-objects/declarative-config/)


Question: title: "Your Title Here" date: YYYY-MM-DD slug: text-for-URL-link-here-no-spaces <ins> author: > Author-1 (Affiliation), Author-2 (Affiliation), Author-3 (Affiliation) </ins> --- ```

This is a Feature Request <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--What would you like to be The blog submission guidelines currently do not reflect the new format required for front matter, particularly the inclusion of author metadata. This discrepancy could lead to confusion and incorrect submissions from contributors who follow the outdated format. The existing guidelines need to be updated to reflect this change. Proposed Solution: Update the example front matter on the to demonstrate the correct format for including author metadata. Ensure that any related content, such as instructions or explanations surrounding the addition of author information, is also updated to reflect the new requirement. Reference of a published blog following the new format: Example of new format: Page to Update: Page URL: source: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /language en /sig docs /area blog
/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 : /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
/priority backlog
/assign


Question: ## Owner references in object specifications Dependent objects have a `metadata.ownerReferences` field that references their <del> owner object. A valid owner reference consists of the object name and a UID within the same namespace as the dependent object. Kubernetes sets the value of </del> <ins> owner object. A valid owner reference consists of the object name and a {{<glossary_tooltip text="UID" term_id="uid">}} within the same {{<glossary_tooltip text="namespace" term_id="namespace">}} as the dependent object. Kubernetes sets the value of </ins> this field automatically for objects that are dependents of other objects like ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers. You can also configure these relationships manually by changing the value of

This is a Feature Request What would you like to be There are terms that can use the addition of a glossary tooltip to show the meaning of the said term. Some terms can add into What's next section like: ReplicaSets, DaemonSets, Deployments, Jobs and CronJobs, and ReplicationControllers. Why is this needed This will enhance user experience and bring more clarity and less confusion. Comments Page to update:
/sig docs /language en /assign
This issue is fixed here .
IMO this is an acceptable change but I'd like another org member to chime in
/triage accepted
Hi Thanks for sharing your feedback and triage accepted.


Question: persistentvolumeclaim/my-pvc created ``` <del> The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout} etc.` </del> <ins> The `--recursive` flag works with any operation that accepts the `--filename,-f` flag such as: `kubectl {create,get,delete,describe,rollout}` etc. </ins> The `--recursive` flag also works when multiple `-f` arguments are provided:

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: Line 143, the backquote is placed at wrong position. The flag works with any operation that accepts the flag such as: Line 456~457, it needs to change hugo code for the consistency with other documents Proposed Solution: Line 143: The flag works with any operation that accepts the flag such as: etc. Line 456~457: Learn about . See . Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /assign


Question: flag `--service-account-extend-token-expiration=false`. Check [Bound Service Account Tokens](https://github.com/kubernetes/enhancements/blob/master/keps/sig-auth/1205-bound-service-account-tokens/README.md) for more details. <del> - `CheckpointContainer`: Enables the kubelet `checkpoint` API. </del> <ins> - `ContainerCheckpoint`: Enables the kubelet `checkpoint` API. </ins> See [Kubelet Checkpoint API](/docs/reference/node/kubelet-checkpoint-api/) for more details. - `ControllerManagerLeaderMigration`: Enables Leader Migration for [kube-controller-manager](/docs/tasks/administer-cluster/controller-manager-leader-migration/#initial-leader-migration-configuration) and

Feature Gate ChecpointContainer is unrecognized by kubelet. I've tried to set up a new 1.25 cluster with kubeadm with kubelet config And it fails with I've also tried to set up another cluster without this feature gate and enable it after, and it goes the same. Kubelet is started and checkpoint api is accessible. To reproduce try to install a new cluster with kubeadm v1.25.0 and use next kubelet config Or try to enable this feature gate on already installed 1.25.0 cluster No response <details</details<detailsBare Metal </details<details</details<detailskubeadm 1.25.0 </details<detailscontainerd </details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. 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
The feature gate name is according to
/sig node
/kind documentation
doesn't list a feature gate for kubelets. has a feature gate named . I'm guessing that this is a docs bug and is incorrect (possibly other docs pages too).
Thank you Yep, using as feature gate name resolves the issue. So this is a doc bug.
/retitle Feature gate misnamed in docs
/transfer website
This issue is now and should fix it. /language en /triage accepted
/sig docs
/priority backlog


Question:
{{ $valid_states := "alpha, beta, deprecated, stable" }} {{ $state := .Get "state" }}  {{ $for_k8s_version := .Get "for_k8s_version" | default (.Page.Param "version")}}   {{ $for_k8s_version := .Get "for_k8s_version" | default (.Page.Param "version") }}  {{ $is_valid := strings.Contains $valid_states $state }} {{ $feature_gate_name := .Get "feature_gate_name" }}    {{ if not $feature_gate_name }} {{ if not $is_valid }} {{ errorf "%q is not a valid feature-state, use one of %q" $state $valid_states }} {{ else }}
 {{ T "feature_state" }} {{T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]

 {{ T "feature_state" }} {{ T "feature_state_kubernetes_label" }} {{ $for_k8s_version }} [{{ $state }}]
  {{ end }}  {{- else -}}     {{ else }}   {{- $featureGateDescriptionFilesPath := "/docs/reference/command-line-tools-reference/feature-gates" -}}    {{- with index (where .Site.Sites "Language.Lang" "eq" "en") 0 -}} {{- with .GetPage $featureGateDescriptionFilesPath -}}    {{- $sortedFeatureGates := sort (.Resources.ByType "page") -}} {{- $featureGateFound := false -}}    {{- range $featureGateFile := $sortedFeatureGates -}} {{- $featureGateNameFromFile := $featureGateFile.Params.Title -}} {{- if eq $featureGateNameFromFile $feature_gate_name -}}    {{- $currentStage := index $featureGateFile.Params.stages (sub (len $featureGateFile.Params.stages) 1) -}} {{- with $currentStage -}}
 {{ T "feature_state" }} {{T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]

 {{ T "feature_state" }} {{ T "feature_state_kubernetes_label" }} v{{ .fromVersion }} [{{ .stage }}]
  {{- $featureGateFound = true -}} {{- end -}} {{- end -}} {{- end -}}    {{- if not $featureGateFound -}}  {{- errorf "Invalid feature gate: '%s' is not recognized or lacks a matching description file in '%s'" $feature_gate_name  (print "en" $featureGateDescriptionFilesPath) -}}   {{- errorf "Invalid feature gate: '%s' is not recognized or lacks a matching description file in '%s'" $feature_gate_name (print "en" $featureGateDescriptionFilesPath) -}}  {{- end -}} {{- end -}}

This is a Bug Report Problem: On the Kubernetes documentation page for Ephemeral Storage Consumption Management (), under the "Filesystem project quota" tab, HTML tags are being displayed incorrectly. This results in the raw HTML code being visible instead of the intended formatted content. Proposed Solution: The HTML tags should be removed from the displayed content, and the text should be properly rendered without the raw HTML markup. The content should be reviewed and corrected to ensure it is presented in a readable and user-friendly format. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--The issue affects the "Ephemeral Storage Consumption Management" section, specifically under "Filesystem project quota." The incorrect display of HTML tags may impact user understanding and the overall readability of the documentation.
/sig docs /assign I will raise a PR for this issue
/language en
/triage accepted Good to fix /help /priority backlog
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 /help /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
Even after removing the tags, the page is still showing raw HTML.
The fix here is either to revise how far things are indented (likely), or perhaps to swap between / and / shortcode markers (less likely).


Question: background-repeat: no-repeat, repeat; background-size: auto 100%, cover; color: #fff; <del> width: 100vw; </del> /* fallback in case calc() fails */ padding: 5vw; padding-bottom: 1em;

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


Question:
A Kubernetes cluster consists of two types of resources:

The Master coordinates the cluster

The Control Plane coordinates the cluster

Nodes are the workers that run applications

This is a Clean Up 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 Change to call the control plane a “control plane”, not a “master”. Why is this needed Kubernetes terms have changed: …however has not yet got that memo. This work would be part of The term “master” is unhelpful when it has connotations of being paired with “slave”. Comments Note that the diagrams also need revising at the same time (if need be, this could be 2 separate PRs that merge together). /language en /wg naming /kind cleanup
/assign
/triage accepted


Question: <!-- overview --> <del> このページでは、クラスター内のノードが使用している[コンテナランタイム](/docs/setup/production-environment/container-runtimes/)を確認する手順を概説しています。 </del> <ins> このページでは、クラスター内のノードが使用している[コンテナランタイム](/ja/docs/setup/production-environment/container-runtimes/)を確認する手順を概説しています。 </ins> クラスターの実行方法によっては、ノード用のコンテナランタイムが事前に設定されている場合と、設定する必要がある場合があります。 マネージドKubernetesサービスを使用している場合、ノードに設定されているコンテナランタイムを確認するためのベンダー固有の方法があるかもしれません。

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. --Update Japanese translation Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --ref. /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
I want to work on this. Have you already started working on it? It seems that some pages linked from here are not translated yet: dockershim-removal template For now, I'm going to start working on dockershim related contents. Feel free to notify me if this conflicts with your work.
I'll assign myself since you haven't assigned youself to this issue. Please tell me if this conflicts with you work. /assign


Question: <ins> --- title: Instalación de Complementos (AddOns) content_type: concept weight: 120 --- <!-- overview --> {{% thirdparty-content %}} Los complementos amplían las funcionalidades de Kubernetes. En esta página se listan algunos de los complementos disponibles con sus respectivos enlaces de instrucciones para su instalación y uso. La lista no pretende ser exhaustiva. <!-- body --> ## Redes y Política de Redes * [ACI](https://www.github.com/noironetworks/aci-containers) (Cisco ACI) proporciona redes de contenedores integradas y seguridad de red. * [Antrea](https://antrea.io/) proporciona servicios de red y seguridad para Kubernetes, aprovechando Open vSwitch como plano de datos de red, opera en la capa 3/4. Antrea es un [proyecto de la CNCF de nivel Sandbox](https://www.cncf.io/projects/antrea/). * [Calico](https://www.tigera.io/project-calico/) es un proveedor de redes y políticas de red. Calico admite un conjunto flexible de opciones de red, para poder elegir la opción más eficiente para su situación, incluidas las redes superpuestas y no superpuestas, con o sin BGP (Border Gateway Protocol). Calico utiliza el mismo motor para aplicar las políticas de red para hosts, Pods, y (si se usa Istio y Envoy) aplicaciones en la capa de la malla de servicios. * [Canal](https://projectcalico.docs.tigera.io/getting-started/kubernetes/flannel/flannel) Es la unión de Flannel y Calico, proporciona redes y políticas de redes. * [Cilium](https://github.com/cilium/cilium) es una solución de red, observabilidad y seguridad con un plano de datos basado en eBPF. Cilium proporciona una red sencilla y plana en capa 3 con la capacidad de abarcar varios clústeres en un modo de enrutamiento nativo o de superposición/encapsulación, y puede aplicar políticas de red en L3-L7 utilizando un modelo de seguridad basado en identidad que está desacoplado del direccionamiento de red. Cilium puede actuar como sustituto de kube-proxy, también ofrece características adicionales de observabilidad y seguridad de manera opcional. Cilium es un [proyecto de la CNCF de nivel Incubación](https://www.cncf.io/projects/cilium/). * [CNI-Genie](https://github.com/cni-genie/CNI-Genie) permite a Kubernetes conectarse sin problemas a una selección de complementos de CNI, como Calico, Canal, Flannel o Weave. CNI-Genie es un [proyecto de la CNCF de nivel Sandbox](https://www.cncf.io/projects/cni-genie/). * [Contiv](https://contivpp.io/) proporciona redes configurables (L3 nativo mediante BGP, con superposición mediante vxlan, L2 clásica y Cisco-SDN/ACI) para diversos casos de uso y un vasto marco de políticas. El proyecto Contiv es de [código abierto](https://github.com/contiv). El [instalador](https://github.com/contiv/install) ofrece opciones de instalación basadas en kubeadm y no basadas en kubeadm. * [Contrail](https://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/), basada en [Tungsten Fabric](https://tungsten.io), es una plataforma de gestión de políticas y virtualización de redes multicloud de código abierto. Contrail y Tungsten Fabric se integran con sistemas de orquestación como Kubernetes, OpenShift, OpenStack y Mesos, y proporcionan modos de aislamiento para máquinas virtuales, contenedores/Pods y cargas de trabajo para bare metal. * [Flannel](https://github.com/flannel-io/flannel#deploying-flannel-manually) es un proveedor de red superpuesta que se puede usar con Kubernetes. * [Knitter](https://github.com/ZTE/Knitter/) es un complemento que soportar múltiples interfaces de red en un Pod de Kubernetes. * [Multus](https://github.com/k8snetworkplumbingwg/multus-cni) es un multicomplemento para soporte de múltiple redes en Kubernetes, que admite todos los complementos de CNI (ej. Calico, Cilium, Contiv, Flannel), además de SRIOV, DPDK, OVS-DPDK y cargas de trabajo basadas en VPP en Kubernetes. * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/) es un proveedor de red para Kubernetes basado en [OVN (Open Virtual Network)](https://github.com/ovn-org/ovn/), es una implementación de red virtual que surgió del proyecto Open vSwitch (OVS). OVN-Kubernetes proporciona una implementación de red basada en la superposición para Kubernetes, incluyendo una implementación basada en OVS de balanceo de carga y política de red. * [Nodus](https://github.com/akraino-edge-stack/icn-nodus) es un complemento de controlador CNI basado en OVN para proveer Service function chaining(SFC) con base nativa para la nube. * [NSX-T](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/index.html)  Container Plug-in (NCP) proporciona integración entre VMware NSX-T y orquestadores de contenedores como Kubernetes, así como integración entre NSX-T y plataformas CaaS/PaaS basadas en contenedores como Pivotal Container Service (PKS) y OpenShift. * [Nuage](https://github.com/nuagenetworks/nuage-kubernetes/blob/v5.1.1-1/docs/kubernetes-1-installation.rst) es una plataforma SDN que proporciona redes basadas en políticas entre Kubernetes Pods y entornos no Kubernetes con visibilidad y supervisión de la seguridad. * [Romana](https://github.com/romana) es una solución de red de capa 3 para las redes de Pods que también son compatibles con la API de [NetworkPolicy](/docs/concepts/services-networking/network-policies/). * [Weave Net](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/) proporciona redes y políticas de red, funciona en ambos lados de una partición de red y no requiere una base de datos externa. ## Detección de Servicios * [CoreDNS](https://coredns.io) es un servidor de DNS flexible y extensible que puede [instalarse](https://github.com/coredns/deployment/tree/master/kubernetes) como DNS dentro del clúster para los Pods. ## Visualización y Control * [Dashboard](https://github.com/kubernetes/dashboard#kubernetes-dashboard) es un panel de control con una interfaz web para Kubernetes. * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s) es una herramienta para visualizar gráficamente tus contenedores, Pods, Services, etc. Utilícela junto con una [cuenta de Weave Cloud](https://cloud.weave.works/) o aloje la interfaz de usuario usted mismo. ## Infraestructura * [KubeVirt](https://kubevirt.io/user-guide/#/installation/installation) es un complemento para ejecutar máquinas virtuales en Kubernetes. Suele ejecutarse en clústeres de Bare metal. * El [detector de problemas de nodo](https://github.com/kubernetes/node-problem-detector) se ejecuta en nodos Linux e informa de los problemas del sistema como [Eventos](/docs/reference/kubernetes-api/cluster-resources/event-v1/) o [Condiciones de nodo](/docs/concepts/architecture/nodes/#condition). ## Complementos Antiguos Hay otros complementos documentados como obsoletos en el directorio [cluster/addons](https://git.k8s.io/kubernetes/cluster/addons). Los que mejor mantenimiento tienen deben estar vinculados aquí. !PRs son bienvenidos! </ins>  No newline at end of file

This is a Feature Request What would you like to be Localize to Spanish Why is this needed There is no Spanish localization for this file. Comments /triage accepted /kind feature /language es /sig docs
/assign
GitHub didn't allow me to assign the following users: nilofe. Note that only with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign 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
Assignment received work performed PR
/assign


Question: {{< comment >}} TODO: Add more information about return codes once CRI implementation have checkpoint/restore. This TODO cannot be fixed before the release, because the CRI implementation need <del> the Kubernetes changes to be merged to implement the new CheckpointContainer CRI API </del> <ins> the Kubernetes changes to be merged to implement the new ContainerCheckpoint CRI API </ins> call. We need to wait after the 1.25 release to fix this. {{< /comment >}}


Question: Atualmente, se algum sistema externo executou a rotação, apenas o conteúdo do arquivo de log mais recente estará disponível através de `kubectl logs`. Por exemplo, se houver um arquivo de 10MB, o `logrotate` executa a rotação e existem dois arquivos, um com 10MB de tamanho e um vazio, o `kubectl logs` retornará uma resposta vazia. {{< /note >}} <del> [cosConfigureHelper]: https://github.com/kubernetes/kubernetes/blob/{{< param "githubbranch" >}}/cluster/gce/gci/configure-helper.sh </del> <ins> [cosConfigureHelper]: https://github.com/kubernetes/kubernetes/blob/master/cluster/gce/gci/configure-helper.sh </ins> ### Logs de componentes do sistema

This is a Bug Report Problem: Regarding , I found the similar broken links on other pages. English pages have already been fixed. ref: pt pages also need to be fixed. Proposed Solution: Fixes broken links including {{< param "githubbranch" }} to master. In the case of link to , fixes to {{< param "fullversion" }}. ref:
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


Question: [options_heading] other = "Opcje" <ins> [outdated_blog__message] other = "Ten artykuł jest starszy niż rok, więc część informacji może być już nieaktualnych. Upewnij się, że zawartość tej strony ciągle jest poprawna." [patch_release] other = "Patch Release" </ins> [post_create_issue] other = "Zgłoś problem"

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


Question: <ins> --- title: 启用拓扑感知提示 content_type: task min-kubernetes-server-version: 1.21 --- <!-- --- reviewers: - robscott title: Enabling Topology Aware Hints content_type: task min-kubernetes-server-version: 1.21 --- --> <!-- overview --> {{< feature-state for_k8s_version="v1.21" state="alpha" >}} <!-- _Topology Aware Hints_ enable topology aware routing with topology hints included in {{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}}. This approach tries to keep traffic close to where it originated from; you might do this to reduce costs, or to improve network performance. --> _拓扑感知提示_ 启用具有拓扑感知能力的路由，其中拓扑感知信息包含在 {{< glossary_tooltip text="EndpointSlices" term_id="endpoint-slice" >}} 中。 此功能尽量将流量限制在它的发起区域附近； 可以降低成本，或者提高网络性能。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- The following prerequisite is needed in order to enable topology aware hints: * Configure the {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to run in iptables mode or IPVS mode * Ensure that you have not disabled EndpointSlices --> 为了启用拓扑感知提示，先要满足以下先决条件： * 配置 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} 以 iptables 或 IPVS 模式运行 * 确保未禁用 EndpointSlices <!-- ## Enable Topology Aware Hints --> ## 启动拓扑感知提示 {#enable-topology-aware-hints} <!-- To enable service topology hints, enable the `TopologyAwareHints` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the kube-apiserver, kube-controller-manager, and kube-proxy: --> 要启用服务拓扑感知，请启用 kube-apiserver、kube-controller-manager、和 kube-proxy 的 [特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/) `TopologyAwareHints`。 ``` --feature-gates="TopologyAwareHints=true" ``` ## {{% heading "whatsnext" %}} <!-- * Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints) for Services * Read [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/) --> * 参阅面向服务的[拓扑感知提示](/zh/docs/concepts/services-networking/topology-aware-hints) * 参阅[用服务连通应用](/zh/docs/concepts/services-networking/connect-applications-service/) </ins>

This is a Feature Request translate /docs/tasks/administer-cluster/enabling-topology-aware- into Chinese. What would you like to be /zh/docs/tasks/administer-cluster/enabling-topology-aware- /language zh /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


Question: <ins> <?xml version="1.0" encoding="utf-8"?> <!-- Generator: Adobe Illustrator 26.1.0, SVG Export Plug-In . SVG Version: 6.00 Build 0)  --> <svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 641.2 280.2" style="enable-background:new 0 0 641.2 280.2;" xml:space="preserve"> <style type="text/css"> .st0{fill:#FFFFFF;} .st1{fill-rule:evenodd;clip-rule:evenodd;fill:#FFFFFF;} .st2{opacity:0.8;fill:#FFFFFF;enable-background:new    ;} .st3{clip-path:url(#SVGID_00000057866974399932008060000010582933722771219127_);} .st4{clip-path:url(#SVGID_00000160162135013417898060000015368290228459631497_);} .st5{clip-path:url(#SVGID_00000134241693529032034310000004163905177999708581_);} </style> <path class="st0" d="M185.6,187.3c1.1-0.3,2.4-0.6,4.1-0.9c1.7-0.3,3.5-0.4,5.2-0.4c1.6-0.1,3.1,0.2,4.6,0.7 c1.1,0.4,2.1,1.2,2.9,2.1c0.7,0.9,1.2,2,1.5,3.2c0.3,1.3,0.5,2.7,0.5,4.1v12.4h-6.1v-11.7c0.1-1.4-0.2-2.9-0.8-4.2 c-0.5-0.8-1.5-1.2-3-1.2c-0.5,0-0.9,0-1.4,0.1c-0.5,0-0.9,0.1-1.3,0.1v16.9h-6.2V187.3L185.6,187.3z M174.2,197.4 c0.1-1.6-0.3-3.1-1.1-4.5c-1.4-1.8-4.1-2.1-5.9-0.7c-0.3,0.2-0.5,0.4-0.7,0.7c-0.9,1.3-1.3,2.9-1.2,4.5c-0.1,1.6,0.3,3.2,1.2,4.6 c1.3,1.8,3.8,2.2,5.7,0.9c0.4-0.3,0.7-0.6,0.9-0.9C173.9,200.6,174.3,199,174.2,197.4 M180.5,197.4c0,1.6-0.2,3.2-0.7,4.7 c-0.5,1.4-1.2,2.6-2.2,3.7c-2,2.2-4.9,3.3-7.8,3.2c-1.5,0-3-0.3-4.4-0.8c-1.3-0.6-2.4-1.4-3.4-2.4c-1-1.1-1.7-2.3-2.2-3.7 c-1.1-3-1.1-6.4,0-9.4c0.5-1.3,1.2-2.6,2.2-3.6c1-1,2.1-1.8,3.4-2.3c1.4-0.6,2.8-0.8,4.3-0.8c1.5,0,2.9,0.3,4.3,0.8 c1.3,0.6,2.4,1.3,3.4,2.3c1,1,1.7,2.3,2.2,3.6C180.2,194.2,180.6,195.8,180.5,197.4 M146.8,209c-4.7,0-8.3-1.3-10.7-3.9 c-2.5-2.6-3.7-6.3-3.7-11.1c0-2.2,0.4-4.3,1.1-6.4c1.4-3.6,4.2-6.3,7.8-7.6c1.9-0.7,3.9-1,5.9-1c1.1,0,2.2,0.1,3.3,0.3 c1,0.2,1.9,0.4,2.6,0.6c0.6,0.2,1.3,0.4,1.9,0.7c0.4,0.1,0.8,0.3,1.1,0.6l-1.9,5.2c-1-0.5-2-0.9-3.1-1.2c-1.3-0.3-2.7-0.5-4-0.5 c-1,0-2,0.2-2.9,0.5c-1,0.3-1.8,0.9-2.5,1.6c-0.8,0.8-1.4,1.8-1.8,2.8c-0.5,1.4-0.7,2.8-0.7,4.2c0,1.2,0.1,2.5,0.4,3.7 c0.3,1.1,0.8,2.1,1.4,3c0.7,0.8,1.6,1.5,2.6,2c1.2,0.5,2.5,0.7,3.8,0.7c0.8,0,1.7-0.1,2.5-0.2c0.7-0.1,1.3-0.2,2-0.4 c0.5-0.1,1-0.3,1.5-0.5c0.4-0.2,0.8-0.4,1.2-0.5l1.8,5.2c-1.2,0.7-2.5,1.2-3.9,1.5C150.7,208.8,148.8,209.1,146.8,209 M122.1,195.3 c0-0.5-0.1-1-0.3-1.5c-0.2-0.5-0.4-0.9-0.7-1.3c-0.3-0.4-0.7-0.7-1.2-1c-0.6-0.2-1.2-0.4-1.8-0.4c-0.6,0-1.2,0.1-1.8,0.4 c-0.5,0.2-0.9,0.5-1.2,0.9c-0.3,0.4-0.6,0.9-0.8,1.4c-0.2,0.5-0.3,1.1-0.4,1.6L122.1,195.3L122.1,195.3z M107.6,197.6 c0-1.7,0.3-3.5,0.9-5.1c0.5-1.4,1.3-2.6,2.4-3.6c0.9-0.9,2.1-1.7,3.3-2.2c1.2-0.5,2.6-0.7,3.9-0.7c2.8-0.2,5.4,0.9,7.4,2.8 c1.8,1.9,2.7,4.7,2.7,8.4v1.2c0,0.4-0.1,0.8-0.1,1.1H114c0.1,1.2,0.7,2.4,1.8,3c1.3,0.8,2.7,1.1,4.2,1.1c1.1,0,2.2-0.1,3.3-0.3 c0.9-0.2,1.8-0.4,2.7-0.8l0.8,5c-0.4,0.2-0.9,0.4-1.3,0.5c-0.6,0.2-1.3,0.3-1.9,0.4c-0.7,0.1-1.4,0.2-2.2,0.3 c-0.8,0.1-1.5,0.1-2.3,0.1c-1.7,0-3.5-0.3-5.1-0.9c-1.4-0.5-2.6-1.3-3.6-2.4c-1-1-1.7-2.2-2.1-3.6 C107.8,200.6,107.6,199.1,107.6,197.6 M103.5,197.5c0,1.6-0.3,3.2-0.8,4.7c-0.5,1.3-1.2,2.6-2.2,3.6c-1,1-2.2,1.8-3.6,2.3 c-1.5,0.5-3.2,0.8-4.8,0.8c-0.8,0-1.6,0-2.4-0.1l-2.4-0.3c-0.8-0.1-1.5-0.2-2.3-0.4c-0.7-0.2-1.4-0.3-1.9-0.5V177l6.2-1v10.9 c0.7-0.3,1.4-0.5,2.2-0.7c0.8-0.2,1.6-0.2,2.4-0.2c1.4,0,2.8,0.3,4.1,0.8c1.2,0.5,2.2,1.3,3,2.3c0.8,1.1,1.4,2.3,1.8,3.6 C103.3,194.3,103.6,195.9,103.5,197.5 M97.2,197.3c0-4-1.5-6-4.4-6c-0.6,0-1.3,0.1-1.9,0.2c-0.5,0.2-1,0.4-1.5,0.6v11.3 c0.4,0.1,0.8,0.1,1.2,0.1c0.5,0,1,0.1,1.5,0.1c1.5,0.1,2.9-0.5,3.8-1.7C96.8,200.6,97.3,199,97.2,197.3 M77,207.7 c-1.1,0.3-2.4,0.6-4.1,0.9c-1.7,0.3-3.5,0.4-5.2,0.4c-1.6,0.1-3.1-0.2-4.6-0.7c-1.1-0.4-2.1-1.2-2.9-2.1c-0.7-1-1.2-2-1.5-3.2 c-0.3-1.3-0.5-2.7-0.5-4.1v-12.2h6.1v11.4c-0.1,1.5,0.2,3,0.8,4.3c0.5,0.9,1.5,1.3,3,1.3c0.5,0,0.9,0,1.4-0.1c0.5,0,0.9-0.1,1.3-0.1 v-16.9H77L77,207.7L77,207.7z M48.4,208.4c-0.6-0.9-1.3-2-2.1-3.1c-0.8-1.1-1.7-2.2-2.6-3.3c-0.9-1.1-1.9-2.1-2.9-3.2 c-0.9-1-2-1.9-3-2.7v12.2h-6.5v-28.8h6.5v10.9c1.7-1.8,3.4-3.6,5.1-5.6c1.7-1.9,3.3-3.7,4.8-5.3h7.7c-2,2.3-3.9,4.6-5.9,6.7 c-2,2.2-4.1,4.3-6.3,6.5c2.4,2.1,4.7,4.3,6.7,6.8c2.2,2.8,4.3,5.7,6.2,8.7h-7.7L48.4,208.4z"/> <path class="st1" d="M100.4,81.2L96.8,82c0-0.5-0.1-1-0.1-1.5c0-3.8,1-7.5,3-10.8l7,6.2c0.1,0.1,0.2,0.2,0.4,0.3 c-0.4,1.1-0.7,2.2-0.8,3.3c-0.2,0.1-0.5,0.1-0.7,0.2L100.4,81.2z M114,60v9.8c-1,0.3-1.9,0.8-2.7,1.4c-0.3-0.2-0.6-0.5-0.9-0.7 l-7.1-5C106.2,62.6,110,60.7,114,60 M65.3,82.6c3.4-14.9,6.3-27.5,9.7-42.4c1.5-6.7,2.5-8.5,8.6-12c8.4-4.9,14.7-8.4,23.7-13.6 c5.6-3.2,6.7-3,6.7,3.9v34.6c-6.3,0.8-12.1,3.7-16.4,8.3l-3-2.1c-0.4-0.2-0.6-0.6-0.7-1c-0.3-0.9-0.8-1.8-1.6-2.4 c-1.4-1.1-3.5-0.9-4.6,0.5c-1.1,1.4-0.9,3.5,0.5,4.6c0.5,0.4,1,0.7,1.6,0.8c0.4,0.1,0.8,0.1,1.2,0.2c0.3,0.1,0.6,0.2,0.9,0.4 l2.8,2.5c-3.1,4.5-4.7,9.9-4.7,15.4c0,1,0.1,2,0.2,3l-6.1,1.3c-0.4,0-0.9,0-1.3,0.1L81.9,85c-4,0.8-8,1.7-12.1,2.6 C64.3,88.9,64.1,87.8,65.3,82.6 M121.1,69.8V60c4,0.7,7.7,2.6,10.7,5.4l-7.7,5.5c-0.1,0.1-0.2,0.2-0.3,0.2 C123,70.6,122.1,70.1,121.1,69.8 M138.3,81.3l-9.6-2.2c-0.1-1-0.4-2.1-0.8-3c0.1-0.1,0.2-0.2,0.3-0.2l7.1-6.3 c2,3.3,3.1,7.1,3.1,10.9C138.3,80.8,138.3,81.1,138.3,81.3 M125.8,28.4c5.2,2.5,8.9,4.3,14.1,6.8c7.2,3.5,14.4,7,21.7,10.4 c1.8,7.8,3.6,15.6,5.3,23.4c1.1,4.7,1.6,7.2,2.7,11.8c1.7,7.3,1.5,7.9-6,6.2l-18.5-4.2c0.1-0.8,0.1-1.6,0.1-2.4 c0-5.5-1.6-11-4.8-15.5l2.6-2.4c0.3-0.3,0.7-0.4,1.1-0.5c1-0.1,1.9-0.4,2.7-1c1.4-1.1,1.6-3.2,0.5-4.6s-3.2-1.6-4.6-0.5l0,0 c-0.5,0.4-0.9,0.8-1.2,1.4c-0.2,0.4-0.3,0.7-0.5,1.1c-0.1,0.3-0.3,0.6-0.6,0.8l-3,2.1c-4.3-4.6-10.1-7.5-16.4-8.3V31.9 C121.1,27,121.5,26.4,125.8,28.4 M119.4,91.4c-0.6,0.1-1.3,0.2-1.9,0.2c-0.6,0-1.2,0-1.8-0.1l-0.3,0.6l-4.4,8.1 c2.1,0.7,4.4,1.1,6.6,1.1c2.3,0,4.5-0.4,6.7-1.1l-4.4-8C119.7,92,119.6,91.7,119.4,91.4 M127.2,86.1l9.6,2.2 c-1.6,3.9-4.3,7.2-7.8,9.5l-3.8-9.2C126,87.9,126.7,87,127.2,86.1 M98.3,88.2l9.6-2.2c0.6,1,1.3,1.8,2.1,2.6l-0.3,0.6l-3.5,8.6 C102.7,95.5,99.9,92.2,98.3,88.2 M176.9,105.1c-4.6,5.7-6.7,8.4-11.3,14.1c-5.2,6.5-9.4,11.8-14.6,18.3c-3.7,4.7-6.4,4.8-12.5,4.8 h-42c-8,0-8.6,0-13.5-6.2c-4.9-6.1-8.7-10.9-13.5-17c-3.8-4.8-4.8-6-8.6-10.8c-5.9-7.4-6.9-10.1,2.3-12.1l28.4-6.4 c2.2,6,6.4,11.1,11.9,14.4l-1.3,3c-0.2,0.4-0.4,0.7-0.8,0.9c-0.9,0.5-1.6,1.2-2,2.1c-0.8,1.6-0.1,3.6,1.5,4.4 c1.6,0.8,3.6,0.1,4.4-1.5c0,0,0,0,0,0c0.3-0.6,0.4-1.2,0.5-1.8c0-0.4,0-0.8-0.1-1.2c0-0.3,0-0.7,0.2-1l1.6-2.9 c3.2,1.2,6.5,1.8,9.9,1.8c3.4,0,6.8-0.6,10-1.9l1.6,2.9c0.2,0.4,0.3,0.8,0.2,1.2c-0.2,1,0,1.9,0.4,2.8c0.8,1.6,2.8,2.3,4.4,1.5 c1.6-0.8,2.3-2.8,1.5-4.4c0,0,0,0,0,0c-0.2-0.6-0.6-1.1-1.1-1.5c-0.3-0.3-0.6-0.5-1-0.7c-0.3-0.2-0.5-0.5-0.6-0.8l-1.3-3.2 c5.5-3.3,9.7-8.4,11.8-14.4l31.3,7.1C180.9,98.3,180.5,100.5,176.9,105.1"/> <path class="st1" d="M121.1,69.8V60c4,0.7,7.7,2.6,10.7,5.4l-7.7,5.5c-0.1,0.1-0.2,0.2-0.3,0.2C123,70.6,122.1,70.1,121.1,69.8 M138.3,81.3l-9.6-2.2c-0.1-1-0.4-2.1-0.8-3c0.1-0.1,0.2-0.2,0.3-0.2l7.1-6.3c2,3.3,3.1,7.1,3.1,10.9 C138.3,80.8,138.3,81.1,138.3,81.3 M125.8,28.4c5.2,2.5,8.9,4.3,14.1,6.8c7.2,3.5,14.4,7,21.7,10.4c1.8,7.8,3.6,15.6,5.3,23.4 c1.1,4.7,1.6,7.2,2.7,11.8c1.7,7.3,1.5,7.9-6,6.2l-18.5-4.2c0.1-0.8,0.1-1.6,0.1-2.4c0-5.5-1.6-11-4.8-15.5l2.6-2.4 c0.3-0.3,0.7-0.4,1.1-0.5c1-0.1,1.9-0.4,2.7-1c1.4-1.1,1.6-3.2,0.5-4.6s-3.2-1.6-4.6-0.5l0,0c-0.5,0.4-0.9,0.8-1.2,1.4 c-0.2,0.4-0.3,0.7-0.5,1.1c-0.1,0.3-0.3,0.6-0.6,0.8l-3,2.1c-4.3-4.6-10.1-7.5-16.4-8.3V31.9C121.1,27,121.5,26.4,125.8,28.4 M127.2,86.1l9.6,2.2c-1.6,3.9-4.3,7.2-7.8,9.5l-3.8-9.2C126,87.9,126.7,87,127.2,86.1 M117.5,101.2v-9.6c0.6,0,1.3-0.1,1.9-0.2 c0.1,0.3,0.2,0.5,0.4,0.7l4.4,8C122.1,100.8,119.8,101.2,117.5,101.2 M176.9,105.1c-4.6,5.7-6.7,8.4-11.3,14.1 c-5.2,6.5-9.4,11.8-14.6,18.3c-3.7,4.7-6.4,4.8-12.5,4.8h-20.9V108c3.4,0,6.8-0.6,10-1.9l1.6,2.9c0.2,0.4,0.3,0.8,0.2,1.2 c-0.2,1,0,1.9,0.4,2.8c0.8,1.6,2.8,2.3,4.4,1.5c1.6-0.8,2.3-2.8,1.5-4.4c-0.2-0.6-0.6-1.1-1.1-1.5c-0.3-0.3-0.6-0.5-1-0.7 c-0.3-0.2-0.5-0.5-0.6-0.8l-1.3-3.2c5.5-3.3,9.7-8.4,11.8-14.4l31.3,7.1C180.9,98.3,180.5,100.5,176.9,105.1"/> <path class="st0" d="M408.9,103.9h-16.6v38.8H431v-16.6h-22.1V103.9z M492,104v22.1h-22l-0.2-0.2v16.8h38.8v-38.8h-16.7L492,104z M392.3,65.1H409l-0.1-0.1V42.9h22l0.1,0.2V26.3h-38.7V65.1z M469.8,26.3v16.6H492v22.2h16.6V26.3L469.8,26.3z"/> <path class="st2" d="M467.8,65.1l-22.2-22.2h24.2V26.3H431v16.8l22.1,22H467.8z M447.8,103.9h-14.7l18.4,18.4l3.8,3.8H431v16.6h38.8 v-16.8l-11-11L447.8,103.9z M492,65.1v24.2l-3.8-3.8l-18.4-18.3v14.7l11.1,11l11,11h16.7V65.1L492,65.1z M431,87.1l-22-22h-16.8 v38.8h16.7V79.7l22.1,22.1L431,87.1z"/> <path class="st0" d="M311.1,185l-4.2,5c-1.8-2.2-4.4-3.6-7.2-3.7c-4.4,0-8,3.6-8,8.1c0,0.1,0,0.2,0,0.2c0,4.8,3.4,8.4,8,8.4 c2.8-0.2,5.3-1.4,7.2-3.4l4.3,4.5c-3.1,3.2-7.3,5-11.8,5.2c-8.6,0-15-6.3-15-14.7c0-8.3,6.6-14.5,15.3-14.5 C304,180.3,308.1,182,311.1,185L311.1,185z M314.6,209v-30.3h7.1V209H314.6z M349.8,198c0,6.8-4.8,11.3-12,11.3s-12.1-4.5-12.1-11.3 s4.8-11.2,12.1-11.2C345,186.8,349.8,191.2,349.8,198L349.8,198z M332.8,198.1c0,3.4,2,5.7,4.9,5.7s4.9-2.3,4.9-5.7s-2-5.7-4.9-5.7 S332.8,194.7,332.8,198.1L332.8,198.1z M375.1,209H368v-3.6c-1.5,2.6-4.3,4.1-7.2,3.9c-4.8,0-7.9-3.3-7.9-8.4V187h7.1v11.9 c0,2.6,1.4,4.2,3.7,4.2c2.7,0,4.3-2.2,4.3-5.2V187h7.1V209z M402.9,209h-7.1v-2.9c-1.6,2.1-4,3.2-6.6,3.2c-6.2,0-10.3-4.6-10.3-11.4 c0-6.7,4-11.2,10.1-11.2c2.7-0.1,5.2,1.1,6.8,3.2v-11.2h7.1V209L402.9,209z M395.8,198.1c0-3.4-2-5.7-4.9-5.7s-4.9,2.3-4.9,5.7 s2,5.8,4.9,5.8C393.9,203.8,395.8,201.5,395.8,198.1z"/> <path class="st0" d="M428.8,209l-13.2-17.6V209h-6.8v-28.6h6.4l13.2,17.7v-17.7h6.8V209H428.8z M460.4,194.6V209h-6.9v-2.5 c-1.4,1.9-3.8,2.9-6.7,2.9c-4.7,0-7.6-2.9-7.6-6.9c0-4.2,3-6.6,8.5-6.7h5.8v-0.3c0-2.2-1.4-3.5-4.3-3.5c-2.3,0.1-4.5,0.8-6.6,1.8 l-2-4.7c3.2-1.6,6.7-2.5,10.2-2.5C456.9,186.7,460.4,189.7,460.4,194.6z M453.5,201.6v-2H449c-2.1,0-3.2,0.7-3.2,2.4 c0,1.6,1.1,2.6,3.1,2.6C451,204.8,452.8,203.5,453.5,201.6z M479.5,207.9c-1.8,1-3.8,1.5-5.9,1.5c-4.3,0-7.3-2.4-7.3-7v-9.7h-3.1 v-4.6h3.1V182h7v6.1h5.8v4.7h-5.8v8.6c0,1.7,0.7,2.5,2,2.4c0.9-0.1,1.8-0.3,2.7-0.7L479.5,207.9z M490.3,180.7 c0.1,2-1.5,3.7-3.5,3.8c-0.1,0-0.1,0-0.2,0c-2.1,0-3.7-1.7-3.7-3.8c0-2,1.7-3.7,3.7-3.7c1.9-0.1,3.6,1.4,3.7,3.3 C490.3,180.5,490.3,180.6,490.3,180.7L490.3,180.7z M483,209v-22h7v22H483z M501,209l-8.3-22h7.3l4.7,15.6l4.8-15.6h7l-8.3,22H501z M539.9,199.9h-15.5c0.5,2.4,2.7,4.2,5.2,4.1c2,0,3.9-0.8,5.3-2.2l3.7,3.6c-2.5,2.6-6,4.1-9.6,3.9c-7.2,0-11.7-4.5-11.7-11.2 c0-6.8,4.7-11.3,11.5-11.3C536.5,186.8,540.3,191.9,539.9,199.9L539.9,199.9z M533.1,196.1c0.2-2.3-1.5-4.3-3.8-4.5 c-0.2,0-0.3,0-0.5,0c-2.5,0-4.1,1.8-4.6,4.5H533.1L533.1,196.1z"/> <path class="st0" d="M568.7,185l-4.2,5c-1.8-2.2-4.4-3.6-7.2-3.7c-4.4,0-8,3.6-8,8.1c0,0.1,0,0.2,0,0.2c0,4.8,3.4,8.4,8,8.4 c2.8-0.2,5.3-1.4,7.2-3.4l4.3,4.5c-3.1,3.2-7.3,5-11.8,5.2c-8.6,0-15-6.3-15-14.7c0-8.3,6.6-14.5,15.3-14.5 C561.6,180.3,565.7,182.1,568.7,185z M593.4,198c0,6.8-4.8,11.3-12,11.3s-12.1-4.5-12.1-11.3s4.8-11.2,12.1-11.2 C588.6,186.8,593.4,191.2,593.4,198z M576.5,198.1c0,3.4,2,5.7,4.9,5.7s4.9-2.3,4.9-5.7s-2-5.7-4.9-5.7S576.5,194.7,576.5,198.1 L576.5,198.1z M619.7,195.1V209h-7v-11.9c0-2.6-1.5-4.2-3.9-4.2c-2.6,0-4.2,1.8-4.5,4.5v11.7h-7.1v-22h7.1v3.6 c1.6-2.6,4.4-4.1,7.4-3.9C616.5,186.7,619.7,190,619.7,195.1L619.7,195.1z"/> <g> <path class="st0" d="M175.9,245.7h4.9l8.6,11.6v-11.6h4.9v19.7h-4.9l-8.6-11.6v11.6h-4.9V245.7z"/> <path class="st0" d="M197.4,258c0-4.3,3.7-7.7,8.3-7.7c4.5,0,8.2,3.5,8.2,7.7s-3.7,7.8-8.2,7.8C201.1,265.7,197.4,262.3,197.4,258z M209.3,258c0-2-1.6-3.7-3.6-3.7c-2,0-3.6,1.7-3.6,3.7s1.6,3.7,3.6,3.7C207.7,261.7,209.3,260,209.3,258z"/> <path class="st0" d="M226.4,250.2v4c-3,0-4.9,1.7-4.9,4.4v6.7h-4.8v-14.8h4.8v2.7C222.5,251.4,224.2,250.2,226.4,250.2z"/> <path class="st0" d="M238.4,264.3c-0.9,0.8-2.3,1.4-3.6,1.4c-2.8,0-4.7-2-4.7-4.8v-6.5h-2v-3.9h2v-4.1h4.6v4.1h3.1v3.9h-3.1v5.6 c0,0.9,0.5,1.6,1.3,1.6c0.5,0,1.1-0.2,1.4-0.5L238.4,264.3z"/> <path class="st0" d="M255.6,256v9.4H251v-8.3c0-1.6-1-2.8-2.5-2.8c-1.5,0-2.6,1.1-2.6,2.6v8.5H241v-20h4.8v6.9c0.9-1.2,2.5-2,4.3-2 C253.4,250.2,255.6,252.6,255.6,256z"/> <path class="st0" d="M280.1,262.4h-7.7l-1.2,3h-5.5l7.8-19.7h5.5l7.8,19.7h-5.5L280.1,262.4z M278.6,258.7l-2.4-6l-2.4,6H278.6z"/> <path class="st0" d="M313.2,256v9.5h-4.7v-8.6c0-1.5-0.9-2.5-2.3-2.5c-1.5,0-2.5,1-2.5,2.3v8.8h-4.6v-8.6c0-1.5-1-2.5-2.4-2.5 c-1.4,0-2.5,1-2.5,2.3v8.8h-4.8v-14.8h4.8v1.9c0.7-1.3,2.1-2.2,3.9-2.2c2.3,0,4.3,1.3,5.1,3.4c0.4-2.1,2.1-3.4,4.4-3.4 C310.7,250.2,313.2,252.6,313.2,256z"/> <path class="st0" d="M327.1,260.7l2.7,2.7c-1.3,1.3-3.8,2.3-6.1,2.3c-4.6,0-8.1-3.2-8.1-7.8c0-4.5,3.4-7.7,7.8-7.7 c4.7,0,7.6,3.4,7.6,9h-10.8c0.4,1.7,1.6,2.8,3.3,2.8C324.8,262.1,326.1,261.5,327.1,260.7z M320.3,256.5h6.1 c-0.3-1.5-1.4-2.5-2.9-2.5C322,253.9,320.8,254.9,320.3,256.5z"/> <path class="st0" d="M343.4,250.2v4c-3,0-4.9,1.7-4.9,4.4v6.7h-4.8v-14.8h4.8v2.7C339.5,251.4,341.3,250.2,343.4,250.2z"/> <path class="st0" d="M346.2,246.2c0-1.3,1.1-2.5,2.6-2.5c1.4,0,2.5,1.2,2.5,2.5c0,1.4-1.1,2.6-2.5,2.6 C347.3,248.8,346.2,247.6,346.2,246.2z M346.3,250.6h4.8v14.8h-4.8V250.6z"/> <path class="st0" d="M353.9,258c0-4.2,3.8-7.7,8.3-7.7c2.5,0,4.6,1,6,2.6l-3.2,2.7c-0.6-0.7-1.7-1.3-2.8-1.3 c-1.9,0-3.5,1.7-3.5,3.7c0,2,1.6,3.8,3.6,3.8c1.1,0,2.2-0.5,2.9-1.3l3.2,2.6c-1.5,1.7-3.5,2.7-6.1,2.7 C357.7,265.7,353.9,262.2,353.9,258z"/> <path class="st0" d="M383.9,256.6v8.8h-4.7v-1.3c-1,1.1-2.6,1.6-4.1,1.6c-3.2,0-5.6-1.9-5.6-4.7c0-2.9,2.7-4.9,6.2-4.9 c1.1,0,2.3,0.3,3.5,0.7v-0.2c0-1.4-1.1-2.5-3.2-2.5c-1.3,0-2.5,0.4-3.7,0.9l-1.5-3.1c2.1-1,4.2-1.7,6.5-1.7 C381,250.2,383.9,252.7,383.9,256.6z M379.2,260.7v-1c-0.8-0.4-1.8-0.6-2.8-0.6c-1.3,0-2.3,0.7-2.3,1.7s0.9,1.7,2.1,1.7 C377.7,262.5,379,261.8,379.2,260.7z"/> <path class="st0" d="M394.4,261.4l7.3-5.4c2.2-1.7,2.8-2.8,2.8-4c0-1.3-1.2-2.2-2.6-2.2c-1.8,0-3.2,0.9-4.7,2.5l-3.1-3 c2.1-2.5,4.6-3.9,7.9-3.9c4.4,0,7.5,2.7,7.5,6.4c0,2.6-1.1,4.6-4.5,7l-3.1,2.2h7.8v4.4h-15.3V261.4z"/> <path class="st0" d="M412.4,255.5c0-6,3.8-10.2,9.1-10.2c5.3,0,9.1,4.2,9.1,10.2c0,6-3.8,10.2-9.1,10.2 C416.1,265.7,412.4,261.5,412.4,255.5z M425.5,255.5c0-3.4-1.7-5.7-4-5.7c-2.3,0-4,2.4-4,5.7s1.7,5.8,4,5.8 C423.8,261.3,425.5,258.9,425.5,255.5z"/> <path class="st0" d="M433,261.4l7.3-5.4c2.2-1.7,2.8-2.8,2.8-4c0-1.3-1.2-2.2-2.6-2.2c-1.8,0-3.2,0.9-4.7,2.5l-3.1-3 c2.1-2.5,4.6-3.9,7.9-3.9c4.4,0,7.5,2.7,7.5,6.4c0,2.6-1.1,4.6-4.5,7l-3.1,2.2h7.8v4.4H433V261.4z"/> <path class="st0" d="M450.9,261.4l7.3-5.4c2.2-1.7,2.8-2.8,2.8-4c0-1.3-1.2-2.2-2.6-2.2c-1.8,0-3.2,0.9-4.7,2.5l-3.1-3 c2.1-2.5,4.6-3.9,7.9-3.9c4.4,0,7.5,2.7,7.5,6.4c0,2.6-1.1,4.6-4.5,7l-3.1,2.2h7.8v4.4h-15.3V261.4z"/> </g> <g> <defs> <rect id="SVGID_1_" x="481.8" y="256.3" width="142.6" height="0.6"/> </defs> <use xlink:href="#SVGID_1_"  style="overflow:visible;fill:#FFFFFF;"/> <clipPath id="SVGID_00000039121392050617286280000004329775547438457989_"> <use xlink:href="#SVGID_1_"  style="overflow:visible;"/> </clipPath> <g style="clip-path:url(#SVGID_00000039121392050617286280000004329775547438457989_);"> <rect x="481.8" y="256.3" class="st0" width="142.6" height="0.6"/> </g> </g> <g> <defs> <rect id="SVGID_00000171707821064887460460000004184522940189294474_" x="16.3" y="256.3" width="139.2" height="0.6"/> </defs> <use xlink:href="#SVGID_00000171707821064887460460000004184522940189294474_"  style="overflow:visible;fill:#FFFFFF;"/> <clipPath id="SVGID_00000143574839413854444570000014173031525488087474_"> <use xlink:href="#SVGID_00000171707821064887460460000004184522940189294474_"  style="overflow:visible;"/> </clipPath> <g style="clip-path:url(#SVGID_00000143574839413854444570000014173031525488087474_);"> <rect x="16.3" y="256.3" class="st0" width="139.2" height="0.6"/> </g> </g> <g> <defs> <rect id="SVGID_00000003807077220869130290000006477256220668862603_" x="242.1" y="13.4" width="0.8" height="205.8"/> </defs> <use xlink:href="#SVGID_00000003807077220869130290000006477256220668862603_"  style="overflow:visible;fill:#FFFFFF;"/> <clipPath id="SVGID_00000094583877443687296950000012884547058532515981_"> <use xlink:href="#SVGID_00000003807077220869130290000006477256220668862603_"  style="overflow:visible;"/> </clipPath> <g style="clip-path:url(#SVGID_00000094583877443687296950000012884547058532515981_);"> <rect x="242.1" y="13.4" class="st0" width="0.8" height="205.8"/> </g> </g> </svg> </ins>

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 An announcement banner for KubeCon NA 2022 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Why is this needed KubeCon NA 2022 is around the corner. It is important we start informing the community about this amazing event by displaying a banner on the Kubernetes website. Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --This change will need steering committee approval. I would set the banner to start on the 22nd of August and end on the 28th of October, 2022 at 18:00 CEST /priority important-soon
Thanks for filing this I think the banner should start on the 15th of October. How does that sound? /priority important-longterm /remove-priority important-soon
15th sounds great!
/triage accepted
/assign


Question: ## Logs and auditing - [ ] Audit logs, if enabled, are protected from general access. <del> - [ ] The `/logs` API is disabled (you are running kube-apiserver with `--enable-logs-handler=false`). Kubernetes includes a `/logs` API endpoint, enabled by default, that lets users request the contents of the API server's `/var/log` directory over HTTP. Accessing that endpoint requires authentication. Allowing broad access to Kubernetes logs can make security information available to a potential attacker. As a good practice, set up a separate means to collect and aggregate control plane logs, and do not use the `/logs` API endpoint. Alternatively, if you run your control plane with the `/logs` API endpoint and limit the content of `/var/log` (within the host or container where the API server is running) to Kubernetes API server logs only. </del> ## Pod placement

<brThere is no flag for , it seems to have already been removed from the code but not from the documentation.
/language en /sig docs /sig security Let this be a good first issue if triaged.
/assign
/triage accepted


Question: body.cid-community .community-section#events { <del> width: 100vw; </del> <ins> width: 100%; </ins> max-width: initial; margin-bottom: 0;


Question: - "`Default`": The Pod inherits the name resolution configuration from the node that the pods run on. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#inheriting-dns-from-the-node) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for more details. - "`ClusterFirst`": Any DNS query that does not match the configured cluster domain suffix, such as "`www.kubernetes.io`", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. <del> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers/#effects-on-pods) </del> <ins> See [related discussion](/docs/tasks/administer-cluster/dns-custom-nameservers) </ins> for details on how DNS queries are handled in those cases. - "`ClusterFirstWithHostNet`": For Pods running with hostNetwork, you should explicitly set its DNS policy "`ClusterFirstWithHostNet`".

says: Pod's DNS Policy : The Pod inherits the name resolution configuration from the node that the pods run on. See related discussion for more details. “Related discussion” is a hyperlink to : Any DNS query that does not match the configured cluster domain suffix, such as "", is forwarded to the upstream nameserver inherited from the node. Cluster administrators may have extra stub-domain and upstream DNS servers configured. See related discussion for details on how DNS queries are handled in those cases. “Related discussion” is a hyperlink to Both hyper targets do not exist in the destination webpage (so that the browser scrolls to the right place). contains a hyperlink “See Inheriting DNS from the node” → , which as above does not exist.
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
/sig docs


Question:
If you haven't worked through the earlier sections, start from Using minikube to create a cluster.

Scaling is accomplished by changing the number of replicas in a Deployment

  NOTE  If you are trying this after the previous section , you may need to start from creating a cluster as the services may have been deleted

Kindly note that you asked us to delete the service in the previous section. Please update the docs by asking to restore the service first before running this command.
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
Could you please provide some details on the issue in the section? /triage needs-information
Page related to the issue: /language en /sig autoscaling
/kind bug
/assign


Question: <ins> apiVersion: v1 kind: Pod metadata: name: nginx spec: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: disktype operator: In values: - ssd containers: - name: nginx image: nginx imagePullPolicy: IfNotPresent </ins>

This is a Feature Request What would you like to be Translate into Japanese. Why is this needed This page has not been translated. Comments /language ja /assign


Question: <ins> --- title: "Linux 系统中的 bash 自动补全功能" description: "Linux 系统中 bash 自动补全功能的一些可选配置。" headless: true --- <!-- --- title: "bash auto-completion on Linux" description: "Some optional configuration for bash auto-completion on Linux." headless: true --- --> <!-- ### Introduction --> ### 简介 {#introduction} <!-- The kubectl completion script for Bash can be generated with the command `kubectl completion bash`. Sourcing the completion script in your shell enables kubectl autocompletion. However, the completion script depends on [**bash-completion**](https://github.com/scop/bash-completion), which means that you have to install this software first (you can test if you have bash-completion already installed by running `type _init_completion`). --> kubectl 的 Bash 补全脚本可以用命令 `kubectl completion bash` 生成。 在 shell 中导入（Sourcing）补全脚本，将启用 kubectl 自动补全功能。 然而，补全脚本依赖于工具 [**bash-completion**](https://github.com/scop/bash-completion)， 所以要先安装它（可以用命令 `type _init_completion` 检查 bash-completion 是否已安装）。 <!-- ### Install bash-completion --> ### 安装 bash-completion {#install-bash-comletion} <!-- bash-completion is provided by many package managers (see [here](https://github.com/scop/bash-completion#installation)). You can install it with `apt-get install bash-completion` or `yum install bash-completion`, etc. The above commands create `/usr/share/bash-completion/bash_completion`, which is the main script of bash-completion. Depending on your package manager, you have to manually source this file in your `~/.bashrc` file. To find out, reload your shell and run `type _init_completion`. If the command succeeds, you're already set, otherwise add the following to your `~/.bashrc` file: --> 很多包管理工具均支持 bash-completion（参见[这里](https://github.com/scop/bash-completion#installation)）。 可以通过 `apt-get install bash-completion` 或 `yum install bash-completion` 等命令来安装它。 上述命令将创建文件 `/usr/share/bash-completion/bash_completion`，它是 bash-completion 的主脚本。 依据包管理工具的实际情况，你需要在 `~/.bashrc` 文件中手工导入此文件。 要查看结果，请重新加载你的 shell，并运行命令 `type _init_completion`。 如果命令执行成功，则设置完成，否则将下面内容添加到文件 `~/.bashrc` 中： ```bash source /usr/share/bash-completion/bash_completion ``` <!-- Reload your shell and verify that bash-completion is correctly installed by typing `type _init_completion`. --> 重新加载 shell，再输入命令 `type _init_completion` 来验证 bash-completion 的安装状态。 <!-- ### Enable kubectl autocompletion --> ### 启动 kubectl 自动补全功能 {#enable-kubectl-autocompletion} <!-- You now need to ensure that the kubectl completion script gets sourced in all your shell sessions. There are two ways in which you can do this: --> 你现在需要确保一点：kubectl 补全脚本已经导入（sourced）到 shell 会话中。 这里有两种验证方法： <!-- - Source the completion script in your `~/.bashrc` file: --> - 在文件 `~/.bashrc` 中导入（source）补全脚本： ```bash echo 'source <(kubectl completion bash)' >>~/.bashrc ``` <!-- - Add the completion script to the `/etc/bash_completion.d` directory: --> - 将补全脚本添加到目录 `/etc/bash_completion.d` 中： ```bash kubectl completion bash >/etc/bash_completion.d/kubectl ``` <!-- If you have an alias for kubectl, you can extend shell completion to work with that alias: --> 如果 kubectl 有关联的别名，你可以扩展 shell 补全来适配此别名： ```bash echo 'alias k=kubectl' >>~/.bashrc echo 'complete -F __start_kubectl k' >>~/.bashrc ``` {{< note >}} <!-- bash-completion sources all completion scripts in `/etc/bash_completion.d`. --> bash-completion 负责导入 `/etc/bash_completion.d` 目录中的所有补全脚本。 {{< /note >}} <!-- Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working. --> 两种方式的效果相同。重新加载 shell 后，kubectl 自动补全功能即可生效。 </ins>

This is a Feature Request translate content/docs/tasks/tools/install-kubectl- into Chinese What would you like to be content/zh/docs/tasks/tools/install-kubectl- /assign /language zh
/triage accepted


Question: ## 논 그레이스풀 노드 셧다운 {#non-graceful-node-shutdown} <del> {{< feature-state state="alpha" for_k8s_version="v1.24" >}} </del> <ins> {{< feature-state state="beta" for_k8s_version="v1.26" >}} </ins> 전달한 명령이 kubelet에서 사용하는 금지 잠금 메커니즘(inhibitor locks mechanism)을 트리거하지 않거나, 또는 사용자 오류(예: ShutdownGracePeriod 및 ShutdownGracePeriodCriticalPods가 제대로 설정되지 않음)로 인해

This is a Feature Request Korean Localization for branch. What would you like to be Any localization contributions for Korean. Comments This issue is to notify the schedule of Korean localization to contributors. is the current work branch for Korean localization. Important dates A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch)  2~3 , main . PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /language ko /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 : ## In English is the current work branch for Korean localization.A Korean localization work branch is merged to branch after we complete around 3~4 weeks job. PR Freeze: 01/16 (PR opened after freeze will be requested to rebase to next work branch) Branch Merge: 01/19 (merge to main branch) PR : 01/16 ( PR , PR ) : 01/19 (main , k8s.io ) /help </details
/milestone dev-1.26-ko.1
/triage accepted
Outdated Korean contents in the dev-1.26-ko.1