Question: This tutorial assumes that you have already set up `minikube`. <del> See [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions. </del> <ins> See __Step 1__ in [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions. {{< note >}} Only execute the instructions in __Step 1, Installation__. The rest is covered on this page. {{< /note >}} </ins> You also need to install `kubectl`. See [Install tools](/docs/tasks/tools/#kubectl) for installation instructions.

The basic tutorial starts at , which leads to , which leads to Since one does not know what is exactly meant with in the second site, one does also the deploy step. Because it's not clearly said "" or so. Then you go back to the second site, to read all through, only to do create/expose again (with little extras), only to go back to the first site and do create/expose again. Back to the first site on step 2, pretty much at the beginning it says: But I did it already 2 times in the current tutorial flow. Now I have 3 deployments, still in the basics deployment tutorial. Its like, there are 3 tutorials to do, which are the same, but also not the same. Instead of leading the user back and forth, I suggest to do one single sufficient tutorial.
Page related to issue: /language en
/retitle Consolidate and streamline Kubernetes basics tutorials to avoid redundancy and confusion
/sig docs
the three tutorial have different purpose. What I understood the purpose of having these as three.: Yes, Its leading to back and forth of the users but I think First link showing the general functionality of the cluster's component. It Should have the link To and then link will be helpful for readers to traverse. This sequence is lacking in the page. Thats the reason why i thing its taking user back and forth several times .
There was a previous attempt at de-duplicating, but it probably has to be done again - after the removal of the Katacoda tutorials, which were using a hosted setup of to run through the tutorials "inline" with the docs
I'll change the title to frame this as a bug. /retitle Multiple, similar Kubernetes basics tutorials that cause confusion /kind bug /triage accepted /priority important-longterm
/lifecycle frozen
Yes You are right! +1
/assign
I will start working on this.


Question: * 确保不发生资源不足。 <del> 集群的性能和稳定性对网络和磁盘 IO 非常敏感。任何资源匮乏都会导致心跳超时，从而导致集群的不稳定。不稳定的情况表明没有选出任何主节点。在这种情况下，集群不能对其当前状态进行任何更改，这意味着不能调度新的 pod。 </del> <ins> 集群的性能和稳定性对网络和磁盘 I/O 非常敏感。任何资源匮乏都会导致心跳超时， 从而导致集群的不稳定。不稳定的情况表明没有选出任何主节点。 在这种情况下，集群不能对其当前状态进行任何更改，这意味着不能调度新的 pod。 </ins> <del> * 保持稳定的 etcd 集群对 Kubernetes 集群的稳定性至关重要。因此，请在专用机器或隔离环境上运行 etcd 集群，以满足[所需资源需求](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-recommendations)。 </del> <ins> * 保持 etcd 集群的稳定对 Kubernetes 集群的稳定性至关重要。 因此，请在专用机器或隔离环境上运行 etcd 集群，以满足 [所需资源需求](https://etcd.io/docs/current/op-guide/hardware/)。 </ins> * 在生产中运行的 etcd 的最低推荐版本是 `3.2.10+`。 <!-- ## Resource requirements <del> Operating etcd with limited resources is suitable only for testing purposes. For deploying in production, advanced hardware configuration is required. Before deploying etcd in production, see [resource requirement reference documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#example-hardware-configurations). </del> <ins> Operating etcd with limited resources is suitable only for testing purposes. For deploying in production, advanced hardware configuration is required. Before deploying etcd in production, see [resource requirement reference](https://etcd.io/docs/current/op-guide/hardware/#example-hardware-configurations). </ins> ## Starting etcd clusters

" etcd "client.cert " etcd etcd " " etcd client.key etcd "
~ GitHub is not the right place for support requests.~ ~If you're looking for help, oyu could ask on .~ ~You can also post your question on the or the forum. There are other support venues with contributions from the wider community of Kubernetes users.~
/triage accepted /kind bug
/remove-kind support
Thanks
/language zh
/priority backlog


Question: <ins> --- title: コンテナランタイムインターフェース(CRI) id: cri date: 2019-03-07 full_link: /docs/concepts/overview/components/#container-runtime short_description: > コンテナランタイムがkubeletと統合するためのAPIです aka: tags: - fundamental --- コンテナランタイムインターフェース(CRI)は、ノード上の{{< glossary_tooltip text="kubelet" term_id="kubelet" >}}と統合するためのコンテナランタイム用APIです。 <!--more--> 詳細については、[CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)のAPIと仕様をご覧ください。 </ins>

Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document:
/area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /area localization /language ja /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/unassign Shubhdeep02 PTAL , thank you
/triage accepted
/assign
Hi thank you for interesting in SIG-docs Japanese Localization project!! Localization requires native or equivalent Japanese language proficiency. It looks you live in Pune, India. Please confirm this before working on this issue. I believe the issues labeled with or (or those you created) are areas where you can contribute more effectively. issues labeled with : issues labeled with : Thank you
/unassign PTAL
Hello, -san, this issue looks good as my first contribution. /assign


Question: dalam bentuk _file-file_ `./username.txt` dan `./password.txt`. ```shell <del> # Buatlah file yang selanjutnya akan digunakan pada contoh-contoh selanjutnya </del> <ins> # Buatlah berkas yang selanjutnya akan digunakan pada contoh-contoh selanjutnya </ins> echo -n 'admin' > ./username.txt echo -n '1f2d1e2e67df' > ./password.txt ```

This issue is intended for contributor workshop as part of Cloud Native Day Indonesia on 7th Nov 2020. Please don't take it if you are not part of the workshop. There are several old translated pages that contain the english glossary "file", supposed to use Indonesian "berkas" as per KBBI. Please claim the task to fix them by giving comments on this Github issue. /language id Tasks to fix "file" -"berkas": [x] docs/tasks/manage-kubernetes-objects/imperative-[x] docs/tasks/manage-kubernetes-objects/declarative-[ ] docs/tasks/manage-kubernetes-objects/imperative-[ ] docs/tasks/configure-pod-container/configure-pod-[ ] docs/tasks/administer-cluster/sysctl-[ ] [x] [ ] docs/concepts/storage/storage-[ ] docs/concepts/services-networking/connect-applications-[ ] docs/concepts/services-[x] [x] docs/concepts/cluster-
/triage accepted
/assign
I'm taking this page docs/tasks/manage-kubernetes-objects/imperative-
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
i'm taking this page docs/tasks/manage-kubernetes-objects/declarative-
may i change this file:
thanks feel free to raise the PR and link this issue
/reopen
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
I take this page :
please let me change another part. I will try to change this file
sure just mention this issue number when you raise the pull request /reopen
Reopened this issue. <detailsIn response to : please let me change another part sure just mention this issue number when you raise the pull request 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
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close.


Question: dalam bentuk _file-file_ `./username.txt` dan `./password.txt`. ```shell <del> # Buatlah file yang selanjutnya akan digunakan pada contoh-contoh selanjutnya </del> <ins> # Buatlah berkas yang selanjutnya akan digunakan pada contoh-contoh selanjutnya </ins> echo -n 'admin' > ./username.txt echo -n '1f2d1e2e67df' > ./password.txt ```

If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle rotten
Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . Send feedback to sig-contributor-experience at . /close
Closing this issue. <detailsIn response to : Rotten issues close after 30d of inactivity. Reopen the issue with . Mark the issue as fresh with . /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> --- layout: blog title: "免费的 Katacoda Kubernetes 教程即将关闭" date: 2023-02-14 slug: kubernetes-katacoda-tutorials-stop-from-2023-03-31 evergreen: true --- <!-- layout: blog title: "Free Katacoda Kubernetes Tutorials Are Shutting Down" date: 2023-02-14 slug: kubernetes-katacoda-tutorials-stop-from-2023-03-31 evergreen: true --> <!-- **Author**: Natali Vlatko, SIG Docs Co-Chair for Kubernetes --> **作者**：Natali Vlatko，Kubernetes SIG Docs 联合主席 **译者**：Michael Yao (DaoCloud) <!-- [Katacoda](https://katacoda.com/kubernetes), the popular learning platform from O’Reilly that has been helping people learn all about Java, Docker, Kubernetes, Python, Go, C++, and more, [shut down for public use in June 2022](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html). However, tutorials specifically for Kubernetes, linked from the Kubernetes website for our project’s users and contributors, remained available and active after this change. Unfortunately, this will no longer be the case, and Katacoda tutorials for learning Kubernetes will cease working after March 31st, 2023. --> [Katacoda](https://katacoda.com/kubernetes) 是 O’Reilly 开设的热门学习平台， 帮助人们学习 Java、Docker、Kubernetes、Python、Go、C++ 和其他更多内容， 这个学习平台于 [2022 年 6 月停止对公众开放](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html)。 但是，从 Kubernetes 网站为相关项目用户和贡献者关联的 Kubernetes 专门教程在那次变更后仍然可用并处于活跃状态。 遗憾的是，接下来情况将发生变化，Katacoda 上有关学习 Kubernetes 的教程将在 2023 年 3 月 31 日之后彻底关闭。 <!-- The Kubernetes Project wishes to thank O'Reilly Media for the many years it has supported the community via the Katacoda learning platform. You can read more about [the decision to shutter katacoda.com](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html) on O'Reilly's own site. With this change, we’ll be focusing on the work needed to remove links to their various tutorials. We have a general issue tracking this topic at [#33936](https://github.com/kubernetes/website/issues/33936) and [GitHub discussion](https://github.com/kubernetes/website/discussions/38878). We’re also interested in researching what other learning platforms could be beneficial for the Kubernetes community, replacing Katacoda with a link to a platform or service that has a similar user experience. However, this research will take time, so we’re actively looking for volunteers to help with this work. If a replacement is found, it will need to be supported by Kubernetes leadership, specifically, SIG Contributor Experience, SIG Docs, and the Kubernetes Steering Committee. --> Kubernetes 项目感谢 O'Reilly Media 多年来通过 Katacoda 学习平台对 Kubernetes 社区的支持。 你可以在 O'Reilly 自有的网站上阅读 [the decision to shutter katacoda.com](https://www.oreilly.com/online-learning/leveraging-katacoda-technology.html) 有关的更多信息。此次变更之后，我们将专注于移除指向 Katacoda 各种教程的链接。 我们通过 [Issue #33936](https://github.com/kubernetes/website/issues/33936) 和 [GitHub 讨论](https://github.com/kubernetes/website/discussions/38878)跟踪此主题相关的常规问题。 我们也有兴趣调研其他哪些学习平台可能对 Kubernetes 社区有益，尝试将 Katacoda 链接替换为具有类似用户体验的平台或服务。 然而，这项调研需要时间，因此我们正在积极寻觅志愿者来协助完成这项工作。 如果找到替代的平台，需要得到 Kubernetes 领导层的支持，特别是 SIG Contributor Experience、SIG Docs 和 Kubernetes Steering Committee。 <!-- The Katacoda shutdown affects 25 tutorial pages, their localizations, as well as the Katacoda Scenario repository: [github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios](https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios). We recommend that any links, guides, or documentation you have that points to the Katacoda learning platform be updated immediately to reflect this change. While we have yet to find a replacement learning solution, the Kubernetes website contains a lot of helpful documentation to support your continued learning and growth. You can find all of our available documentation tutorials for Kubernetes at https://k8s.io/docs/tutorials/. --> Katacoda 的关闭会影响 25 个英文教程页面、对应的多语言页面以及 Katacoda Scenario仓库： [github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios](https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios)。 我们建议你立即更新指向 Katacoda 学习平台的所有链接、指南或文档，以反映这一变化。 虽然我们还没有找到替代这个学习平台的解决方案，但 Kubernetes 网站本身就包含了大量有用的文档可助你继续学习和成长。 你可以在 https://k8s.io/docs/tutorials/ 找到所有可用的 Kubernetes 文档教程。 <!-- If you have any questions regarding the Katacoda shutdown, or subsequent link removal from Kubernetes tutorial pages, please feel free to comment on the [general issue tracking the shutdown](https://github.com/kubernetes/website/issues/33936), or visit the #sig-docs channel on the Kubernetes Slack. --> 如果你对 Katacoda 关闭或后续从 Kubernetes 教程页面移除相关链接有任何疑问， 请在 [general issue tracking the shutdown](https://github.com/kubernetes/website/issues/33936) 上发表评论，或加入 Kubernetes Slack 的 #sig-docs 频道。 </ins>

Plan to localize recently. This issue is opened to avoid any probable conflicts. /assign /language zh
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
/close
Closing this issue. <detailsIn response to : /close </details


Question: * Learn more about [Kubernetes finalizers](/docs/concepts/overview/working-with-objects/finalizers/). * Learn about [garbage collection](/docs/concepts/architecture/garbage-collection). <del> * Read the API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System). </del>  No newline at end of file <ins> * Read the API reference for [object metadata](/docs/reference/kubernetes-api/common-definitions/object-meta/#System). </ins>

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: ``` ```shell <del> kubectl get pods -l run=cattle </del> <ins> kubectl get pods -l app=cattle </ins> ``` ``` NAME                      READY     STATUS    RESTARTS   AGE

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: After creating and scaling deployment using command kubectl create deployment cattle -- kubectl scale deployment cattle --replicas=5 When we execute below command to list pods with options -l kubectl get pods -l run=cattle O/P is No resources found in production namespace. Proposed Solution: kubectl get pods -l app=cattle Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/assign
can you / have you confirmed that this is a bug? If so, it's be good to record this issue as /kind bug
Yes, this is a bug. When was changed to , the label should have changed from to . This needs to be updated on a couple of other pages as well. /kind bug
/priority backlog


Question: The exact versions for below mapping table are for docker cli v1.40 and crictl v1.19.0. Please note that the list is not exhaustive. For example, it doesn't include experimental commands of docker cli. <ins> {{< note >}} </ins> Warn: the output format of CRICTL is similar to Docker CLI, despite some missing columns for some CLI. Make sure to check output for the specific command if your script output parsing. <ins> {{< /note >}} </ins> ### Retrieve Debugging Information

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. --Why is this needed mentions: (it's also OK to change to the correct case) Comments /language en /kind cleanup
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
/good-first-issue
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign


Question: ### Default deny all ingress traffic <del> You can create a "default" isolation policy for a namespace by creating a NetworkPolicy that selects all pods but does not allow any ingress traffic to those pods. </del> <ins> You can create a "default" ingress isolation policy for a namespace by creating a NetworkPolicy that selects all pods but does not allow any ingress traffic to those pods. </ins> {{< codenew file="service/networking/network-policy-default-deny-ingress.yaml" >}} <del> This ensures that even pods that aren't selected by any other NetworkPolicy will still be isolated. This policy does not change the default egress isolation behavior. </del> <ins> This ensures that even pods that aren't selected by any other NetworkPolicy will still be isolated for ingress. This policy does not affect isolation for egress from any pod. </ins> <del> ### Default allow all ingress traffic </del> <ins> ### Allow all ingress traffic </ins> <del> If you want to allow all traffic to all pods in a namespace (even if policies are added that cause some pods to be treated as "isolated"), you can create a policy that explicitly allows all traffic in that namespace. </del> <ins> If you want to allow all incoming connections to all pods in a namespace, you can create a policy that explicitly allows that. </ins> {{< codenew file="service/networking/network-policy-allow-all-ingress.yaml" >}} <ins> With this policy in place, no additional policy or policies can cause any incoming connection to those pods to be denied.  This policy has no effect on isolation for egress from any pod. </ins> ### Default deny all egress traffic You can create a "default" egress isolation policy for a namespace by creating a NetworkPolicy that selects all pods but does not allow any egress traffic from those pods.

As discussed in the sig-networking mailing list (), has not been fully updated since the introduction of egress filtering.
/sig network /sig docs /kind bug (it's a bug because the doc should already have been updated) /language en /triage accepted
/priority backlog


Question: <ins> --- title: CRI-O id: cri-o date: 2019-05-14 full_link: https://cri-o.io/#what-is-cri-o short_description: > Kubernetesに特化した軽量コンテナランタイム aka: tags: - tool --- Kubernetes CRIと一緒にOCIコンテナランタイムを使うためのツールです。 <!--more--> CRI-OはOpen Container Initiative (OCI) [runtime spec](https://www.github.com/opencontainers/runtime-spec)と互換性がある{{< glossary_tooltip text="コンテナ" term_id="container" >}}ランタイムを使用できるようにするための{{< glossary_tooltip term_id="cri" >}}の実装の１つです。 CRI-Oのデプロイによって、Kubernetesは任意のOCI準拠のランタイムを、{{< glossary_tooltip text="Pod" term_id="pod" >}}を実行するためのコンテナランタイムとして利用することと、リモートレジストリからOCIコンテナイメージを取得することができるようになります。 </ins>

Note that this issue is for Japanese Speaker This is a Feature Request What would you like to be Translate into Japanese Why is this needed There is no Japanese translation for this page Comments File to translate: Original: Japanese Localization document: /area localization /language ja /good-first-issue
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Note that this issue is for Japanese Speaker Original: /language ja /good-first-issue Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
/triage accepted


Question: ### Dead link issues Depending on where the dead link is reported, different actions are required to resolve the issue. Dead links in the API and Kubectl docs are automation issues and should be assigned a P1 until the problem can be fully understood. All other dead links are issues that need to be manually fixed and can be assigned a P3. <ins> ### Support requests or code bug reports Some issues that are opened for docs are actually issues with the underlying code, or requests for assistance when something (such as a tutorial) didn't work. Since these issues aren't related to documentation requests or problems, it is appropriate to respond directing the requester to potential support avenues, and if relevant, where an appropriate issue can be filed if the problem is a bug report. - example support request response ``` Thank you for this report, This sounds more like a request for support and less like an issue specifically for docs. I encourage you to bring your question to the `#kubernetes-users` channel in [Kubernetes slack](http://slack.k8s.io/). You can also search resources like [Stack Overflow](http://stackoverflow.com/questions/tagged/kubernetes) for answers  to similar questions. You can also open issues for Kubernetes functionality in https://github.com/kubernetes/kubernetes. If this is a documentation issue, please re-open this issue. ``` - example code bug report response ``` Thank you for this report, This sounds more like an issue with the code than an issue with the documentation. Please open an issue at https://github.com/kubernetes/kubernetes/issues. If this is a documentation issue, please re-open this issue. ``` </ins> {% endcapture %}

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... [ ] Feature Request [x] Bug Report Problem: For users using K8S versions 1.8 and lower that don't have the fix contained in it may be necessary to set for the OpenStack cloud provider when installing on OpenStack clusters that expose their Cinder endpoint using paths rather than ports to avoid auto-detection errors such as: This includes for users trying out K8S on a devstack environment, and potentially other deployment tools. In this situation it is possible to resolve using: Valid values for are: With being the default. Proposed Solution: Highlight the bs-version parameter as optional (so not minimal configuration) but required in some circumstances. Page to Update:


Question:
 --- title: Hello Minikube content_template: templates/tutorial weight: 5 menu: main: title: "Cominciamo!" weight: 10 post: >
Sei pronto a cominciare con Kubernetes? Crea un Kubernetes cluster ed esegui un'appliczione di esempio.
 card: name: tutorials weight: 10 --- {{% capture overview %}} Questo tutorial mostra come eseguire una semplice applicazione in Kubernetes utilizzando [Minikube](/docs/setup/learning-environment/minikube) e Katacoda. Katacoda permette di operare su un'installazione di Kubernetes dal tuo browser. {{< note >}} Come alternativa, è possibile eseguire questo tutorial [installando minikube](/docs/tasks/tools/install-minikube/) localmente. {{< /note >}} {{% /capture %}} {{% capture objectives %}} * Rilasciare una semplice applicazione su Minikube. * Eseguire l'applicazione. * Visualizzare i log dell'applicazione. {{% /capture %}} {{% capture prerequisites %}} Questo tutorial fornisce una container image che utilizza NGINX per risponde a tutte le richieste con un echo che visualizza i dati della richiesta stessa. {{% /capture %}} {{% capture lessoncontent %}} ## Crea un Minikube cluster 1. Click **Launch Terminal** {{< kat-button >}} {{< note >}}Se hai installato Minikube localmente, esegui `minikube start`.{{< /note >}} 2. Apri la console di Kubernetes nel browser: ```shell minikube dashboard ``` 3. Katacoda environment only: In alto alla finestra del terminale, fai click segno più, e a seguire click su **Select port to view on Host 1**. 4. Katacoda environment only: Inserisci `30000`, a seguire click su **Display Port**. ## Crea un Deployment Un Kubernetes [*Pod*](/docs/concepts/workloads/pods/pod/) è un gruppo di uno o più Containers, che sono uniti tra loro dal punto di vista amministrativo e che condividono lo stesso network. Il Pod in questo tutorial ha un solo Container. Un Kubernetes [*Deployment*](/docs/concepts/workloads/controllers/deployment/) monitora lo stato del Pod ed eventualmente provvedere a farlo ripartire nel caso questo termini. L'uso dei Deployments è la modalità raccomandata per gestire la creazione e lo scaling dei Pods. 1. Usa il comando `kubectl create` per creare un Deployment che gestisce un singolo Pod. Il Pod eseguirà un Container basato sulla Docker image specificata. ```shell kubectl create deployment hello-node --image=k8s.gcr.io/echoserver:1.4 ``` 2. Visualizza il Deployment: ```shell kubectl get deployments ``` L'output del comando è simile a: ``` NAME         READY   UP-TO-DATE   AVAILABLE   AGE hello-node   1/1     1            1           1m ``` 3. Visualizza il Pod creato dal Deployment: ```shell kubectl get pods ``` L'output del comando è simile a: ``` NAME                          READY     STATUS    RESTARTS   AGE hello-node-5f76cf6ccf-br9b5   1/1       Running   0          1m ``` 4. Visualizza gli eventi del cluster Kubernetes: ```shell kubectl get events ``` 5. Visualizza la configurazione di `kubectl`: ```shell kubectl config view ``` {{< note >}}Per maggiori informazioni sui comandi di `kubectl`, vedi [kubectl overview](/docs/user-guide/kubectl-overview/).{{< /note >}} ## Crea un Service Con le impostazioni di default, un Pod è accessibile solamente dagli indirizzi IP interni al Kubernetes cluster. Per far si che il Container `hello-node` sia accessibile dall'esterno del Kubernetes virtual network, è necessario esporre il Pod utilizzando un Kubernetes [*Service*](/docs/concepts/services-networking/service/). 1. Esponi il Pod su internet untilizzando il comando `kubectl expose`: ```shell kubectl expose deployment hello-node --type=LoadBalancer --port=8080 ``` Il flag `--type=LoadBalancer` indica la volontà di esporre il Service all'esterno del Kubernetes cluster. 2. Visualizza il Servizio appena creato: ```shell kubectl get services ``` L'output del comando è simile a: ``` NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE hello-node   LoadBalancer   10.108.144.78   <pending>     8080:30369/TCP   21s kubernetes   ClusterIP      10.96.0.1       <none>        443/TCP          23m ``` Nei cloud providers che supportano i servizi di tipo load balancers, viene fornito un indirizzo IP pubblico per permettere l'acesso al Service. Su Minikube, il service type `LoadBalancer` rende il Service accessibile attraverso il comando `minikube service`. 3. Esegui il comando: ```shell minikube service hello-node ``` 4. Katacoda environment only: Fai click segno più, e a seguire click su **Select port to view on Host 1**. 5. Katacoda environment only: Fai attenzione al numero di 5 cifre visualizzato a fianco di `8080` nell'output del comando. Questo port number è generato casualmente e può essere diverso nel tuo caso. Inserisci il tuo port number nella textbox, e a seguire fai click su Display Port. Nell'esempio precedente, avresti scritto `30369`. Questo apre un finestra nel browser dove l'applicazione visuallizza l'echo delle richieste ricevute. ## Attiva gli addons Minikube include un set {{< glossary_tooltip text="addons" term_id="addons" >}} che possono essere attivati, disattivati o eseguti nel ambiente Kubernetes locale. 1. Elenca gli addons disponibili: ```shell minikube addons list ``` L'output del comando è simile a: ``` addon-manager: enabled dashboard: enabled default-storageclass: enabled efk: disabled freshpod: disabled gvisor: disabled helm-tiller: disabled ingress: disabled ingress-dns: disabled logviewer: disabled metrics-server: disabled nvidia-driver-installer: disabled nvidia-gpu-device-plugin: disabled registry: disabled registry-creds: disabled storage-provisioner: enabled storage-provisioner-gluster: disabled ``` 2. Attiva un addon, per esempio, `metrics-server`: ```shell minikube addons enable metrics-server ``` L'output del comando è simile a: ``` metrics-server was successfully enabled ``` 3. Visualizza i Pods ed i Service creati in precedenza: ```shell kubectl get pod,svc -n kube-system ``` L'output del comando è simile a: ``` NAME                                        READY     STATUS    RESTARTS   AGE pod/coredns-5644d7b6d9-mh9ll                1/1       Running   0          34m pod/coredns-5644d7b6d9-pqd2t                1/1       Running   0          34m pod/metrics-server-67fb648c5                1/1       Running   0          26s pod/etcd-minikube                           1/1       Running   0          34m pod/influxdb-grafana-b29w8                  2/2       Running   0          26s pod/kube-addon-manager-minikube             1/1       Running   0          34m pod/kube-apiserver-minikube                 1/1       Running   0          34m pod/kube-controller-manager-minikube        1/1       Running   0          34m pod/kube-proxy-rnlps                        1/1       Running   0          34m pod/kube-scheduler-minikube                 1/1       Running   0          34m pod/storage-provisioner                     1/1       Running   0          34m NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE service/metrics-server         ClusterIP   10.96.241.45    <none>        80/TCP              26s service/kube-dns               ClusterIP   10.96.0.10      <none>        53/UDP,53/TCP       34m service/monitoring-grafana     NodePort    10.99.24.54     <none>        80:30002/TCP        26s service/monitoring-influxdb    ClusterIP   10.111.169.94   <none>        8083/TCP,8086/TCP   26s ``` 4. Disabilita `metrics-server`: ```shell minikube addons disable metrics-server ``` L'output del comando è simile a: ``` metrics-server was successfully disabled ``` ## Clean up Adesso puoi procedere a fare clean up delle risorse che hai creato nel tuo cluster: ```shell kubectl delete service hello-node kubectl delete deployment hello-node ``` Eventualmente, puoi stoppare la Minikube virtual machine (VM): ```shell minikube stop ``` Eventualmente, puoi cancellare la Minikube VM: ```shell minikube delete ``` {{% /capture %}} {{% capture whatsnext %}} * Approfondisci la tua conoscenza dei [Deployments](/docs/concepts/workloads/controllers/deployment/). * Approfondisci la tua conoscenza di [Rilasciare applicazioni](/docs/tasks/run-application/run-stateless-application-deployment/). * Approfondisci la tua conoscenza dei [Services](/docs/concepts/services-networking/service/). {{% /capture %}}

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: batch/v1 kind: Job metadata: name: 'indexed-job' spec: completions: 5 parallelism: 3 completionMode: Indexed template: spec: restartPolicy: Never initContainers: - name: 'input' image: 'docker.io/library/bash' command: - "bash" - "-c" - | items=(foo bar baz qux xyz) echo ${items[$JOB_COMPLETION_INDEX]} > /input/data.txt volumeMounts: - mountPath: /input name: input containers: - name: 'worker' image: 'docker.io/library/busybox' command: - "rev" - "/input/data.txt" volumeMounts: - mountPath: /input name: input volumes: - name: input emptyDir: {} </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
/triage accepted


Question: For more information about `kubeadm init` arguments, see the [kubeadm reference guide](/docs/reference/setup-tools/kubeadm/kubeadm/). <del> For a complete list of configuration options, see the [configuration file documentation](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file). </del> <ins> To configure `kubeadm init` with a configuration file see [Using kubeadm init with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file). </ins> To customize control plane components, including optional IPv6 assignment to liveness probe for control plane components and etcd server, provide extra arguments to each component as documented in [custom arguments](/docs/setup/production-environment/tools/kubeadm/control-plane-flags/).

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> --- title: 在 Linux 系统中安装并设置 kubectl content_type: task weight: 10 card: name: tasks weight: 20 title: 在 Linux 系统中安装 kubectl --- <!-- --- reviewers: - mikedanese title: Install and Set Up kubectl on Linux content_type: task weight: 10 card: name: tasks weight: 20 title: Install kubectl on Linux --- --> ## {{% heading "prerequisites" %}} <!-- You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. Using the latest version of kubectl helps avoid unforeseen issues. --> kubectl 版本和集群版本之间的差异必须在一个小版本号内。 例如：v1.2 版本的客户端只能与 v1.1、v1.2 和 v1.3 版本的集群一起工作。 用最新版的 kubectl 有助于避免不可预见的问题。 <!-- ## Install kubectl on Linux --> ## 在 Linux 系统中安装 kubectl {#install-kubectl-on-linux} <!-- The following methods exist for installing kubectl on Linux: --> 在 Linux 系统中安装 kubectl 有如下几种方法： - [{{% heading "prerequisites" %}}](#{{% heading "prerequisites" %}}) - [在 Linux 系统中安装 kubectl](#install-kubectl-on-linux) - [用 curl 在 Linux 系统中安装 kubectl](#install-kubectl-binary-with-curl-on-linux) - [用原生包管理工具安装](#install-using-native-package-management) - [用其他包管理工具安装](#install-using-other-package-management) - [作为谷歌云 SDK 的一部分，在 Linux 中安装](#install-on-linux-as-part-of-the-google-cloud-sdk) - [验证 kubectl 配置](#verify-kubectl-configration) - [可选的 kubectl 配置](#optional-kubectl-configurations) - [启用 shell 自动补全功能](#enable-shell-autocompletion) - [{{% heading "whatsnext" %}}](#{{% heading "whatsnext" %}}) <!-- ### Install kubectl binary with curl on Linux --> ### 用 curl 在 Linux 系统中安装 kubectl {#install-kubectl-binary-with-curl-on-linux} <!-- 1. Download the latest release with the command: --> 1. 用以下命令下载最新发行版： ```bash curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl" ``` {{< note >}} <!-- To download a specific version, replace the `$(curl -L -s https://dl.k8s.io/release/stable.txt)` portion of the command with the specific version. For example, to download version {{< param "fullversion" >}} on Linux, type: --> 如需下载某个指定的版本，请用指定版本号替换该命令的这一部分： `$(curl -L -s https://dl.k8s.io/release/stable.txt)`。 例如，要在 Linux 中下载 {{< param "fullversion" >}} 版本，请输入： ```bash curl -LO https://dl.k8s.io/release/{{< param "fullversion" >}}/bin/linux/amd64/kubectl ``` {{< /note >}} <!-- 1. Validate the binary (optional) Download the kubectl checksum file: --> 1. 验证该可执行文件（可选步骤） 下载 kubectl 校验和文件： ```bash curl -LO "https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl.sha256" ``` <!-- Validate the kubectl binary against the checksum file: --> 基于校验和文件，验证 kubectl 的可执行文件： ```bash echo "$(<kubectl.sha256) kubectl" | sha256sum --check ``` <!-- If valid, the output is: --> 验证通过时，输出为： ```console kubectl: OK ``` <!-- If the check fails, `sha256` exits with nonzero status and prints output similar to: --> 验证失败时，`sha256` 将以非零值退出，并打印如下输出： ```bash kubectl: FAILED sha256sum: WARNING: 1 computed checksum did NOT match ``` {{< note >}} <!-- Download the same version of the binary and checksum. --> 下载的 kubectl 与校验和文件版本必须相同。 {{< /note >}} <!-- 1. Install kubectl --> 1. 安装 kubectl ```bash sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl ``` {{< note >}} <!-- If you do not have root access on the target system, you can still install kubectl to the `~/.local/bin` directory: --> 即使你没有目标系统的 root 权限，仍然可以将 kubectl 安装到目录 `~/.local/bin` 中： ```bash mkdir -p ~/.local/bin/kubectl mv ./kubectl ~/.local/bin/kubectl # and then add ~/.local/bin/kubectl to $PATH ``` {{< /note >}} <!-- 1. Test to ensure the version you installed is up-to-date: --> 1. 执行测试，以保障你安装的版本是最新的： ```bash kubectl version --client ``` <!-- ### Install using native package management --> ### 用原生包管理工具安装 {#install-using-native-package-management} {{< tabs name="kubectl_install" >}} {{< tab name="Ubuntu、Debian 或 HypriotOS" codelang="bash" >}} sudo apt-get update && sudo apt-get install -y apt-transport-https gnupg2 curl curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add - echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee -a /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubectl {{< /tab >}} {{< tab name="CentOS、RHEL 或 Fedora" codelang="bash" >}}cat <<EOF > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=Kubernetes baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64 enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg EOF yum install -y kubectl {{< /tab >}} {{< /tabs >}} <!-- ### Install using other package management --> ### 用其他包管理工具安装 {#install-using-other-package-management} {{< tabs name="other_kubectl_install" >}} {{% tab name="Snap" %}} <!-- If you are on Ubuntu or another Linux distribution that support [snap](https://snapcraft.io/docs/core/install) package manager, kubectl is available as a [snap](https://snapcraft.io/) application. --> 如果你使用的 Ubuntu 或其他 Linux 发行版，内建支持 [snap](https://snapcraft.io/docs/core/install) 包管理工具， 则可用 [snap](https://snapcraft.io/) 命令安装 kubectl。 ```shell snap install kubectl --classic kubectl version --client ``` {{% /tab %}} {{% tab name="Homebrew" %}} <!-- If you are on Linux and using [Homebrew](https://docs.brew.sh/Homebrew-on-Linux) package manager, kubectl is available for [installation](https://docs.brew.sh/Homebrew-on-Linux#install). --> 如果你使用 Linux 系统，并且装了 [Homebrew](https://docs.brew.sh/Homebrew-on-Linux) 包管理工具， 则可以使用这种方式[安装](https://docs.brew.sh/Homebrew-on-Linux#install) kubectl。 ```shell brew install kubectl kubectl version --client ``` {{% /tab %}} {{< /tabs >}} <!-- ### Install on Linux as part of the Google Cloud SDK --> ### 作为谷歌云 SDK 的一部分，在 Linux 上安装 {#install-on-linux-as-part-of-the-google-cloud-sdk} {{< include "included/install-kubectl-gcloud.md" >}} <!-- ## Verify kubectl configuration --> ## 验证 kubectl 配置 {#verify-kubectl-configration} {{< include "included/verify-kubectl.md" >}} ## kubectl 的可选配置 {#optional-kubectl-configurations} ### 启用 shell 自动补全功能 {#enable-shell-autocompletion} <!-- kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing. Below are the procedures to set up autocompletion for Bash and Zsh. --> kubectl 为 Bash 和 Zsh 提供自动补全功能，可以减轻许多输入的负担。 下面是为 Bash 和 Zsh 设置自动补全功能的操作步骤。 {{< tabs name="kubectl_autocompletion" >}} {{< tab name="Bash" include="included/optional-kubectl-configs-bash-linux.md" />}} {{< tab name="Zsh" include="included/optional-kubectl-configs-zsh.md" />}} {{< /tabs >}} ## {{% heading "whatsnext" %}} {{< include "included/kubectl-whats-next.md" >}} </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: title: Code Contributor id: code-contributor date: 2018-04-12 <del> full_link: /docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > A person who develops and contributes code to the Kubernetes open source codebase.

Problem: The text on is not working, it should point to these Check the page for the problem. Page to Update: Proposed Solution: It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the texts Code Contributor to and not to this . /kind document /assign /language en
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : Problem: The text on is not working, it should point to these It should resolve this issue by adding a simple link and enhancing the document line. Update the link on the texts to and not to this . /assign /language en 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
duplicate triage this issue will fix it
Hey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /triage accepted /good-first-issue /assign amolmote
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Hey, thanks for amolmote to notice, I created an issue that was a duplicate of this one, there is some more information available there . I'll mark this one as a good first issue as well and put the previously assigned person. /good-first-issue /assign amolmote 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.


Question: title: Code Contributor id: code-contributor date: 2018-04-12 <del> full_link: /docs/community/devel/ </del> <ins> full_link: https://github.com/kubernetes/community/tree/master/contributors/devel </ins> short_description: > A person who develops and contributes code to the Kubernetes open source codebase.

</details
Oh, I just noticed that already assign themselves on this issue. Since it's been a bit more than two months, please tell amolmote if you are still working on this one or if it's okay that they take over.


Question: --> DaemonSet 确保所有符合条件的节点都运行该 Pod 的一个副本。 通常，运行 Pod 的节点由 Kubernetes 调度器选择。 <del> 不过，DaemonSet pods 由 DaemonSet 控制器创建和调度。这就带来了以下问题： </del> <ins> 不过，DaemonSet Pods 由 DaemonSet 控制器创建和调度。这就带来了以下问题： </ins> * Pod 行为的不一致性：正常 Pod 在被创建后等待调度时处于 `Pending` 状态， DaemonSet Pods 创建后不会处于 `Pending` 状态下。这使用户感到困惑。

“ DaemonSet spec.template.“ “”“”
Mind propose a fix?
/triage accepted
/language zh (I presume)
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /language zh (I presume) Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
yes,this is chinese languge,“”change to“”
/assign


Question: <!-- Create a DaemonSet based on the YAML file: --> <del> 基于 YAML 文件创建 DaemonSet: </del> <ins> 基于 YAML 文件创建 DaemonSet： </ins> ``` kubectl apply -f https://k8s.io/examples/controllers/daemonset.yaml


Question: other = "报告问题" [layouts_docs_partials_feedback_thanks] <del> other = "感谢反馈。如果您有一个关于如何使用 Kubernetes 的特定的、需要答案的问题，可以访问" </del> <ins> other = "感谢反馈。如果你有一个关于如何使用 Kubernetes 的具体问题需要答案，可以访问" </ins> [layouts_docs_search_fetching] other = "检索结果中.."

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 zh-cn
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /language zh-cn 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
/sig-docs
/language zh
/triage accepted /assign


Question:
The Master is responsible for managing the cluster. The master coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.

A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster. Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes master. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.

The Control Plane is responsible for managing the cluster. The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates.

A node is a VM or a physical computer that serves as a worker machine in a Kubernetes cluster. Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane. The node should also have tools for handling container operations, such as containerd or Docker. A Kubernetes cluster that handles production traffic should have a minimum of three nodes.

Masters manage the cluster and the nodes that are used to host the running applications.

Control Planes manage the cluster and the nodes that are used to host the running applications.

When you deploy applications on Kubernetes, you tell the master to start the application containers. The master schedules the containers to run on the cluster's nodes. The nodes communicate with the master using the Kubernetes API, which the master exposes. End users can also use the Kubernetes API directly to interact with the cluster.

When you deploy applications on Kubernetes, you tell the control plane to start the application containers. The control plane schedules the containers to run on the cluster's nodes. The nodes communicate with the control plane using the Kubernetes API, which the control plane exposes. End users can also use the Kubernetes API directly to interact with the cluster.

A Kubernetes cluster can be deployed on either physical or virtual machines. To get started with Kubernetes development, you can use Minikube.  Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node. Minikube is available for Linux, macOS, and Windows systems. The Minikube CLI provides basic bootstrapping operations for working with your cluster, including start, stop, status, and delete. For this tutorial, however, you'll use a provided online terminal with Minikube pre-installed.

A Kubernetes cluster can be deployed on either physical or virtual machines. To get started with Kubernetes development, you can use Minikube. Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node. Minikube is available for Linux, macOS, and Windows systems. The Minikube CLI provides basic bootstrapping operations for working with your cluster, including start, stop, status, and delete. For this tutorial, however, you'll use a provided online terminal with Minikube pre-installed.

Now that you know what Kubernetes is, let's go to the online tutorial and start our first cluster!

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: - protocol: TCP port: 80 targetPort: 9376 <del> nodePort: 30061 </del> clusterIP: 10.0.171.239 loadBalancerIP: 78.11.24.19 type: LoadBalancer

<!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!--Required Information--This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [x] Bug Report Problem: In the service type: LoadBalancer example configuration, having the field NodePort wouldn't work. Proposed Solution: To remove the NodePort configuration in the example config. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--


Question: You can renew your certificates manually at any time with the `kubeadm certs renew` command. <del> This command performs the renewal using CA (or front-proxy-CA) certificate and key stored in `/etc/kubernetes/pki`. </del> <ins> This command performs the renewal using CA (or front-proxy-CA) certificate and key stored in `/etc/kubernetes/pki`. After running the command you should restart the control plane Pods. This is required since dynamic certificate reload is currently not supported for all components and certificates. [Static Pods](/docs/tasks/configure-pod-containerstatic-pod/) are managed by the local kubelet and not by the API Server, thus kubectl cannot be used to delete and restart them. To restart a static Pod you can temporarily remove its manifest file from `/etc/kubernetes/manifests/` and wait for 20 seconds (see the `fileCheckFrequency` value in [KubeletConfiguration struct](/docs/ reference/config-api/kubelet-config.v1beta1/). The kubelet will terminate the Pod if it's no longer in the manifest directory. You can then move the file back and after another `fileCheckFrequency` period, the kubelet will recreate the Pod and the certificate renewal for the component can complete. </ins> {{< warning >}} If you are running an HA cluster, this command needs to be executed on all the control-plane nodes.

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: After manually certificate renewal, , and need to be properly restarted. This should be described in (maybe) this section: , and currently not. Ref: Proposed Solution: Describe if , and need to be restarted, and also describe the proper way to restart them. Page to Update:
/sig cluster-lifecycle /help PRs welcome /priority backlog given prints instructions that users must restart. etcd should be included in this list. there are multiple ways to restart the static pods: rename the folder for more than 20 seconds []. the containers using the container runtime CLI (setup specific). ... i'd prefer option 1. [] see
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 : /sig cluster-lifecycle /help PRs welcome given prints instructions that users must restart. temporary rename the folder for more than 20 seconds []. restart the containers using the container runtime CLI (setup specific). ... see </details
/remove-kind bug
/triage accepted /kind cleanup
Hi, I would like to help but I have a question first. How does changing the name of help? I mean the behavior of Kubelet is not clear for me regarding this fileFrequencyCheck and the corresponding docs do not help, too. I like to explain that in certificate renewal docs, too.
The better place to document details about the static pod refresh timeouts is the "creating static pods page: If you remove a manifest file, the kubelet will find out about that every ~20sec and remove the pod from managent. If the file is then brought back the kubelet will recreate the pod acting like a restart.


Question: - `token-secret`: A random 16 character string as the actual token secret. Required. - `description`: A human-readable string that describes what the token is used for. Optional. <del> - `expiration`: An absolute UTC time using RFC3339 specifying when the token </del> <ins> - `expiration`: An absolute UTC time using [RFC3339](https://datatracker.ietf.org/doc/html/rfc3339) specifying when the token </ins> should be expired. Optional. - `usage-bootstrap-<usage>`: A boolean flag indicating additional usage for the bootstrap token.

This is a Feature Request What would you like to be Add Hyperlink to under in concept page. Why is this needed Adding the hyperlink will helps the readers to know about RFC3339. Comments /sig docs /language en
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 auth
Fixed it here:


Question: > __Important!__ A volume can only be mounted using one access mode at a time, even if it supports many.  For example, a GCEPersistentDisk can be mounted as ReadWriteOnce by a single node or ReadOnlyMany by many nodes, but not at the same time. <ins> | Volume Plugin        | ReadWriteOnce| ReadOnlyMany| ReadWriteMany| | :---                 |     :---:    |    :---:    |    :---:     | | AWSElasticBlockStore | x            | -           | -            | | AzureFile            | x            | x           | x            | | CephFS               | x            | x           | x            | | Cinder               | x            | -           | -            | | FC                   | x            | x           | -            | | FlexVolume           | x            | x           | -            | | GCEPersistentDisk    | x            | x           | -            | | Glusterfs            | x            | x           | x            | | HostPath             | x            | -           | -            | | iSCSI                | x            | x           | -            | | NFS                  | x            | x           | x            | | RDB                  | x            | x           | -            | | VsphereVolume        | x            | -           | -            | </ins> ### Recycling Policy Current recycling policies are:

This is a... <!-- choose one by changing [ ] to [x] --- [ ] Feature Request [X] Bug Report Problem: The command to create the sock-shop application error out (it's also not necessary to create the namespace beforehand as that is already define in ): Proposed Solution: Change the command to: Page to Update: Kubernetes Version: 1.6.1
I think this is an issue that needs to be fixed in socks shop.
This merged PR should resolve the issue


Question: ## {{% heading "prerequisites" %}} <del> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. </del> <ins> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v{{< skew latestVersion >}} client can communicate with v{{< skew prevMinorVersion >}}, v{{< skew latestVersion >}}, and v{{< skew nextMinorVersion >}} control planes. </ins> Using the latest version of kubectl helps avoid unforeseen issues. ## Install kubectl on Linux

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are a couple of issues with existing wording: “master” should be read “control plane” versions aren't current. Proposed Solution: Replace that text with: Page to Update: Additional Information: /language en /kind bug /wg naming
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
/help If you're picking this up and want to be extra neat, replace those specific version numbers with shortcodes that automatically fill in based on the current release; for example:
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help </details
/assign


Question: <ins> --- title: 名前空間レベルでのPodセキュリティの標準の適用 content_type: チュートリアル weight: 20 --- {{% alert title="Note" %}} このチュートリアルは、新しいクラスターにのみ適用されます。 {{% /alert %}} Podセキュリティアドミッション(PSA)は、[ベータへ進み](/blog/2021/12/09/pod-security-admission-beta/)、v1.23以降でデフォルトで有効になっています。 Podセキュリティアドミッションは、Podが作成される際に、[Podセキュリティの標準](/ja/docs/concepts/security/pod-security-standards/)の適用の認可を制御するものです。 このチュートリアルでは、一度に1つの名前空間で`baseline` Podセキュリティ標準を強制します。 Podセキュリティの標準を複数の名前空間に一度にクラスターレベルで適用することもできます。やり方については[クラスターレベルでのPodセキュリティの標準の適用](/docs/tutorials/security/cluster-level-pss/)を参照してください。 ## {{% heading "prerequisites" %}} ワークステーションに以下をインストールしてください: - [KinD](https://kind.sigs.k8s.io/docs/user/quick-start/#installation) - [kubectl](/ja/docs/tasks/tools/) ## クラスターの作成 1. 以下のように`KinD`クラスターを作成します。 ```shell kind create cluster --name psa-ns-level ``` 出力は次のようになります: ``` Creating cluster "psa-ns-level" ... ✓ Ensuring node image (kindest/node:v{{< skew currentPatchVersion >}}) 🖼 ✓ Preparing nodes 📦 ✓ Writing configuration 📜 ✓ Starting control-plane 🕹 ✓ Installing CNI 🔌 ✓ Installing StorageClass 💾 Set kubectl context to "kind-psa-ns-level" You can now use your cluster with: kubectl cluster-info --context kind-psa-ns-level Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/ ``` 1. kubectl のコンテキストを新しいクラスターにセットします: ```shell kubectl cluster-info --context kind-psa-ns-level ``` 出力は次のようになります: ``` Kubernetes control plane is running at https://127.0.0.1:50996 CoreDNS is running at https://127.0.0.1:50996/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. ``` ## 名前空間の作成 `example`と呼ぶ新しい名前空間を作成します: ```shell kubectl create ns example ``` 出力は次のようになります: ``` namespace/example created ``` ## 名前空間へのPodセキュリティの標準チェックの有効化 1. ビルトインのPod Security Admissionでサポートされているラベルを使って、この名前空間のPodセキュリティの標準を有効にします。 このステップでは、_baseline_ Podセキュリティの標準の最新バージョンに合わないPodについて警告するチェックを設定します。 ```shell kubectl label --overwrite ns example  pod-security.kubernetes.io/warn=baseline  pod-security.kubernetes.io/warn-version=latest ``` 2. ラベルを使って、任意の名前空間に対して複数のPodセキュリティの標準チェックを設定できます。 以下のコマンドは、`baseline` Podセキュリティの標準を`enforce`(強制)としますが、`restricted` Podセキュリティの標準には最新バージョンに準じて`warn`(警告)および`audit`(監査)とします(デフォルト値)。 ```shell kubectl label --overwrite ns example  pod-security.kubernetes.io/enforce=baseline  pod-security.kubernetes.io/enforce-version=latest  pod-security.kubernetes.io/warn=restricted  pod-security.kubernetes.io/warn-version=latest  pod-security.kubernetes.io/audit=restricted  pod-security.kubernetes.io/audit-version=latest ``` ## Podセキュリティの標準の強制の実証 1. `example`名前空間内に`baseline` Podを作成します: ```shell kubectl apply -n example -f https://k8s.io/examples/security/example-baseline-pod.yaml ``` Podは正常に起動しますが、出力には警告が含まれています。例えば: ``` Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "nginx" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "nginx" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "nginx" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "nginx" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost") pod/nginx created ``` 1. `default`名前空間内に`baseline` Podを作成します: ```shell kubectl apply -n default -f https://k8s.io/examples/security/example-baseline-pod.yaml ``` 出力は次のようになります: ``` pod/nginx created ``` `example`名前空間にだけ、Podセキュリティの標準のenforceと警告の設定が適用されました。 `default`名前空間内では、警告なしに同じPodを作成できました。 ## 後片付け では、上記で作成したクラスターを、以下のコマンドを実行して削除します: ```shell kind delete cluster --name psa-ns-level ``` ## {{% heading "whatsnext" %}} - 前出の一連の手順を一度に全て行うために[シェルスクリプト](/examples/security/kind-with-namespace-level-baseline-pod-security.sh)を実行します。 1. KinDクラスターを作成します。 2. 新しい名前空間を作成します。 3. `enforce`モードでは`baseline` Podセキュリティの標準を適用し、`warn`および`audit`モードでは`restricted` Podセキュリティの標準を適用します。 4. これらのPodセキュリティの標準を適用した新しいPodを作成します。 - [Podのセキュリティアドミッション](/ja/docs/concepts/security/pod-security-admission/) - [Podセキュリティの標準](/ja/docs/concepts/security/pod-security-standards/) - [クラスターレベルでのPodセキュリティの標準の適用](/ja/docs/tutorials/security/cluster-level-pss/) </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 <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Translate into Japanese Why is this needed Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language ja /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: title: Picking the Right Solution --- <del> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to rack of </del> <ins> Kubernetes can run on various platforms: from your laptop, to VMs on a cloud provider, to a rack of </ins> bare metal servers. The effort required to set up a cluster varies from running a single command to crafting your own customized cluster. Use this guide to choose a solution that fits your needs.


Question: } body.cid-community #videos { <del> width: 100vw; </del> <ins> width: 100%; </ins> max-width: initial; padding: 0.5em 5vw 5% 5vw; /* fallback in case calc() fails */ background-color: #eeeeee;

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:
  For your first Deployment, you'll use a Node.js application packaged in a Docker container. (If you didn't already try creating a Node.js application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial).   For your first Deployment, you'll use a hello-node application packaged in a Docker container that uses NGINX to echo back all the requests. (If you didn't already try creating a hello-node application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial).

Now that you know what Deployments are, let's go to the online tutorial and deploy our first app!

The below sentence is there towards the end of this page: (If you didn't already try creating a application and deploying it using a container, you can do that first by following the instructions from the Hello Minikube tutorial). But the "Hello Minkube" tutorial link has nothing about creating any application or deploying it.
This is indeed a documentation bug. The v1.4 echoserver uses NGINX without Good spot, /kind bug /language en /triage accepted /priority backlog
/assign


Question: {{% capture whatsnext %}} <del> - [Learn about how to use `kubectl` for application introspection and debugging.](/docs/tasks/debug-application-cluster/debug-application-introspection/) - [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/) </del> <ins> - Learn about [how to use `kubectl` for application introspection and debugging](/docs/tasks/debug-application-cluster/debug-application-introspection/). - See [Configuration Best Practices and Tips](/docs/concepts/configuration/overview/). </ins> {{% /capture %}}

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: {{% /tab %}} {{% tab name="URL copy and paste" %}} <del> If you don't want minikube to open a web browser for you, run the dashboard command with the </del> <ins> If you don't want minikube to open a web browser for you, run the `dashboard` subcommand with the </ins> `--url` flag. `minikube` outputs a URL that you can open in the browser you prefer. Open a **new** terminal, and run:

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page has a broken link / anchor named "Open Dashboard with URL" in the Dashboard section. The markdown anchor named #open-dashboard-with-url cannot be resolved. Proposed Solution: This link / anchor needs to be fixed, however I am not able to understand what section it referred to in the first place. Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
/language en /sig docs
Page related to the issue:
I think the URL should be replaced with
Let's wait for the opinions of other members regarding the same.
I would to like to work on this issue is the triage gets accepted.
Thanks. I checked further. Please check . Here you will find the section for the "Open Dashboard with URL". It seems this section was removed in later versions of this page, but the anchor/link was not removed.
The anchor for "Open Dashboard with URL," , is now obsolete as we've integrated this content into tab layout (Launch a browser, URL copy and paste) on the.
Pull request has been submitted quite some time ago to handle this issue, and it's awaiting review and approval for merging.
Indeed. Once is approved, it will address this issue. I do not see anyone actively working on this PR since many days. has volunteered to help. please take a look at There are some suggestions from in the PR already.
/triage accepted


Question:
Histogram	 Admission controller latency histogram in seconds, identified by name and broken out for each operation and API resource and type (validate or admit).
name

operation

rejected

type

   None

apiserver_admission_step_admission_duration_seconds	 STABLE	 Histogram	 Admission sub-step latency histogram in seconds, broken out for each operation and API resource and step type (validate or admit).
operation

rejected

type

   None

apiserver_admission_webhook_admission_duration_seconds	 STABLE	 Histogram	 Admission webhook latency histogram in seconds, identified by name and broken out for each operation and API resource and type (validate or admit).
name

operation

rejected

type

   None

apiserver_current_inflight_requests	 STABLE	 Gauge	 Maximal number of currently used inflight request limit of this apiserver per request kind in last second.
request_kind

   None

apiserver_longrunning_requests	 STABLE	 Gauge	 Gauge of all active long-running apiserver requests broken out by verb, group, version, resource, scope and component. Not all requests are tracked this way.
component

group

resource

scope

subresource

verb

version

   None

apiserver_request_duration_seconds	 STABLE	 Histogram	 Response latency distribution in seconds for each verb, dry run value, group, version, resource, subresource, scope and component.
component

dry_run

group

resource

scope

subresource

verb

version

   None

apiserver_request_total	 STABLE	 Counter	 Counter of apiserver requests broken out for each verb, dry run value, group, version, resource, scope, component, and HTTP response code.
code

component

dry_run

group

resource

scope

subresource

verb

version

   None

apiserver_requested_deprecated_apis	 STABLE	 Gauge	 Gauge of deprecated APIs that have been requested, broken out by API group, version, resource, subresource, and removed_release.
group

removed_release

resource

subresource

version

   None

apiserver_response_sizes	 STABLE	 Histogram	 Response size distribution in bytes for each group, version, verb, resource, subresource, scope and component.
component

group

resource

scope

subresource

verb

version

   None

apiserver_storage_objects	 STABLE	 Gauge	 Number of stored objects at the time of last check split by kind.
resource

cronjob_controller_job_creation_skew_duration_seconds	 STABLE	 Histogram	 Time between when a cronjob is scheduled to be run, and when the corresponding job is created

job_controller_job_pods_finished_total	 STABLE	 Counter	 The number of finished Pods that are fully tracked
completion_mode

result

job_controller_job_sync_duration_seconds	 STABLE	 Histogram	 The time it took to sync a job
action

completion_mode

result

job_controller_job_syncs_total	 STABLE	 Counter	 The number of job syncs
action

completion_mode

result

job_controller_jobs_finished_total	 STABLE	 Counter	 The number of finished jobs
completion_mode

reason

result

   None

node_collector_evictions_total	 STABLE	 Counter	 Number of Node evictions that happened since current instance of NodeController started.
zone

   None

scheduler_framework_extension_point_duration_seconds	 STABLE	 Histogram	 Latency for running all plugins of a specific extension point.
extension_point

profile

status

   None

scheduler_pending_pods	 STABLE	 Gauge	  Number of pending pods, by the queue type. 'active' means number of pods in activeQ; 'backoff' means number of pods in backoffQ; 'unschedulable' means number of pods in unschedulablePods that the scheduler attempted to schedule and failed; 'gated' is the number of unschedulable pods that the scheduler never attempted to schedule because they are gated.	   Number of pending pods, by the queue type. 'active' means number of pods in activeQ; 'backoff' means number of pods in backoffQ; 'unschedulable' means number of pods in unschedulablePods.
queue

   None

scheduler_pod_scheduling_attempts	 STABLE	 Histogram	 Number of attempts to successfully schedule a pod.
   None	 None

scheduler_pod_scheduling_duration_seconds	 STABLE	 Histogram	 E2e latency for a pod being scheduled which may include multiple scheduling attempts.
attempts

   None

scheduler_preemption_attempts_total	 STABLE	 Counter	 Total preemption attempts in the cluster till now
   None	 None

scheduler_preemption_victims	 STABLE	 Histogram	 Number of selected preemption victims
   None	 None

scheduler_queue_incoming_pods_total	 STABLE	 Counter	 Number of pods added to scheduling queues by event and queue type.
event

queue

   None

scheduler_schedule_attempts_total	 STABLE	 Counter	 Number of attempts to schedule pods, by the result. 'unschedulable' means a pod could not be scheduled, while 'error' means an internal scheduler problem.
profile

result

   None

scheduler_scheduling_attempt_duration_seconds	 STABLE	 Histogram	 Scheduling attempt latency in seconds (scheduling algorithm + binding)
profile

result

   None

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: documents metrics for Kubernetes v1.26 but that's incorrect because at the time I'm filing this the live documentation is for Kubernetes v1.25 Proposed Solution: Revert whichever PR bumped the document too early or do a careful partial revert that only omits the v1.26 changes Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--Additional Information: /sig instrumentation /language en If v1.26 gets released before we fix this, it's OK to close the issue. Consider a backport to the v1.25 docs, though.
/assign
/triage accepted
/assign


Question: {{% /capture %}} <ins> ## インストールの確認 ハイパーバイザーとMinikube両方のインストール成功を確認するため、以下のコマンドをローカルKubernetesクラスターを起動するために実行してください: {{< note >}} `minikube start`で`--vm-driver`の設定をするため、次の`<driver_name>`の部分では、インストールしたハイパーバイザーの名前を小文字で入力してください。`--vm-driver`値のすべてのリストは、[specifying the VM driver documentation](https://kubernetes.io/docs/setup/learning-environment/minikube/#specifying-the-vm-driver)で確認できます。 {{< /note >}} ```shell minikube start --vm-driver=<driver_name> ``` `minikube start`が完了した場合、次のコマンドを実行してクラスターの状態を確認します。 ```shell minikube status ``` クラスターが起動していると、`minikube status`の出力はこのようになります。 ``` host: Running kubelet: Running apiserver: Running kubeconfig: Configured ``` 選択したハイパーバイザーでMinikubeが動作しているか確認した後は、そのままMinikubeを使い続けることもできます。また、クラスターを停止することもできます。クラスターを停止するためには、次を実行してください。 ```shell minikube stop ``` </ins> ## ローカル状態のクリーンアップ {#cleanup-local-state} もし以前に　Minikubeをインストールしていたら、以下のコマンドを実行します。

This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update tasks/tools/install- to follow v1.17 of the original (Englist) text. Why is this needed content/ja/docs/tasks/tools/install- is outdated. Comments /language ja /good-first-issue File to update Original https://v1- diff between translated and v1.17 Note Currently, we use branch. Please open a PR targeting the branch. ref If you have a question, feel free to ask us at #kubernetes-docs-ja channel.
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --Update tasks/tools/install- to follow v1.17 of the original (Englist) text. content/ja/docs/tasks/tools/install- is outdated. /language ja /good-first-issue Currently, we use branch. Please open a PR targeting the branch. 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
/assign
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details


Question: <ins> --- title: Node Affinityを利用してPodをノードに割り当てる min-kubernetes-server-version: v1.10 content_type: task weight: 120 --- <!-- overview --> このページでは、Node Affinityを利用して、PodをKubernetesクラスター内の特定のノードに割り当てる方法を説明します。 ## {{% heading "prerequisites" %}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} <!-- steps --> ## ノードにラベルを追加する 1. クラスター内のノードを一覧表示して、ラベルを確認します。 ```shell kubectl get nodes --show-labels ``` 出力は次のようになります。 ```shell NAME      STATUS    ROLES    AGE     VERSION        LABELS worker0   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker0 worker1   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker1 worker2   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker2 ``` 1. ノードを選択して、ラベルを追加します。 ```shell kubectl label nodes <your-node-name> disktype=ssd ``` ここで、`<your-node-name>`は選択したノードの名前で置換します。 1. 選択したノードに`disktype=ssd`ラベルがあることを確認します。 ```shell kubectl get nodes --show-labels ``` 出力は次のようになります。 ``` NAME      STATUS    ROLES    AGE     VERSION        LABELS worker0   Ready     <none>   1d      v1.13.0        ...,disktype=ssd,kubernetes.io/hostname=worker0 worker1   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker1 worker2   Ready     <none>   1d      v1.13.0        ...,kubernetes.io/hostname=worker2 ``` この出力を見ると、`worker0`ノードに`disktype=ssd`というラベルが追加されたことがわかります。 ## required node affinityを使用してPodをスケジューリングする 以下に示すマニフェストには、`requiredDuringSchedulingIgnoredDuringExecution`に`disktype: ssd`というnode affinityを使用したPodが書かれています。このように書くと、Podは`disktype=ssd`というラベルを持つノードにだけスケジューリングされるようになります。 {{< codenew file="pods/pod-nginx-required-affinity.yaml" >}} 1. マニフェストを適用して、選択したノード上にスケジューリングされるPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/pod-nginx-required-affinity.yaml ``` 1. Podが選択したノード上で実行されていることを確認します。 ```shell kubectl get pods --output=wide ``` 出力は次のようになります。 ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` ## preferred node affinityを使用してPodをスケジューリングする 以下に示すマニフェストには、`preferredDuringSchedulingIgnoredDuringExecution`に`disktype: ssd`というnode affinityを使用したPodが書かれています。このように書くと、Podは`disktype=ssd`というラベルを持つノードに優先的にスケジューリングされるようになります。 {{< codenew file="pods/pod-nginx-preferred-affinity.yaml" >}} 1. マニフェストを適用して、選択したノード上にスケジューリングされるPodを作成します。 ```shell kubectl apply -f https://k8s.io/examples/pods/pod-nginx-preferred-affinity.yaml ``` 1. Podが選択したノード上で実行されていることを確認します。 ```shell kubectl get pods --output=wide ``` 出力は次のようになります。 ``` NAME     READY     STATUS    RESTARTS   AGE    IP           NODE nginx    1/1       Running   0          13s    10.200.0.4   worker0 ``` ## {{% heading "whatsnext" %}} [Node Affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)についてさらに学ぶ。 </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> --- layout: blog title: "聚焦 SIG Usability" date: 2021-07-15 slug: sig-usability-spotlight-2021 --- <!-- layout: blog title: "Spotlight on SIG Usability" date: 2021-07-15 slug: sig-usability-spotlight-2021 --> <!-- **Author:** Kunal Kushwaha, Civo --> **作者：** Kunal Kushwaha、Civo <!-- ## Introduction --> ## 介绍 <!-- Are you interested in learning about what [SIG Usability](https://github.com/kubernetes/community/tree/master/sig-usability) does and how you can get involved? Well, you're at the right place. SIG Usability is all about making Kubernetes more accessible to new folks, and its main activity is conducting user research for the community. In this blog, we have summarized our conversation with [Gaby Moreno](https://twitter.com/morengab), who walks us through the various aspects of being a part of the SIG and shares some insights about how others can get involved. --> 你是否有兴趣了解 [SIG Usability](https://github.com/kubernetes/community/tree/master/sig-usability) 做什么？ 你是否想知道如何参与？那你来对地方了。 SIG Usability 旨在让 Kubernetes 更易于触达新的伙伴，其主要活动是针对社区实施用户调研。 在本博客中，我们总结了与 Gaby Moreno 的对话， 他向我们介绍了成为 SIG 成员的各个方面，并分享了一些关于其他人如何参与的见解。 <!-- Gaby is a co-lead for SIG Usability. She works as a Product Designer at IBM and enjoys working on the user experience of open, hybrid cloud technologies like Kubernetes, OpenShift, Terraform, and Cloud Foundry. --> Gaby 是 SIG Usability 的联合负责人。 她在 IBM 担任产品设计师， 喜欢研究 Kubernetes、OpenShift、Terraform 和 Cloud Foundry 等开放式混合云技术的用户体验。 <!-- ## A summary of our conversation --> ## 我们谈话的摘要 <!-- ### Q. Could you tell us a little about what SIG Usability does? --> ### 问：你能告诉我们一些关于 SIG Usability 的事情吗？ <!-- A. SIG Usability at a high level started because there was no dedicated user experience team for Kubernetes. The extent of SIG Usability is focussed on the end-client ease of use of the Kubernetes project. The main activity is user research for the community, which includes speaking to Kubernetes users. --> 答：简单而言，启动 SIG Usability 的原因是那时 Kubernetes 没有专门的用户体验团队。 SIG Usability 的关注领域集中在为 Kubernetes 项目最终客户提供的易用性上。 主要活动是社区的用户调研，包括对 Kubernetes 用户宣讲。 <!-- This covers points like user experience and accessibility. The objectives of the SIG are to guarantee that the Kubernetes project is maximally usable by people of a wide range of foundations and capacities, such as incorporating internationalization and ensuring the openness of documentation. --> 所涉及的包括用户体验和可访问性等方面。 SIG 的目标是确保 Kubernetes 项目能够最大限度地被具有各类不同基础和能力的人使用， 例如引入文档的国际化并确保其开放性。 <!-- ### Q. Why should new and existing contributors consider joining SIG Usability? --> ### 问：为什么新的和现有的贡献者应该考虑加入 SIG Usability？ <!-- A. There are plenty of territories where new contributors can begin. For example: --> 答：新的贡献者可以在很多领域着手。例如： <!-- - User research projects, where people can help understand the usability of the end-user experiences, including error messages, end-to-end tasks, etc. --> - 用户研究项目可以让人们帮助了解最终用户体验的可用性，包括错误消息、端到端任务等。 <!-- - Accessibility guidelines for Kubernetes community artifacts, examples include: internationalization of documentation, color choices for people with color blindness, ensuring compatibility with screen reader technology, user interface design for core components with user interfaces, and more. --> - Kubernetes 社区组件的可访问性指南，包括：文档的国际化、色盲人群的颜色选择、 确保与屏幕阅读器技术的兼容性、核心 UI 组件的用户界面设计等等。 <!-- ### Q. What do you do to help new contributors get started? --> ### 问：如何帮助新的贡献者入门？ <!-- A. New contributors can get started by shadowing one of the user interviews, going through user interview transcripts, analyzing them, and designing surveys. --> 答：新的贡献者们刚开始可以旁观参与其中一个用户访谈，浏览用户访谈记录，分析这些记录并设计调查过程。 <!-- SIG Usability is also open to new project ideas. If you have an idea, we’ll do what we can to support it. There are regular SIG Meetings where people can ask their questions live. These meetings are also recorded for those who may not be able to attend. As always, you can reach out to us on Slack as well. --> SIG Usability 也对新的项目想法持开放态度。 如果你有想法，我们将尽我们所能支持它。 我们有定期的 SIG 会议，人们可以现场提问。 这些会议也会录制会议视频，方便那些可能无法参会的人。 与往常一样，你也可以在 Slack 上与我们联系。 <!-- ### Q. What does the survey include? --> ### 问：调查包括什么？ <!-- A. In simple terms, the survey gathers information about how people use Kubernetes, such as trends in learning to deploy a new system, error messages they receive, and workflows. --> 答：简单来说，调查会收集人们如何使用 Kubernetes 的信息， 例如学习部署新系统的趋势、他们收到的错误消息和工作流程。 <!-- One of our goals is to standardize the responses accordingly. The ultimate goal is to analyze survey responses for important user stories whose needs aren't being met. --> 我们的目标之一是根据需要对反馈进行标准化。 最终目标是分析那些需求没有得到满足的重要用户故事的调查反馈。 <!-- ### Q. Are there any particular skills you’d like to recruit for? What skills are contributors to SIG Usability likely to learn? --> ### 问：招募贡献者时你希望他们具备什么特别的技能吗？SIG Usability 的贡献者可能要学习哪些技能？ <!-- A. Although contributing to SIG Usability does not have any pre-requisites as such, experience with user research, qualitative research, or prior experience with how to conduct an interview would be great plus points. Quantitative research, like survey design and screening, is also helpful and something that we expect contributors to learn. --> 答：虽然为 SIG Usability 做贡献没有任何先决条件， 但用户研究、定性研究的经验或之前如何进行访谈的经验将是很好的加分项。 定量研究，如调查设计和筛选，也很有帮助，也是我们希望贡献者学习的东西。 <!-- ### Q. What are you getting positive feedback on, and what’s coming up next for SIG Usability? --> ### 问：您在哪些方面获得了积极的反馈，以及 SIG Usability 接下来会发生什么？ <!-- A. We have had new members joining and coming to monthly meetings regularly and showing interests in becoming a contributor and helping the community. We have also had a lot of people reach out to us via Slack showcasing their interest in the SIG. --> 答：我们一直有新成员加入并经常参加月度会议，并表现出对成为贡献者和帮助社区的兴趣。 我们也有很多人通过 Slack 与我们联系，表达他们对 SIG 的兴趣。 <!-- Currently, we are focused on finishing the study mentioned in our [talk](https://www.youtube.com/watch?v=Byn0N_ZstE0), also our project for this year. We are always happy to have new contributors join us. --> 目前，我们正专注于完成我们[演讲](https://www.youtube.com/watch?v=Byn0N_ZstE0)中提到的调研， 也是我们今年的项目。我们总是很高兴有新的贡献者加入我们。 <!-- ### Q: Any closing thoughts/resources you’d like to share? --> ### 问：在结束之前，你还有什么想法/资源要分享吗？ <!-- A. We love meeting new contributors and assisting them in investigating different Kubernetes project spaces. We will work with and team up with other SIGs to facilitate engaging with end-users, running studies, and help them integrate accessible design practices into their development practices. --> 答：我们喜欢结识新的贡献者并帮助他们研究不同的 Kubernetes 项目领域。 我们将与其他 SIG 合作，以促进与最终用户的互动，开展调研，并帮助他们将可访问的设计实践整合到他们的开发实践中。 <!-- Here are some resources for you to get started: - [GitHub](https://github.com/kubernetes/community/tree/master/sig-usability) - [Mailing list](https://groups.google.com/g/kubernetes-sig-usability) - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fusability) - [Slack](https://slack.k8s.io/) - [Slack channel #sig-usability](https://kubernetes.slack.com/archives/CLC5EF63T) --> 这里有一些资源供你入门： - [GitHub](https://github.com/kubernetes/community/tree/master/sig-usability) - [邮件列表](https://groups.google.com/g/kubernetes-sig-usability) - [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/sig%2Fusability) - [Slack](https://slack.k8s.io/) - [Slack 频道 #sig-usability](https://kubernetes.slack.com/archives/CLC5EF63T) <!-- ## Wrap Up --> ## 总结 <!-- SIG Usability hosted a [KubeCon talk](https://www.youtube.com/watch?v=Byn0N_ZstE0) about studying Kubernetes users' experiences. The talk focuses on updates to the user study projects, understanding who is using Kubernetes, what they are trying to achieve, how the project is addressing their needs, and where we need to improve the project and the client experience. Join the SIG's update to find out about the most recent research results, what the plans are for the forthcoming year, and how to get involved in the upstream usability team as a contributor! --> SIG Usability 举办了一个关于调研 Kubernetes 用户体验的 [KubeCon 演讲](https://www.youtube.com/watch?v=Byn0N_ZstE0)。 演讲的重点是用户调研项目的更新，了解谁在使用 Kubernetes、他们试图实现什么、项目如何满足他们的需求、以及我们需要改进项目和客户体验的地方。 欢迎加入 SIG 的更新，了解最新的调研成果、来年的计划以及如何作为贡献者参与上游可用性团队！ </ins>

Problem: do not have chinese docs: Proposed Solution: add chinese docs in website Comments /language zh /assign
/triage accepted


Question: ## {{% heading "prerequisites" %}} <del> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. </del> <ins> You must use a kubectl version that is within one minor version difference of your cluster. For example, a v{{< skew latestVersion >}} client can communicate with v{{< skew prevMinorVersion >}}, v{{< skew latestVersion >}}, and v{{< skew nextMinorVersion >}} control planes. </ins> Using the latest version of kubectl helps avoid unforeseen issues. ## Install kubectl on Windows


Question: RELEASE="$(curl -sSL https://dl.k8s.io/release/stable.txt)" ARCH="amd64" cd $DOWNLOAD_DIR <del> sudo curl -L --remote-name-all https://storage.googleapis.com/kubernetes-release/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </del> <ins> sudo curl -L --remote-name-all https://dl.k8s.io/release/${RELEASE}/bin/linux/${ARCH}/{kubeadm,kubelet,kubectl} </ins> sudo chmod +x {kubeadm,kubelet,kubectl} RELEASE_VERSION="v0.4.0"

This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: There are still references to instead of is the correct advertised download host and will eventually move to be fastly shielding a fully community-owned bucket ref: Proposed Solution: Replace with Also replace any references with using if applicable. Page to Update: Assorted e.g. , <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the label. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
hi Not a problem, didn't see anyone assigned to this issue. I am unassigning myself and assigning it to you. /unassign
/assign
Hi, I found a small issue with your proposed changes regarding one of the URLs, which is mentioned twice in the file. While returns as expected, I am getting an nginx-rendered HTML page saying for the new command () instead. As I understand, it happens due to the redirect configured on the new web server. Thus, works fine for me (it returns as expected).
i see Let me update it, thanks your work
Just done, please review all of PRs
Thanks!
And yes: These will need to follow redirects, in the future the tentative plan is it will redirect to a CDN in front of a different bucket created in a fully project / SIG-K8s-Infra controlled GCP or AWS account. I would recommend for downloading with curl more generally, even in docs / usage for other hosts.