{"query_id": "q-en-website-6c9793323877074c1ab8bed498d978e7b8c770cbf71894447380fade48ea2ce8", "query": "I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).\nUbuntu is getting a big rewrite as well.", "positive_passages": [{"docid": "doc-en-website-4d931fe999353187c06548c585f3b70717d13486ff34c63a20088e3e57735361", "text": "kubectl get statefulset web ``` ``` NAME DESIRED CURRENT AGE web 2 1 20s NAME READY AGE web 2/2 37s ``` ### Ordered Pod creation", "commid": "website_pr_45878"}], "negative_passages": []} {"query_id": "q-en-website-6c9793323877074c1ab8bed498d978e7b8c770cbf71894447380fade48ea2ce8", "query": "I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).\nUbuntu is getting a big rewrite as well.", "positive_passages": [{"docid": "doc-en-website-ecc8275384a843e56c3a837ce446673c765d876b5fa888ab63d7487e4142204a", "text": "image again: ```shell kubectl patch statefulset web --type='json' -p='[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\":\"gcr.io/google_containers/nginx-slim:0.8\"}]' kubectl patch statefulset web --type='json' -p='[{\"op\": \"replace\", \"path\": \"/spec/template/spec/containers/0/image\", \"value\":\"registry.k8s.io/nginx-slim:0.8\"}]' ``` ``` statefulset.apps/web patched", "commid": "website_pr_45878"}], "negative_passages": []} {"query_id": "q-en-website-6c9793323877074c1ab8bed498d978e7b8c770cbf71894447380fade48ea2ce8", "query": "I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).\nUbuntu is getting a big rewrite as well.", "positive_passages": [{"docid": "doc-en-website-ecf0e4a44494a263191661470d953fe8bf18155f81289cf7bd94f19218d5a994", "text": "used in this tutorial. Follow the necessary steps, based on your environment, storage configuration, and provisioning method, to ensure that all storage is reclaimed. {{< /note >}} No newline at end of file {{< /note >}} ", "commid": "website_pr_45878"}], "negative_passages": []} {"query_id": "q-en-website-6c9793323877074c1ab8bed498d978e7b8c770cbf71894447380fade48ea2ce8", "query": "I wish /docs/getting-started-guides/ listed both Ubuntu guides in the Bare Metal section, noting the networking for each (the listed one uses Flannel, the omitted one (but it is in the navigation panel on the left) uses Calico).\nUbuntu is getting a big rewrite as well.", "positive_passages": [{"docid": "doc-en-website-8db1c68a74169337aafc4e8e2f76878241c5f6bdbdb3da7c18ef80536f7aeba3", "text": "spec: containers: - name: nginx image: registry.k8s.io/nginx-slim:0.8 image: registry.k8s.io/nginx-slim:0.7 ports: - containerPort: 80 name: web", "commid": "website_pr_45878"}], "negative_passages": []} {"query_id": "q-en-website-7c3bfb760b0f32dbb78080eee4e9d6eaa1c0d612259f5fd19aad6cdea5095731", "query": "I wish /docs/getting-started-guides/docker/ I wish this page existed", "positive_passages": [{"docid": "doc-en-website-feb1b56d73eb351ca2c0e9187e1de25f88dfe0a0838a071c3a942c2f86ef5ee6", "text": "(backward-compatible) changes to the way the Kubernetes cluster DNS server processes DNS queries, to facilitate the lookup of federated services (which span multiple Kubernetes clusters). See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more details on Cluster Federation and multi-site support. ## References", "commid": "website_pr_1158"}], "negative_passages": []} {"query_id": "q-en-website-7c3bfb760b0f32dbb78080eee4e9d6eaa1c0d612259f5fd19aad6cdea5095731", "query": "I wish /docs/getting-started-guides/docker/ I wish this page existed", "positive_passages": [{"docid": "doc-en-website-0131b3cf171ebce25201685759bb09324016e9d2074e036d39fbb0811320f0cc", "text": " # *Stop. This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes* The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md) ", "commid": "website_pr_1158"}], "negative_passages": []} {"query_id": "q-en-website-7c3bfb760b0f32dbb78080eee4e9d6eaa1c0d612259f5fd19aad6cdea5095731", "query": "I wish /docs/getting-started-guides/docker/ I wish this page existed", "positive_passages": [{"docid": "doc-en-website-aa24104ef5b6f48b9b3410565bcf1354e6025f250daed1139d4471fff99d9c2b", "text": "### SEE ALSO * [kubectl](kubectl.md)\t - kubectl controls the Kubernetes cluster manager * [kubectl](../kubectl.md)\t - kubectl controls the Kubernetes cluster manager ###### Auto generated by spf13/cobra on 12-Aug-2016", "commid": "website_pr_1158"}], "negative_passages": []} {"query_id": "q-en-website-704711b8d85ea90b2f7cb8a2c7c182243d082f6c0e8af556022569a6264b69f4", "query": "Cites looking at a cephfs example, that promptly 404's once clicked\nIt appears this should actually point to: not", "positive_passages": [{"docid": "doc-en-website-2d2136945f6f69d736d0bb595266ff6153f7bbc042fc17fcefd8d21d820d6c44", "text": "__Important: You must have your own Ceph server running with the share exported before you can use it__ See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/cephfs/) for more details. See the [CephFS example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/volumes/cephfs/) for more details. ### gitRepo", "commid": "website_pr_1263"}], "negative_passages": []} {"query_id": "q-en-website-21bb091eede30dbf5ec9bec1da9c5d739e9b28caf374946bbe4f712557051894", "query": "A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?\nThank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:", "positive_passages": [{"docid": "doc-en-website-03d8dd2526c0dd1890944f8882ba747c0697e3d582500fabf9046a1f44309df4", "text": "path: /docs/getting-started-guides/ovirt/ - title: OpenStack Heat path: /docs/getting-started-guides/openstack-heat/ - title: CoreOS on Multinode Cluster path: /docs/getting-started-guides/coreos/coreos_multinode_cluster/ - title: rkt section: - title: Running Kubernetes with rkt", "commid": "website_pr_1689"}], "negative_passages": []} {"query_id": "q-en-website-21bb091eede30dbf5ec9bec1da9c5d739e9b28caf374946bbe4f712557051894", "query": "A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?\nThank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:", "positive_passages": [{"docid": "doc-en-website-b3fd57e578e9311b491bcd23b71b470b465aae9c0c10c0176f394a59d7c3e969", "text": "[CoreOS](http://coreos.com) templates for CloudStack are built [nightly](http://stable.release.core-os.net/amd64-usr/current/). CloudStack operators need to [register](http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/templates.html) this template in their cloud before proceeding with these Kubernetes deployment instructions. This guide uses an [Ansible playbook](https://github.com/runseb/ansible-kubernetes). This is a completely automated, a single playbook deploys Kubernetes based on the coreOS [instructions](/docs/getting-started-guides/coreos/coreos_multinode_cluster). This is completely automated, a single playbook deploys Kubernetes. This [Ansible](http://ansibleworks.com) playbook deploys Kubernetes on a CloudStack based Cloud using CoreOS images. The playbook, creates an ssh key pair, creates a security group and associated rules and finally starts coreOS instances configured via cloud-init.", "commid": "website_pr_1689"}], "negative_passages": []} {"query_id": "q-en-website-21bb091eede30dbf5ec9bec1da9c5d739e9b28caf374946bbe4f712557051894", "query": "A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?\nThank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:", "positive_passages": [{"docid": "doc-en-website-728c2cd9d487c1cefed85d0c42db500055e666bd9a7cb7fab155fd875ed0ad74", "text": " --- assignees: - dchen1107 --- Use the [master.yaml](/docs/getting-started-guides/coreos/cloud-configs/master.yaml) and [node.yaml](/docs/getting-started-guides/coreos/cloud-configs/node.yaml) cloud-configs to provision a multi-node Kubernetes cluster. > **Attention**: This requires at least CoreOS version **[695.0.0][coreos695]**, which includes `etcd2`. [coreos695]: https://coreos.com/releases/#695.0.0 * TOC {:toc} ### AWS *Attention:* Replace `` below for a [suitable version of CoreOS image for AWS](https://coreos.com/docs/running-coreos/cloud-providers/ec2/). #### Provision the Master ```shell aws ec2 create-security-group --group-name kubernetes --description \"Kubernetes Security Group\" aws ec2 authorize-security-group-ingress --group-name kubernetes --protocol tcp --port 22 --cidr 0.0.0.0/0 aws ec2 authorize-security-group-ingress --group-name kubernetes --protocol tcp --port 80 --cidr 0.0.0.0/0 aws ec2 authorize-security-group-ingress --group-name kubernetes --source-security-group-name kubernetes ``` ```shell aws ec2 run-instances --image-id --key-name --region us-west-2 --security-groups kubernetes --instance-type m3.medium --user-data file://master.yaml ``` #### Capture the private IP address ```shell aws ec2 describe-instances --instance-id ``` #### Edit node.yaml Edit `node.yaml` and replace all instances of `` with the private IP address of the master node. #### Provision worker nodes ```shell aws ec2 run-instances --count 1 --image-id --key-name --region us-west-2 --security-groups kubernetes --instance-type m3.medium --user-data file://node.yaml ``` ### Google Compute Engine (GCE) *Attention:* Replace `` below for a [suitable version of CoreOS image for Google Compute Engine](https://coreos.com/docs/running-coreos/cloud-providers/google-compute-engine/). #### Provision the Master ```shell gcloud compute instances create master --image-project coreos-cloud --image --boot-disk-size 200GB --machine-type n1-standard-1 --zone us-central1-a --metadata-from-file user-data=master.yaml ``` #### Capture the private IP address ```shell gcloud compute instances list ``` #### Edit node.yaml Edit `node.yaml` and replace all instances of `` with the private IP address of the master node. #### Provision worker nodes ```shell gcloud compute instances create node1 --image-project coreos-cloud --image --boot-disk-size 200GB --machine-type n1-standard-1 --zone us-central1-a --metadata-from-file user-data=node.yaml ``` #### Establish network connectivity Next, setup an ssh tunnel to the master so you can run kubectl from your local host. In one terminal, run `gcloud compute ssh master --ssh-flag=\"-L 8080:127.0.0.1:8080\"` and in a second run `gcloud compute ssh master --ssh-flag=\"-R 8080:127.0.0.1:8080\"`. ### OpenStack These instructions are for running on the command line. Most of this you can also do through the Horizon dashboard. These instructions were tested on the Ice House release on a Metacloud distribution of OpenStack but should be similar if not the same across other versions/distributions of OpenStack. #### Make sure you can connect with OpenStack Make sure the environment variables are set for OpenStack such as: ```shell OS_TENANT_ID OS_PASSWORD OS_AUTH_URL OS_USERNAME OS_TENANT_NAME ``` Test this works with something like: ```shell nova list ``` #### Get a Suitable CoreOS Image You'll need a [suitable version of CoreOS image for OpenStack](https://coreos.com/os/docs/latest/booting-on-openstack.html) Once you download that, upload it to glance. An example is shown below: ```shell glance image-create --name CoreOS723 --container-format bare --disk-format qcow2 --file coreos_production_openstack_image.img --is-public True ``` #### Create security group ```shell nova secgroup-create kubernetes \"Kubernetes Security Group\" nova secgroup-add-rule kubernetes tcp 22 22 0.0.0.0/0 nova secgroup-add-rule kubernetes tcp 80 80 0.0.0.0/0 ``` #### Provision the Master ```shell nova boot --image --key-name --flavor --security-group kubernetes --user-data files/master.yaml kube-master ``` `` is the CoreOS image name. In our example we can use the image we created in the previous step and put in 'CoreOS723' `` is the keypair name that you already generated to access the instance. `` is the flavor ID you use to size the instance. Run `nova flavor-list` to get the IDs. 3 on the system this was tested with gives the m1.large size. The important part is to ensure you have the files/master.yml as this is what will do all the post boot configuration. This path is relevant so we are assuming in this example that you are running the nova command in a directory where there is a subdirectory called files that has the master.yml file in it. Absolute paths also work. Next, assign it a public IP address: ```shell nova floating-ip-list ``` Get an IP address that's free and run: ```shell nova floating-ip-associate kube-master ``` where `` is the IP address that was available from the `nova floating-ip-list` command. #### Provision Worker Nodes Edit `node.yaml` and replace all instances of `` with the private IP address of the master node. You can get this by running `nova show kube-master` assuming you named your instance kube master. This is not the floating IP address you just assigned it. ```shell nova boot --image --key-name --flavor --security-group kubernetes --user-data files/node.yaml minion01 ``` This is basically the same as the master nodes but with the node.yaml post-boot script instead of the master. No newline at end of file", "commid": "website_pr_1689"}], "negative_passages": []} {"query_id": "q-en-website-21bb091eede30dbf5ec9bec1da9c5d739e9b28caf374946bbe4f712557051894", "query": "A user linked to this guide from an issue: I believe that guide is unmaintained. It still specifies k8s 1.1.2. can we delete?\nThank you. Yes, this guide was unmaintained and community contributed. I am OK with this change. devin-donnelly wrote:", "positive_passages": [{"docid": "doc-en-website-3faadd1ebf3ea382a78bc1ca86d5e63fcae9e8cba05d372577426b3fc065720c", "text": "These guides are maintained by community members, cover specific platforms and use cases, and experiment with different ways of configuring Kubernetes on CoreOS. [**Multi-node Cluster**](/docs/getting-started-guides/coreos/coreos_multinode_cluster) Set up a single master, multi-worker cluster on your choice of platform: AWS, GCE, or VMware Fusion.
[**Easy Multi-node Cluster on Google Compute Engine**](https://github.com/rimusz/coreos-multi-node-k8s-gce/blob/master/README.md) Scripted installation of a single master, multi-worker cluster on GCE. Kubernetes components are managed by [fleet](https://github.com/coreos/fleet).", "commid": "website_pr_1689"}], "negative_passages": []} {"query_id": "q-en-website-b754501671935e51c3e92ac67ce3fae64a85f9bf2e5c6a04100b27ebf949c0a9", "query": " Many applications rely on configuration which is used during either application initialization or runtime. Most of the times there is a requirement to adjust values assigned to configuration parameters. ConfigMaps is the kubernetes way to inject application pods with configuration data. ConfigMaps are the Kubernetes way to inject application pods with configuration data. ConfigMaps allow you to decouple configuration artifacts from image content to keep containerized applications portable. This page provides a series of usage examples demonstrating how to create ConfigMaps and configure Pods using data stored in ConfigMaps.", "commid": "website_pr_35160"}], "negative_passages": []} {"query_id": "q-en-website-51038e62ec692514644fb5a5ee80edb5938a1ae998dd622e421a4616a3629d32", "query": "This is a... [x] Bug Report Problem: The documentation mentions \"optional\" in the restrictions for configmap, but doesn't explain how to use it anywhere else in the documentation. You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as \u201coptional\u201d). If you reference a ConfigMap that doesn\u2019t exist, the Pod won\u2019t start. Likewise, references to keys that don\u2019t exist in the ConfigMap will prevent the pod from starting. Please see for the feature. It appears it got lost in the 1.5-1.6 upgrade. Proposed Solution: Restore the copy from that wrote. Page to Update:\nFor clarity, the copy from got removed here:\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/language en /remove-lifecycle stale /assign\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\n/priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nStale 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-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle stale\n/remove-lifecycle rotten\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nRelevant to /remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nThis awesome feature is still missing in the documentation, Can someone please add it ?\nwere you thinking of opening a pull request? We'd be happy to help you with that.\n/remove-lifecycle stale\n/lifecycle frozen\n/triage accepted\nI don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on it. Thank you! /unassign\n/assign", "positive_passages": [{"docid": "doc-en-website-9bb4140590615da30cd68838dc5662a398db0c01599d75880f90a4a76a8eb061", "text": "You can project keys to specific paths and specific permissions on a per-file basis. The [Secrets](/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod) user guide explains the syntax. ### Optional References A ConfigMap reference may be marked \"optional\". If the ConfigMap is non-existent, the mounted volume will be empty. If the ConfigMap exists, but the referenced key is non-existent the path will be absent beneath the mount point. ### Mounted ConfigMaps are updated automatically When a mounted ConfigMap is updated, the projected content is eventually updated too. This applies in the case where an optionally referenced ConfigMap comes into existence after a pod has started. Kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, it uses its local TTL-based cache for getting the current value of the ConfigMap. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the pod can be as long as kubelet sync period (1 minute by default) + TTL of ConfigMaps cache (1 minute by default) in kubelet. {{< note >}} A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive ConfigMap updates. {{< /note >}} ", "commid": "website_pr_35160"}], "negative_passages": []} {"query_id": "q-en-website-51038e62ec692514644fb5a5ee80edb5938a1ae998dd622e421a4616a3629d32", "query": "This is a... [x] Bug Report Problem: The documentation mentions \"optional\" in the restrictions for configmap, but doesn't explain how to use it anywhere else in the documentation. You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as \u201coptional\u201d). If you reference a ConfigMap that doesn\u2019t exist, the Pod won\u2019t start. Likewise, references to keys that don\u2019t exist in the ConfigMap will prevent the pod from starting. Please see for the feature. It appears it got lost in the 1.5-1.6 upgrade. Proposed Solution: Restore the copy from that wrote. Page to Update:\nFor clarity, the copy from got removed here:\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/language en /remove-lifecycle stale /assign\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\n/priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nStale 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-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle stale\n/remove-lifecycle rotten\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nRelevant to /remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nThis awesome feature is still missing in the documentation, Can someone please add it ?\nwere you thinking of opening a pull request? We'd be happy to help you with that.\n/remove-lifecycle stale\n/lifecycle frozen\n/triage accepted\nI don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on it. Thank you! /unassign\n/assign", "positive_passages": [{"docid": "doc-en-website-7e29ee430b8c990b7e4a900bf8d07223a402bae2bc54119cf61ad64788e785c2", "text": "### Restrictions - You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as \"optional\"). If you reference a ConfigMap that doesn't exist, the Pod won't start. Likewise, references to keys that don't exist in the ConfigMap will prevent the pod from starting. - You must create a ConfigMap before referencing it in a Pod specification, or mark the ConfigMap as \"optional\" (see [Optional ConfigMaps](#optional-configmaps)). If you reference a ConfigMap that doesn't exist, or hasn't been marked as \"optional\" the Pod won't start. Likewise, references to keys that don't exist in the ConfigMap will prevent the pod from starting. - If you use `envFrom` to define environment variables from ConfigMaps, keys that are considered invalid will be skipped. The pod will be allowed to start, but the invalid names will be recorded in the event log (`InvalidVariableNames`). The log message lists each skipped key. For example:", "commid": "website_pr_35160"}], "negative_passages": []} {"query_id": "q-en-website-51038e62ec692514644fb5a5ee80edb5938a1ae998dd622e421a4616a3629d32", "query": "This is a... [x] Bug Report Problem: The documentation mentions \"optional\" in the restrictions for configmap, but doesn't explain how to use it anywhere else in the documentation. You must create a ConfigMap before referencing it in a Pod specification (unless you mark the ConfigMap as \u201coptional\u201d). If you reference a ConfigMap that doesn\u2019t exist, the Pod won\u2019t start. Likewise, references to keys that don\u2019t exist in the ConfigMap will prevent the pod from starting. Please see for the feature. It appears it got lost in the 1.5-1.6 upgrade. Proposed Solution: Restore the copy from that wrote. Page to Update:\nFor clarity, the copy from got removed here:\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/language en /remove-lifecycle stale /assign\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\n/priority backlog\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nStale 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-testing, kubernetes/test-infra and/or . /lifecycle rotten\n/remove-lifecycle stale\n/remove-lifecycle rotten\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nRelevant to /remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\nThis awesome feature is still missing in the documentation, Can someone please add it ?\nwere you thinking of opening a pull request? We'd be happy to help you with that.\n/remove-lifecycle stale\n/lifecycle frozen\n/triage accepted\nI don't see any updates; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on it. Thank you! /unassign\n/assign", "positive_passages": [{"docid": "doc-en-website-c099f7a26ce8744a369b5ee2928035bda62bb95677d152ca73a51db7ac450d39", "text": "- You can't use ConfigMaps for {{< glossary_tooltip text=\"static pods\" term_id=\"static-pod\" >}}, because the Kubelet does not support this. ### Optional ConfigMaps In a Pod, or pod template, you can mark a reference to a ConfigMap as _optional_. If the ConfigMap is non-existent, the configuration for which it provides data in the Pod (e.g. environment variable, mounted volume) will be empty. If the ConfigMap exists, but the referenced key is non-existent the data is also empty. #### Optional ConfigMap in environment variables There might be situations where environment variables are not always required. You can mark an environment variables for a container as optional, like this: ```yaml apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: gcr.io/google_containers/busybox command: [ \"/bin/sh\", \"-c\", \"env\" ] env: - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: name: a-config key: akey optional: true # mark the variable as optional restartPolicy: Never ``` If you run this pod, and there is no ConfigMap named `a-config`, the output is empty. If you run this pod, and there is a ConfigMap named `a-config` but that ConfigMap doesn't have a key named `akey`, the output is also empty. If you do set a value for `akey` in the `a-config` ConfigMap, this pod prints that value and then terminates. #### Optional ConfigMap via volume plugin Volumes and files provided by a ConfigMap can be also be marked as optional. The ConfigMap or the key specified does not have to exist. The mount path for such items will always be created. ```yaml apiVersion: v1 kind: Pod metadata: name: dapi-test-pod spec: containers: - name: test-container image: gcr.io/google_containers/busybox command: [ \"/bin/sh\", \"-c\", \"ls /etc/config\" ] volumeMounts: - name: config-volume mountPath: /etc/config volumes: - name: config-volume configMap: name: no-config optional: true # mark the source ConfigMap as optional restartPolicy: Never ``` If you run this pod, and there is no ConfigMap named `no-config`, the mounted volume will be empty. ### Mounted ConfigMaps are updated automatically When a mounted ConfigMap is updated, the projected content is eventually updated too. This applies in the case where an optionally referenced ConfigMap comes into existence after a pod has started. The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, it uses its local TTL-based cache for getting the current value of the ConfigMap. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the pod can be as long as kubelet sync period (1 minute by default) + TTL of ConfigMaps cache (1 minute by default) in kubelet. {{< note >}} A container using a ConfigMap as a [subPath](/docs/concepts/storage/volumes/#using-subpath) volume will not receive ConfigMap updates. {{< /note >}} ## {{% heading \"whatsnext\" %}}", "commid": "website_pr_35160"}], "negative_passages": []} {"query_id": "q-en-website-4afba6044ff3696b96a39858ca2f9b851d298aea89ca34755cae692a2d9246db", "query": "This is a Bug Report This issue appeared recently within kubernetes/website. Links in follow the next pattern , see a square bracket inside of the . I tried to follow in order to find a source of the issue, but wasn't able to do so. my best guesses: Source for generation for 1_17 branch was corrupted. Backend was replaced by something else but not commited (i don't believe in this). This can be temporary content (on ein PR) as toolset for kubernetes-sigs/reference-docs .\n/kind bug /priority backlog\nping\nI am looking now\n, you are referring to a link problem in the reference? I don't immediately see a problem. Can you provide an example of a command that has a link issue? Thanks! I see a link that appears incorrectly formatted, such as the flag in the command, Though, the link does work for me.\nI plan on updating the build instructions and README.\nany link that follow pattern . If we ware talking about from the root of the kubernetes-sigs/reference-docs, it would be any link in usage block. Almost all of them are anchor links, so problem isn't visible at first. search for or , last symbol of the link is clearly not suppose to be a link (at least its not a link in source yaml) P.S. Is it worth time to update build instructions now? Isn't going to change generator backend to htmlwriter?\n, I have a feeling there is a miscommunication. I am not sure what you are referring to. I thought you are logging an issue specifically to the kubectl reference. Please provide a specific example.\nok. for on link to for on link yourself why is in link. diff for kubernetes/website (kubectl-) and see how links are formed. -become right bracket in the href attribute. P.S. just updated one of the search links as i forgot to copy/paste last element of the link (). P.P.S. looks like regular expression issue.\nI see. I think we are referring to the same problem -- the right bracket.\nShould I close issue or you prefer to have it opened untill kubernetes-sigs/reference-docs is opened?\n, I would leave this issue open as a reminder for next release. Thanks! NOTE: The links were manually fixed for the 1.17 release (search/replace).\ngot it!", "positive_passages": [{"docid": "doc-en-website-54de64bf48abb13034d701d6c164d8dfd189b9bc379464ff0ee14c6d45ab26c5", "text": "- title: kube-proxy CLI path: /docs/admin/kube-proxy/ - title: kub-scheduler CLI - title: kube-scheduler CLI path: /docs/admin/kube-scheduler/ - title: kubelet CLI", "commid": "website_pr_142"}], "negative_passages": []} {"query_id": "q-en-website-7d3321bca9e7ebeb2f06ae54cd8f3fdd46cb18668a0bde460a9209f94135ca27", "query": "This is a Bug Report Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code. Originally part of the kube-controller-manager, the cloud-controller-manager is responsible to decoupling the interoperability logic between Kubernetes and the underlying cloud infrastructure, enabling cloud providers to release features at a different pace compared to the main project. ", "commid": "website_pr_20135"}], "negative_passages": []} {"query_id": "q-en-website-7d3321bca9e7ebeb2f06ae54cd8f3fdd46cb18668a0bde460a9209f94135ca27", "query": "This is a Bug Report [HostAliases](/docs/reference/generated/kubernetes-api/v1.13/#hostalias-v1-corev) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods. [HostAliases](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#hostalias-v1-core) is an optional list of hostnames and IP addresses that will be injected into the Pod's hosts file if specified. This is only valid for non-hostNetwork Pods. ", "commid": "website_pr_20135"}], "negative_passages": []} {"query_id": "q-en-website-2f3fd470287390ca4daf7fc8552bc81c59d253d1849029abbf7223f282e6082f", "query": "This is a Feature Request \uc6cc\ucee4 \ub178\ub4dc\ub294 \uc560\ud50c\ub9ac\ucf00\uc774\uc158\uc758 \uad6c\uc131\uc694\uc18c\uc778 {{< glossary_tooltip text=\"\ud30c\ub4dc\" term_id=\"pod\" >}}\ub97c \ud638\uc2a4\ud2b8\ud55c\ub2e4. {{< glossary_tooltip text=\"\ucee8\ud2b8\ub864 \ud50c\ub808\uc778\" term_id=\"control-plane\" >}}\uc740 \uc6cc\ucee4 \ub178\ub4dc\uc640", "commid": "website_pr_20705"}], "negative_passages": []} {"query_id": "q-en-website-c61567fff240682de3bd42a6f74f485487c27753e007c77eedf8cf355cf49008", "query": "This is a Bug Report Problem: missing double quote (\") after the word services in the last table Proposed Solution: Add the missing double quote (\") Page to Update:", "positive_passages": [{"docid": "doc-en-website-88b1c8b615dd2be5154effa2359dc4a5852ffe62c8a8b4bdb6bd8f2a78bee0fb", "text": " ", "commid": "website_pr_20721"}], "negative_passages": []} {"query_id": "q-en-website-f2bec3e57dc4a28e15acf85ac2963210cda2b8ac0476c09ffaf22a80b161833b", "query": "I would like to have the \"Container Lifecycle Hooks\" page to be translated into Italian page /language it /priority important-soon\n/remove-priority important-soon /priority important-longterm\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale\n/remove-lifecycle stale\nHi I am taking this issue! :smile: /assign /lifecycle active\nthis can help (you can find specific instructions for the web-site) Ping me if you need help\nHi I have finished my issue! PR ! Let me know!", "positive_passages": [{"docid": "doc-en-website-401c0b1324b400dc0eed991046b248b5ece37b930825bd44788b7e5bc44102cc", "text": " --- title: Container Lifecycle Hooks content_type: concept weight: 30 --- Questa pagina descrive come i Container gestiti con kubelet possono utilizzare il lifecycle hook framework dei Container per l'esecuzione di codice eseguito in corrispondenza di alcuni eventi durante il loro ciclo di vita. ## Overview Analogamente a molti framework di linguaggi di programmazione che hanno degli hooks legati al ciclo di vita dei componenti, come ad esempio Angular, Kubernetes fornisce ai Container degli hook legati al loro ciclo di vita dei Container. Gli hook consentono ai Container di essere consapevoli degli eventi durante il loro ciclo di gestione ed eseguire del codice implementato in un handler quando il corrispondente hook viene eseguito. ## Container hooks Esistono due tipi di hook che vengono esposti ai Container: `PostStart` Questo hook viene eseguito successivamente alla creazione del container. Tuttavia, non vi \u00e8 garanzia che questo hook venga eseguito prima dell'ENTRYPOINT del container. Non vengono passati parametri all'handler. `PreStop` Questo hook viene eseguito prima della terminazione di un container a causa di una richiesta API o di un evento di gestione, come ad esempio un fallimento delle sonde di liveness/startup, preemption, risorse contese e altro. Una chiamata all'hook di `PreStop` fallisce se il container \u00e8 in stato terminated o completed e l'hook deve finire prima che possa essere inviato il segnale di TERM per fermare il container. Il conto alla rovescia per la terminazione del Pod (grace period) inizia prima dell'esecuzione dell'hook `PreStop`, quindi indipendentemente dall'esito dell'handler, il container terminer\u00e0 entro il grace period impostato. Non vengono passati parametri all'handler. Una descrizione pi\u00f9 dettagliata riguardante al processo di terminazione dei Pod pu\u00f2 essere trovata in [Terminazione dei Pod](/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination). ### Implementazione degli hook handler I Container possono accedere a un hook implementando e registrando un handler per tale hook. Ci sono due tipi di handler che possono essere implementati per i Container: * Exec - Esegue un comando specifico, tipo `pre-stop.sh`, all'interno dei cgroup e namespace del Container. Le risorse consumate dal comando vengono contate sul Container. * HTTP - Esegue una richiesta HTTP verso un endpoint specifico del Container. ### Esecuzione dell'hook handler Quando viene richiamato l'hook legato al lifecycle del Container, il sistema di gestione di Kubernetes esegue l'handler secondo l'azione dell'hook, `httpGet` e `tcpSocket` vengono eseguiti dal processo kubelet, mentre `exec` \u00e8 eseguito nel Container. Le chiamate agli handler degli hook sono sincrone rispetto al contesto del Pod che contiene il Container. Questo significa che per un hook `PostStart`, l'ENTRYPOINT e l'hook si attivano in modo asincrono. Tuttavia, se l'hook impiega troppo tempo per essere eseguito o si blocca, il container non pu\u00f2 raggiungere lo stato di `running`. Gli hook di `PreStop` non vengono eseguiti in modo asincrono dall'evento di stop del container; l'hook deve completare la sua esecuzione prima che l'evento TERM possa essere inviato. Se un hook di `PreStop` si blocca durante la sua esecuzione, la fase del Pod rimarr\u00e0 `Terminating` finch\u00e8 il Pod non sar\u00e0 rimosso forzatamente dopo la scadenza del suo `terminationGracePeriodSeconds`. Questo grace period si applica al tempo totale necessario per effettuare sia l'esecuzione dell'hook di `PreStop` che per l'arresto normale del container. Se, per esempio, il `terminationGracePeriodSeconds` \u00e8 di 60, e l'hook impiega 55 secondi per essere completato, e il container impiega 10 secondi per fermarsi normalmente dopo aver ricevuto il segnale, allora il container verr\u00e0 terminato prima di poter completare il suo arresto, poich\u00e9 `terminationGracePeriodSeconds` \u00e8 inferiore al tempo totale (55+10) necessario perch\u00e9 queste due cose accadano. Se un hook `PostStart` o `PreStop` fallisce, allora il container viene terminato. Gli utenti dovrebbero mantenere i loro handler degli hook i pi\u00f9 leggeri possibili. Ci sono casi, tuttavia, in cui i comandi di lunga durata hanno senso, come il salvataggio dello stato del container prima della sua fine. ### Garanzia della chiamata dell'hook La chiamata degli hook avviene *almeno una volta*, il che significa che un hook pu\u00f2 essere chiamato pi\u00f9 volte da un dato evento, come per `PostStart` o `PreStop`. Sta all'implementazione dell'hook gestire correttamente questo aspetto. Generalmente, vengono effettuate singole chiamate agli hook. Se, per esempio, la destinazione di hook HTTP non \u00e8 momentaneamente in grado di ricevere traffico, non c'\u00e8 alcun tentativo di re invio. In alcuni rari casi, tuttavia, pu\u00f2 verificarsi una doppia chiamata. Per esempio, se un kubelet si riavvia nel mentre dell'invio di un hook, questo potrebbe essere chiamato per una seconda volta dopo che il kubelet \u00e8 tornato in funzione. ### Debugging Hook handlers I log di un handler di hook non sono esposti negli eventi del Pod. Se un handler fallisce per qualche ragione, trasmette un evento. Per il `PostStart`, questo \u00e8 l'evento di `FailedPostStartHook`, e per il `PreStop`, questo \u00e8 l'evento di `FailedPreStopHook`. Puoi vedere questi eventi eseguendo `kubectl describe pod `. Ecco alcuni esempi di output di eventi dall'esecuzione di questo comando: ``` Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 1m 1m 1 {default-scheduler } Normal Scheduled Successfully assigned test-1730497541-cq1d2 to gke-test-cluster-default-pool-a07e5d30-siqd 1m 1m 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Pulling pulling image \"test:1.0\" 1m 1m 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Created Created container with docker id 5c6a256a2567; Security:[seccomp=unconfined] 1m 1m 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Pulled Successfully pulled image \"test:1.0\" 1m 1m 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Started Started container with docker id 5c6a256a2567 38s 38s 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Killing Killing container with docker id 5c6a256a2567: PostStart handler: Error executing in Docker Container: 1 37s 37s 1 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Normal Killing Killing container with docker id 8df9fdfd7054: PostStart handler: Error executing in Docker Container: 1 38s 37s 2 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} Warning FailedSync Error syncing pod, skipping: failed to \"StartContainer\" for \"main\" with RunContainerError: \"PostStart handler: Error executing in Docker Container: 1\" 1m 22s 2 {kubelet gke-test-cluster-default-pool-a07e5d30-siqd} spec.containers{main} Warning FailedPostStartHook ``` ## {{% heading \"whatsnext\" %}} * Approfondisci [Container environment](/docs/concepts/containers/container-environment/). * Esegui un tutorial su come [definire degli handlers per i Container lifecycle events](/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/). ", "commid": "website_pr_26740"}], "negative_passages": []} {"query_id": "q-en-website-14ccad1c3859430e7cb0dd7e8f4e13280e4f08b474f28bdc82254ad431c9e596", "query": "This is a Bug Report ## Be the PR Wrangler for a week SIG Docs [approvers](/docs/contribute/participating/#approvers) take week-long turns [wrangling PRs](https://github.com/kubernetes/website/wiki/PR-Wranglers) for the repository. The PR wrangler\u2019s duties include: - Review [open pull requests](https://github.com/kubernetes/website/pulls) daily for quality and adherence to the [Style](/docs/contribute/style/style-guide/) and [Content](/docs/contribute/style/content-guide/) guides. - Review the smallest PRs (`size/XS`) first, then iterate towards the largest (`size/XXL`). - Review as many PRs as you can. - Ensure that the CLA is signed by each contributor. - Help new contributors sign the [CLA](https://github.com/kubernetes/community/blob/master/CLA.md). - Use [this](https://github.com/zparnold/k8s-docs-pr-botherer) script to automatically remind contributors that haven\u2019t signed the CLA to sign the CLA. - Provide feedback on proposed changes and help facilitate technical reviews from members of other SIGs. - Provide inline suggestions on the PR for the proposed content changes. - If you need to verify content, comment on the PR and request more details. - Assign relevant `sig/` label(s). - If needed, assign reviewers from the `reviewers:` block in the file's front matter. - Assign `Docs Review` and `Tech Review` labels to indicate the PR's review status. - Assign `Needs Doc Review` or `Needs Tech Review` for PRs that haven't yet been reviewed. - Assign `Doc Review: Open Issues` or `Tech Review: Open Issues` for PRs that have been reviewed and require further input or action before merging. - Assign `/lgtm` and `/approve` labels to PRs that can be merged. - Merge PRs when they are ready, or close PRs that shouldn\u2019t be accepted. - Consider accepting accurate technical content even if the content meets only some of the docs' [style guidelines](/docs/contribute/style/style-guide/). Open a new issue with the label `good first issue` to address style concerns. - Triage and tag incoming issues daily. See [Triage and categorize issues](/docs/contribute/review/for-approvers/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata. ### Helpful GitHub queries for wranglers The following queries are helpful when wrangling. After working through these queries, the remaining list of PRs to be reviewed is usually small. These queries specifically exclude localization PRs, and only include the `master` branch (except for the last one). - [No CLA, not eligible to merge](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22cncf-cla%3A+no%22+-label%3Ado-not-merge+label%3Alanguage%2Fen): Remind the contributor to sign the CLA. If they have already been reminded by both the bot and a human, close the PR and remind them that they can open it after signing the CLA. **Do not review PRs whose authors have not signed the CLA!** - [Needs LGTM](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-label%3Algtm+): If it needs technical review, loop in one of the reviewers suggested by the bot. If it needs docs review or copy-editing, either suggest changes or add a copyedit commit to the PR to move it along. - [Has LGTM, needs docs approval](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+label%3Algtm): Determine whether any additional changes or updates need to be made for the PR to be merged. If you think the PR is ready to be merged, comment `/approve`. - [Quick Wins](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+base%3Amaster+-label%3A%22do-not-merge%2Fwork-in-progress%22+-label%3A%22do-not-merge%2Fhold%22+label%3A%22cncf-cla%3A+yes%22+label%3A%22size%2FXS%22+label%3A%22language%2Fen%22+): If it\u2019s a small PR against master with no clear blockers. (change \"XS\" in the size label as you work through the PRs [XS, S, M, L, XL, XXL]). - [Not against master](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-base%3Amaster): If it's against a `dev-` branch, it's for an upcoming release. Make sure the [release meister](https://github.com/kubernetes/sig-release/tree/master/release-team) knows about it by adding a comment with `/assign @`. If it's against an old branch, help the PR author figure out whether it's targeted against the best branch. ### When to close Pull Requests Reviews and approvals are one tool to keep our PR queue short and current. Another tool is closure. - Close any PR where the CLA hasn\u2019t been signed for two weeks. PR authors can reopen the PR after signing the CLA, so this is a low-risk way to make sure nothing gets merged without a signed CLA. - Close any PR where the author has not responded to comments or feedback in 2 or more weeks. Don't be afraid to close pull requests. Contributors can easily reopen and resume works in progress. Oftentimes a closure notice is what spurs an author to resume and finish their contribution. To close a pull request, leave a `/close` comment on the PR. {{< note >}} An automated service, [`fejta-bot`](https://github.com/fejta-bot) automatically marks issues as stale after 90 days of inactivity, then closes them after an additional 30 days of inactivity when they become rotten. PR wranglers should close issues after 14-30 days of inactivity. {{< /note >}} ## Propose improvements SIG Docs [members](/docs/contribute/participating/#members) can propose improvements.", "commid": "website_pr_22284"}], "negative_passages": []} {"query_id": "q-en-website-c71a8f405f5293cc7a583f0da67b4603d51c0636ad459431eef31cebe4bb403e", "query": "Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.\n/assign /kind cleanup\n/language en", "positive_passages": [{"docid": "doc-en-website-80220942f11cc5d9dd4a8eff29f17dd8e2d3408e15aecb350a3634284db7a333", "text": "When you\u2019re ready to stop recording, click Stop. The video uploads automatically to YouTube. The video uploads automatically to YouTube. No newline at end of file", "commid": "website_pr_22284"}], "negative_passages": []} {"query_id": "q-en-website-c71a8f405f5293cc7a583f0da67b4603d51c0636ad459431eef31cebe4bb403e", "query": "Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.\n/assign /kind cleanup\n/language en", "positive_passages": [{"docid": "doc-en-website-d01e3f14db03d6646e7288edf7ce0e22a408b209c1061872031a7f6f6dfaf745", "text": " --- title: PR wranglers content_type: concept weight: 20 --- SIG Docs [approvers](/docs/contribute/participating/roles-and-responsibilites/#approvers) take week-long shifts [managing pull requests](https://github.com/kubernetes/website/wiki/PR-Wranglers) for the repository. This section covers the duties of a PR wrangler. For more information on giving good reviews, see [Reviewing changes](/docs/contribute/review/). ## Duties Each day in a week-long shift as PR Wrangler: - Triage and tag incoming issues daily. See [Triage and categorize issues](/docs/contribute/review/for-approvers/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata. - Review [open pull requests](https://github.com/kubernetes/website/pulls) for quality and adherence to the [Style](/docs/contribute/style/style-guide/) and [Content](/docs/contribute/style/content-guide/) guides. - Start with the smallest PRs (`size/XS`) first, and end with the largest (`size/XXL`). Review as many PRs as you can. - Make sure PR contributors sign the [CLA](https://github.com/kubernetes/community/blob/master/CLA.md). - Use [this](https://github.com/zparnold/k8s-docs-pr-botherer) script to remind contributors that haven\u2019t signed the CLA to do so. - Provide feedback on changes and ask for technical reviews from members of other SIGs. - Provide inline suggestions on the PR for the proposed content changes. - If you need to verify content, comment on the PR and request more details. - Assign relevant `sig/` label(s). - If needed, assign reviewers from the `reviewers:` block in the file's front matter. - Use the `/approve` comment to approve a PR for merging. Merge the PR when ready. - PRs should have a `/lgtm` comment from another member before merging. - Consider accepting technically accurate content that doesn't meet the [style guidelines](/docs/contribute/style/style-guide/). Open a new issue with the label `good first issue` to address style concerns. ### Helpful GitHub queries for wranglers The following queries are helpful when wrangling. After working through these queries, the remaining list of PRs to review is usually small. These queries exclude localization PRs. All queries are against the main branch except the last one. - [No CLA, not eligible to merge](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22cncf-cla%3A+no%22+-label%3Ado-not-merge+label%3Alanguage%2Fen): Remind the contributor to sign the CLA. If both the bot and a human have reminded them, close the PR and remind them that they can open it after signing the CLA. **Do not review PRs whose authors have not signed the CLA!** - [Needs LGTM](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-label%3Algtm+): Lists PRs that need an LGTM from a member. If the PR needs technical review, loop in one of the reviewers suggested by the bot. If the content needs work, add suggestions and feedback in-line. - [Has LGTM, needs docs approval](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+label%3Algtm): Lists PRs that need an `/approve` comment to merge. - [Quick Wins](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+base%3Amaster+-label%3A%22do-not-merge%2Fwork-in-progress%22+-label%3A%22do-not-merge%2Fhold%22+label%3A%22cncf-cla%3A+yes%22+label%3A%22size%2FXS%22+label%3A%22language%2Fen%22+): Lists PRs against the main branch with no clear blockers. (change \"XS\" in the size label as you work through the PRs [XS, S, M, L, XL, XXL]). - [Not against the main branch](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+-label%3Ado-not-merge+label%3Alanguage%2Fen+-base%3Amaster): If the PR is against a `dev-` branch, it's for an upcoming release. Assign the [docs release manager](https://github.com/kubernetes/sig-release/tree/master/release-team#kubernetes-release-team-roles) using: `/assign @`. If the PR is against an old branch, help the author figure out whether it's targeted against the best branch. ### When to close Pull Requests Reviews and approvals are one tool to keep our PR queue short and current. Another tool is closure. Close PRs where: - The author hasn't signed the CLA for two weeks. Authors can reopen the PR after signing the CLA. This is a low-risk way to make sure nothing gets merged without a signed CLA. - The author has not responded to comments or feedback in 2 or more weeks. Don't be afraid to close pull requests. Contributors can easily reopen and resume works in progress. Often a closure notice is what spurs an author to resume and finish their contribution. To close a pull request, leave a `/close` comment on the PR. {{< note >}} The [`fejta-bot`](https://github.com/fejta-bot) bot marks issues as stale after 90 days of inactivity. After 30 more days it marks issues as rotten and closes them. PR wranglers should close issues after 14-30 days of inactivity. {{< /note >}} No newline at end of file", "commid": "website_pr_22284"}], "negative_passages": []} {"query_id": "q-en-website-c71a8f405f5293cc7a583f0da67b4603d51c0636ad459431eef31cebe4bb403e", "query": "Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.\n/assign /kind cleanup\n/language en", "positive_passages": [{"docid": "doc-en-website-f3594193750eec65a99e32a1e70e4c68608a6f4651b951eb8e9da4bfda62fe8c", "text": "- Visit the Netlify page preview for a PR to make sure things look good before approving. - Participate in the [PR Wrangler rotation schedule](https://github.com/kubernetes/website/wiki/PR-Wranglers) for weekly rotations. SIG Docs expects all approvers to participate in this rotation. See [Be the PR Wrangler for a week](/docs/contribute/advanced#be-the-pr-wrangler-for-a-week) rotation. See [PR wranglers](/docs/contribute/participating/pr-wranglers/). for more details. ### Becoming an approver", "commid": "website_pr_22284"}], "negative_passages": []} {"query_id": "q-en-website-c71a8f405f5293cc7a583f0da67b4603d51c0636ad459431eef31cebe4bb403e", "query": "Umbrella issue: Take Advanced Contributing Be a PR Wrangler for a week topic and create a new page, Participating in SIG Docs PR Wranglers.\n/assign /kind cleanup\n/language en", "positive_passages": [{"docid": "doc-en-website-56f2f2bd06b6e9f07a8c1a6dcefa1b03c9bc6c96c0c9fde6b04e9c9d3be5f051", "text": "2. Assign the PR to one or more current SIG Docs approvers. If approved, a SIG Docs lead adds you to the appropriate GitHub team. Once added, [K8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home) assigns and suggests you as a reviewer on new pull requests. No newline at end of file If approved, a SIG Docs lead adds you to the appropriate GitHub team. Once added, [@k8s-ci-robot](https://github.com/kubernetes/test-infra/tree/master/prow#bots-home) assigns and suggests you as a reviewer on new pull requests. ## {{% heading \"whatsnext\" %}} - Read about [PR wrangling](/docs/contribute/participating/pr-wranglers), a role all approvers take on rotation. No newline at end of file", "commid": "website_pr_22284"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. title: Intro to Windows support in Kubernetes title: Kubernetes\u306eWindows\u30b5\u30dd\u30fc\u30c8\u6982\u8981 content_type: concept weight: 65 --- Windows applications constitute a large portion of the services and applications that run in many organizations. [Windows containers](https://aka.ms/windowscontainers) provide a modern way to encapsulate processes and package dependencies, making it easier to use DevOps practices and follow cloud native patterns for Windows applications. Kubernetes has become the defacto standard container orchestrator, and the release of Kubernetes 1.14 includes production support for scheduling Windows containers on Windows nodes in a Kubernetes cluster, enabling a vast ecosystem of Windows applications to leverage the power of Kubernetes. Organizations with investments in Windows-based applications and Linux-based applications don't have to look for separate orchestrators to manage their workloads, leading to increased operational efficiencies across their deployments, regardless of operating system. Windows\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306f\u3001\u591a\u304f\u306e\u7d44\u7e54\u3067\u5b9f\u884c\u3055\u308c\u3066\u3044\u308b\u30b5\u30fc\u30d3\u30b9\u3084\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306e\u5927\u90e8\u5206\u3092\u5360\u3081\u3066\u3044\u307e\u3059\u3002[Windows\u30b3\u30f3\u30c6\u30ca](https://aka.ms/windowscontainers)\u306f\u3001\u30d7\u30ed\u30bb\u30b9\u3068\u30d1\u30c3\u30b1\u30fc\u30b8\u306e\u4f9d\u5b58\u95a2\u4fc2\u3092\u4e00\u3064\u306b\u307e\u3068\u3081\u308b\u6700\u65b0\u306e\u65b9\u6cd5\u3092\u63d0\u4f9b\u3057\u3001DevOps\u30d7\u30e9\u30af\u30c6\u30a3\u30b9\u306e\u4f7f\u7528\u3068Windows\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306e\u30af\u30e9\u30a6\u30c9\u30cd\u30a4\u30c6\u30a3\u30d6\u30d1\u30bf\u30fc\u30f3\u306e\u8ffd\u6c42\u3092\u5bb9\u6613\u306b\u3057\u307e\u3059\u3002Kubernetes\u306f\u4e8b\u5b9f\u4e0a\u3001\u6a19\u6e96\u7684\u306a\u30b3\u30f3\u30c6\u30ca\u30aa\u30fc\u30b1\u30b9\u30c8\u30ec\u30fc\u30bf\u306b\u306a\u308a\u307e\u3057\u305f\u3002Kubernetes 1.14\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u306f\u3001Kubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u5185\u306eWindows\u30ce\u30fc\u30c9\u3067Windows\u30b3\u30f3\u30c6\u30ca\u3092\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u3059\u308b\u672c\u756a\u74b0\u5883\u30b5\u30dd\u30fc\u30c8\u304c\u542b\u307e\u308c\u305f\u306e\u3067\u3001Windows\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306e\u5e83\u5927\u306a\u30a8\u30b3\u30b7\u30b9\u30c6\u30e0\u306b\u304a\u3044\u3066\u3001Kubernetes\u3092\u6709\u52b9\u7684\u306b\u6d3b\u7528\u3067\u304d\u307e\u3059\u3002Windows\u30d9\u30fc\u30b9\u306e\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u3068Linux\u30d9\u30fc\u30b9\u306e\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306b\u6295\u8cc7\u3057\u3066\u3044\u308b\u7d44\u7e54\u306f\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3092\u7ba1\u7406\u3059\u308b\u500b\u5225\u306e\u30aa\u30fc\u30b1\u30b9\u30c8\u30ec\u30fc\u30bf\u30fc\u304c\u4e0d\u8981\u3068\u306a\u308b\u305f\u3081\u3001\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u306b\u95a2\u4fc2\u306a\u304f\u5c0e\u5165\u5168\u4f53\u306e\u904b\u7528\u52b9\u7387\u304c\u5411\u4e0a\u3057\u307e\u3059\u3002 ## Windows containers in Kubernetes ## Kubernetes\u306eWindows\u30b3\u30f3\u30c6\u30ca To enable the orchestration of Windows containers in Kubernetes, simply include Windows nodes in your existing Linux cluster. Scheduling Windows containers in [Pods](/ja/docs/concepts/workloads/pods/pod-overview/) on Kubernetes is as simple and easy as scheduling Linux-based containers. Kubernetes\u3067Windows\u30b3\u30f3\u30c6\u30ca\u306e\u30aa\u30fc\u30b1\u30b9\u30c8\u30ec\u30fc\u30b7\u30e7\u30f3\u3092\u6709\u52b9\u306b\u3059\u308b\u306b\u306f\u3001\u65e2\u5b58\u306eLinux\u30af\u30e9\u30b9\u30bf\u30fc\u306bWindows\u30ce\u30fc\u30c9\u3092\u542b\u3081\u308b\u3060\u3051\u3067\u3059\u3002Kubernetes\u306e[Pod](/ja/docs/concepts/workloads/pods/pod-overview/)\u3067Windows\u30b3\u30f3\u30c6\u30ca\u3092\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3059\u308b\u3053\u3068\u306f\u3001Linux\u30d9\u30fc\u30b9\u306e\u30b3\u30f3\u30c6\u30ca\u3092\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3059\u308b\u306e\u3068\u540c\u3058\u304f\u3089\u3044\u30b7\u30f3\u30d7\u30eb\u3067\u7c21\u5358\u3067\u3059\u3002 In order to run Windows containers, your Kubernetes cluster must include multiple operating systems, with control plane nodes running Linux and workers running either Windows or Linux depending on your workload needs. Windows Server 2019 is the only Windows operating system supported, enabling [Kubernetes Node](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node) on Windows (including kubelet, [container runtime](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd), and kube-proxy). For a detailed explanation of Windows distribution channels see the [Microsoft documentation](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19). Windows\u30b3\u30f3\u30c6\u30ca\u3092\u5b9f\u884c\u3059\u308b\u306b\u306f\u3001Kubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u8907\u6570\u306e\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3092\u542b\u3081\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u30ce\u30fc\u30c9\u306fLinux\u3001\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306f\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306e\u30cb\u30fc\u30ba\u306b\u5fdc\u3058\u3066Windows\u307e\u305f\u306fLinux\u3067\u5b9f\u884c\u3057\u307e\u3059\u3002Windows Server 2019\u306f\u3001\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u308b\u552f\u4e00\u306eWindows\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3067\u3042\u308a\u3001Windows\uff08kubelet\u3001[\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd)\u3001kube-proxy\u3092\u542b\u3080\uff09\u3067[Kubernetes\u30ce\u30fc\u30c9](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node)\u3092\u6709\u52b9\u306b\u3057\u307e\u3059\u3002Windows\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u30c1\u30e3\u30f3\u30cd\u30eb\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001[Microsoft\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8](https://docs.microsoft.com/en-us/windows-server/get-started-19/servicing-channels-19)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 {{< note >}} The Kubernetes control plane, including the [master components](/ja/docs/concepts/overview/components/), continues to run on Linux. There are no plans to have a Windows-only Kubernetes cluster. [\u30de\u30b9\u30bf\u30fc\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8](/ja/docs/concepts/overview/components/)\u3092\u542b\u3080Kubernetes\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u306f\u3001Linux\u3067\u5b9f\u884c\u3057\u7d9a\u3051\u307e\u3059\u3002Windows\u306e\u307f\u306eKubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u3092\u5c0e\u5165\u3059\u308b\u8a08\u753b\u306f\u3042\u308a\u307e\u305b\u3093\u3002 {{< /note >}} {{< note >}} In this document, when we talk about Windows containers we mean Windows containers with process isolation. Windows containers with [Hyper-V isolation](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container) is planned for a future release. \u3053\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3067\u306f\u3001Windows\u30b3\u30f3\u30c6\u30ca\u306b\u3064\u3044\u3066\u8aac\u660e\u3059\u308b\u5834\u5408\u3001\u30d7\u30ed\u30bb\u30b9\u5206\u96e2\u306eWindows\u30b3\u30f3\u30c6\u30ca\u3092\u610f\u5473\u3057\u307e\u3059\u3002[Hyper-V\u5206\u96e2](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container)\u306eWindows\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u5c06\u6765\u30ea\u30ea\u30fc\u30b9\u304c\u8a08\u753b\u3055\u308c\u3066\u3044\u307e\u3059\u3002 {{< /note >}} ## Supported Functionality and Limitations ## \u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u308b\u6a5f\u80fd\u3068\u5236\u9650 ### Supported Functionality ### \u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u308b\u6a5f\u80fd #### Compute #### \u30b3\u30f3\u30d4\u30e5\u30fc\u30c8 From an API and kubectl perspective, Windows containers behave in much the same way as Linux-based containers. However, there are some notable differences in key functionality which are outlined in the limitation section. API\u3068kubectl\u306e\u89b3\u70b9\u304b\u3089\u898b\u308b\u3068\u3001Windows\u30b3\u30f3\u30c6\u30ca\u306fLinux\u30d9\u30fc\u30b9\u306e\u30b3\u30f3\u30c6\u30ca\u3068\u307b\u3068\u3093\u3069\u540c\u3058\u3088\u3046\u306b\u52d5\u4f5c\u3057\u307e\u3059\u3002\u305f\u3060\u3057\u3001\u5236\u9650\u30bb\u30af\u30b7\u30e7\u30f3\u3067\u6982\u8aac\u3055\u308c\u3066\u3044\u308b\u4e3b\u8981\u306a\u6a5f\u80fd\u306b\u306f\u3001\u3044\u304f\u3064\u304b\u306e\u9855\u8457\u306a\u9055\u3044\u304c\u3042\u308a\u307e\u3059\u3002 Let's start with the operating system version. Refer to the following table for Windows operating system support in Kubernetes. A single heterogeneous Kubernetes cluster can have both Windows and Linux worker nodes. Windows containers have to be scheduled on Windows nodes and Linux containers on Linux nodes. \u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u304b\u3089\u59cb\u3081\u307e\u3057\u3087\u3046\u3002Kubernetes\u306eWindows\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u306e\u30b5\u30dd\u30fc\u30c8\u306b\u3064\u3044\u3066\u306f\u3001\u6b21\u306e\u8868\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002\u5358\u4e00\u306e\u7570\u7a2eKubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u306f\u3001Windows\u3068Linux\u306e\u4e21\u65b9\u306e\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u3092\u6301\u3064\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002Windows\u30b3\u30f3\u30c6\u30ca\u306fWindows\u30ce\u30fc\u30c9\u3067\u3001Linux\u30b3\u30f3\u30c6\u30ca\u306fLinux\u30ce\u30fc\u30c9\u3067\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 | Kubernetes version | Host OS version (Kubernetes Node) | | | | Kubernetes \u30d0\u30fc\u30b8\u30e7\u30f3 | \u30db\u30b9\u30c8OS \u30d0\u30fc\u30b8\u30e7\u30f3 (Kubernetes \u30ce\u30fc\u30c9) | | | | --- | --- | --- | --- | | | *Windows Server 1709* | *Windows Server 1803* | *Windows Server 1809/Windows Server 2019* | | *Kubernetes v1.14* | Not Supported | Not Supported| Supported for Windows Server containers Builds 17763.* with Docker EE-basic 18.09 | | *Kubernetes v1.14* | \u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 | \u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093| Windows Server containers Builds 17763.* \u3068 Docker EE-basic 18.09 \u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059 | {{< note >}} We don't expect all Windows customers to update the operating system for their apps frequently. Upgrading your applications is what dictates and necessitates upgrading or introducing new nodes to the cluster. For the customers that chose to upgrade their operating system for containers running on Kubernetes, we will offer guidance and step-by-step instructions when we add support for a new operating system version. This guidance will include recommended upgrade procedures for upgrading user applications together with cluster nodes. Windows nodes adhere to Kubernetes [version-skew policy](/ja/docs/setup/release/version-skew-policy/) (node to control plane versioning) the same way as Linux nodes do today. \u3059\u3079\u3066\u306eWindows\u30e6\u30fc\u30b6\u30fc\u304c\u30a2\u30d7\u30ea\u306e\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3092\u983b\u7e41\u306b\u66f4\u65b0\u3059\u308b\u3053\u3068\u306f\u671b\u3093\u3067\u3044\u307e\u305b\u3093\u3002\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306e\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u306f\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u65b0\u3057\u3044\u30ce\u30fc\u30c9\u3092\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u307e\u305f\u306f\u5c0e\u5165\u3059\u308b\u3053\u3068\u3092\u8981\u6c42\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002Kubernetes\u3067\u5b9f\u884c\u3055\u308c\u3066\u3044\u308b\u30b3\u30f3\u30c6\u30ca\u306e\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3092\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u3059\u308b\u3053\u3068\u3092\u9078\u629e\u3057\u305f\u304a\u5ba2\u69d8\u306b\u306f\u3001\u65b0\u3057\u3044\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u30d0\u30fc\u30b8\u30e7\u30f3\u306e\u30b5\u30dd\u30fc\u30c8\u8ffd\u52a0\u6642\u306b\u3001\u30ac\u30a4\u30c0\u30f3\u30b9\u3068\u6bb5\u968e\u7684\u306a\u6307\u793a\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002\u3053\u306e\u30ac\u30a4\u30c0\u30f3\u30b9\u306b\u306f\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u30ce\u30fc\u30c9\u3068\u5171\u306b\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u3092\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u3059\u308b\u305f\u3081\u306e\u63a8\u5968\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u624b\u9806\u304c\u542b\u307e\u308c\u307e\u3059\u3002Windows\u30ce\u30fc\u30c9\u306f\u3001\u73fe\u5728\u306eLinux\u30ce\u30fc\u30c9\u3068\u540c\u3058\u3088\u3046\u306b\u3001Kubernetes[\u30d0\u30fc\u30b8\u30e7\u30f3\u30b9\u30ad\u30e5\u30fc\u30dd\u30ea\u30b7\u30fc](/ja/docs/setup/release/version-skew-policy/)\uff08\u30ce\u30fc\u30c9\u304b\u3089\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u7ba1\u7406\uff09\u306b\u6e96\u62e0\u3057\u3066\u3044\u307e\u3059\u3002 {{< /note >}} {{< note >}} The Windows Server Host Operating System is subject to the [Windows Server ](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing) licensing. The Windows Container images are subject to the [Supplemental License Terms for Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula). Windows Server\u30db\u30b9\u30c8\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u306b\u306f\u3001[Windows Server](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing)\u30e9\u30a4\u30bb\u30f3\u30b9\u304c\u9069\u7528\u3055\u308c\u307e\u3059\u3002Windows\u30b3\u30f3\u30c6\u30ca\u30a4\u30e1\u30fc\u30b8\u306b\u306f\u3001[Windows\u30b3\u30f3\u30c6\u30ca\u306e\u8ffd\u52a0\u30e9\u30a4\u30bb\u30f3\u30b9\u6761\u9805](https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula)\u30e9\u30a4\u30bb\u30f3\u30b9\u304c\u63d0\u4f9b\u3055\u308c\u307e\u3059\u3002 {{< /note >}} {{< note >}} Windows containers with process isolation have strict compatibility rules, [where the host OS version must match the container base image OS version](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility). Once we support Windows containers with Hyper-V isolation in Kubernetes, the limitation and compatibility rules will change. \u30d7\u30ed\u30bb\u30b9\u5206\u96e2\u306eWindows\u30b3\u30f3\u30c6\u30ca\u306b\u306f\u3001\u53b3\u683c\u306a\u4e92\u63db\u6027\u30eb\u30fc\u30eb\u304c\u3042\u308a\u307e\u3059[\u30db\u30b9\u30c8OS\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u30d9\u30fc\u30b9\u30a4\u30e1\u30fc\u30b8\u306eOS\u30d0\u30fc\u30b8\u30e7\u30f3\u3068\u4e00\u81f4\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059](https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility)\u3002Kubernetes\u3067Hyper-V\u5206\u96e2\u306eWindows\u30b3\u30f3\u30c6\u30ca\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u3068\u3001\u5236\u9650\u3068\u4e92\u63db\u6027\u30eb\u30fc\u30eb\u304c\u5909\u66f4\u3055\u308c\u307e\u3059\u3002 {{< /note >}} Key Kubernetes elements work the same way in Windows as they do in Linux. In this section, we talk about some of the key workload enablers and how they map to Windows. Kubernetes\u306e\u4e3b\u8981\u306a\u8981\u7d20\u306f\u3001Windows\u3067\u3082Linux\u3068\u540c\u3058\u3088\u3046\u306b\u6a5f\u80fd\u3057\u307e\u3059\u3002\u3053\u306e\u30bb\u30af\u30b7\u30e7\u30f3\u3067\u306f\u3001\u4e3b\u8981\u306a\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30a4\u30cd\u30fc\u30d6\u30e9\u30fc\u306e\u3044\u304f\u3064\u304b\u3068\u3001\u305d\u308c\u3089\u304cWindows\u306b\u3069\u306e\u3088\u3046\u306b\u30de\u30c3\u30d7\u3055\u308c\u308b\u304b\u306b\u3064\u3044\u3066\u8aac\u660e\u3057\u307e\u3059\u3002 * [Pods](/ja/docs/concepts/workloads/pods/pod-overview/) A Pod is the basic building block of Kubernetes\u2013the smallest and simplest unit in the Kubernetes object model that you create or deploy. You may not deploy Windows and Linux containers in the same Pod. All containers in a Pod are scheduled onto a single Node where each Node represents a specific platform and architecture. The following Pod capabilities, properties and events are supported with Windows containers: Pod\u306f\u3001Kubernetes\u306e\u57fa\u672c\u7684\u306a\u30d3\u30eb\u30c7\u30a3\u30f3\u30b0\u30d6\u30ed\u30c3\u30af\u3067\u3059\u3002\u4f5c\u6210\u307e\u305f\u306f\u30c7\u30d7\u30ed\u30a4\u3059\u308bKubernetes\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u30e2\u30c7\u30eb\u306e\u6700\u5c0f\u304b\u3064\u6700\u3082\u5358\u7d14\u306a\u30e6\u30cb\u30c3\u30c8\u3067\u3059\u3002Windows\u3068Linux\u306e\u30b3\u30f3\u30c6\u30ca\u3092\u540c\u3058Pod\u306b\u30c7\u30d7\u30ed\u30a4\u3059\u308b\u3053\u3068\u306f\u3067\u304d\u307e\u305b\u3093\u3002Pod\u5185\u306e\u3059\u3079\u3066\u306e\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u5404\u30ce\u30fc\u30c9\u304c\u7279\u5b9a\u306e\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3068\u30a2\u30fc\u30ad\u30c6\u30af\u30c1\u30e3\u3092\u8868\u3059\u5358\u4e00\u306e\u30ce\u30fc\u30c9\u306b\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3055\u308c\u307e\u3059\u3002\u6b21\u306ePod\u6a5f\u80fd\u3001\u30d7\u30ed\u30d1\u30c6\u30a3\u3001\u304a\u3088\u3073\u30a4\u30d9\u30f3\u30c8\u304cWindows\u30b3\u30f3\u30c6\u30ca\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002: * Single or multiple containers per Pod with process isolation and volume sharing * Pod status fields * Readiness and Liveness probes * postStart & preStop container lifecycle events * ConfigMap, Secrets: as environment variables or volumes * \u30d7\u30ed\u30bb\u30b9\u5206\u96e2\u3068\u30dc\u30ea\u30e5\u30fc\u30e0\u5171\u6709\u3092\u5099\u3048\u305fPod\u3054\u3068\u306e\u5358\u4e00\u307e\u305f\u306f\u8907\u6570\u306e\u30b3\u30f3\u30c6\u30ca * Pod\u30b9\u30c6\u30fc\u30bf\u30b9\u30d5\u30a3\u30fc\u30eb\u30c9 * Readiness\u3068Liveness Probe * postStart\u3068preStop\u30b3\u30f3\u30c6\u30ca\u306e\u30e9\u30a4\u30d5\u30b5\u30a4\u30af\u30eb\u30a4\u30d9\u30f3\u30c8 * ConfigMap, Secrets: \u74b0\u5883\u5909\u6570\u307e\u305f\u306f\u30dc\u30ea\u30e5\u30fc\u30e0\u3068\u3057\u3066 * EmptyDir * Named pipe host mounts * Resource limits * \u540d\u524d\u4ed8\u304d\u30d1\u30a4\u30d7\u30db\u30b9\u30c8\u30de\u30a6\u30f3\u30c8 * \u30ea\u30bd\u30fc\u30b9\u5236\u9650 * [Controllers](/ja/docs/concepts/workloads/controllers/) Kubernetes controllers handle the desired state of Pods. The following workload controllers are supported with Windows containers: Kubernetes\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u306f\u3001Pod\u306e\u671b\u307e\u3057\u3044\u72b6\u614b\u3092\u51e6\u7406\u3057\u307e\u3059\u3002\u6b21\u306e\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u3001Windows\u30b3\u30f3\u30c6\u30ca\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002: * ReplicaSet * ReplicationController", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. A Kubernetes Service is an abstraction which defines a logical set of Pods and a policy by which to access them - sometimes called a micro-service. You can use services for cross-operating system connectivity. In Windows, services can utilize the following types, properties and capabilities: Kubernetes Service\u306f\u3001Pod\u306e\u8ad6\u7406\u30bb\u30c3\u30c8\u3068Pod\u306b\u30a2\u30af\u30bb\u30b9\u3059\u308b\u305f\u3081\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u5b9a\u7fa9\u3059\u308b\u62bd\u8c61\u6982\u5ff5\u3067\u3059\u3002\u30de\u30a4\u30af\u30ed\u30b5\u30fc\u30d3\u30b9\u3068\u547c\u3070\u308c\u308b\u3053\u3068\u3082\u3042\u308a\u307e\u3059\u3002\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u9593\u306e\u63a5\u7d9a\u306bService\u3092\u4f7f\u7528\u3067\u304d\u307e\u3059\u3002Windows\u3067\u306eService\u306f\u3001\u6b21\u306e\u30bf\u30a4\u30d7\u3001\u30d7\u30ed\u30d1\u30c6\u30a3\u3068\u6a5f\u80fd\u3092\u5229\u7528\u3067\u304d\u307e\u3059\u3002: * Service Environment variables * \u30b5\u30fc\u30d3\u30b9\u74b0\u5883\u5909\u6570 * NodePort * ClusterIP * LoadBalancer * ExternalName * Headless services Pods, Controllers and Services are critical elements to managing Windows workloads on Kubernetes. However, on their own they are not enough to enable the proper lifecycle management of Windows workloads in a dynamic cloud native environment. We added support for the following features: Pod\u3001Controller\u3001Service\u306f\u3001Kubernetes\u3067Windows\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3092\u7ba1\u7406\u3059\u308b\u305f\u3081\u306e\u91cd\u8981\u306a\u8981\u7d20\u3067\u3059\u3002\u305f\u3060\u3057\u3001\u305d\u308c\u3060\u3051\u3067\u306f\u3001\u52d5\u7684\u306a\u30af\u30e9\u30a6\u30c9\u30cd\u30a4\u30c6\u30a3\u30d6\u74b0\u5883\u3067Windows\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306e\u9069\u5207\u306a\u30e9\u30a4\u30d5\u30b5\u30a4\u30af\u30eb\u7ba1\u7406\u3092\u53ef\u80fd\u306b\u3059\u308b\u306e\u306b\u5341\u5206\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u6b21\u306e\u6a5f\u80fd\u306e\u30b5\u30dd\u30fc\u30c8\u3092\u8ffd\u52a0\u3057\u307e\u3057\u305f\uff1a * Pod and container metrics * Horizontal Pod Autoscaler support * Pod\u3068\u30b3\u30f3\u30c6\u30ca\u306e\u30e1\u30c8\u30ea\u30af\u30b9 * Horizontal Pod Autoscaler\u30b5\u30dd\u30fc\u30c8 * kubectl Exec * Resource Quotas * Scheduler preemption * \u30ea\u30bd\u30fc\u30b9\u30af\u30a6\u30a9\u30fc\u30bf * Scheduler\u306e\u30d7\u30ea\u30a8\u30f3\u30d7\u30b7\u30e7\u30f3 #### Container Runtime #### \u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0 Docker EE-basic 18.09 is required on Windows Server 2019 / 1809 nodes for Kubernetes. This works with the dockershim code included in the kubelet. Additional runtimes such as CRI-ContainerD may be supported in later Kubernetes versions. Kubernetes\u306eWindows Server 2019/1809\u30ce\u30fc\u30c9\u3067\u306f\u3001Docker EE-basic 18.09\u304c\u5fc5\u8981\u3067\u3059\u3002\u3053\u308c\u306f\u3001kubelet\u306b\u542b\u307e\u308c\u3066\u3044\u308bdockershim\u30b3\u30fc\u30c9\u3067\u52d5\u4f5c\u3057\u307e\u3059\u3002CRI-ContainerD\u306a\u3069\u306e\u8ffd\u52a0\u306e\u30e9\u30f3\u30bf\u30a4\u30e0\u306f\u3001Kubernetes\u306e\u4ee5\u964d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002 #### Persistent Storage #### \u6c38\u7d9a\u5316\u30b9\u30c8\u30ec\u30fc\u30b8 Kubernetes [volumes](/docs/concepts/storage/volumes/) enable complex applications, with data persistence and Pod volume sharing requirements, to be deployed on Kubernetes. Management of persistent volumes associated with a specific storage back-end or protocol includes actions such as: provisioning/de-provisioning/resizing of volumes, attaching/detaching a volume to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod that needs to persist data. The code implementing these volume management actions for a specific storage back-end or protocol is shipped in the form of a Kubernetes volume [plugin](/docs/concepts/storage/volumes/#types-of-volumes). The following broad classes of Kubernetes volume plugins are supported on Windows: Kubernetes[\u30dc\u30ea\u30e5\u30fc\u30e0](/docs/concepts/storage/volumes/)\u3092\u4f7f\u7528\u3059\u308b\u3068\u3001\u30c7\u30fc\u30bf\u306e\u6c38\u7d9a\u6027\u3068Pod\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u5171\u6709\u8981\u4ef6\u3092\u5099\u3048\u305f\u8907\u96d1\u306a\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u3092Kubernetes\u306b\u30c7\u30d7\u30ed\u30a4\u3067\u304d\u307e\u3059\u3002\u7279\u5b9a\u306e\u30b9\u30c8\u30ec\u30fc\u30b8\u30d0\u30c3\u30af\u30a8\u30f3\u30c9\u307e\u305f\u306f\u30d7\u30ed\u30c8\u30b3\u30eb\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u6c38\u7d9a\u5316\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u7ba1\u7406\u306b\u306f\u3001\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0/\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u89e3\u9664/\u30b5\u30a4\u30ba\u5909\u66f4\u3001Kubernetes\u30ce\u30fc\u30c9\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30a2\u30bf\u30c3\u30c1/\u30c7\u30bf\u30c3\u30c1\u3001\u304a\u3088\u3073\u30c7\u30fc\u30bf\u3092\u6c38\u7d9a\u5316\u3059\u308b\u5fc5\u8981\u304c\u3042\u308bPod\u5185\u306e\u500b\u5225\u306e\u30b3\u30f3\u30c6\u30ca\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30de\u30a6\u30f3\u30c8/\u30de\u30a6\u30f3\u30c8\u89e3\u9664\u306a\u3069\u306e\u30a2\u30af\u30b7\u30e7\u30f3\u304c\u542b\u307e\u308c\u307e\u3059\u3002\u7279\u5b9a\u306e\u30b9\u30c8\u30ec\u30fc\u30b8\u30d0\u30c3\u30af\u30a8\u30f3\u30c9\u307e\u305f\u306f\u30d7\u30ed\u30c8\u30b3\u30eb\u306b\u5bfe\u3057\u3066\u3053\u308c\u3089\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u7ba1\u7406\u30a2\u30af\u30b7\u30e7\u30f3\u3092\u5b9f\u88c5\u3059\u308b\u30b3\u30fc\u30c9\u306f\u3001Kubernetes\u30dc\u30ea\u30e5\u30fc\u30e0[\u30d7\u30e9\u30b0\u30a4\u30f3](/docs/concepts/storage/volumes/#types-of-volumes)\u306e\u5f62\u5f0f\u3067\u51fa\u8377\u3055\u308c\u307e\u3059\u3002\u6b21\u306e\u5e45\u5e83\u3044\u30af\u30e9\u30b9\u306eKubernetes\u30dc\u30ea\u30e5\u30fc\u30e0\u30d7\u30e9\u30b0\u30a4\u30f3\u304cWindows\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002: ##### In-tree Volume Plugins Code associated with in-tree volume plugins ship as part of the core Kubernetes code base. Deployment of in-tree volume plugins do not require installation of additional scripts or deployment of separate containerized plugin components. These plugins can handle: provisioning/de-provisioning and resizing of volumes in the storage backend, attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod. The following in-tree plugins support Windows nodes: ##### In-tree\u30dc\u30ea\u30e5\u30fc\u30e0\u30d7\u30e9\u30b0\u30a4\u30f3 In-tree\u30dc\u30ea\u30e5\u30fc\u30e0\u30d7\u30e9\u30b0\u30a4\u30f3\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u30b3\u30fc\u30c9\u306f\u3001\u30b3\u30a2Kubernetes\u30b3\u30fc\u30c9\u30d9\u30fc\u30b9\u306e\u4e00\u90e8\u3068\u3057\u3066\u63d0\u4f9b\u3055\u308c\u307e\u3059\u3002In-tree\u30dc\u30ea\u30e5\u30fc\u30e0\u30d7\u30e9\u30b0\u30a4\u30f3\u306e\u30c7\u30d7\u30ed\u30a4\u3067\u306f\u3001\u8ffd\u52a0\u306e\u30b9\u30af\u30ea\u30d7\u30c8\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u305f\u308a\u3001\u500b\u5225\u306e\u30b3\u30f3\u30c6\u30ca\u5316\u3055\u308c\u305f\u30d7\u30e9\u30b0\u30a4\u30f3\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u3092\u30c7\u30d7\u30ed\u30a4\u3057\u305f\u308a\u3059\u308b\u5fc5\u8981\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u3053\u308c\u3089\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001\u30b9\u30c8\u30ec\u30fc\u30b8\u30d0\u30c3\u30af\u30a8\u30f3\u30c9\u3067\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0/\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u89e3\u9664\u3068\u30b5\u30a4\u30ba\u5909\u66f4\u3001Kubernetes\u30ce\u30fc\u30c9\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30a2\u30bf\u30c3\u30c1/\u30a2\u30bf\u30c3\u30c1\u89e3\u9664\u3001Pod\u5185\u306e\u500b\u3005\u306e\u30b3\u30f3\u30c6\u30ca\u30fc\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30de\u30a6\u30f3\u30c8/\u30de\u30a6\u30f3\u30c8\u89e3\u9664\u3092\u51e6\u7406\u3067\u304d\u307e\u3059\u3002\u6b21\u306eIn-tree\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001Windows\u30ce\u30fc\u30c9\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u3059\u3002: * [awsElasticBlockStore](/docs/concepts/storage/volumes/#awselasticblockstore) * [azureDisk](/docs/concepts/storage/volumes/#azuredisk)", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. Code associated with [FlexVolume](/docs/concepts/storage/volumes/#flexVolume) plugins ship as out-of-tree scripts or binaries that need to be deployed directly on the host. FlexVolume plugins handle attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod. Provisioning/De-provisioning of persistent volumes associated with FlexVolume plugins may be handled through an external provisioner that is typically separate from the FlexVolume plugins. The following FlexVolume [plugins](https://github.com/Microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows), deployed as powershell scripts on the host, support Windows nodes: [FlexVolume](/docs/concepts/storage/volumes/#flexVolume)\u30d7\u30e9\u30b0\u30a4\u30f3\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u30b3\u30fc\u30c9\u306f\u3001\u30db\u30b9\u30c8\u306b\u76f4\u63a5\u30c7\u30d7\u30ed\u30a4\u3059\u308b\u5fc5\u8981\u304c\u3042\u308bout-of-tree\u306e\u30b9\u30af\u30ea\u30d7\u30c8\u307e\u305f\u306f\u30d0\u30a4\u30ca\u30ea\u3068\u3057\u3066\u51fa\u8377\u3055\u308c\u307e\u3059\u3002FlexVolume\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001Kubernetes\u30ce\u30fc\u30c9\u3068\u306e\u9593\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30a2\u30bf\u30c3\u30c1/\u30c7\u30bf\u30c3\u30c1\u3001\u304a\u3088\u3073Pod\u5185\u306e\u500b\u3005\u306e\u30b3\u30f3\u30c6\u30ca\u3068\u306e\u9593\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30de\u30a6\u30f3\u30c8/\u30de\u30a6\u30f3\u30c8\u89e3\u9664\u3092\u51e6\u7406\u3057\u307e\u3059\u3002FlexVolume\u30d7\u30e9\u30b0\u30a4\u30f3\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u6c38\u7d9a\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0/\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u89e3\u9664\u306f\u3001\u901a\u5e38FlexVolume\u30d7\u30e9\u30b0\u30a4\u30f3\u3068\u306f\u5225\u306e\u5916\u90e8\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u62c5\u5f53\u8005\u3092\u901a\u3058\u3066\u51e6\u7406\u3067\u304d\u307e\u3059\u3002\u6b21\u306eFlexVolume[\u30d7\u30e9\u30b0\u30a4\u30f3](https://github.com/Microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows)\u306f\u3001Powershell\u30b9\u30af\u30ea\u30d7\u30c8\u3068\u3057\u3066\u30db\u30b9\u30c8\u306b\u30c7\u30d7\u30ed\u30a4\u3055\u308c\u3001Windows\u30ce\u30fc\u30c9\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u307e\u3059\u3002: * [SMB](https://github.com/microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows/plugins/microsoft.com~smb.cmd) * [iSCSI](https://github.com/microsoft/K8s-Storage-Plugins/tree/master/flexvolume/windows/plugins/microsoft.com~iscsi.cmd) ##### CSI Plugins ##### CSI\u30d7\u30e9\u30b0\u30a4\u30f3 {{< feature-state for_k8s_version=\"v1.16\" state=\"alpha\" >}} Code associated with {{< glossary_tooltip text=\"CSI\" term_id=\"csi\" >}} plugins ship as out-of-tree scripts and binaries that are typically distributed as container images and deployed using standard Kubernetes constructs like DaemonSets and StatefulSets. CSI plugins handle a wide range of volume management actions in Kubernetes: provisioning/de-provisioning/resizing of volumes, attaching/detaching of volumes to/from a Kubernetes node and mounting/dismounting a volume to/from individual containers in a pod, backup/restore of persistent data using snapshots and cloning. CSI plugins typically consist of node plugins (that run on each node as a DaemonSet) and controller plugins. {{< glossary_tooltip text=\"CSI\" term_id=\"csi\" >}}\u30d7\u30e9\u30b0\u30a4\u30f3\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u305f\u30b3\u30fc\u30c9\u306f\u3001\u901a\u5e38\u3001\u30b3\u30f3\u30c6\u30ca\u30a4\u30e1\u30fc\u30b8\u3068\u3057\u3066\u914d\u5e03\u3055\u308c\u3001DaemonSets\u3084StatefulSets\u306a\u3069\u306e\u6a19\u6e96\u306eKubernetes\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u3092\u4f7f\u7528\u3057\u3066\u30c7\u30d7\u30ed\u30a4\u3055\u308c\u308bout-of-tree\u306e\u30b9\u30af\u30ea\u30d7\u30c8\u304a\u3088\u3073\u30d0\u30a4\u30ca\u30ea\u3068\u3057\u3066\u51fa\u8377\u3055\u308c\u307e\u3059\u3002CSI\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001Kubernetes\u306e\u5e45\u5e83\u3044\u30dc\u30ea\u30e5\u30fc\u30e0\u7ba1\u7406\u30a2\u30af\u30b7\u30e7\u30f3\u3092\u51e6\u7406\u3057\u307e\u3059:\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0/\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u89e3\u9664/\u30b5\u30a4\u30ba\u5909\u66f4\u3001Kubernetes\u30ce\u30fc\u30c9\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30a2\u30bf\u30c3\u30c1/\u30dc\u30ea\u30e5\u30fc\u30e0\u304b\u3089\u306e\u30c7\u30bf\u30c3\u30c1\u3001Pod\u5185\u306e\u500b\u3005\u306e\u30b3\u30f3\u30c6\u30ca\u3078\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30de\u30a6\u30f3\u30c8/\u30de\u30a6\u30f3\u30c8\u89e3\u9664\u3001\u30d0\u30c3\u30af\u30a2\u30c3\u30d7/\u30b9\u30ca\u30c3\u30d7\u30b7\u30e7\u30c3\u30c8\u3068\u30af\u30ed\u30fc\u30cb\u30f3\u30b0\u3092\u4f7f\u7528\u3057\u305f\u6c38\u7d9a\u30c7\u30fc\u30bf\u306e\u30d0\u30c3\u30af\u30a2\u30c3\u30d7/\u30ea\u30b9\u30c8\u30a2\u3002CSI\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u901a\u5e38\u3001\u30ce\u30fc\u30c9\u30d7\u30e9\u30b0\u30a4\u30f3\uff08\u5404\u30ce\u30fc\u30c9\u3067DaemonSet\u3068\u3057\u3066\u5b9f\u884c\u3055\u308c\u308b\uff09\u3068\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u69cb\u6210\u3055\u308c\u307e\u3059\u3002 CSI node plugins (especially those associated with persistent volumes exposed as either block devices or over a shared file-system) need to perform various privileged operations like scanning of disk devices, mounting of file systems, etc. These operations differ for each host operating system. For Linux worker nodes, containerized CSI node plugins are typically deployed as privileged containers. For Windows worker nodes, privileged operations for containerized CSI node plugins is supported using [csi-proxy](https://github.com/kubernetes-csi/csi-proxy), a community-managed, stand-alone binary that needs to be pre-installed on each Windows node. Please refer to the deployment guide of the CSI plugin you wish to deploy for further details. CSI\u30ce\u30fc\u30c9\u30d7\u30e9\u30b0\u30a4\u30f3\uff08\u7279\u306b\u3001\u30d6\u30ed\u30c3\u30af\u30c7\u30d0\u30a4\u30b9\u307e\u305f\u306f\u5171\u6709\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u3068\u3057\u3066\u516c\u958b\u3055\u308c\u305f\u6c38\u7d9a\u30dc\u30ea\u30e5\u30fc\u30e0\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u3066\u3044\u308b\u30d7\u30e9\u200b\u200b\u30b0\u30a4\u30f3\uff09\u306f\u3001\u30c7\u30a3\u30b9\u30af\u30c7\u30d0\u30a4\u30b9\u306e\u30b9\u30ad\u30e3\u30f3\u3001\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306e\u30de\u30a6\u30f3\u30c8\u306a\u3069\u3001\u3055\u307e\u3056\u307e\u306a\u7279\u6a29\u64cd\u4f5c\u3092\u5b9f\u884c\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u64cd\u4f5c\u306f\u3001\u30db\u30b9\u30c8\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3054\u3068\u306b\u7570\u306a\u308a\u307e\u3059\u3002Linux\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306e\u5834\u5408\u3001\u30b3\u30f3\u30c6\u30ca\u5316\u3055\u308c\u305fCSI\u30ce\u30fc\u30c9\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u901a\u5e38\u3001\u7279\u6a29\u30b3\u30f3\u30c6\u30ca\u3068\u3057\u3066\u30c7\u30d7\u30ed\u30a4\u3055\u308c\u307e\u3059\u3002Windows\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306e\u5834\u5408\u3001\u30b3\u30f3\u30c6\u30ca\u5316\u3055\u308c\u305fCSI\u30ce\u30fc\u30c9\u30d7\u30e9\u30b0\u30a4\u30f3\u306e\u7279\u6a29\u64cd\u4f5c\u306f\u3001[csi-proxy](https://github.com/kubernetes-csi/csi-proxy)\u3092\u4f7f\u7528\u3057\u3066\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u307e\u3059\u3002\u5404Windows\u30ce\u30fc\u30c9\u306b\u30d7\u30ea\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u3066\u3044\u308b\u3002\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001\u5c55\u958b\u3059\u308bCSI\u30d7\u30e9\u30b0\u30a4\u30f3\u306e\u5c55\u958b\u30ac\u30a4\u30c9\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 #### Networking #### \u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0 Networking for Windows containers is exposed through [CNI plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/). Windows containers function similarly to virtual machines in regards to networking. Each container has a virtual network adapter (vNIC) which is connected to a Hyper-V virtual switch (vSwitch). The Host Networking Service (HNS) and the Host Compute Service (HCS) work together to create containers and attach container vNICs to networks. HCS is responsible for the management of containers whereas HNS is responsible for the management of networking resources such as: Windows\u30b3\u30f3\u30c6\u30ca\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306f\u3001[CNI\u30d7\u30e9\u30b0\u30a4\u30f3](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)\u3092\u901a\u3058\u3066\u516c\u958b\u3055\u308c\u307e\u3059\u3002Windows\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306b\u95a2\u3057\u3066\u4eee\u60f3\u30de\u30b7\u30f3\u3068\u540c\u69d8\u306b\u6a5f\u80fd\u3057\u307e\u3059\u3002\u5404\u30b3\u30f3\u30c6\u30ca\u306b\u306f\u3001Hyper-V\u4eee\u60f3\u30b9\u30a4\u30c3\u30c1\uff08vSwitch\uff09\u306b\u63a5\u7d9a\u3055\u308c\u3066\u3044\u308b\u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a2\u30c0\u30d7\u30bf\u30fc\uff08vNIC\uff09\u304c\u3042\u308a\u307e\u3059\u3002Host Network Service\uff08HNS\uff09\u3068Host Compute Service\uff08HCS\uff09\u306f\u9023\u643a\u3057\u3066\u30b3\u30f3\u30c6\u30ca\u3092\u4f5c\u6210\u3057\u3001\u30b3\u30f3\u30c6\u30cavNIC\u3092\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306b\u63a5\u7d9a\u3057\u307e\u3059\u3002HCS\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u7ba1\u7406\u3092\u62c5\u5f53\u3059\u308b\u306e\u306b\u5bfe\u3057\u3001HNS\u306f\u6b21\u306e\u3088\u3046\u306a\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30ea\u30bd\u30fc\u30b9\u306e\u7ba1\u7406\u3092\u62c5\u5f53\u3057\u307e\u3059\u3002: * Virtual networks (including creation of vSwitches) * Endpoints / vNICs * Namespaces * Policies (Packet encapsulations, Load-balancing rules, ACLs, NAT'ing rules, etc.) * \u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\uff08vSwitch\u306e\u4f5c\u6210\u3092\u542b\u3080\uff09 * \u30a8\u30f3\u30c9\u30dd\u30a4\u30f3\u30c8/vNIC * \u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9 * \u30dd\u30ea\u30b7\u30fc\uff08\u30d1\u30b1\u30c3\u30c8\u306e\u30ab\u30d7\u30bb\u30eb\u5316\u3001\u8ca0\u8377\u5206\u6563\u30eb\u30fc\u30eb\u3001ACL\u3001NAT\u30eb\u30fc\u30eb\u306a\u3069\uff09 The following service spec types are supported: \u6b21\u306eService\u30bf\u30a4\u30d7\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002: * NodePort * ClusterIP * LoadBalancer * ExternalName Windows supports five different networking drivers/modes: L2bridge, L2tunnel, Overlay, Transparent, and NAT. In a heterogeneous cluster with Windows and Linux worker nodes, you need to select a networking solution that is compatible on both Windows and Linux. The following out-of-tree plugins are supported on Windows, with recommendations on when to use each CNI: Windows\u306f\u3001L2bridge\u3001L2tunnel\u3001Overlay\u3001Transparent\u3001NAT\u306e5\u3064\u306e\u7570\u306a\u308b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30c9\u30e9\u30a4\u30d0\u30fc/\u30e2\u30fc\u30c9\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u3059\u3002Windows\u3068Linux\u306e\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u3092\u6301\u3064\u7570\u7a2e\u30af\u30e9\u30b9\u30bf\u30fc\u3067\u306f\u3001Windows\u3068Linux\u306e\u4e21\u65b9\u3067\u4e92\u63db\u6027\u306e\u3042\u308b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3092\u9078\u629e\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u4ee5\u4e0b\u306e\u30c4\u30ea\u30fc\u5916\u30d7\u30e9\u30b0\u30a4\u30f3\u304cWindows\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u304a\u308a\u3001\u5404CNI\u3092\u3044\u3064\u4f7f\u7528\u3059\u308b\u304b\u306b\u95a2\u3059\u308b\u63a8\u5968\u4e8b\u9805\u304c\u3042\u308a\u307e\u3059\u3002: | Network Driver | Description | Container Packet Modifications | Network Plugins | Network Plugin Characteristics | | \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30c9\u30e9\u30a4\u30d0\u30fc | \u8aac\u660e | \u30b3\u30f3\u30c6\u30ca\u30d1\u30b1\u30c3\u30c8\u306e\u5909\u66f4 | \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3 | \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3\u306e\u7279\u6027 | | -------------- | ----------- | ------------------------------ | --------------- | ------------------------------ | | L2bridge | Containers are attached to an external vSwitch. Containers are attached to the underlay network, although the physical network doesn't need to learn the container MACs because they are rewritten on ingress/egress. Inter-container traffic is bridged inside the container host. | MAC is rewritten to host MAC, IP remains the same. | [win-bridge](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-bridge), [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md), Flannel host-gateway uses win-bridge | win-bridge uses L2bridge network mode, connects containers to the underlay of hosts, offering best performance. Requires user-defined routes (UDR) for inter-node connectivity. | | L2Tunnel | This is a special case of l2bridge, but only used on Azure. All packets are sent to the virtualization host where SDN policy is applied. | MAC rewritten, IP visible on the underlay network | [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) | Azure-CNI allows integration of containers with Azure vNET, and allows them to leverage the set of capabilities that [Azure Virtual Network provides](https://azure.microsoft.com/en-us/services/virtual-network/). For example, securely connect to Azure services or use Azure NSGs. See [azure-cni for some examples](https://docs.microsoft.com/en-us/azure/aks/concepts-network#azure-cni-advanced-networking) | | Overlay (Overlay networking for Windows in Kubernetes is in *alpha* stage) | Containers are given a vNIC connected to an external vSwitch. Each overlay network gets its own IP subnet, defined by a custom IP prefix.The overlay network driver uses VXLAN encapsulation. | Encapsulated with an outer header. | [Win-overlay](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-overlay), Flannel VXLAN (uses win-overlay) | win-overlay should be used when virtual container networks are desired to be isolated from underlay of hosts (e.g. for security reasons). Allows for IPs to be re-used for different overlay networks (which have different VNID tags) if you are restricted on IPs in your datacenter. This option requires [KB4489899](https://support.microsoft.com/help/4489899) on Windows Server 2019. | | Transparent (special use case for [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)) | Requires an external vSwitch. Containers are attached to an external vSwitch which enables intra-pod communication via logical networks (logical switches and routers). | Packet is encapsulated either via [GENEVE](https://datatracker.ietf.org/doc/draft-gross-geneve/) or [STT](https://datatracker.ietf.org/doc/draft-davie-stt/) tunneling to reach pods which are not on the same host.
Packets are forwarded or dropped via the tunnel metadata information supplied by the ovn network controller.
NAT is done for north-south communication. | [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes) | [Deploy via ansible](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib). Distributed ACLs can be applied via Kubernetes policies. IPAM support. Load-balancing can be achieved without kube-proxy. NATing is done without using iptables/netsh. | | NAT (*not used in Kubernetes*) | Containers are given a vNIC connected to an internal vSwitch. DNS/DHCP is provided using an internal component called [WinNAT](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/) | MAC and IP is rewritten to host MAC/IP. | [nat](https://github.com/Microsoft/windows-container-networking/tree/master/plugins/nat) | Included here for completeness | | L2bridge | \u30b3\u30f3\u30c6\u30ca\u306f\u5916\u90e8\u306evSwitch\u306b\u63a5\u7d9a\u3055\u308c\u307e\u3059\u3002\u30b3\u30f3\u30c6\u30ca\u306f\u30a2\u30f3\u30c0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306b\u63a5\u7d9a\u3055\u308c\u307e\u3059\u304c\u3001\u7269\u7406\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306f\u30b3\u30f3\u30c6\u30ca\u306eMAC\u3092\u4e0a\u308a/\u4e0b\u308a\u3067\u66f8\u304d\u63db\u3048\u308b\u305f\u3081\u3001MAC\u3092\u5b66\u7fd2\u3059\u308b\u5fc5\u8981\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u30b3\u30f3\u30c6\u30ca\u9593\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u30db\u30b9\u30c8\u5185\u3067\u30d6\u30ea\u30c3\u30b8\u3055\u308c\u307e\u3059\u3002 | MAC\u306f\u30db\u30b9\u30c8\u306eMAC\u306b\u66f8\u304d\u63db\u3048\u3089\u308c\u3001IP\u306f\u5909\u308f\u308a\u307e\u305b\u3093\u3002| [win-bridge](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-bridge)\u3001[Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md)\u3001Flannel\u30db\u30b9\u30c8\u30b2\u30fc\u30c8\u30a6\u30a7\u30a4\u306f\u3001win-bridge\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002 | win-bridge\u306fL2bridge\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30e2\u30fc\u30c9\u3092\u4f7f\u7528\u3057\u3066\u3001\u30b3\u30f3\u30c6\u30ca\u3092\u30db\u30b9\u30c8\u306e\u30a2\u30f3\u30c0\u30fc\u30ec\u30a4\u306b\u63a5\u7d9a\u3057\u3066\u3001\u6700\u9ad8\u306e\u30d1\u30d5\u30a9\u30fc\u30de\u30f3\u30b9\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002\u30ce\u30fc\u30c9\u9593\u63a5\u7d9a\u306b\u306f\u30e6\u30fc\u30b6\u30fc\u5b9a\u7fa9\u30eb\u30fc\u30c8\uff08UDR\uff09\u304c\u5fc5\u8981\u3067\u3059\u3002 | | L2Tunnel | \u3053\u308c\u306fl2bridge\u306e\u7279\u6b8a\u306a\u30b1\u30fc\u30b9\u3067\u3059\u304c\u3001Azure\u3067\u306e\u307f\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002\u3059\u3079\u3066\u306e\u30d1\u30b1\u30c3\u30c8\u306f\u3001SDN\u30dd\u30ea\u30b7\u30fc\u304c\u9069\u7528\u3055\u308c\u3066\u3044\u308b\u4eee\u60f3\u5316\u30db\u30b9\u30c8\u306b\u9001\u4fe1\u3055\u308c\u307e\u3059\u3002| MAC\u304c\u66f8\u304d\u63db\u3048\u3089\u308c\u3001IP\u304c\u30a2\u30f3\u30c0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3067\u8868\u793a\u3055\u308c\u307e\u3059\u3002 | [Azure-CNI](https://github.com/Azure/azure-container-networking/blob/master/docs/cni.md) | Azure-CNI\u3092\u4f7f\u7528\u3059\u308b\u3068\u3001\u30b3\u30f3\u30c6\u30ca\u3092Azure vNET\u3068\u7d71\u5408\u3057\u3001[Azure Virtual Network\u304c\u63d0\u4f9b](https://azure.microsoft.com/en-us/services/virtual-network/)\u3059\u308b\u4e00\u9023\u306e\u6a5f\u80fd\u3092\u6d3b\u7528\u3067\u304d\u307e\u3059\u3002\u305f\u3068\u3048\u3070\u3001Azure\u30b5\u30fc\u30d3\u30b9\u306b\u5b89\u5168\u306b\u63a5\u7d9a\u3059\u308b\u304b\u3001Azure NSG\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002[azure-cni\u306e\u3044\u304f\u3064\u304b\u306e\u4f8b](https://docs.microsoft.com/en-us/azure/aks/concepts-network#azure-cni-advanced-networking)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002| | \u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\uff08Kubernetes\u306eWindows\u7528\u306e\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306f *\u30a2\u30eb\u30d5\u30a1* \u6bb5\u968e\u3067\u3059\uff09| \u30b3\u30f3\u30c6\u30ca\u306b\u306f\u3001\u5916\u90e8\u306evSwitch\u306b\u63a5\u7d9a\u3055\u308c\u305fvNIC\u304c\u4ed8\u4e0e\u3055\u308c\u307e\u3059\u3002\u5404\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306f\u3001\u30ab\u30b9\u30bf\u30e0IP\u30d7\u30ec\u30d5\u30a3\u30c3\u30af\u30b9\u3067\u5b9a\u7fa9\u3055\u308c\u305f\u72ec\u81ea\u306eIP\u30b5\u30d6\u30cd\u30c3\u30c8\u3092\u53d6\u5f97\u3057\u307e\u3059\u3002\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30c9\u30e9\u30a4\u30d0\u30fc\u306f\u3001VXLAN\u3092\u4f7f\u7528\u3057\u3066\u30ab\u30d7\u30bb\u30eb\u5316\u3057\u307e\u3059\u3002 | \u5916\u90e8\u30d8\u30c3\u30c0\u30fc\u3067\u30ab\u30d7\u30bb\u30eb\u5316\u3055\u308c\u307e\u3059\u3002 | [Win-overlay](https://github.com/containernetworking/plugins/tree/master/plugins/main/windows/win-overlay)\u3001Flannel VXLAN (win-overlay\u3092\u4f7f\u7528) | win-overlay\u306f\u3001\u4eee\u60f3\u30b3\u30f3\u30c6\u30ca\u30fc\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u30db\u30b9\u30c8\u306e\u30a2\u30f3\u30c0\u30fc\u30ec\u30a4\u304b\u3089\u5206\u96e2\u3059\u308b\u5fc5\u8981\u304c\u3042\u308b\u5834\u5408\u306b\u4f7f\u7528\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\uff08\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u4e0a\u306e\u7406\u7531\u306a\u3069\uff09\u3002\u30c7\u30fc\u30bf\u30bb\u30f3\u30bf\u30fc\u5185\u306eIP\u304c\u5236\u9650\u3055\u308c\u3066\u3044\u308b\u5834\u5408\u306b\u3001\uff08\u7570\u306a\u308bVNID\u30bf\u30b0\u3092\u6301\u3064\uff09\u7570\u306a\u308b\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3067IP\u3092\u518d\u5229\u7528\u3067\u304d\u308b\u3088\u3046\u306b\u3057\u307e\u3059\u3002\u3053\u306e\u30aa\u30d7\u30b7\u30e7\u30f3\u306b\u306f\u3001Windows Server 2019\u3067[KB4489899](https://support.microsoft.com/help/4489899)\u304c\u5fc5\u8981\u3067\u3059\u3002| | \u900f\u904e\u7684\uff08[ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes)\u306e\u7279\u5225\u306a\u4f7f\u7528\u4f8b\uff09 | \u5916\u90e8\u306evSwitch\u304c\u5fc5\u8981\u3067\u3059\u3002\u30b3\u30f3\u30c6\u30ca\u306f\u5916\u90e8\u306evSwitch\u306b\u63a5\u7d9a\u3055\u308c\u3001\u8ad6\u7406\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\uff08\u8ad6\u7406\u30b9\u30a4\u30c3\u30c1\u304a\u3088\u3073\u30eb\u30fc\u30bf\u30fc\uff09\u3092\u4ecb\u3057\u305fPod\u5185\u901a\u4fe1\u3092\u53ef\u80fd\u306b\u3057\u307e\u3059\u3002 | \u30d1\u30b1\u30c3\u30c8\u306f\u3001[GENEVE](https://datatracker.ietf.org/doc/draft-gross-geneve/)\u307e\u305f\u306f[STT](https://datatracker.ietf.org/doc/draft-davie-stt/)\u30c8\u30f3\u30cd\u30ea\u30f3\u30b0\u3092\u4ecb\u3057\u3066\u30ab\u30d7\u30bb\u30eb\u5316\u3055\u308c\u3001\u540c\u3058\u30db\u30b9\u30c8\u4e0a\u306b\u306a\u3044\u30dd\u30c3\u30c9\u306b\u5230\u9054\u3057\u307e\u3059\u3002\u30d1\u30b1\u30c3\u30c8\u306f\u3001ovn\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306b\u3088\u3063\u3066\u63d0\u4f9b\u3055\u308c\u308b\u30c8\u30f3\u30cd\u30eb\u30e1\u30bf\u30c7\u30fc\u30bf\u60c5\u5831\u3092\u4ecb\u3057\u3066\u8ee2\u9001\u307e\u305f\u306f\u30c9\u30ed\u30c3\u30d7\u3055\u308c\u307e\u3059\u3002NAT\u306f\u5357\u5317\u901a\u4fe1\u306e\u305f\u3081\u306b\u884c\u308f\u308c\u307e\u3059\u3002 | [ovn-kubernetes](https://github.com/openvswitch/ovn-kubernetes) | [ansible\u7d4c\u7531\u3067\u30c7\u30d7\u30ed\u30a4](https://github.com/openvswitch/ovn-kubernetes/tree/master/contrib)\u3057\u307e\u3059\u3002\u5206\u6563ACL\u306f\u3001Kubernetes\u30dd\u30ea\u30b7\u30fc\u3092\u4ecb\u3057\u3066\u9069\u7528\u3067\u304d\u307e\u3059\u3002 IPAM\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u307e\u3059\u3002\u8ca0\u8377\u5206\u6563\u306f\u3001kube-proxy\u306a\u3057\u3067\u5b9f\u73fe\u3067\u304d\u307e\u3059\u3002 NAT\u306f\u3001ip\u200b\u200btables/netsh\u3092\u4f7f\u7528\u305b\u305a\u306b\u884c\u308f\u308c\u307e\u3059\u3002 | | NAT\uff08*Kubernetes\u3067\u306f\u4f7f\u7528\u3055\u308c\u307e\u305b\u3093*\uff09 | \u30b3\u30f3\u30c6\u30ca\u306b\u306f\u3001\u5185\u90e8\u306evSwitch\u306b\u63a5\u7d9a\u3055\u308c\u305fvNIC\u304c\u4ed8\u4e0e\u3055\u308c\u307e\u3059\u3002DNS/DHCP\u306f\u3001[WinNAT](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/)\u3068\u547c\u3070\u308c\u308b\u5185\u90e8\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u3092\u4f7f\u7528\u3057\u3066\u63d0\u4f9b\u3055\u308c\u307e\u3059\u3002 | MAC\u304a\u3088\u3073IP\u306f\u30db\u30b9\u30c8MAC/IP\u306b\u66f8\u304d\u63db\u3048\u3089\u308c\u307e\u3059\u3002 | [nat](https://github.com/Microsoft/windows-container-networking/tree/master/plugins/nat) | \u5b8c\u5168\u3092\u671f\u3059\u305f\u3081\u306b\u3053\u3053\u306b\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002 | As outlined above, the [Flannel](https://github.com/coreos/flannel) CNI [meta plugin](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel) is also supported on [Windows](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel#windows-support-experimental) via the [VXLAN network backend](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan) (**alpha support** ; delegates to win-overlay) and [host-gateway network backend](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw) (stable support; delegates to win-bridge). This plugin supports delegating to one of the reference CNI plugins (win-overlay, win-bridge), to work in conjunction with Flannel daemon on Windows (Flanneld) for automatic node subnet lease assignment and HNS network creation. This plugin reads in its own configuration file (cni.conf), and aggregates it with the environment variables from the FlannelD generated subnet.env file. It then delegates to one of the reference CNI plugins for network plumbing, and sends the correct configuration containing the node-assigned subnet to the IPAM plugin (e.g. host-local). \u4e0a\u3067\u6982\u8aac\u3057\u305f\u3088\u3046\u306b\u3001[Flannel](https://github.com/coreos/flannel) CNI[\u30e1\u30bf\u30d7\u30e9\u30b0\u30a4\u30f3](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel)\u306f\u3001[VXLAN\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d0\u30c3\u30af\u30a8\u30f3\u30c9](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)\uff08**\u30a2\u30eb\u30d5\u30a1\u30b5\u30dd\u30fc\u30c8**\u3001win-overlay\u3078\u306e\u30c7\u30ea\u30b2\u30fc\u30c8\uff09\u304a\u3088\u3073[\u30db\u30b9\u30c8\u30b2\u30fc\u30c8\u30a6\u30a7\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d0\u30c3\u30af\u30a8\u30f3\u30c9](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#host-gw)\uff08\u5b89\u5b9a\u3057\u305f\u30b5\u30dd\u30fc\u30c8\u3001win-bridge\u3078\u306e\u30c7\u30ea\u30b2\u30fc\u30c8\uff09\u3092\u4ecb\u3057\u3066[Windows](https://github.com/containernetworking/plugins/tree/master/plugins/meta/flannel#windows-support-experimental)\u3067\u3082\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u307e\u3059\u3002\u3053\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001\u53c2\u7167CNI\u30d7\u30e9\u30b0\u30a4\u30f3\uff08win-overlay\u3001win-bridge\uff09\u306e1\u3064\u3078\u306e\u59d4\u4efb\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3001Windows\u306eFlannel\u30c7\u30fc\u30e2\u30f3\uff08Flanneld\uff09\u3068\u9023\u643a\u3057\u3066\u3001\u30ce\u30fc\u30c9\u306e\u30b5\u30d6\u30cd\u30c3\u30c8\u30ea\u30fc\u30b9\u306e\u81ea\u52d5\u5272\u308a\u5f53\u3066\u3068HNS\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u4f5c\u6210\u3092\u884c\u3044\u307e\u3059\u3002\u3053\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u306f\u3001\u72ec\u81ea\u306e\u69cb\u6210\u30d5\u30a1\u30a4\u30eb\uff08cni.conf\uff09\u3092\u8aad\u307f\u53d6\u308a\u3001FlannelD\u3067\u751f\u6210\u3055\u308c\u305fsubnet.env\u30d5\u30a1\u30a4\u30eb\u304b\u3089\u306e\u74b0\u5883\u5909\u6570\u3068\u7d71\u5408\u3057\u307e\u3059\u3002\u6b21\u306b\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30df\u30f3\u30b0\u7528\u306e\u53c2\u7167CNI\u30d7\u30e9\u30b0\u30a4\u30f3\u306e1\u3064\u306b\u59d4\u4efb\u3057\u3001\u30ce\u30fc\u30c9\u5272\u308a\u5f53\u3066\u30b5\u30d6\u30cd\u30c3\u30c8\u3092\u542b\u3080\u6b63\u3057\u3044\u69cb\u6210\u3092IPAM\u30d7\u30e9\u30b0\u30a4\u30f3\uff08\u30db\u30b9\u30c8\u30ed\u30fc\u30ab\u30eb\u306a\u3069\uff09\u306b\u9001\u4fe1\u3057\u307e\u3059\u3002 For the node, pod, and service objects, the following network flows are supported for TCP/UDP traffic: Node\u3001Pod\u3001\u304a\u3088\u3073Service\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u5834\u5408\u3001TCP/UDP\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306b\u5bfe\u3057\u3066\u6b21\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u307e\u3059\u3002: * Pod -> Pod (IP) * Pod -> Pod (Name) * Pod -> Service (Cluster IP) * Pod -> Service (PQDN, but only if there are no \".\") * Pod -> Service (PQDN\u3001\u305f\u3060\u3057\u3001\u300c.\u300d\u304c\u306a\u3044\u5834\u5408\u306e\u307f) * Pod -> Service (FQDN) * Pod -> External (IP) * Pod -> External (DNS) * Node -> Pod * Pod -> Node The following IPAM options are supported on Windows: Windows\u3067\u306f\u3001\u6b21\u306eIPAM\u30aa\u30d7\u30b7\u30e7\u30f3\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002 * [Host-local](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local) * HNS IPAM (Inbox platform IPAM, this is a fallback when no IPAM is set) * [Azure-vnet-ipam](https://github.com/Azure/azure-container-networking/blob/master/docs/ipam.md) (for azure-cni only) * [\u30db\u30b9\u30c8\u30ed\u30fc\u30ab\u30eb](https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local) * HNS IPAM (\u53d7\u4fe1\u30c8\u30ec\u30a4\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0IPAM\u3001\u3053\u308c\u306fIPAM\u304c\u8a2d\u5b9a\u3055\u308c\u3066\u3044\u306a\u3044\u5834\u5408\u306e\u30d5\u30a9\u30fc\u30eb\u30d0\u30c3\u30af) * [Azure-vnet-ipam](https://github.com/Azure/azure-container-networking/blob/master/docs/ipam.md)\uff08azure-cni\u306e\u307f\uff09 ### Limitations ### \u5236\u9650 #### Control Plane #### \u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3 Windows is only supported as a worker node in the Kubernetes architecture and component matrix. This means that a Kubernetes cluster must always include Linux master nodes, zero or more Linux worker nodes, and zero or more Windows worker nodes. Windows\u306f\u3001Kubernetes\u30a2\u30fc\u30ad\u30c6\u30af\u30c1\u30e3\u3068\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u30de\u30c8\u30ea\u30c3\u30af\u30b9\u306e\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u3068\u3057\u3066\u306e\u307f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u3064\u307e\u308a\u3001Kubernetes\u30af\u30e9\u30b9\u30bf\u306b\u306f\u5e38\u306bLinux\u30de\u30b9\u30bf\u30fc\u30ce\u30fc\u30c9\u30010\u4ee5\u4e0a\u306eLinux\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u30010\u4ee5\u4e0a\u306eWindows\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u304c\u542b\u307e\u308c\u3066\u3044\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 #### Compute #### \u30b3\u30f3\u30d4\u30e5\u30fc\u30c8 ##### Resource management and process isolation ##### \u30ea\u30bd\u30fc\u30b9\u7ba1\u7406\u3068\u30d7\u30ed\u30bb\u30b9\u5206\u96e2 Linux cgroups are used as a pod boundary for resource controls in Linux. Containers are created within that boundary for network, process and file system isolation. The cgroups APIs can be used to gather cpu/io/memory stats. In contrast, Windows uses a Job object per container with a system namespace filter to contain all processes in a container and provide logical isolation from the host. There is no way to run a Windows container without the namespace filtering in place. This means that system privileges cannot be asserted in the context of the host, and thus privileged containers are not available on Windows. Containers cannot assume an identity from the host because the Security Account Manager (SAM) is separate. Linux cgroups\u306f\u3001Linux\u306e\u30ea\u30bd\u30fc\u30b9\u3092\u5236\u5fa1\u3059\u308bPod\u306e\u5883\u754c\u3068\u3057\u3066\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3001\u30d7\u30ed\u30bb\u30b9\u3001\u304a\u3088\u3073\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u3092\u5206\u96e2\u3059\u308b\u306e\u305f\u3081\u306b\u3001\u305d\u306e\u5883\u754c\u5185\u306b\u4f5c\u6210\u3055\u308c\u307e\u3059\u3002cgroups API\u3092\u4f7f\u7528\u3057\u3066\u3001cpu/io/memory\u306e\u7d71\u8a08\u3092\u53ce\u96c6\u3067\u304d\u307e\u3059\u3002\u5bfe\u7167\u7684\u306b\u3001Windows\u306f\u30b7\u30b9\u30c6\u30e0\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u30d5\u30a3\u30eb\u30bf\u30fc\u3092\u5099\u3048\u305f\u30b3\u30f3\u30c6\u30ca\u3054\u3068\u306e\u30b8\u30e7\u30d6\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092\u4f7f\u7528\u3057\u3066\u3001\u30b3\u30f3\u30c6\u30ca\u5185\u306e\u3059\u3079\u3066\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u683c\u7d0d\u3057\u3001\u30db\u30b9\u30c8\u304b\u3089\u306e\u8ad6\u7406\u7684\u306a\u5206\u96e2\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u30d5\u30a3\u30eb\u30bf\u30ea\u30f3\u30b0\u3092\u884c\u308f\u305a\u306bWindows\u30b3\u30f3\u30c6\u30ca\u3092\u5b9f\u884c\u3059\u308b\u65b9\u6cd5\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u3053\u308c\u306f\u3001\u30db\u30b9\u30c8\u306e\u74b0\u5883\u3067\u306f\u30b7\u30b9\u30c6\u30e0\u7279\u6a29\u3092\u4e3b\u5f35\u3067\u304d\u306a\u3044\u305f\u3081\u3001Windows\u3067\u306f\u7279\u6a29\u30b3\u30f3\u30c6\u30ca\u3092\u4f7f\u7528\u3067\u304d\u306a\u3044\u3053\u3068\u3092\u610f\u5473\u3057\u307e\u3059\u3002\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30ab\u30a6\u30f3\u30c8\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\uff08SAM\uff09\u304c\u72ec\u7acb\u3057\u3066\u3044\u308b\u305f\u3081\u3001\u30b3\u30f3\u30c6\u30ca\u306f\u30db\u30b9\u30c8\u304b\u3089ID\u3092\u5f15\u304d\u53d7\u3051\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u305b\u3093\u3002 ##### Operating System Restrictions ##### \u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u306e\u5236\u9650 Windows has strict compatibility rules, where the host OS version must match the container base image OS version. Only Windows containers with a container operating system of Windows Server 2019 are supported. Hyper-V isolation of containers, enabling some backward compatibility of Windows container image versions, is planned for a future release. Windows\u306b\u306f\u53b3\u5bc6\u306a\u4e92\u63db\u6027\u30eb\u30fc\u30eb\u304c\u3042\u308a\u3001\u30db\u30b9\u30c8OS\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u3068\u30b3\u30f3\u30c6\u30ca\u306e\u30d9\u30fc\u30b9\u30a4\u30e1\u30fc\u30b8OS\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306f\u3001\u4e00\u81f4\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002Windows Server 2019\u306e\u30b3\u30f3\u30c6\u30ca\u30aa\u30da\u30ec\u30fc\u30c6\u30a3\u30f3\u30b0\u30b7\u30b9\u30c6\u30e0\u3092\u5099\u3048\u305fWindows\u30b3\u30f3\u30c6\u30ca\u306e\u307f\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u307e\u3059\u3002Hyper-V\u5206\u96e2\u306e\u30b3\u30f3\u30c6\u30ca\u306f\u3001Windows\u30b3\u30f3\u30c6\u30ca\u306e\u30a4\u30e1\u30fc\u30b8\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u4e0b\u4f4d\u4e92\u63db\u6027\u3092\u6301\u305f\u305b\u308b\u3053\u3068\u306f\u3001\u5c06\u6765\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u8a08\u753b\u3055\u308c\u3066\u3044\u307e\u3059\u3002 ##### Feature Restrictions ##### \u6a5f\u80fd\u5236\u9650 * TerminationGracePeriod: not implemented * Single file mapping: to be implemented with CRI-ContainerD * Termination message: to be implemented with CRI-ContainerD * Privileged Containers: not currently supported in Windows containers * HugePages: not currently supported in Windows containers * The existing node problem detector is Linux-only and requires privileged containers. In general, we don't expect this to be used on Windows because privileged containers are not supported * Not all features of shared namespaces are supported (see API section for more details) * TerminationGracePeriod\uff1a\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * \u5358\u4e00\u30d5\u30a1\u30a4\u30eb\u306e\u30de\u30c3\u30d4\u30f3\u30b0\uff1aCRI-ContainerD\u3067\u5b9f\u88c5\u3055\u308c\u307e\u3059 * \u7d42\u4e86\u30e1\u30c3\u30bb\u30fc\u30b8\uff1aCRI-ContainerD\u3067\u5b9f\u88c5\u3055\u308c\u307e\u3059 * \u7279\u6a29\u30b3\u30f3\u30c6\u30ca\uff1a\u73fe\u5728Windows\u30b3\u30f3\u30c6\u30ca\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * HugePages\uff1a\u73fe\u5728Windows\u30b3\u30f3\u30c6\u30ca\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * \u65e2\u5b58\u306e\u30ce\u30fc\u30c9\u554f\u984c\u3092\u691c\u51fa\u3059\u308b\u6a5f\u80fd\u306fLinux\u5c02\u7528\u3067\u3042\u308a\u3001\u7279\u6a29\u30b3\u30f3\u30c6\u30ca\u304c\u5fc5\u8981\u3067\u3059\u3002\u4e00\u822c\u7684\u306b\u3001\u7279\u6a29\u30b3\u30f3\u30c6\u30ca\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u306a\u3044\u305f\u3081\u3001\u3053\u308c\u304cWindows\u3067\u4f7f\u7528\u3055\u308c\u308b\u3053\u3068\u306f\u60f3\u5b9a\u3057\u3066\u3044\u307e\u305b\u3093\u3002 * \u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u5171\u6709\u306b\u3064\u3044\u3066\u306f\u3001\u3059\u3079\u3066\u306e\u6a5f\u80fd\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u308b\u308f\u3051\u3067\u306f\u3042\u308a\u307e\u305b\u3093\uff08\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001API\u30bb\u30af\u30b7\u30e7\u30f3\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\uff09 ##### Memory Reservations and Handling ##### \u30e1\u30e2\u30ea\u4e88\u7d04\u3068\u51e6\u7406 Windows does not have an out-of-memory process killer as Linux does. Windows always treats all user-mode memory allocations as virtual, and pagefiles are mandatory. The net effect is that Windows won't reach out of memory conditions the same way Linux does, and processes page to disk instead of being subject to out of memory (OOM) termination. If memory is over-provisioned and all physical memory is exhausted, then paging can slow down performance. Windows\u306b\u306f\u3001Linux\u306e\u3088\u3046\u306a\u30e1\u30e2\u30ea\u4e0d\u8db3\u306e\u30d7\u30ed\u30bb\u30b9\u30ad\u30e9\u30fc\u306f\u3042\u308a\u307e\u305b\u3093\u3002Windows\u306f\u5e38\u306b\u5168\u30e6\u30fc\u30b6\u30fc\u30e2\u30fc\u30c9\u306e\u30e1\u30e2\u30ea\u5272\u308a\u5f53\u3066\u3092\u4eee\u60f3\u3068\u3057\u3066\u6271\u3044\u3001\u30da\u30fc\u30b8\u30d5\u30a1\u30a4\u30eb\u306f\u5fc5\u9808\u3067\u3059\u3002\u6b63\u5473\u306e\u52b9\u679c\u306f\u3001Windows\u306fLinux\u306e\u3088\u3046\u306a\u30e1\u30e2\u30ea\u4e0d\u8db3\u306e\u72b6\u614b\u306b\u306f\u306a\u3089\u305a\u3001\u30e1\u30e2\u30ea\u4e0d\u8db3\uff08OOM\uff09\u7d42\u4e86\u306e\u5f71\u97ff\u3092\u53d7\u3051\u308b\u4ee3\u308f\u308a\u306b\u30da\u30fc\u30b8\u3092\u30c7\u30a3\u30b9\u30af\u306b\u51e6\u7406\u3057\u307e\u3059\u3002\u30e1\u30e2\u30ea\u304c\u904e\u5270\u306b\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3055\u308c\u3001\u7269\u7406\u30e1\u30e2\u30ea\u306e\u3059\u3079\u3066\u304c\u4f7f\u3044\u679c\u305f\u3055\u308c\u308b\u3068\u3001\u30da\u30fc\u30b8\u30f3\u30b0\u306b\u3088\u3063\u3066\u30d1\u30d5\u30a9\u30fc\u30de\u30f3\u30b9\u304c\u4f4e\u4e0b\u3059\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002 Keeping memory usage within reasonable bounds is possible with a two-step process. First, use the kubelet parameters `--kubelet-reserve` and/or `--system-reserve` to account for memory usage on the node (outside of containers). This reduces [NodeAllocatable](/ja/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable)). As you deploy workloads, use resource limits (must set only limits or limits must equal requests) on containers. This also subtracts from NodeAllocatable and prevents the scheduler from adding more pods once a node is full. 2\u30b9\u30c6\u30c3\u30d7\u306e\u30d7\u30ed\u30bb\u30b9\u3067\u3001\u30e1\u30e2\u30ea\u4f7f\u7528\u91cf\u3092\u59a5\u5f53\u306a\u7bc4\u56f2\u5185\u306b\u4fdd\u3064\u3053\u3068\u304c\u53ef\u80fd\u3067\u3059\u3002\u307e\u305a\u3001kubelet\u30d1\u30e9\u30e1\u30fc\u30bf`--kubelet-reserve`\u3084`--system-reserve`\u3092\u4f7f\u7528\u3057\u3066\u3001\u30ce\u30fc\u30c9\uff08\u30b3\u30f3\u30c6\u30ca\u5916\uff09\u3067\u306e\u30e1\u30e2\u30ea\u4f7f\u7528\u91cf\u3092\u660e\u78ba\u306b\u3057\u307e\u3059\u3002\u3053\u308c\u306b\u3088\u308a\u3001[NodeAllocatable](/ja/docs/tasks/administer-cluster/reserve-compute-resources/#node-allocatable))\u304c\u524a\u6e1b\u3055\u308c\u307e\u3059\u3002\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3092\u30c7\u30d7\u30ed\u30a4\u3059\u308b\u3068\u304d\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u306b\u30ea\u30bd\u30fc\u30b9\u5236\u9650\u3092\u304b\u3051\u307e\u3059\uff08\u5236\u9650\u306e\u307f\u3092\u8a2d\u5b9a\u3059\u308b\u304b\u3001\u5236\u9650\u304c\u8981\u6c42\u3068\u7b49\u3057\u304f\u306a\u3051\u308c\u3070\u306a\u308a\u307e\u305b\u3093\uff09\u3002\u3053\u308c\u306b\u3088\u308a\u3001NodeAllocatable\u3082\u5dee\u3057\u5f15\u304b\u308c\u3001\u30ce\u30fc\u30c9\u306e\u30ea\u30bd\u30fc\u30b9\u304c\u30d5\u30eb\u306a\u72b6\u614b\u306b\u306a\u308b\u3068Scheduler\u304cPod\u3092\u8ffd\u52a0\u3067\u304d\u306a\u304f\u306a\u308a\u307e\u3059\u3002 A best practice to avoid over-provisioning is to configure the kubelet with a system reserved memory of at least 2GB to account for Windows, Docker, and Kubernetes processes. \u904e\u5270\u306a\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3092\u56de\u907f\u3059\u308b\u305f\u3081\u306e\u30d9\u30b9\u30c8\u30d7\u30e9\u30af\u30c6\u30a3\u30b9\u306f\u3001Windows\u3001Docker\u3001\u304a\u3088\u3073Kubernetes\u306e\u30d7\u30ed\u30bb\u30b9\u306b\u5bfe\u5fdc\u3059\u308b\u305f\u3081\u306b\u3001\u6700\u4f4e2GB\u306e\u30e1\u30e2\u30ea\u3092\u4e88\u7d04\u3057\u305f\u30b7\u30b9\u30c6\u30e0\u3067kubelet\u3092\u69cb\u6210\u3059\u308b\u3053\u3068\u3067\u3059\u3002 The behavior of the flags behave differently as described below: \u30d5\u30e9\u30b0\u306e\u632f\u821e\u3044\u306b\u3064\u3044\u3066\u306f\u3001\u6b21\u306e\u3088\u3046\u306a\u7570\u306a\u308b\u52d5\u4f5c\u3092\u3057\u307e\u3059\u3002: * `--kubelet-reserve`, `--system-reserve` , and `--eviction-hard` flags update Node Allocatable * Eviction by using `--enforce-node-allocable` is not implemented * Eviction by using `--eviction-hard` and `--eviction-soft` are not implemented * MemoryPressure Condition is not implemented * There are no OOM eviction actions taken by the kubelet * Kubelet running on the windows node does not have memory restrictions. `--kubelet-reserve` and `--system-reserve` do not set limits on kubelet or processes running on the host. This means kubelet or a process on the host could cause memory resource starvation outside the node-allocatable and scheduler * `--kubelet-reserve`\u3001`--system-reserve`\u3001\u304a\u3088\u3073`--eviction-hard`\u30d5\u30e9\u30b0\u306f\u30ce\u30fc\u30c9\u306e\u5272\u308a\u5f53\u3066\u53ef\u80fd\u6570\u3092\u66f4\u65b0\u3057\u307e\u3059 * `--enforce-node-allocable`\u3092\u4f7f\u7528\u3057\u305f\u6392\u9664\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * `--eviction-hard`\u304a\u3088\u3073`--eviction-soft`\u3092\u4f7f\u7528\u3057\u305f\u6392\u9664\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * MemoryPressure\u306e\u5236\u7d04\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * kubelet\u306b\u3088\u3063\u3066\u5b9f\u884c\u3055\u308c\u308bOOM\u3092\u6392\u9664\u3059\u308b\u3053\u3068\u306f\u3042\u308a\u307e\u305b\u3093 * Windows\u30ce\u30fc\u30c9\u3067\u5b9f\u884c\u3055\u308c\u3066\u3044\u308bKubelet\u306b\u306f\u30e1\u30e2\u30ea\u5236\u9650\u304c\u3042\u308a\u307e\u305b\u3093\u3002`--kubelet-reserve`\u3068`--system-reserve`\u306f\u3001\u30db\u30b9\u30c8\u3067\u5b9f\u884c\u3055\u308c\u3066\u3044\u308bkubelet\u307e\u305f\u306f\u30d7\u30ed\u30bb\u30b9\u306b\u5236\u9650\u3092\u8a2d\u5b9a\u3057\u307e\u305b\u3093\u3002\u3053\u308c\u306f\u3001\u30db\u30b9\u30c8\u4e0a\u306ekubelet\u307e\u305f\u306f\u30d7\u30ed\u30bb\u30b9\u304c\u3001NodeAllocatable\u3068Scheduler\u306e\u5916\u3067\u30e1\u30e2\u30ea\u30ea\u30bd\u30fc\u30b9\u4e0d\u8db3\u3092\u5f15\u304d\u8d77\u3053\u3059\u53ef\u80fd\u6027\u304c\u3042\u308b\u3053\u3068\u3092\u610f\u5473\u3057\u307e\u3059\u3002 #### Storage #### \u30b9\u30c8\u30ec\u30fc\u30b8 Windows has a layered filesystem driver to mount container layers and create a copy filesystem based on NTFS. All file paths in the container are resolved only within the context of that container. Windows\u306b\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u30ec\u30a4\u30e4\u30fc\u3092\u30de\u30a6\u30f3\u30c8\u3057\u3066\u3001NTFS\u306b\u57fa\u3065\u3044\u3066\u8907\u88fd\u3055\u308c\u305f\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u3092\u4f5c\u308b\u305f\u3081\u306e\u30ec\u30a4\u30e4\u30fc\u69cb\u9020\u306e\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u30c9\u30e9\u30a4\u30d0\u30fc\u304c\u3042\u308a\u307e\u3059\u3002\u30b3\u30f3\u30c6\u30ca\u5185\u306e\u3059\u3079\u3066\u306e\u30d5\u30a1\u30a4\u30eb\u30d1\u30b9\u306f\u3001\u305d\u306e\u30b3\u30f3\u30c6\u30ca\u306e\u74b0\u5883\u5185\u3060\u3051\u3067\u6c7a\u3081\u3089\u308c\u307e\u3059\u3002 * Volume mounts can only target a directory in the container, and not an individual file * Volume mounts cannot project files or directories back to the host filesystem * Read-only filesystems are not supported because write access is always required for the Windows registry and SAM database. However, read-only volumes are supported * Volume user-masks and permissions are not available. Because the SAM is not shared between the host & container, there's no mapping between them. All permissions are resolved within the context of the container * \u30dc\u30ea\u30e5\u30fc\u30e0\u30de\u30a6\u30f3\u30c8\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u5185\u306e\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u306e\u307f\u3092\u5bfe\u8c61\u306b\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u3001\u500b\u5225\u306e\u30d5\u30a1\u30a4\u30eb\u306f\u5bfe\u8c61\u306b\u3067\u304d\u307e\u305b\u3093 * \u30dc\u30ea\u30e5\u30fc\u30e0\u30de\u30a6\u30f3\u30c8\u306f\u3001\u30d5\u30a1\u30a4\u30eb\u307e\u305f\u306f\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u3092\u30db\u30b9\u30c8\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306b\u6295\u5f71\u3059\u308b\u3053\u3068\u306f\u3067\u304d\u307e\u305b\u3093 * Windows\u30ec\u30b8\u30b9\u30c8\u30ea\u3068SAM\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u306b\u306f\u5e38\u306b\u66f8\u304d\u8fbc\u307f\u30a2\u30af\u30bb\u30b9\u304c\u5fc5\u8981\u3067\u3042\u308b\u305f\u3081\u3001\u8aad\u307f\u53d6\u308a\u5c02\u7528\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002\u305f\u3060\u3057\u3001\u8aad\u307f\u53d6\u308a\u5c02\u7528\u30dc\u30ea\u30e5\u30fc\u30e0\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059 * \u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30e6\u30fc\u30b6\u30fc\u30de\u30b9\u30af\u3068\u6a29\u9650\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3002SAM\u306f\u30db\u30b9\u30c8\u3068\u30b3\u30f3\u30c6\u30ca\u9593\u3067\u5171\u6709\u3055\u308c\u306a\u3044\u305f\u3081\u3001\u305d\u308c\u3089\u306e\u9593\u306e\u30de\u30c3\u30d4\u30f3\u30b0\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u3059\u3079\u3066\u306e\u6a29\u9650\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u74b0\u5883\u5185\u3067\u6c7a\u3081\u3089\u308c\u307e\u3059 As a result, the following storage functionality is not supported on Windows nodes \u305d\u306e\u7d50\u679c\u3001\u6b21\u306e\u30b9\u30c8\u30ec\u30fc\u30b8\u6a5f\u80fd\u306fWindows\u30ce\u30fc\u30c9\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u307e\u305b\u3093\u3002 * Volume subpath mounts. Only the entire volume can be mounted in a Windows container. * Subpath volume mounting for Secrets * Host mount projection * DefaultMode (due to UID/GID dependency) * Read-only root filesystem. Mapped volumes still support readOnly * Block device mapping * Memory as the storage medium * File system features like uui/guid, per-user Linux filesystem permissions * NFS based storage/volume support * Expanding the mounted volume (resizefs) * \u30dc\u30ea\u30e5\u30fc\u30e0\u30b5\u30d6\u30d1\u30b9\u306e\u30de\u30a6\u30f3\u30c8\u3002Windows\u30b3\u30f3\u30c6\u30ca\u306b\u30de\u30a6\u30f3\u30c8\u3067\u304d\u308b\u306e\u306f\u30dc\u30ea\u30e5\u30fc\u30e0\u5168\u4f53\u3060\u3051\u3067\u3059\u3002 * \u30b7\u30fc\u30af\u30ec\u30c3\u30c8\u306e\u30b5\u30d6\u30d1\u30b9\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30de\u30a6\u30f3\u30c8 * \u30db\u30b9\u30c8\u30de\u30a6\u30f3\u30c8\u30d7\u30ed\u30b8\u30a7\u30af\u30b7\u30e7\u30f3 * DefaultMode\uff08UID/GID\u4f9d\u5b58\u95a2\u4fc2\u306b\u3088\u308b\uff09 * \u8aad\u307f\u53d6\u308a\u5c02\u7528\u306e\u30eb\u30fc\u30c8\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u3002\u30de\u30c3\u30d7\u3055\u308c\u305f\u30dc\u30ea\u30e5\u30fc\u30e0\u306f\u5f15\u304d\u7d9a\u304d\u8aad\u307f\u53d6\u308a\u5c02\u7528\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u307e\u3059 * \u30d6\u30ed\u30c3\u30af\u30c7\u30d0\u30a4\u30b9\u30de\u30c3\u30d4\u30f3\u30b0 * \u8a18\u61b6\u5a92\u4f53\u3068\u3057\u3066\u306e\u30e1\u30e2\u30ea * uui/guid\u3001\u30e6\u30fc\u30b6\u30fc\u3054\u3068\u306eLinux\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u6a29\u9650\u306a\u3069\u306e\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u6a5f\u80fd * NFS\u30d9\u30fc\u30b9\u306e\u30b9\u30c8\u30ec\u30fc\u30b8/\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u30b5\u30dd\u30fc\u30c8 * \u30de\u30a6\u30f3\u30c8\u3055\u308c\u305f\u30dc\u30ea\u30e5\u30fc\u30e0\u306e\u62e1\u5f35\uff08resizefs\uff09 #### Networking #### \u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0 Windows Container Networking differs in some important ways from Linux networking. The [Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture) contains additional details and background. Windows\u30b3\u30f3\u30c6\u30ca\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u306f\u3001Linux\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u3068\u306f\u3044\u304f\u3064\u304b\u306e\u91cd\u8981\u306a\u5b9f\u88c5\u65b9\u6cd5\u306e\u9055\u3044\u304c\u3042\u308a\u307e\u3059\u3002[Microsoft documentation for Windows Container Networking](https://docs.microsoft.com/en-us/virtualization/windowscontainers/container-networking/architecture)\u306b\u306f\u3001\u8ffd\u52a0\u306e\u8a73\u7d30\u3068\u80cc\u666f\u304c\u3042\u308a\u307e\u3059\u3002 The Windows host networking networking service and virtual switch implement namespacing and can create virtual NICs as needed for a pod or container. However, many configurations such as DNS, routes, and metrics are stored in the Windows registry database rather than /etc/... files as they are on Linux. The Windows registry for the container is separate from that of the host, so concepts like mapping /etc/resolv.conf from the host into a container don't have the same effect they would on Linux. These must be configured using Windows APIs run in the context of that container. Therefore CNI implementations need to call the HNS instead of relying on file mappings to pass network details into the pod or container. Windows\u30db\u30b9\u30c8\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30b5\u30fc\u30d3\u30b9\u3068\u4eee\u60f3\u30b9\u30a4\u30c3\u30c1\u306f\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u3092\u5b9f\u88c5\u3057\u3066\u3001Pod\u307e\u305f\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u5fc5\u8981\u306b\u5fdc\u3058\u3066\u4eee\u60f3NIC\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002\u305f\u3060\u3057\u3001DNS\u3001\u30eb\u30fc\u30c8\u3001\u30e1\u30c8\u30ea\u30c3\u30af\u306a\u3069\u306e\u591a\u304f\u306e\u69cb\u6210\u306f\u3001Linux\u306e\u3088\u3046\u306a/etc/...\u30d5\u30a1\u30a4\u30eb\u3067\u306f\u306a\u304f\u3001Windows\u30ec\u30b8\u30b9\u30c8\u30ea\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u306b\u4fdd\u5b58\u3055\u308c\u307e\u3059\u3002\u30b3\u30f3\u30c6\u30ca\u306eWindows\u30ec\u30b8\u30b9\u30c8\u30ea\u306f\u30db\u30b9\u30c8\u306e\u30ec\u30b8\u30b9\u30c8\u30ea\u3068\u306f\u5225\u3067\u3042\u308b\u305f\u3081\u3001\u30db\u30b9\u30c8\u304b\u3089\u30b3\u30f3\u30c6\u30ca\u3078\u306e/etc/resolv.conf\u306e\u30de\u30c3\u30d4\u30f3\u30b0\u306a\u3069\u306e\u6982\u5ff5\u306f\u3001Linux\u306e\u5834\u5408\u3068\u540c\u3058\u52b9\u679c\u3092\u3082\u305f\u3089\u3057\u307e\u305b\u3093\u3002\u3053\u308c\u3089\u306f\u3001\u305d\u306e\u30b3\u30f3\u30c6\u30ca\u306e\u74b0\u5883\u3067\u5b9f\u884c\u3055\u308c\u308bWindows API\u3092\u4f7f\u7528\u3057\u3066\u69cb\u6210\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u3057\u305f\u304c\u3063\u3066\u3001CNI\u306e\u5b9f\u88c5\u306f\u3001\u30d5\u30a1\u30a4\u30eb\u30de\u30c3\u30d4\u30f3\u30b0\u306b\u4f9d\u5b58\u3059\u308b\u4ee3\u308f\u308a\u306bHNS\u3092\u547c\u3073\u51fa\u3057\u3066\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u8a73\u7d30\u3092Pod\u307e\u305f\u306f\u30b3\u30f3\u30c6\u30ca\u306b\u6e21\u3059\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 The following networking functionality is not supported on Windows nodes \u6b21\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u6a5f\u80fd\u306fWindows\u30ce\u30fc\u30c9\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * Host networking mode is not available for Windows pods * Local NodePort access from the node itself fails (works for other nodes or external clients) * Accessing service VIPs from nodes will be available with a future release of Windows Server * Overlay networking support in kube-proxy is an alpha release. In addition, it requires [KB4482887](https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887) to be installed on Windows Server 2019 * Local Traffic Policy and DSR mode * Windows containers connected to l2bridge, l2tunnel, or overlay networks do not support communicating over the IPv6 stack. There is outstanding Windows platform work required to enable these network drivers to consume IPv6 addresses and subsequent Kubernetes work in kubelet, kube-proxy, and CNI plugins. * Outbound communication using the ICMP protocol via the win-overlay, win-bridge, and Azure-CNI plugin. Specifically, the Windows data plane ([VFP](https://www.microsoft.com/en-us/research/project/azure-virtual-filtering-platform/)) doesn't support ICMP packet transpositions. This means: * ICMP packets directed to destinations within the same network (e.g. pod to pod communication via ping) work as expected and without any limitations * TCP/UDP packets work as expected and without any limitations * ICMP packets directed to pass through a remote network (e.g. pod to external internet communication via ping) cannot be transposed and thus will not be routed back to their source * Since TCP/UDP packets can still be transposed, one can substitute `ping ` with `curl ` to be able to debug connectivity to the outside world. * \u30db\u30b9\u30c8\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30e2\u30fc\u30c9\u306fWindows Pod\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093 * \u30ce\u30fc\u30c9\u81ea\u4f53\u304b\u3089\u306e\u30ed\u30fc\u30ab\u30ebNodePort\u30a2\u30af\u30bb\u30b9\u306f\u5931\u6557\u3057\u307e\u3059\uff08\u4ed6\u306e\u30ce\u30fc\u30c9\u307e\u305f\u306f\u5916\u90e8\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u3067\u6a5f\u80fd\uff09 * \u30ce\u30fc\u30c9\u304b\u3089\u306eService VIP\u3078\u306e\u30a2\u30af\u30bb\u30b9\u306f\u3001Windows Server\u306e\u5c06\u6765\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u5229\u7528\u53ef\u80fd\u306b\u306a\u308b\u4e88\u5b9a\u3067\u3059 * kube-proxy\u306e\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30b5\u30dd\u30fc\u30c8\u306f\u30a2\u30eb\u30d5\u30a1\u30ea\u30ea\u30fc\u30b9\u3067\u3059\u3002\u3055\u3089\u306b\u3001[KB4482887](https://support.microsoft.com/en-us/help/4482887/windows-10-update-kb4482887)\u304cWindows Server 2019\u306b\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u3066\u3044\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059 * \u30ed\u30fc\u30ab\u30eb\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u30dd\u30ea\u30b7\u30fc\u3068DSR\u30e2\u30fc\u30c9 * l2bridge\u3001l2tunnel\u3001\u307e\u305f\u306f\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306b\u63a5\u7d9a\u3055\u308c\u305fWindows\u30b3\u30f3\u30c6\u30ca\u306f\u3001IPv6\u30b9\u30bf\u30c3\u30af\u3092\u4ecb\u3057\u305f\u901a\u4fe1\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u305b\u3093\u3002\u3053\u308c\u3089\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30c9\u30e9\u30a4\u30d0\u30fc\u304cIPv6\u30a2\u30c9\u30ec\u30b9\u3092\u4f7f\u7528\u3067\u304d\u308b\u3088\u3046\u306b\u3059\u308b\u305f\u3081\u306b\u5fc5\u8981\u306a\u6a5f\u80fd\u3068\u3057\u3066\u3001\u512a\u308c\u305fWindows\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u306e\u6a5f\u80fd\u304c\u3042\u308a\u3001\u305d\u308c\u306b\u7d9a\u3044\u3066\u3001kubelet\u3001kube-proxy\u3001\u304a\u3088\u3073CNI\u30d7\u30e9\u30b0\u30a4\u30f3\u3068\u3044\u3063\u305fKubernetes\u306e\u6a5f\u80fd\u304c\u3042\u308a\u307e\u3059\u3002 * win-overlay\u3001win-bridge\u3001\u304a\u3088\u3073Azure-CNI\u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u4ecb\u3057\u305fICMP\u30d7\u30ed\u30c8\u30b3\u30eb\u3092\u4f7f\u7528\u3057\u305f\u30a2\u30a6\u30c8\u30d0\u30a6\u30f3\u30c9\u901a\u4fe1\u3002\u5177\u4f53\u7684\u306b\u306f\u3001Windows\u30c7\u30fc\u30bf\u30d7\u30ec\u30fc\u30f3([VFP](https://www.microsoft.com/en-us/research/project/azure-virtual-filtering-platform/))\u306f\u3001ICMP\u30d1\u30b1\u30c3\u30c8\u306e\u7f6e\u304d\u63db\u3048\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u305b\u3093\u3002\u3053\u308c\u306e\u610f\u5473\u306f\uff1a * \u540c\u3058\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u5185\u306e\u5b9b\u5148\u306b\u5411\u3051\u3089\u308c\u305fICMP\u30d1\u30b1\u30c3\u30c8\uff08ping\u3092\u4ecb\u3057\u305fPod\u9593\u901a\u4fe1\u306a\u3069\uff09\u306f\u671f\u5f85\u3069\u304a\u308a\u306b\u6a5f\u80fd\u3057\u3001\u5236\u9650\u306f\u3042\u308a\u307e\u305b\u3093 * TCP/UDP\u30d1\u30b1\u30c3\u30c8\u306f\u671f\u5f85\u3069\u304a\u308a\u306b\u6a5f\u80fd\u3057\u3001\u5236\u9650\u306f\u3042\u308a\u307e\u305b\u3093 * \u30ea\u30e2\u30fc\u30c8\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\uff08Pod\u304b\u3089ping\u7d4c\u7531\u306e\u5916\u90e8\u30a4\u30f3\u30bf\u30fc\u30cd\u30c3\u30c8\u901a\u4fe1\u306a\u3069\uff09\u3092\u901a\u904e\u3059\u308b\u3088\u3046\u306b\u6307\u793a\u3055\u308c\u305fICMP\u30d1\u30b1\u30c3\u30c8\u306f\u7f6e\u304d\u63db\u3048\u3067\u304d\u306a\u3044\u305f\u3081\u3001\u30bd\u30fc\u30b9\u306b\u30eb\u30fc\u30c6\u30a3\u30f3\u30b0\u3055\u308c\u307e\u305b\u3093\u3002 * TCP/UDP\u30d1\u30b1\u30c3\u30c8\u306f\u5f15\u304d\u7d9a\u304d\u7f6e\u304d\u63db\u3048\u3067\u304d\u308b\u305f\u3081\u3001`ping `\u3092`curl `\u306b\u7f6e\u304d\u63db\u3048\u308b\u3053\u3068\u3067\u3001\u5916\u90e8\u3078\u306e\u63a5\u7d9a\u3092\u30c7\u30d0\u30c3\u30b0\u3067\u304d\u307e\u3059\u3002 These features were added in Kubernetes v1.15: \u3053\u308c\u3089\u306e\u6a5f\u80fd\u306fKubernetes v1.15\u3067\u8ffd\u52a0\u3055\u308c\u307e\u3057\u305f\u3002 * `kubectl port-forward` ##### CNI Plugins ##### CNI\u30d7\u30e9\u30b0\u30a4\u30f3 * Windows reference network plugins win-bridge and win-overlay do not currently implement [CNI spec](https://github.com/containernetworking/cni/blob/master/SPEC.md) v0.4.0 due to missing \"CHECK\" implementation. * The Flannel VXLAN CNI has the following limitations on Windows: * Windows\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3\u306ewin-bridge\u3068win-overlay\u306f\u3001[CNI\u4ed5\u69d8](https://github.com/containernetworking/cni/blob/master/SPEC.md)v0.4.0\u306b\u304a\u3044\u3066\u300cCHECK\u300d\u5b9f\u88c5\u304c\u306a\u3044\u305f\u3081\u3001\u4eca\u306e\u3068\u3053\u308d\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 * Flannel VXLAN CNI\u306b\u3064\u3044\u3066\u306f\u3001Windows\u3067\u6b21\u306e\u5236\u9650\u304c\u3042\u308a\u307e\u3059\u3002: 1. Node-pod connectivity isn't possible by design. It's only possible for local pods with Flannel [PR 1096](https://github.com/coreos/flannel/pull/1096) 2. We are restricted to using VNI 4096 and UDP port 4789. The VNI limitation is being worked on and will be overcome in a future release (open-source flannel changes). See the official [Flannel VXLAN](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan) backend docs for more details on these parameters. 1. Node-pod\u306e\u76f4\u63a5\u9593\u63a5\u7d9a\u306f\u8a2d\u8a08\u4e0a\u4e0d\u53ef\u80fd\u3067\u3059\u3002Flannel[PR 1096](https://github.com/coreos/flannel/pull/1096)\u3092\u4f7f\u7528\u3059\u308b\u30ed\u30fc\u30ab\u30ebPod\u3067\u306e\u307f\u53ef\u80fd\u3067\u3059 2. VNI 4096\u3068UDP\u30dd\u30fc\u30c84789\u306e\u4f7f\u7528\u306b\u5236\u9650\u3055\u308c\u3066\u3044\u307e\u3059\u3002VNI\u306e\u5236\u9650\u306f\u73fe\u5728\u53d6\u308a\u7d44\u3093\u3067\u304a\u308a\u3001\u5c06\u6765\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u89e3\u6c7a\u3055\u308c\u308b\u4e88\u5b9a\u3067\u3059\uff08\u30aa\u30fc\u30d7\u30f3\u30bd\u30fc\u30b9\u306eflannel\u306e\u5909\u66f4\uff09\u3002\u3053\u308c\u3089\u306e\u30d1\u30e9\u30e1\u30fc\u30bf\u30fc\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001\u516c\u5f0f\u306e[Flannel VXLAN](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)\u30d0\u30c3\u30af\u30a8\u30f3\u30c9\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002 ##### DNS {#dns-limitations} * ClusterFirstWithHostNet is not supported for DNS. Windows treats all names with a '.' as a FQDN and skips PQDN resolution * On Linux, you have a DNS suffix list, which is used when trying to resolve PQDNs. On Windows, we only have 1 DNS suffix, which is the DNS suffix associated with that pod's namespace (mydns.svc.cluster.local for example). Windows can resolve FQDNs and services or names resolvable with just that suffix. For example, a pod spawned in the default namespace, will have the DNS suffix **default.svc.cluster.local**. On a Windows pod, you can resolve both **kubernetes.default.svc.cluster.local** and **kubernetes**, but not the in-betweens, like **kubernetes.default** or **kubernetes.default.svc**. * On Windows, there are multiple DNS resolvers that can be used. As these come with slightly different behaviors, using the `Resolve-DNSName` utility for name query resolutions is recommended. * ClusterFirstWithHostNet\u306f\u3001DNS\u3067\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002Windows\u3067\u306f\u3001FQDN\u3068\u3057\u3066\u3059\u3079\u3066\u306e\u540d\u524d\u3092\u300c.\u300d\u3067\u6271\u3044\u3001PQDN\u3067\u306e\u540d\u524d\u89e3\u6c7a\u306f\u30b9\u30ad\u30c3\u30d7\u3057\u307e\u3059\u3002 * Linux\u3067\u306f\u3001PQDN\u3067\u540d\u524d\u89e3\u6c7a\u3057\u3088\u3046\u3068\u3059\u308b\u3068\u304d\u306b\u4f7f\u7528\u3059\u308bDNS\u30b5\u30d5\u30a3\u30c3\u30af\u30b9\u30ea\u30b9\u30c8\u304c\u3042\u308a\u307e\u3059\u3002Windows\u3067\u306f\u30011\u3064\u306eDNS\u30b5\u30d5\u30a3\u30c3\u30af\u30b9\u3057\u304b\u3042\u308a\u307e\u305b\u3093\u3002\u3053\u308c\u306f\u3001\u305d\u306ePod\u306eNamespace\u306b\u95a2\u9023\u4ed8\u3051\u3089\u308c\u3066\u3044\u308bDNS\u30b5\u30d5\u30a3\u30c3\u30af\u30b9\u3067\u3059\uff08\u305f\u3068\u3048\u3070\u3001mydns.svc.cluster.local\uff09\u3002Windows\u3067\u306f\u3001\u305d\u306e\u30b5\u30d5\u30a3\u30c3\u30af\u30b9\u3060\u3051\u3067\u540d\u524d\u89e3\u6c7a\u53ef\u80fd\u306aFQDN\u304a\u3088\u3073Service\u307e\u305f\u306fName\u3067\u306e\u540d\u524d\u89e3\u6c7a\u304c\u3067\u304d\u307e\u3059\u3002\u305f\u3068\u3048\u3070\u3001default\u306eNamespace\u3067\u751f\u6210\u3055\u308c\u305fPod\u306b\u306f\u3001DNS\u30b5\u30d5\u30a3\u30c3\u30af\u30b9**default.svc.cluster.local**\u304c\u4ed8\u3051\u3089\u308c\u307e\u3059\u3002Windows\u306ePod\u3067\u306f\u3001**kubernetes.default.svc.cluster.local**\u3068**kubernetes**\u306e\u4e21\u65b9\u3092\u540d\u524d\u89e3\u6c7a\u3067\u304d\u307e\u3059\u304c\u3001**kubernetes.default**\u3084**kubernetes.default.svc**\u306e\u3088\u3046\u306a\u4e2d\u9593\u3067\u306e\u540d\u524d\u89e3\u6c7a\u306f\u3067\u304d\u307e\u305b\u3093\u3002 * Windows\u3067\u306f\u3001\u8907\u6570\u306eDNS\u30ea\u30be\u30eb\u30d0\u30fc\u3092\u4f7f\u7528\u3067\u304d\u307e\u3059\u3002\u3053\u308c\u3089\u306b\u306f\u5c11\u3057\u7570\u306a\u308b\u52d5\u4f5c\u304c\u4ed8\u5c5e\u3057\u3066\u3044\u308b\u305f\u3081\u3001\u30cd\u30fc\u30e0\u30af\u30a8\u30ea\u306e\u89e3\u6c7a\u306b\u306f`Resolve-DNSName`\u30e6\u30fc\u30c6\u30a3\u30ea\u30c6\u30a3\u3092\u4f7f\u7528\u3059\u308b\u3053\u3068\u3092\u304a\u52e7\u3081\u3057\u307e\u3059\u3002 ##### Security ##### \u30bb\u30ad\u30e5\u30ea\u30c6\u30a3 Secrets are written in clear text on the node's volume (as compared to tmpfs/in-memory on linux). This means customers have to do two things Secret\u306f\u30ce\u30fc\u30c9\u306e\u30dc\u30ea\u30e5\u30fc\u30e0\u306b\u5e73\u6587\u30c6\u30ad\u30b9\u30c8\u3067\u66f8\u304d\u8fbc\u307e\u308c\u307e\u3059\uff08Linux\u306etmpfs/in-memory\u306e\u6bd4\u8f03\u3068\u3057\u3066\uff09\u3002\u3053\u308c\u306f\u30ab\u30b9\u30bf\u30de\u30fc\u304c2\u3064\u306e\u3053\u3068\u3092\u884c\u3046\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059 1. Use file ACLs to secure the secrets file location 2. Use volume-level encryption using [BitLocker](https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-deploy-on-windows-server) 1. \u30d5\u30a1\u30a4\u30ebACL\u3092\u4f7f\u7528\u3057\u3066Secret\u30d5\u30a1\u30a4\u30eb\u306e\u5834\u6240\u3092\u4fdd\u8b77\u3059\u308b 2. [BitLocker](https://docs.microsoft.com/en-us/windows/security/information-protection/bitlocker/bitlocker-how-to-deploy-on-windows-server)\u3092\u4f7f\u3063\u3066\u3001\u30dc\u30ea\u30e5\u30fc\u30e0\u30ec\u30d9\u30eb\u306e\u6697\u53f7\u5316\u3092\u4f7f\u7528\u3059\u308b [RunAsUser ](/docs/concepts/policy/pod-security-policy/#users-and-groups)is not currently supported on Windows. The workaround is to create local accounts before packaging the container. The RunAsUsername capability may be added in a future release. [RunAsUser](/docs/concepts/policy/pod-security-policy/#users-and-groups)\u306f\u3001\u73fe\u5728Windows\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002\u56de\u907f\u7b56\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u3092\u30d1\u30c3\u30b1\u30fc\u30b8\u5316\u3059\u308b\u524d\u306b\u30ed\u30fc\u30ab\u30eb\u30a2\u30ab\u30a6\u30f3\u30c8\u3092\u4f5c\u6210\u3059\u308b\u3053\u3068\u3067\u3059\u3002RunAsUsername\u6a5f\u80fd\u306f\u3001\u5c06\u6765\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u8ffd\u52a0\u3055\u308c\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002 Linux specific pod security context privileges such as SELinux, AppArmor, Seccomp, Capabilities (POSIX Capabilities), and others are not supported. SELinux\u3001AppArmor\u3001Seccomp\u3001\u7279\u6027\uff08POSIX\u6a5f\u80fd\uff09\u306e\u3088\u3046\u306a\u3001Linux\u56fa\u6709\u306ePod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u74b0\u5883\u306e\u6a29\u9650\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 In addition, as mentioned already, privileged containers are not supported on Windows. \u3055\u3089\u306b\u3001\u65e2\u306b\u8ff0\u3079\u305f\u3088\u3046\u306b\u7279\u6a29\u4ed8\u304d\u30b3\u30f3\u30c6\u30ca\u306f\u3001Windows\u306b\u304a\u3044\u3066\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 #### API There are no differences in how most of the Kubernetes APIs work for Windows. The subtleties around what's different come down to differences in the OS and container runtime. In certain situations, some properties on workload APIs such as Pod or Container were designed with an assumption that they are implemented on Linux, failing to run on Windows. \u307b\u3068\u3093\u3069\u306eKubernetes API\u304cWindows\u3067\u3082\u6a5f\u80fd\u3059\u308b\u3053\u3068\u306b\u9055\u3044\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u305d\u306e\u308f\u305a\u304b\u306a\u9055\u3044\u306fOS\u3068\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u306e\u9055\u3044\u306b\u3088\u308b\u3082\u306e\u3067\u3059\u3002\u7279\u5b9a\u306e\u72b6\u6cc1\u3067\u306f\u3001Pod\u3084\u30b3\u30f3\u30c6\u30ca\u306a\u3069\u306e\u30ef\u30fc\u30af\u30ed\u30fc\u30c9API\u306e\u4e00\u90e8\u306e\u30d7\u30ed\u30d1\u30c6\u30a3\u304c\u3001Linux\u3067\u5b9f\u88c5\u3055\u308c\u3066\u3044\u308b\u304c\u3001Windows\u3067\u306f\u5b9f\u884c\u3067\u304d\u306a\u3044\u3053\u3068\u3092\u524d\u63d0\u306b\u8a2d\u8a08\u3055\u308c\u3066\u3044\u307e\u3059\u3002 At a high level, these OS concepts are different: \u9ad8\u3044\u30ec\u30d9\u30eb\u3067\u3001\u3053\u308c\u3089OS\u306e\u30b3\u30f3\u30bb\u30d7\u30c8\u306b\u9055\u3044\u304c\u308a\u307e\u3059\u3002: * Identity - Linux uses userID (UID) and groupID (GID) which are represented as integer types. User and group names are not canonical - they are just an alias in `/etc/groups` or `/etc/passwd` back to UID+GID. Windows uses a larger binary security identifier (SID) which is stored in the Windows Security Access Manager (SAM) database. This database is not shared between the host and containers, or between containers. * File permissions - Windows uses an access control list based on SIDs, rather than a bitmask of permissions and UID+GID * File paths - convention on Windows is to use `` instead of `/`. The Go IO libraries typically accept both and just make it work, but when you're setting a path or command line that's interpreted inside a container, `` may be needed. * Signals - Windows interactive apps handle termination differently, and can implement one or more of these: * A UI thread handles well-defined messages including WM_CLOSE * Console apps handle ctrl-c or ctrl-break using a Control Handler * Services register a Service Control Handler function that can accept SERVICE_CONTROL_STOP control codes * ID - Linux\u3067\u306f\u3001Integer\u578b\u3068\u3057\u3066\u8868\u3055\u308c\u308buserID\uff08UID\uff09\u3068groupID\uff08GID\uff09\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002\u30e6\u30fc\u30b6\u30fc\u540d\u3068\u30b0\u30eb\u30fc\u30d7\u540d\u306f\u6b63\u898f\u3067\u306f\u3042\u308a\u307e\u305b\u3093 - \u305d\u308c\u3089\u306f\u3001UID+GID\u306e\u80cc\u5f8c\u306b\u3042\u308b`/etc/groups`\u307e\u305f\u306f`/etc/passwd`\u306e\u5358\u306a\u308b\u30a8\u30a4\u30ea\u30a2\u30b9\u3067\u3059\u3002Windows\u306f\u3001Windows Security Access Manager\uff08SAM\uff09\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u306b\u683c\u7d0d\u3055\u308c\u3066\u3044\u308b\u3088\u308a\u5927\u304d\u306a\u30d0\u30a4\u30ca\u30ea\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u8b58\u5225\u5b50\uff08SID\uff09\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002\u3053\u306e\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u306f\u3001\u30db\u30b9\u30c8\u3068\u30b3\u30f3\u30c6\u30ca\u9593\u3001\u307e\u305f\u306f\u30b3\u30f3\u30c6\u30ca\u9593\u3067\u5171\u6709\u3055\u308c\u307e\u305b\u3093\u3002 * \u30d5\u30a1\u30a4\u30eb\u6a29\u9650 - Windows\u306f\u3001\u6a29\u9650\u3068UID+GID\u306e\u30d3\u30c3\u30c8\u30de\u30b9\u30af\u3067\u306f\u306a\u304f\u3001SID\u306b\u57fa\u3065\u304f\u30a2\u30af\u30bb\u30b9\u5236\u5fa1\u30ea\u30b9\u30c8\u3092\u4f7f\u7528\u3057\u307e\u3059 * \u30d5\u30a1\u30a4\u30eb\u30d1\u30b9 - Windows\u306e\u898f\u5247\u3067\u306f\u3001`/`\u3067\u306f\u306a\u304f``\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002Go IO\u30e9\u30a4\u30d6\u30e9\u30ea\u306f\u901a\u5e38\u4e21\u65b9\u3092\u53d7\u3051\u5165\u308c\u3001\u305d\u308c\u3092\u6a5f\u80fd\u3055\u305b\u308b\u3060\u3051\u3067\u3059\u304c\u3001\u30b3\u30f3\u30c6\u30ca\u5185\u3067\u89e3\u91c8\u3055\u308c\u308b\u30d1\u30b9\u307e\u305f\u306f\u30b3\u30de\u30f3\u30c9\u30e9\u30a4\u30f3\u3092\u8a2d\u5b9a\u3059\u308b\u5834\u5408\u3001``\u304c\u5fc5\u8981\u306b\u306a\u308b\u5834\u5408\u304c\u3042\u308a\u307e\u3059\u3002 * \u30b7\u30b0\u30ca\u30eb - Windows\u306e\u30a4\u30f3\u30bf\u30e9\u30af\u30c6\u30a3\u30d6\u306a\u30a2\u30d7\u30ea\u306f\u7d42\u4e86\u3092\u7570\u306a\u308b\u65b9\u6cd5\u3067\u51e6\u7406\u3057\u3001\u6b21\u306e1\u3064\u4ee5\u4e0a\u3092\u5b9f\u88c5\u3067\u304d\u307e\u3059\u3002: * UI\u30b9\u30ec\u30c3\u30c9\u306f\u3001WM_CLOSE\u3092\u542b\u3080\u660e\u78ba\u306b\u5b9a\u7fa9\u3055\u308c\u305f\u30e1\u30c3\u30bb\u30fc\u30b8\u3092\u51e6\u7406\u3057\u307e\u3059 * \u30b3\u30f3\u30bd\u30fc\u30eb\u30a2\u30d7\u30ea\u306f\u3001\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30cf\u30f3\u30c9\u30e9\u30fc\u3092\u4f7f\u7528\u3057\u3066ctrl-c\u307e\u305f\u306fctrl-break\u3092\u51e6\u7406\u3057\u307e\u3059 * \u30b5\u30fc\u30d3\u30b9\u306f\u3001SERVICE_CONTROL_STOP\u5236\u5fa1\u30b3\u30fc\u30c9\u3092\u53d7\u3051\u5165\u308c\u308b\u3053\u3068\u304c\u3067\u304d\u308b\u30b5\u30fc\u30d3\u30b9\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30cf\u30f3\u30c9\u30e9\u30fc\u95a2\u6570\u3092\u767b\u9332\u3057\u307e\u3059\u3002 Exit Codes follow the same convention where 0 is success, nonzero is failure. The specific error codes may differ across Windows and Linux. However, exit codes passed from the Kubernetes components (kubelet, kube-proxy) are unchanged. \u7d42\u4e86\u30b3\u30fc\u30c9\u306f\u30010\u304c\u6210\u529f\u30010\u4ee5\u5916\u304c\u5931\u6557\u306e\u5834\u5408\u3068\u540c\u3058\u898f\u5247\u306b\u5f93\u3044\u307e\u3059\u3002\u7279\u5b9a\u306e\u30a8\u30e9\u30fc\u30b3\u30fc\u30c9\u306f\u3001Windows\u3068Linux\u3067\u7570\u306a\u308b\u5834\u5408\u304c\u3042\u308a\u307e\u3059\u3002\u305f\u3060\u3057\u3001Kubernetes\u306e\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\uff08kubelet\u3001kube-proxy\uff09\u304b\u3089\u6e21\u3055\u308c\u308b\u7d42\u4e86\u30b3\u30fc\u30c9\u306f\u5909\u66f4\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 ##### V1.Container * V1.Container.ResourceRequirements.limits.cpu and V1.Container.ResourceRequirements.limits.memory - Windows doesn't use hard limits for CPU allocations. Instead, a share system is used. The existing fields based on millicores are scaled into relative shares that are followed by the Windows scheduler. [see: kuberuntime/helpers_windows.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/helpers_windows.go), [see: resource controls in Microsoft docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/resource-controls) * Huge pages are not implemented in the Windows container runtime, and are not available. They require [asserting a user privilege](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support) that's not configurable for containers. * V1.Container.ResourceRequirements.requests.cpu and V1.Container.ResourceRequirements.requests.memory - Requests are subtracted from node available resources, so they can be used to avoid overprovisioning a node. However, they cannot be used to guarantee resources in an overprovisioned node. They should be applied to all containers as a best practice if the operator wants to avoid overprovisioning entirely. * V1.Container.SecurityContext.allowPrivilegeEscalation - not possible on Windows, none of the capabilities are hooked up * V1.Container.SecurityContext.Capabilities - POSIX capabilities are not implemented on Windows * V1.Container.SecurityContext.privileged - Windows doesn't support privileged containers * V1.Container.SecurityContext.procMount - Windows doesn't have a /proc filesystem * V1.Container.SecurityContext.readOnlyRootFilesystem - not possible on Windows, write access is required for registry & system processes to run inside the container * V1.Container.SecurityContext.runAsGroup - not possible on Windows, no GID support * V1.Container.SecurityContext.runAsNonRoot - Windows does not have a root user. The closest equivalent is ContainerAdministrator which is an identity that doesn't exist on the node. * V1.Container.SecurityContext.runAsUser - not possible on Windows, no UID support as int. * V1.Container.SecurityContext.seLinuxOptions - not possible on Windows, no SELinux * V1.Container.terminationMessagePath - this has some limitations in that Windows doesn't support mapping single files. The default value is /dev/termination-log, which does work because it does not exist on Windows by default. * V1.Container.ResourceRequirements.limits.cpu\u304a\u3088\u3073V1.Container.ResourceRequirements.limits.memory - Windows\u306f\u3001CPU\u5272\u308a\u5f53\u3066\u306b\u30cf\u30fc\u30c9\u5236\u9650\u3092\u4f7f\u7528\u3057\u307e\u305b\u3093\u3002\u4ee3\u308f\u308a\u306b\u3001\u5171\u6709\u30b7\u30b9\u30c6\u30e0\u304c\u4f7f\u7528\u3055\u308c\u307e\u3059\u3002\u30df\u30ea\u30b3\u30a2\u306b\u57fa\u3065\u304f\u65e2\u5b58\u306e\u30d5\u30a3\u30fc\u30eb\u30c9\u306f\u3001Windows\u30b9\u30b1\u30b8\u30e5\u30fc\u30e9\u30fc\u306b\u3088\u3063\u3066\u8ffd\u5f93\u3055\u308c\u308b\u76f8\u5bfe\u5171\u6709\u306b\u30b9\u30b1\u30fc\u30ea\u30f3\u30b0\u3055\u308c\u307e\u3059\u3002[\u53c2\u7167: kuberuntime/helpers_windows.go](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kuberuntime/helpers_windows.go)\u3001[\u53c2\u7167: resource controls in Microsoft docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/resource-controls) * Huge Pages\u306f\u3001Windows\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u306b\u306f\u5b9f\u88c5\u3055\u308c\u3066\u306a\u3044\u306e\u3067\u3001\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3002\u30b3\u30f3\u30c6\u30ca\u306b\u5bfe\u3057\u3066\u8a2d\u5b9a\u3067\u304d\u306a\u3044[\u30e6\u30fc\u30b6\u30fc\u7279\u6a29\u3092\u4e3b\u5f35](https://docs.microsoft.com/en-us/windows/desktop/Memory/large-page-support)\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 * V1.Container.ResourceRequirements.requests.cpu\u304a\u3088\u3073V1.Container.ResourceRequirements.requests.memory - \u30ea\u30af\u30a8\u30b9\u30c8\u306f\u30ce\u30fc\u30c9\u306e\u5229\u7528\u53ef\u80fd\u306a\u30ea\u30bd\u30fc\u30b9\u304b\u3089\u5dee\u3057\u5f15\u304b\u308c\u308b\u306e\u3067\u3001\u30ce\u30fc\u30c9\u306e\u30aa\u30fc\u30d0\u30fc\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3092\u56de\u907f\u3059\u308b\u305f\u3081\u306b\u4f7f\u7528\u3067\u304d\u307e\u3059\u3002\u305f\u3060\u3057\u3001\u904e\u5270\u306b\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3055\u308c\u305f\u30ce\u30fc\u30c9\u306e\u30ea\u30bd\u30fc\u30b9\u3092\u4fdd\u8a3c\u3059\u308b\u305f\u3081\u306b\u4f7f\u7528\u3059\u308b\u3053\u3068\u306f\u3067\u304d\u307e\u305b\u3093\u3002\u30aa\u30da\u30ec\u30fc\u30bf\u30fc\u304c\u5b8c\u5168\u306b\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3057\u904e\u304e\u306a\u3044\u3088\u3046\u306b\u3059\u308b\u5834\u5408\u306f\u3001\u30d9\u30b9\u30c8\u30d7\u30e9\u30af\u30c6\u30a3\u30b9\u3068\u3057\u3066\u3053\u308c\u3089\u3092\u3059\u3079\u3066\u306e\u30b3\u30f3\u30c6\u30ca\u306b\u9069\u7528\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 * V1.Container.SecurityContext.allowPrivilegeEscalation - Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3001\u63a5\u7d9a\u3055\u308c\u3066\u3044\u308b\u6a5f\u80fd\u306f\u3042\u308a\u307e\u305b\u3093 * V1.Container.SecurityContext.Capabilities - POSIX\u6a5f\u80fd\u306fWindows\u3067\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093 * V1.Container.SecurityContext.privileged - Windows\u3067\u306f\u7279\u6a29\u30b3\u30f3\u30c6\u30ca\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u305b\u3093 * V1.Container.SecurityContext.procMount - Windows\u3067\u306f/proc\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u304c\u3042\u308a\u307e\u305b\u3093 * V1.Container.SecurityContext.readOnlyRootFilesystem - Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3001\u30ec\u30b8\u30b9\u30c8\u30ea\u304a\u3088\u3073\u30b7\u30b9\u30c6\u30e0\u30d7\u30ed\u30bb\u30b9\u304c\u30b3\u30f3\u30c6\u30ca\u5185\u3067\u5b9f\u884c\u3059\u308b\u306b\u306f\u3001\u66f8\u304d\u8fbc\u307f\u30a2\u30af\u30bb\u30b9\u304c\u5fc5\u8981\u3067\u3059 * V1.Container.SecurityContext.runAsGroup - Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3001GID\u306e\u30b5\u30dd\u30fc\u30c8\u3082\u3042\u308a\u307e\u305b\u3093 * V1.Container.SecurityContext.runAsNonRoot - Windows\u3067\u306froot\u30e6\u30fc\u30b6\u30fc\u304c\u5b58\u5728\u3057\u307e\u305b\u3093\u3002\u6700\u3082\u8fd1\u3044\u3082\u306e\u306f\u3001\u30ce\u30fc\u30c9\u306b\u5b58\u5728\u3057\u306a\u3044ID\u3067\u3042\u308bContainerAdministrator\u3067\u3059\u3002 * V1.Container.SecurityContext.runAsUser - Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3002int\u3068\u3057\u3066\u306eUID\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 * V1.Container.SecurityContext.seLinuxOptions - Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093\u3001SELinux\u304c\u3042\u308a\u307e\u305b\u3093 * V1.Container.terminationMessagePath - \u3053\u308c\u306f\u3001Windows\u304c\u5358\u4e00\u30d5\u30a1\u30a4\u30eb\u306e\u30de\u30c3\u30d4\u30f3\u30b0\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u306a\u3044\u3068\u3044\u3046\u70b9\u3067\u3044\u304f\u3064\u304b\u306e\u5236\u9650\u304c\u3042\u308a\u307e\u3059\u3002\u30c7\u30d5\u30a9\u30eb\u30c8\u5024\u306f/dev/termination-log\u3067\u3042\u308a\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u306fWindows\u306b\u5b58\u5728\u3057\u306a\u3044\u305f\u3081\u52d5\u4f5c\u3057\u307e\u3059\u3002 ##### V1.Pod * V1.Pod.hostIPC, v1.pod.hostpid - host namespace sharing is not possible on Windows * V1.Pod.hostNetwork - There is no Windows OS support to share the host network * V1.Pod.dnsPolicy - ClusterFirstWithHostNet - is not supported because Host Networking is not supported on Windows. * V1.Pod.podSecurityContext - see V1.PodSecurityContext below * V1.Pod.shareProcessNamespace - this is a beta feature, and depends on Linux namespaces which are not implemented on Windows. Windows cannot share process namespaces or the container's root filesystem. Only the network can be shared. * V1.Pod.terminationGracePeriodSeconds - this is not fully implemented in Docker on Windows, see: [reference](https://github.com/moby/moby/issues/25982). The behavior today is that the ENTRYPOINT process is sent CTRL_SHUTDOWN_EVENT, then Windows waits 5 seconds by default, and finally shuts down all processes using the normal Windows shutdown behavior. The 5 second default is actually in the Windows registry [inside the container](https://github.com/moby/moby/issues/25982#issuecomment-426441183), so it can be overridden when the container is built. * V1.Pod.volumeDevices - this is a beta feature, and is not implemented on Windows. Windows cannot attach raw block devices to pods. * V1.Pod.volumes - EmptyDir, Secret, ConfigMap, HostPath - all work and have tests in TestGrid * V1.emptyDirVolumeSource - the Node default medium is disk on Windows. Memory is not supported, as Windows does not have a built-in RAM disk. * V1.VolumeMount.mountPropagation - mount propagation is not supported on Windows. * V1.Pod.hostIPC\u3001v1.pod.hostpid - Windows\u3067\u306f\u30db\u30b9\u30c8\u306e\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u3092\u5171\u6709\u3059\u308b\u3053\u3068\u306f\u3067\u304d\u307e\u305b\u3093 * V1.Pod.hostNetwork - \u30db\u30b9\u30c8\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u5171\u6709\u3059\u308b\u305f\u3081\u306eWindows OS\u30b5\u30dd\u30fc\u30c8\u306f\u3042\u308a\u307e\u305b\u3093 * V1.Pod.dnsPolicy - ClusterFirstWithHostNet - Windows\u3067\u306f\u30db\u30b9\u30c8\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u304c\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u306a\u3044\u305f\u3081\u3001\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 * V1.Pod.podSecurityContext - \u4ee5\u4e0b\u306eV1.PodSecurityContext\u3092\u53c2\u7167 * V1.Pod.shareProcessNamespace - \u3053\u308c\u306f\u30d9\u30fc\u30bf\u7248\u306e\u6a5f\u80fd\u3067\u3042\u308a\u3001Windows\u306b\u5b9f\u88c5\u3055\u308c\u3066\u3044\u306a\u3044Linux\u306eNamespace\u6a5f\u80fd\u306b\u4f9d\u5b58\u3057\u3066\u3044\u307e\u3059\u3002Windows\u3067\u306f\u3001\u30d7\u30ed\u30bb\u30b9\u306e\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u307e\u305f\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u30eb\u30fc\u30c8\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u3092\u5171\u6709\u3067\u304d\u307e\u305b\u3093\u3002\u5171\u6709\u3067\u304d\u308b\u306e\u306f\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3060\u3051\u3067\u3059\u3002 * V1.Pod.terminationGracePeriodSeconds - \u3053\u308c\u306fWindows\u306eDocker\u306b\u5b8c\u5168\u306b\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002[\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9](https://github.com/moby/moby/issues/25982)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002\u4eca\u65e5\u306e\u52d5\u4f5c\u3067\u306f\u3001ENTRYPOINT\u30d7\u30ed\u30bb\u30b9\u306bCTRL_SHUTDOWN_EVENT\u304c\u9001\u4fe1\u3055\u308c\u3001Windows\u3067\u306f\u30c7\u30d5\u30a9\u30eb\u30c8\u30675\u79d2\u5f85\u6a5f\u3057\u3001\u6700\u5f8c\u306b\u901a\u5e38\u306eWindows\u30b7\u30e3\u30c3\u30c8\u30c0\u30a6\u30f3\u52d5\u4f5c\u3092\u4f7f\u7528\u3057\u3066\u3059\u3079\u3066\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u30b7\u30e3\u30c3\u30c8\u30c0\u30a6\u30f3\u3057\u307e\u3059\u30025\u79d2\u306e\u30c7\u30d5\u30a9\u30eb\u30c8\u306f\u3001\u5b9f\u969b\u306b\u306fWindows\u30ec\u30b8\u30b9\u30c8\u30ea\u30fc[\u30b3\u30f3\u30c6\u30ca\u5185](https://github.com/moby/moby/issues/25982#issuecomment-426441183)\u306b\u3042\u308b\u305f\u3081\u3001\u30b3\u30f3\u30c6\u30ca\u4f5c\u6210\u6642\u306b\u30aa\u30fc\u30d0\u30fc\u30e9\u30a4\u30c9\u3067\u304d\u307e\u3059\u3002 * V1.Pod.volumeDevices - \u3053\u308c\u306f\u30d9\u30fc\u30bf\u6a5f\u80fd\u3067\u3042\u308a\u3001Windows\u306b\u306f\u5b9f\u88c5\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002Windows\u3067\u306f\u3001raw\u30d6\u30ed\u30c3\u30af\u30c7\u30d0\u30a4\u30b9\u3092Pod\u306b\u63a5\u7d9a\u3067\u304d\u307e\u305b\u3093\u3002 * V1.Pod.volumes-EmptyDir\u3001Secret\u3001ConfigMap\u3001HostPath - \u3059\u3079\u3066\u52d5\u4f5c\u3057\u3001TestGrid\u306b\u30c6\u30b9\u30c8\u304c\u3042\u308a\u307e\u3059 * V1.emptyDirVolumeSource - \u30ce\u30fc\u30c9\u306e\u30c7\u30d5\u30a9\u30eb\u30c8\u306e\u30e1\u30c7\u30a3\u30a2\u306fWindows\u306e\u30c7\u30a3\u30b9\u30af\u3067\u3059\u3002Windows\u3067\u306f\u3001RAM\u30c7\u30a3\u30b9\u30af\u304c\u7d44\u307f\u8fbc\u307e\u308c\u3066\u3044\u306a\u3044\u305f\u3081\u3001\u30e1\u30e2\u30ea\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 * V1.VolumeMount.mountPropagation - mount propagation\u306f\u3001Windows\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 ##### V1.PodSecurityContext None of the PodSecurityContext fields work on Windows. They're listed here for reference. Windows\u3067\u306f\u3001PodSecurityContext\u30d5\u30a3\u30fc\u30eb\u30c9\u306f\u3069\u308c\u3082\u6a5f\u80fd\u3057\u307e\u305b\u3093\u3002\u3053\u308c\u3089\u306f\u53c2\u7167\u7528\u306b\u3053\u3053\u306b\u30ea\u30b9\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002 * V1.PodSecurityContext.SELinuxOptions - SELinux is not available on Windows * V1.PodSecurityContext.RunAsUser - provides a UID, not available on Windows * V1.PodSecurityContext.RunAsGroup - provides a GID, not available on Windows * V1.PodSecurityContext.RunAsNonRoot - Windows does not have a root user. The closest equivalent is ContainerAdministrator which is an identity that doesn't exist on the node. * V1.PodSecurityContext.SupplementalGroups - provides GID, not available on Windows * V1.PodSecurityContext.Sysctls - these are part of the Linux sysctl interface. There's no equivalent on Windows. * V1.PodSecurityContext.SELinuxOptions - SELinux\u306f\u3001Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093 * V1.PodSecurityContext.RunAsUser - UID\u3092\u63d0\u4f9b\u3057\u307e\u3059\u304c\u3001Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093 * V1.PodSecurityContext.RunAsGroup - GID\u3092\u63d0\u4f9b\u3057\u307e\u3059\u304c\u3001Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093 * V1.PodSecurityContext.RunAsNonRoot - Windows\u306b\u306froot\u30e6\u30fc\u30b6\u30fc\u304c\u3042\u308a\u307e\u305b\u3093\u3002\u6700\u3082\u8fd1\u3044\u3082\u306e\u306f\u3001\u30ce\u30fc\u30c9\u306b\u5b58\u5728\u3057\u306a\u3044ID\u3067\u3042\u308bContainerAdministrator\u3067\u3059\u3002 * V1.PodSecurityContext.SupplementalGroups - GID\u3092\u63d0\u4f9b\u3057\u307e\u3059\u304c\u3001Windows\u3067\u306f\u4f7f\u7528\u3067\u304d\u307e\u305b\u3093 * V1.PodSecurityContext.Sysctls - \u3053\u308c\u3089\u306fLinux\u306esysctl\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30fc\u30b9\u306e\u4e00\u90e8\u3067\u3059\u3002Windows\u306b\u306f\u540c\u7b49\u306e\u3082\u306e\u306f\u3042\u308a\u307e\u305b\u3093\u3002 ## Getting Help and Troubleshooting {#troubleshooting} ## \u30d8\u30eb\u30d7\u3068\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u3092\u5b66\u3076 {#troubleshooting} Your main source of help for troubleshooting your Kubernetes cluster should start with this [section](/docs/tasks/debug-application-cluster/troubleshooting/). Some additional, Windows-specific troubleshooting help is included in this section. Logs are an important element of troubleshooting issues in Kubernetes. Make sure to include them any time you seek troubleshooting assistance from other contributors. Follow the instructions in the SIG-Windows [contributing guide on gathering logs](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs). Kubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u306e\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u306e\u4e3b\u306a\u30d8\u30eb\u30d7\u30bd\u30fc\u30b9\u306f\u3001\u3053\u306e[\u30bb\u30af\u30b7\u30e7\u30f3](/docs/tasks/debug-application-cluster/troubleshooting/)\u304b\u3089\u59cb\u3081\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u3053\u306e\u30bb\u30af\u30b7\u30e7\u30f3\u306b\u306f\u3001\u3044\u304f\u3064\u304b\u8ffd\u52a0\u7684\u306a\u3001Windows\u56fa\u6709\u306e\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u30d8\u30eb\u30d7\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002\u30ed\u30b0\u306f\u3001Kubernetes\u306b\u304a\u3051\u308b\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u554f\u984c\u306e\u91cd\u8981\u306a\u8981\u7d20\u3067\u3059\u3002\u4ed6\u306e\u30b3\u30f3\u30c8\u30ea\u30d3\u30e5\u30fc\u30bf\u30fc\u304b\u3089\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u306e\u652f\u63f4\u3092\u6c42\u3081\u308b\u3068\u304d\u306f\u3001\u5fc5\u305a\u305d\u308c\u3089\u3092\u542b\u3081\u3066\u304f\u3060\u3055\u3044\u3002SIG-Windows[\u30ed\u30b0\u53ce\u96c6\u306b\u95a2\u3059\u308b\u30b3\u30f3\u30c8\u30ea\u30d3\u30e5\u30fc\u30c8\u30ac\u30a4\u30c9](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs)\u306e\u6307\u793a\u306b\u5f93\u3063\u3066\u304f\u3060\u3055\u3044\u3002 1. How do I know start.ps1 completed successfully? 1. start.ps1\u304c\u6b63\u5e38\u306b\u5b8c\u4e86\u3057\u305f\u3053\u3068\u3092\u3069\u306e\u3088\u3046\u306b\u78ba\u8a8d\u3067\u304d\u307e\u3059\u304b\uff1f You should see kubelet, kube-proxy, and (if you chose Flannel as your networking solution) flanneld host-agent processes running on your node, with running logs being displayed in separate PowerShell windows. In addition to this, your Windows node should be listed as \"Ready\" in your Kubernetes cluster. \u30ce\u30fc\u30c9\u4e0a\u3067kubelet\u3001kube-proxy\u3001\u304a\u3088\u3073\uff08\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3068\u3057\u3066Flannel\u3092\u9078\u629e\u3057\u305f\u5834\u5408\uff09flanneld\u30db\u30b9\u30c8\u30a8\u30fc\u30b8\u30a7\u30f3\u30c8\u30d7\u30ed\u30bb\u30b9\u304c\u5b9f\u884c\u3055\u308c\u3001\u5b9f\u884c\u30ed\u30b0\u304c\u500b\u5225\u306ePowerShell\u30a6\u30a3\u30f3\u30c9\u30a6\u306b\u8868\u793a\u3055\u308c\u307e\u3059\u3002\u3053\u308c\u306b\u52a0\u3048\u3066\u3001Windows\u30ce\u30fc\u30c9\u304cKubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u3067\u300cReady\u300d\u3068\u3057\u3066\u8868\u793a\u3055\u308c\u3066\u3044\u308b\u306f\u305a\u3067\u3059\u3002 1. Can I configure the Kubernetes node processes to run in the background as services? 1. Kubernetes\u30ce\u30fc\u30c9\u306e\u30d7\u30ed\u30bb\u30b9\u3092\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066\u30d0\u30c3\u30af\u30b0\u30e9\u30a6\u30f3\u30c9\u3067\u5b9f\u884c\u3059\u308b\u3088\u3046\u306b\u69cb\u6210\u3067\u304d\u307e\u3059\u304b\uff1f Kubelet and kube-proxy are already configured to run as native Windows Services, offering resiliency by re-starting the services automatically in the event of failure (for example a process crash). You have two options for configuring these node components as services. Kubelet\u3068kube-proxy\u306f\u3001\u30cd\u30a4\u30c6\u30a3\u30d6\u306eWindows\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066\u5b9f\u884c\u3059\u308b\u3088\u3046\u306b\u65e2\u306b\u69cb\u6210\u3055\u308c\u3066\u3044\u307e\u3059\u3001\u969c\u5bb3\uff08\u4f8b\u3048\u3070\u3001\u30d7\u30ed\u30bb\u30b9\u306e\u30af\u30e9\u30c3\u30b7\u30e5\uff09\u304c\u767a\u751f\u3057\u305f\u5834\u5408\u306b\u30b5\u30fc\u30d3\u30b9\u3092\u81ea\u52d5\u7684\u306b\u518d\u8d77\u52d5\u3059\u308b\u3053\u3068\u306b\u3088\u308a\u3001\u5fa9\u5143\u6027\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u30ce\u30fc\u30c9\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u3092\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066\u69cb\u6210\u3059\u308b\u306b\u306f\u30012\u3064\u306e\u30aa\u30d7\u30b7\u30e7\u30f3\u304c\u3042\u308a\u307e\u3059\u3002 1. As native Windows Services 1. \u30cd\u30a4\u30c6\u30a3\u30d6Windows\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066 Kubelet & kube-proxy can be run as native Windows Services using `sc.exe`. Kubelet\u3068kube-proxy\u306f\u3001`sc.exe`\u3092\u4f7f\u7528\u3057\u3066\u30cd\u30a4\u30c6\u30a3\u30d6\u306eWindows\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066\u5b9f\u884c\u3067\u304d\u307e\u3059\u3002 ```powershell # Create the services for kubelet and kube-proxy in two separate commands # 2\u3064\u306e\u500b\u5225\u306e\u30b3\u30de\u30f3\u30c9\u3067kubelet\u304a\u3088\u3073kube-proxy\u306e\u30b5\u30fc\u30d3\u30b9\u3092\u4f5c\u6210\u3059\u308b sc.exe create binPath= \" --service \" # Please note that if the arguments contain spaces, they must be escaped. # \u5f15\u6570\u306b\u30b9\u30da\u30fc\u30b9\u304c\u542b\u307e\u308c\u3066\u3044\u308b\u5834\u5408\u306f\u3001\u30a8\u30b9\u30b1\u30fc\u30d7\u3059\u308b\u5fc5\u8981\u304c\u3042\u308b\u3053\u3068\u306b\u6ce8\u610f\u3057\u3066\u304f\u3060\u3055\u3044\u3002 sc.exe create kubelet binPath= \"C:kubelet.exe --service --hostname-override 'minion' \" # Start the services # \u30b5\u30fc\u30d3\u30b9\u3092\u958b\u59cb\u3059\u308b Start-Service kubelet Start-Service kube-proxy # Stop the service # \u30b5\u30fc\u30d3\u30b9\u3092\u505c\u6b62\u3059\u308b Stop-Service kubelet (-Force) Stop-Service kube-proxy (-Force) # Query the service status # \u30b5\u30fc\u30d3\u30b9\u306e\u72b6\u614b\u3092\u554f\u3044\u5408\u308f\u305b\u308b Get-Service kubelet Get-Service kube-proxy ``` 1. Using nssm.exe 1. nssm.exe\u306e\u4f7f\u7528 You can also always use alternative service managers like [nssm.exe](https://nssm.cc/) to run these processes (flanneld, kubelet & kube-proxy) in the background for you. You can use this [sample script](https://github.com/Microsoft/SDN/tree/master/Kubernetes/flannel/register-svc.ps1), leveraging nssm.exe to register kubelet, kube-proxy, and flanneld.exe to run as Windows services in the background. \u307e\u305f\u3001[nssm.exe](https://nssm.cc/)\u306a\u3069\u306e\u4ee3\u66ff\u30b5\u30fc\u30d3\u30b9\u30de\u30cd\u30fc\u30b8\u30e3\u30fc\u3092\u4f7f\u7528\u3057\u3066\u3001\u3053\u308c\u3089\u306e\u30d7\u30ed\u30bb\u30b9\uff08flanneld\u3001kubelet\u3001kube-proxy\uff09\u3092\u30d0\u30c3\u30af\u30b0\u30e9\u30a6\u30f3\u30c9\u3067\u5b9f\u884c\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002\u3053\u306e[\u30b5\u30f3\u30d7\u30eb\u30b9\u30af\u30ea\u30d7\u30c8](https://github.com/Microsoft/SDN/tree/master/Kubernetes/flannel/register-svc.ps1)\u3092\u4f7f\u7528\u3059\u308b\u3068\u3001nssm.exe\u3092\u5229\u7528\u3057\u3066kubelet\u3001kube-proxy\u3001flanneld.exe\u3092\u767b\u9332\u3057\u3001Windows\u30b5\u30fc\u30d3\u30b9\u3068\u3057\u3066\u30d0\u30c3\u30af\u30b0\u30e9\u30a6\u30f3\u30c9\u3067\u5b9f\u884c\u3067\u304d\u307e\u3059\u3002 ```powershell register-svc.ps1 -NetworkMode -ManagementIP -ClusterCIDR -KubeDnsServiceIP -LogDir # NetworkMode = The network mode l2bridge (flannel host-gw, also the default value) or overlay (flannel vxlan) chosen as a network solution # ManagementIP = The IP address assigned to the Windows node. You can use ipconfig to find this # ClusterCIDR = The cluster subnet range. (Default value 10.244.0.0/16) # KubeDnsServiceIP = The Kubernetes DNS service IP (Default value 10.96.0.10) # LogDir = The directory where kubelet and kube-proxy logs are redirected into their respective output files (Default value C:k) # NetworkMode = \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3068\u3057\u3066\u9078\u629e\u3055\u308c\u305f\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30e2\u30fc\u30c9l2bridge\uff08flannel host-gw\u3001\u3053\u308c\u3082\u30c7\u30d5\u30a9\u30eb\u30c8\u5024\uff09\u307e\u305f\u306foverlay\uff08flannel vxlan\uff09 # ManagementIP = Windows\u30ce\u30fc\u30c9\u306b\u5272\u308a\u5f53\u3066\u3089\u308c\u305fIP\u30a2\u30c9\u30ec\u30b9\u3002 ipconfig\u3092\u4f7f\u7528\u3057\u3066\u3053\u308c\u3092\u898b\u3064\u3051\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059 # ClusterCIDR = \u30af\u30e9\u30b9\u30bf\u30fc\u306e\u30b5\u30d6\u30cd\u30c3\u30c8\u7bc4\u56f2\u3002\uff08\u30c7\u30d5\u30a9\u30eb\u30c8\u5024 10.244.0.0/16\uff09 # KubeDnsServiceIP = Kubernetes DNS\u30b5\u30fc\u30d3\u30b9IP\uff08\u30c7\u30d5\u30a9\u30eb\u30c8\u5024 10.96.0.10\uff09 # LogDir = kubelet\u304a\u3088\u3073kube-proxy\u30ed\u30b0\u304c\u305d\u308c\u305e\u308c\u306e\u51fa\u529b\u30d5\u30a1\u30a4\u30eb\u306b\u30ea\u30c0\u30a4\u30ec\u30af\u30c8\u3055\u308c\u308b\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\uff08\u30c7\u30d5\u30a9\u30eb\u30c8\u5024 C:k\uff09 ``` If the above referenced script is not suitable, you can manually configure nssm.exe using the following examples. \u4e0a\u8a18\u306e\u30b9\u30af\u30ea\u30d7\u30c8\u304c\u9069\u5207\u3067\u306a\u3044\u5834\u5408\u306f\u3001\u6b21\u306e\u4f8b\u3092\u4f7f\u7528\u3057\u3066nssm.exe\u3092\u624b\u52d5\u3067\u69cb\u6210\u3067\u304d\u307e\u3059\u3002 ```powershell # Register flanneld.exe # flanneld.exe\u3092\u767b\u9332\u3059\u308b nssm install flanneld C:flannelflanneld.exe nssm set flanneld AppParameters --kubeconfig-file=c:kconfig --iface= --ip-masq=1 --kube-subnet-mgr=1 nssm set flanneld AppEnvironmentExtra NODE_NAME= nssm set flanneld AppDirectory C:flannel nssm start flanneld # Register kubelet.exe # Microsoft releases the pause infrastructure container at mcr.microsoft.com/k8s/core/pause:1.2.0 # For more info search for \"pause\" in the \"Guide for adding Windows Nodes in Kubernetes\" # kubelet.exe\u3092\u767b\u9332 # \u30de\u30a4\u30af\u30ed\u30bd\u30d5\u30c8\u306f\u3001mcr.microsoft.com/k8s/core/pause:1.2.0\u3068\u3057\u3066\u30dd\u30fc\u30ba\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u30b3\u30f3\u30c6\u30ca\u3092\u30ea\u30ea\u30fc\u30b9 # \u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001\u300cKubernetes\u306bWindows\u30ce\u30fc\u30c9\u3092\u8ffd\u52a0\u3059\u308b\u305f\u3081\u306e\u30ac\u30a4\u30c9\u300d\u3067\u300cpause\u300d\u3092\u691c\u7d22\u3057\u3066\u304f\u3060\u3055\u3044 nssm install kubelet C:kkubelet.exe nssm set kubelet AppParameters --hostname-override= --v=6 --pod-infra-container-image=mcr.microsoft.com/k8s/core/pause:1.2.0 --resolv-conf=\"\" --allow-privileged=true --enable-debugging-handlers --cluster-dns= --cluster-domain=cluster.local --kubeconfig=c:kconfig --hairpin-mode=promiscuous-bridge --image-pull-progress-deadline=20m --cgroups-per-qos=false --log-dir= --logtostderr=false --enforce-node-allocatable=\"\" --network-plugin=cni --cni-bin-dir=c:kcni --cni-conf-dir=c:kcniconfig nssm set kubelet AppDirectory C:k nssm start kubelet # Register kube-proxy.exe (l2bridge / host-gw) # kube-proxy.exe\u3092\u767b\u9332\u3059\u308b (l2bridge / host-gw) nssm install kube-proxy C:kkube-proxy.exe nssm set kube-proxy AppDirectory c:k nssm set kube-proxy AppParameters --v=4 --proxy-mode=kernelspace --hostname-override=--kubeconfig=c:kconfig --enable-dsr=false --log-dir= --logtostderr=false", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. # Register kube-proxy.exe (overlay / vxlan) # kube-proxy.exe\u3092\u767b\u9332\u3059\u308b (overlay / vxlan) nssm install kube-proxy C:kkube-proxy.exe nssm set kube-proxy AppDirectory c:k nssm set kube-proxy AppParameters --v=4 --proxy-mode=kernelspace --feature-gates=\"WinOverlay=true\" --hostname-override= --kubeconfig=c:kconfig --network-name=vxlan0 --source-vip= --enable-dsr=false --log-dir= --logtostderr=false", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. For initial troubleshooting, you can use the following flags in [nssm.exe](https://nssm.cc/) to redirect stdout and stderr to a output file: \u6700\u521d\u306e\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u3067\u306f\u3001[nssm.exe](https://nssm.cc/)\u3067\u6b21\u306e\u30d5\u30e9\u30b0\u3092\u4f7f\u7528\u3057\u3066\u3001stdout\u304a\u3088\u3073stderr\u3092\u51fa\u529b\u30d5\u30a1\u30a4\u30eb\u306b\u30ea\u30c0\u30a4\u30ec\u30af\u30c8\u3067\u304d\u307e\u3059\u3002: ```powershell nssm set AppStdout C:kmysvc.log nssm set AppStderr C:kmysvc.log ``` For additional details, see official [nssm usage](https://nssm.cc/usage) docs. \u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001\u516c\u5f0f\u306e[nssm\u306e\u4f7f\u7528\u6cd5](https://nssm.cc/usage)\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 1. My Windows Pods do not have network connectivity 1. Windows Pod\u306b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u63a5\u7d9a\u304c\u3042\u308a\u307e\u305b\u3093 If you are using virtual machines, ensure that MAC spoofing is enabled on all the VM network adapter(s). \u4eee\u60f3\u30de\u30b7\u30f3\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306f\u3001\u3059\u3079\u3066\u306eVM\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a2\u30c0\u30d7\u30bf\u30fc\u3067MAC\u30b9\u30d7\u30fc\u30d5\u30a3\u30f3\u30b0\u304c\u6709\u52b9\u306b\u306a\u3063\u3066\u3044\u308b\u3053\u3068\u3092\u78ba\u8a8d\u3057\u3066\u304f\u3060\u3055\u3044\u3002 1. My Windows Pods cannot ping external resources 1. Windows Pod\u304c\u5916\u90e8\u30ea\u30bd\u30fc\u30b9\u306bping\u3067\u304d\u307e\u305b\u3093 Windows Pods do not have outbound rules programmed for the ICMP protocol today. However, TCP/UDP is supported. When trying to demonstrate connectivity to resources outside of the cluster, please substitute `ping ` with corresponding `curl ` commands. \u73fe\u5728\u3001Windows Pod\u306b\u306f\u3001ICMP\u30d7\u30ed\u30c8\u30b3\u30eb\u7528\u306b\u30d7\u30ed\u30b0\u30e9\u30e0\u3055\u308c\u305f\u9001\u4fe1\u30eb\u30fc\u30eb\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u305f\u3060\u3057\u3001TCP/UDP\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u30af\u30e9\u30b9\u30bf\u30fc\u5916\u306e\u30ea\u30bd\u30fc\u30b9\u3078\u306e\u63a5\u7d9a\u3092\u5b9f\u8a3c\u3059\u308b\u5834\u5408\u306f\u3001`ping `\u306b\u5bfe\u5fdc\u3059\u308b`curl `\u30b3\u30de\u30f3\u30c9\u306b\u7f6e\u304d\u63db\u3048\u3066\u304f\u3060\u3055\u3044\u3002 If you are still facing problems, most likely your network configuration in [cni.conf](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf) deserves some extra attention. You can always edit this static file. The configuration update will apply to any newly created Kubernetes resources. \u305d\u308c\u3067\u3082\u554f\u984c\u304c\u89e3\u6c7a\u3057\u306a\u3044\u5834\u5408\u306f\u3001[cni.conf](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf)\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u69cb\u6210\u306b\u5024\u3059\u308b\u53ef\u80fd\u6027\u304c\u3042\u308b\u306e\u3067\u3001\u3044\u304f\u3064\u304b\u306e\u7279\u5225\u306a\u6ce8\u610f\u304c\u5fc5\u8981\u3067\u3059\u3002\u3053\u306e\u9759\u7684\u30d5\u30a1\u30a4\u30eb\u306f\u3044\u3064\u3067\u3082\u7de8\u96c6\u3067\u304d\u307e\u3059\u3002\u69cb\u6210\u306e\u66f4\u65b0\u306f\u3001\u65b0\u3057\u304f\u4f5c\u6210\u3055\u308c\u305f\u3059\u3079\u3066\u306eKubernetes\u30ea\u30bd\u30fc\u30b9\u306b\u9069\u7528\u3055\u308c\u307e\u3059\u3002 One of the Kubernetes networking requirements (see [Kubernetes model](/ja/docs/concepts/cluster-administration/networking/)) is for cluster communication to occur without NAT internally. To honor this requirement, there is an [ExceptionList](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf#L20) for all the communication where we do not want outbound NAT to occur. However, this also means that you need to exclude the external IP you are trying to query from the ExceptionList. Only then will the traffic originating from your Windows pods be SNAT'ed correctly to receive a response from the outside world. In this regard, your ExceptionList in `cni.conf` should look as follows: Kubernetes\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u8981\u4ef6\u306e1\u3064(\u53c2\u7167[Kubernetes\u30e2\u30c7\u30eb](/ja/docs/concepts/cluster-administration/networking/))\u306f\u3001\u5185\u90e8\u3067NAT\u3092\u4f7f\u7528\u305b\u305a\u306b\u30af\u30e9\u30b9\u30bf\u30fc\u901a\u4fe1\u3092\u884c\u3046\u305f\u3081\u306e\u3082\u306e\u3067\u3059\u3002\u3053\u306e\u8981\u4ef6\u3092\u9075\u5b88\u3059\u308b\u305f\u3081\u306b\u3001\u3059\u3079\u3066\u306e\u901a\u4fe1\u306b[ExceptionList](https://github.com/Microsoft/SDN/blob/master/Kubernetes/flannel/l2bridge/cni/config/cni.conf#L20)\u304c\u3042\u308a\u3001\u30a2\u30a6\u30c8\u30d0\u30a6\u30f3\u30c9NAT\u304c\u767a\u751f\u3057\u306a\u3044\u3088\u3046\u306b\u3057\u307e\u3059\u3002\u305f\u3060\u3057\u3001\u3053\u308c\u306f\u3001\u30af\u30a8\u30ea\u3057\u3088\u3046\u3068\u3057\u3066\u3044\u308b\u5916\u90e8IP\u3092ExceptionList\u304b\u3089\u9664\u5916\u3059\u308b\u5fc5\u8981\u304c\u3042\u308b\u3053\u3068\u3082\u610f\u5473\u3057\u307e\u3059\u3002\u305d\u3046\u3057\u3066\u521d\u3081\u3066\u3001Windows Pod\u304b\u3089\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u304cSNAT\u51e6\u7406\u3055\u308c\u3001\u5916\u90e8\u304b\u3089\u306e\u5fdc\u7b54\u3092\u53d7\u4fe1\u3067\u304d\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002\u3053\u306e\u70b9\u3067\u3001`cni.conf`\u306eExceptionList\u306f\u6b21\u306e\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002: ```conf \"ExceptionList\": [ \"10.244.0.0/16\", # Cluster subnet \"10.96.0.0/12\", # Service subnet \"10.127.130.0/24\" # Management (host) subnet \"10.244.0.0/16\", # \u30af\u30e9\u30b9\u30bf\u30fc\u306e\u30b5\u30d6\u30cd\u30c3\u30c8 \"10.96.0.0/12\", # Service\u306e\u30b5\u30d6\u30cd\u30c3\u30c8 \"10.127.130.0/24\" # \u7ba1\u7406 (\u30db\u30b9\u30c8) \u306e\u30b5\u30d6\u30cd\u30c3\u30c8 ] ``` 1. My Windows node cannot access NodePort service 1. Windows\u30ce\u30fc\u30c9\u304cNodePort Service\u306b\u30a2\u30af\u30bb\u30b9\u3067\u304d\u307e\u305b\u3093 Local NodePort access from the node itself fails. This is a known limitation. NodePort access works from other nodes or external clients. \u30ce\u30fc\u30c9\u81ea\u4f53\u304b\u3089\u306e\u30ed\u30fc\u30ab\u30ebNodePort\u30a2\u30af\u30bb\u30b9\u306f\u5931\u6557\u3057\u307e\u3059\u3002\u3053\u308c\u306f\u65e2\u77e5\u306e\u5236\u9650\u3067\u3059\u3002NodePort\u30a2\u30af\u30bb\u30b9\u306f\u3001\u4ed6\u306e\u30ce\u30fc\u30c9\u307e\u305f\u306f\u5916\u90e8\u30af\u30e9\u30a4\u30a2\u30f3\u30c8\u304b\u3089\u884c\u3048\u307e\u3059\u3002 1. vNICs and HNS endpoints of containers are being deleted 1. \u30b3\u30f3\u30c6\u30ca\u306evNIC\u3068HNS\u30a8\u30f3\u30c9\u30dd\u30a4\u30f3\u30c8\u304c\u524a\u9664\u3055\u308c\u3066\u3044\u307e\u3059 This issue can be caused when the `hostname-override` parameter is not passed to [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/). To resolve it, users need to pass the hostname to kube-proxy as follows: \u3053\u306e\u554f\u984c\u306f\u3001`hostname-override`\u30d1\u30e9\u30e1\u30fc\u30bf\u304c[kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/)\u306b\u6e21\u3055\u308c\u306a\u3044\u5834\u5408\u306b\u767a\u751f\u3059\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002\u3053\u308c\u3092\u89e3\u6c7a\u3059\u308b\u306b\u306f\u3001\u30e6\u30fc\u30b6\u30fc\u306f\u6b21\u306e\u3088\u3046\u306b\u30db\u30b9\u30c8\u540d\u3092kube-proxy\u306b\u6e21\u3059\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002: ```powershell C:kkube-proxy.exe --hostname-override=$(hostname) ``` 1. With flannel my nodes are having issues after rejoining a cluster 1. flannel\u3092\u4f7f\u7528\u3059\u308b\u3068\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u518d\u53c2\u52a0\u3057\u305f\u5f8c\u3001\u30ce\u30fc\u30c9\u306b\u554f\u984c\u304c\u767a\u751f\u3057\u307e\u3059 Whenever a previously deleted node is being re-joined to the cluster, flannelD tries to assign a new pod subnet to the node. Users should remove the old pod subnet configuration files in the following paths: \u4ee5\u524d\u306b\u524a\u9664\u3055\u308c\u305f\u30ce\u30fc\u30c9\u304c\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u518d\u53c2\u52a0\u3059\u308b\u3068\u304d\u306f\u3044\u3064\u3082\u3001flannelD\u306f\u65b0\u3057\u3044Pod\u30b5\u30d6\u30cd\u30c3\u30c8\u3092\u30ce\u30fc\u30c9\u306b\u5272\u308a\u5f53\u3066\u3088\u3046\u3068\u3057\u307e\u3059\u3002\u30e6\u30fc\u30b6\u30fc\u306f\u3001\u6b21\u306e\u30d1\u30b9\u306b\u3042\u308b\u53e4\u3044Pod\u30b5\u30d6\u30cd\u30c3\u30c8\u69cb\u6210\u30d5\u30a1\u30a4\u30eb\u3092\u524a\u9664\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002: ```powershell Remove-Item C:kSourceVip.json Remove-Item C:kSourceVipRequest.json ``` 1. After launching `start.ps1`, flanneld is stuck in \"Waiting for the Network to be created\" 1. `start.ps1`\u3092\u8d77\u52d5\u3057\u305f\u5f8c\u3001flanneld\u304c\u300c\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u304c\u4f5c\u6210\u3055\u308c\u308b\u306e\u3092\u5f85\u3063\u3066\u3044\u307e\u3059\u300d\u3068\u8868\u793a\u3055\u308c\u305f\u307e\u307e\u306b\u306a\u308a\u307e\u3059 There are numerous reports of this [issue which are being investigated](https://github.com/coreos/flannel/issues/1066); most likely it is a timing issue for when the management IP of the flannel network is set. A workaround is to simply relaunch start.ps1 or relaunch it manually as follows: \u3053\u306e[\u8abf\u67fb\u4e2d\u306e\u554f\u984c](https://github.com/coreos/flannel/issues/1066)\u306b\u95a2\u3059\u308b\u591a\u6570\u306e\u5831\u544a\u304c\u3042\u308a\u307e\u3059\u3002\u6700\u3082\u53ef\u80fd\u6027\u304c\u9ad8\u3044\u306e\u306f\u3001flannel\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u7ba1\u7406IP\u304c\u8a2d\u5b9a\u3055\u308c\u308b\u30bf\u30a4\u30df\u30f3\u30b0\u306e\u554f\u984c\u3067\u3059\u3002\u56de\u907f\u7b56\u306f\u3001\u5358\u7d14\u306bstart.ps1\u3092\u518d\u8d77\u52d5\u3059\u308b\u304b\u3001\u6b21\u306e\u3088\u3046\u306b\u624b\u52d5\u3067\u518d\u8d77\u52d5\u3059\u308b\u3053\u3068\u3067\u3059\u3002: ```powershell PS C:> [Environment]::SetEnvironmentVariable(\"NODE_NAME\", \"\") PS C:> C:flannelflanneld.exe --kubeconfig-file=c:kconfig --iface= --ip-masq=1 --kube-subnet-mgr=1 ``` 1. My Windows Pods cannot launch because of missing `/run/flannel/subnet.env` 1. `/run/flannel/subnet.env`\u304c\u306a\u3044\u305f\u3081\u3001Windows Pod\u3092\u8d77\u52d5\u3067\u304d\u307e\u305b\u3093 This indicates that Flannel didn't launch correctly. You can either try to restart flanneld.exe or you can copy the files over manually from `/run/flannel/subnet.env` on the Kubernetes master to` C:runflannelsubnet.env` on the Windows worker node and modify the `FLANNEL_SUBNET` row to a different number. For example, if node subnet 10.244.4.1/24 is desired: \u3053\u308c\u306f\u3001Flannel\u304c\u6b63\u3057\u304f\u8d77\u52d5\u3057\u306a\u304b\u3063\u305f\u3053\u3068\u3092\u793a\u3057\u3066\u3044\u307e\u3059\u3002 flanneld.exe\u306e\u518d\u8d77\u52d5\u3092\u8a66\u307f\u308b\u304b\u3001Kubernetes\u30de\u30b9\u30bf\u30fc\u306e`/run/flannel/subnet.env`\u304b\u3089Windows\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306e`C:runflannelsubnet.env`\u306b\u624b\u52d5\u3067\u30d5\u30a1\u30a4\u30eb\u3092\u30b3\u30d4\u30fc\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002\u300cFLANNEL_SUBNET\u300d\u884c\u3092\u5225\u306e\u756a\u53f7\u306b\u5909\u66f4\u3057\u307e\u3059\u3002\u305f\u3068\u3048\u3070\u3001\u30ce\u30fc\u30c9\u30b5\u30d6\u30cd\u30c3\u30c810.244.4.1/24\u304c\u5fc5\u8981\u306a\u5834\u5408\u306f\u4ee5\u4e0b\u3068\u306a\u308a\u307e\u3059\u3002: ```env FLANNEL_NETWORK=10.244.0.0/16", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. 1. My Windows node cannot access my services using the service IP 1. Windows\u30ce\u30fc\u30c9\u304cService IP\u3092\u4f7f\u7528\u3057\u3066Service\u306b\u30a2\u30af\u30bb\u30b9\u3067\u304d\u306a\u3044 This is a known limitation of the current networking stack on Windows. Windows Pods are able to access the service IP however. \u3053\u308c\u306f\u3001Windows\u4e0a\u306e\u73fe\u5728\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30b9\u30bf\u30c3\u30af\u306e\u65e2\u77e5\u306e\u5236\u9650\u3067\u3059\u3002\u305f\u3060\u3057\u3001Windows Pod\u306fService IP\u306b\u30a2\u30af\u30bb\u30b9\u3067\u304d\u307e\u3059\u3002 1. No network adapter is found when starting kubelet 1. kubelet\u306e\u8d77\u52d5\u6642\u306b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a2\u30c0\u30d7\u30bf\u30fc\u304c\u898b\u3064\u304b\u308a\u307e\u305b\u3093 The Windows networking stack needs a virtual adapter for Kubernetes networking to work. If the following commands return no results (in an admin shell), virtual network creation \u2014 a necessary prerequisite for Kubelet to work \u2014 has failed: Windows\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30b9\u30bf\u30c3\u30af\u304cKubernetes\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u3092\u52d5\u304b\u3059\u306b\u306f\u3001\u4eee\u60f3\u30a2\u30c0\u30d7\u30bf\u30fc\u304c\u5fc5\u8981\u3067\u3059\u3002\u6b21\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3057\u3066\u3082\u7d50\u679c\u304c\u8fd4\u3055\u308c\u306a\u3044\u5834\u5408\uff08\u7ba1\u7406\u30b7\u30a7\u30eb\u3067\uff09\u3001\u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u4f5c\u6210\uff08Kubelet\u304c\u6a5f\u80fd\u3059\u308b\u305f\u3081\u306b\u5fc5\u8981\u306a\u524d\u63d0\u6761\u4ef6\uff09\u306b\u5931\u6557\u3057\u305f\u3053\u3068\u306b\u306a\u308a\u307e\u3059\u3002: ```powershell Get-HnsNetwork | ? Name -ieq \"cbr0\" Get-NetAdapter | ? Name -Like \"vEthernet (Ethernet*\" ``` Often it is worthwhile to modify the [InterfaceName](https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start.ps1#L6) parameter of the start.ps1 script, in cases where the host's network adapter isn't \"Ethernet\". Otherwise, consult the output of the `start-kubelet.ps1` script to see if there are errors during virtual network creation. \u30db\u30b9\u30c8\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a2\u30c0\u30d7\u30bf\u30fc\u304c\u300c\u30a4\u30fc\u30b5\u30cd\u30c3\u30c8\u300d\u3067\u306f\u306a\u3044\u5834\u5408\u3001\u591a\u304f\u306e\u5834\u5408\u3001start.ps1\u30b9\u30af\u30ea\u30d7\u30c8\u306e[InterfaceName](https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start.ps1#L6)\u30d1\u30e9\u30e1\u30fc\u30bf\u30fc\u3092\u4fee\u6b63\u3059\u308b\u4fa1\u5024\u304c\u3042\u308a\u307e\u3059\u3002\u305d\u3046\u3067\u306a\u3044\u5834\u5408\u306f`start-kubelet.ps1`\u30b9\u30af\u30ea\u30d7\u30c8\u306e\u51fa\u529b\u7d50\u679c\u3092\u8abf\u3079\u3066\u3001\u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u4f5c\u6210\u4e2d\u306b\u30a8\u30e9\u30fc\u304c\u306a\u3044\u304b\u78ba\u8a8d\u3057\u307e\u3059\u3002 1. My Pods are stuck at \"Container Creating\" or restarting over and over 1. Pod\u304c\u300cContainer Creating\u300d\u3068\u8868\u793a\u3055\u308c\u305f\u307e\u307e\u52d5\u304b\u306a\u304f\u306a\u3063\u305f\u308a\u3001\u4f55\u5ea6\u3082\u518d\u8d77\u52d5\u3092\u7e70\u308a\u8fd4\u3057\u307e\u3059 Check that your pause image is compatible with your OS version. The [instructions](https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/deploying-resources) assume that both the OS and the containers are version 1803. If you have a later version of Windows, such as an Insider build, you need to adjust the images accordingly. Please refer to the Microsoft's [Docker repository](https://hub.docker.com/u/microsoft/) for images. Regardless, both the pause image Dockerfile and the sample service expect the image to be tagged as :latest. Pause\u30a4\u30e1\u30fc\u30b8\u304cOS\u30d0\u30fc\u30b8\u30e7\u30f3\u3068\u4e92\u63db\u6027\u304c\u3042\u308b\u3053\u3068\u3092\u78ba\u8a8d\u3057\u3066\u304f\u3060\u3055\u3044\u3002[\u8aac\u660e](https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/deploying-resources)\u3067\u306f\u3001OS\u3068\u30b3\u30f3\u30c6\u30ca\u306e\u4e21\u65b9\u304c\u30d0\u30fc\u30b8\u30e7\u30f31803\u3067\u3042\u308b\u3068\u60f3\u5b9a\u3057\u3066\u3044\u307e\u3059\u3002\u305d\u308c\u4ee5\u964d\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306eWindows\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306f\u3001Insider\u30d3\u30eb\u30c9\u306a\u3069\u3067\u306f\u3001\u305d\u308c\u306b\u5fdc\u3058\u3066\u30a4\u30e1\u30fc\u30b8\u3092\u8abf\u6574\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u30a4\u30e1\u30fc\u30b8\u306b\u3064\u3044\u3066\u306f\u3001Microsoft\u306e[Docker\u30ec\u30b8\u30b9\u30c8\u30ea](https://hub.docker.com/u/microsoft/)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002\u3044\u305a\u308c\u306b\u3057\u3066\u3082\u3001Pause\u30a4\u30e1\u30fc\u30b8\u306eDockerfile\u3068\u30b5\u30f3\u30d7\u30eb\u30b5\u30fc\u30d3\u30b9\u306e\u4e21\u65b9\u3067\u3001\u30a4\u30e1\u30fc\u30b8\u306b:latest\u306e\u30bf\u30b0\u304c\u4ed8\u3051\u3089\u308c\u3066\u3044\u308b\u3068\u60f3\u5b9a\u3057\u3066\u3044\u307e\u3059\u3002 Starting with Kubernetes v1.14, Microsoft releases the pause infrastructure container at `mcr.microsoft.com/k8s/core/pause:1.2.0`. For more information search for \"pause\" in the [Guide for adding Windows Nodes in Kubernetes](../user-guide-windows-nodes). Kubernetes v1.14\u4ee5\u964d\u3001Microsoft\u306fPause\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u30b3\u30f3\u30c6\u30ca\u3092`mcr.microsoft.com/k8s/core/pause:1.2.0`\u3067\u30ea\u30ea\u30fc\u30b9\u3057\u3066\u3044\u307e\u3059\u3002\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001[Kubernetes\u306bWindows\u30ce\u30fc\u30c9\u3092\u8ffd\u52a0\u3059\u308b\u305f\u3081\u306e\u30ac\u30a4\u30c9](../user-guide-windows-nodes)\u3067\u300cPause\u300d\u3092\u691c\u7d22\u3057\u3066\u304f\u3060\u3055\u3044\u3002 1. DNS resolution is not properly working 1. DNS\u540d\u524d\u89e3\u6c7a\u304c\u6b63\u3057\u304f\u6a5f\u80fd\u3057\u3066\u3044\u306a\u3044 Check the DNS limitations for Windows in this [section](#dns-limitations). \u3053\u306e[\u30bb\u30af\u30b7\u30e7\u30f3](#dns-limitations)\u3067DNS\u306e\u5236\u9650\u3092\u78ba\u8a8d\u3057\u3066\u304f\u3060\u3055\u3044\u3002 1. `kubectl port-forward` fails with \"unable to do port forwarding: wincat not found\" 1. `kubectl port-forward`\u304c\u300c\u30dd\u30fc\u30c8\u8ee2\u9001\u3092\u5b9f\u884c\u3067\u304d\u307e\u305b\u3093:wincat\u304c\u898b\u3064\u304b\u308a\u307e\u305b\u3093\u300d\u3067\u5931\u6557\u3057\u307e\u3059 This was implemented in Kubernetes 1.15, and the pause infrastructure container `mcr.microsoft.com/k8s/core/pause:1.2.0`. Be sure to use these versions or newer ones. If you would like to build your own pause infrastructure container, be sure to include [wincat](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat) \u3053\u308c\u306fKubernetes 1.15\u3001\u304a\u3088\u3073Pause\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u30b3\u30f3\u30c6\u30ca`mcr.microsoft.com/k8s/core/pause:1.2.0`\u3067\u5b9f\u88c5\u3055\u308c\u307e\u3057\u305f\u3002\u5fc5\u305a\u3053\u308c\u3089\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u4ee5\u964d\u3092\u4f7f\u7528\u3057\u3066\u304f\u3060\u3055\u3044\u3002 \u72ec\u81ea\u306ePause\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u30b3\u30f3\u30c6\u30ca\u3092\u69cb\u7bc9\u3059\u308b\u5834\u5408\u306f\u3001\u5fc5\u305a[wincat](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat)\u3092\u542b\u3081\u3066\u304f\u3060\u3055\u3044\u3002 1. My Kubernetes installation is failing because my Windows Server node is behind a proxy 1. Windows Server\u30ce\u30fc\u30c9\u304c\u30d7\u30ed\u30ad\u30b7\u306e\u80cc\u5f8c\u306b\u3042\u308b\u305f\u3081\u3001Kubernetes\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u304c\u5931\u6557\u3057\u307e\u3059 If you are behind a proxy, the following PowerShell environment variables must be defined: \u30d7\u30ed\u30ad\u30b7\u306e\u80cc\u5f8c\u306b\u3042\u308b\u5834\u5408\u306f\u3001\u6b21\u306ePowerShell\u74b0\u5883\u5909\u6570\u3092\u5b9a\u7fa9\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002: ```PowerShell [Environment]::SetEnvironmentVariable(\"HTTP_PROXY\", \"http://proxy.example.com:80/\", [EnvironmentVariableTarget]::Machine) [Environment]::SetEnvironmentVariable(\"HTTPS_PROXY\", \"http://proxy.example.com:443/\", [EnvironmentVariableTarget]::Machine) ``` 1. What is a `pause` container? 1. `pause`\u30b3\u30f3\u30c6\u30ca\u3068\u306f\u4f55\u3067\u3059\u304b In a Kubernetes Pod, an infrastructure or \"pause\" container is first created to host the container endpoint. Containers that belong to the same pod, including infrastructure and worker containers, share a common network namespace and endpoint (same IP and port space). Pause containers are needed to accommodate worker containers crashing or restarting without losing any of the networking configuration. Kubernetes Pod\u3067\u306f\u3001\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u307e\u305f\u306f\u300cpause\u300d\u30b3\u30f3\u30c6\u30ca\u304c\u6700\u521d\u306b\u4f5c\u6210\u3055\u308c\u3001\u30b3\u30f3\u30c6\u30ca\u30a8\u30f3\u30c9\u30dd\u30a4\u30f3\u30c8\u3092\u30db\u30b9\u30c8\u3057\u307e\u3059\u3002\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u3084\u30ef\u30fc\u30ab\u30fc\u30b3\u30f3\u30c6\u30ca\u306a\u3069\u3001\u540c\u3058Pod\u306b\u5c5e\u3059\u308b\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u5171\u901a\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30cd\u30fc\u30e0\u30b9\u30da\u30fc\u30b9\u3068\u30a8\u30f3\u30c9\u30dd\u30a4\u30f3\u30c8\uff08\u540c\u3058IP\u3068\u30dd\u30fc\u30c8\u30b9\u30da\u30fc\u30b9\uff09\u3092\u5171\u6709\u3057\u307e\u3059\u3002Pause\u30b3\u30f3\u30c6\u30ca\u306f\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u69cb\u6210\u3092\u5931\u3046\u3053\u3068\u306a\u304f\u30af\u30e9\u30c3\u30b7\u30e5\u307e\u305f\u306f\u518d\u8d77\u52d5\u3059\u308b\u30ef\u30fc\u30ab\u30fc\u30b3\u30f3\u30c6\u30ca\u306b\u5bfe\u5fdc\u3059\u308b\u305f\u3081\u306b\u5fc5\u8981\u3067\u3059\u3002 The \"pause\" (infrastructure) image is hosted on Microsoft Container Registry (MCR). You can access it using `docker pull mcr.microsoft.com/k8s/core/pause:1.2.0`. For more details, see the [DOCKERFILE](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat). \u300cpause\u300d\uff08\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\uff09\u30a4\u30e1\u30fc\u30b8\u306f\u3001Microsoft Container Registry\uff08MCR\uff09\u3067\u30db\u30b9\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u3002`docker pull mcr.microsoft.com/k8s/core/pause:1.2.0`\u3092\u4f7f\u7528\u3057\u3066\u30a2\u30af\u30bb\u30b9\u3067\u304d\u307e\u3059\u3002\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001[DOCKERFILE](https://github.com/kubernetes-sigs/sig-windows-tools/tree/master/cmd/wincat)\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002 ### Further investigation ### \u3055\u3089\u306a\u308b\u8abf\u67fb If these steps don't resolve your problem, you can get help running Windows containers on Windows nodes in Kubernetes through: \u3053\u308c\u3089\u306e\u624b\u9806\u3067\u554f\u984c\u304c\u89e3\u6c7a\u3057\u306a\u3044\u5834\u5408\u306f\u3001\u6b21\u306e\u65b9\u6cd5\u3067\u3001Kubernetes\u306eWindows\u30ce\u30fc\u30c9\u3067Windows\u30b3\u30f3\u30c6\u30ca\u3092\u5b9f\u884c\u3059\u308b\u969b\u306e\u30d8\u30eb\u30d7\u3092\u5229\u7528\u3067\u304d\u307e\u3059\u3002: * StackOverflow [Windows Server Container](https://stackoverflow.com/questions/tagged/windows-server-container) topic * Kubernetes Official Forum [discuss.kubernetes.io](https://discuss.kubernetes.io/) * StackOverflow [Windows Server Container](https://stackoverflow.com/questions/tagged/windows-server-container)\u30c8\u30d4\u30c3\u30af * Kubernetes\u30aa\u30d5\u30a3\u30b7\u30e3\u30eb\u30d5\u30a9\u30fc\u30e9\u30e0 [discuss.kubernetes.io](https://discuss.kubernetes.io/) * Kubernetes Slack [#SIG-Windows Channel](https://kubernetes.slack.com/messages/sig-windows) ## Reporting Issues and Feature Requests ## Issue\u3068Feature\u30ea\u30af\u30a8\u30b9\u30c8\u306e\u5831\u544a If you have what looks like a bug, or you would like to make a feature request, please use the [GitHub issue tracking system](https://github.com/kubernetes/kubernetes/issues). You can open issues on [GitHub](https://github.com/kubernetes/kubernetes/issues/new/choose) and assign them to SIG-Windows. You should first search the list of issues in case it was reported previously and comment with your experience on the issue and add additional logs. SIG-Windows Slack is also a great avenue to get some initial support and troubleshooting ideas prior to creating a ticket. \u30d0\u30b0\u306e\u3088\u3046\u306a\u3082\u306e\u304c\u3042\u308b\u5834\u5408\u3001\u307e\u305f\u306fFeature\u30ea\u30af\u30a8\u30b9\u30c8\u3092\u884c\u3046\u5834\u5408\u306f\u3001[GitHub\u306eIssue\u30b7\u30b9\u30c6\u30e0](https://github.com/kubernetes/kubernetes/issues)\u3092\u4f7f\u7528\u3057\u3066\u304f\u3060\u3055\u3044\u3002[GitHub](https://github.com/kubernetes/kubernetes/issues/new/choose)\u3067Issue\u3092\u958b\u3044\u3066\u3001SIG-Windows\u306b\u5272\u308a\u5f53\u3066\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002\u4ee5\u524d\u306b\u5831\u544a\u3055\u308c\u305f\u5834\u5408\u306f\u3001\u307e\u305aIssue\u30ea\u30b9\u30c8\u3092\u691c\u7d22\u3057\u3001Issue\u306b\u3064\u3044\u3066\u306e\u7d4c\u9a13\u3092\u30b3\u30e1\u30f3\u30c8\u3057\u3066\u3001\u8ffd\u52a0\u306e\u30ed\u30b0\u3092\u52a0\u3048\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002SIG-Windows Slack\u306f\u3001\u30c1\u30b1\u30c3\u30c8\u3092\u4f5c\u6210\u3059\u308b\u524d\u306b\u3001\u521d\u671f\u30b5\u30dd\u30fc\u30c8\u3068\u30c8\u30e9\u30d6\u30eb\u30b7\u30e5\u30fc\u30c6\u30a3\u30f3\u30b0\u306e\u30a2\u30a4\u30c7\u30a2\u3092\u5f97\u308b\u305f\u3081\u306e\u7d20\u6674\u3089\u3057\u3044\u624b\u6bb5\u3067\u3082\u3042\u308a\u307e\u3059\u3002 If filing a bug, please include detailed information about how to reproduce the problem, such as: \u30d0\u30b0\u3092\u5831\u544a\u3059\u308b\u5834\u5408\u306f\u3001\u554f\u984c\u306e\u518d\u73fe\u65b9\u6cd5\u306b\u95a2\u3059\u308b\u6b21\u306e\u3088\u3046\u306a\u8a73\u7d30\u60c5\u5831\u3092\u542b\u3081\u3066\u304f\u3060\u3055\u3044\u3002: * Kubernetes version: kubectl version * Environment details: Cloud provider, OS distro, networking choice and configuration, and Docker version * Detailed steps to reproduce the problem * [Relevant logs](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs) * Tag the issue sig/windows by commenting on the issue with `/sig windows` to bring it to a SIG-Windows member's attention * Kubernetes\u306e\u30d0\u30fc\u30b8\u30e7\u30f3: kubectl\u306e\u30d0\u30fc\u30b8\u30e7\u30f3 * \u74b0\u5883\u306e\u8a73\u7d30: \u30af\u30e9\u30a6\u30c9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3001OS\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u3001\u9078\u629e\u3057\u305f\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u3068\u69cb\u6210\u3001\u304a\u3088\u3073Docker\u306e\u30d0\u30fc\u30b8\u30e7\u30f3 * \u554f\u984c\u3092\u518d\u73fe\u3059\u308b\u305f\u3081\u306e\u8a73\u7d30\u306a\u624b\u9806 * [\u95a2\u9023\u3059\u308b\u30ed\u30b0](https://github.com/kubernetes/community/blob/master/sig-windows/CONTRIBUTING.md#gathering-logs) * `/sig windows`\u3067Issue\u306b\u30b3\u30e1\u30f3\u30c8\u3057\u3066\u3001Issue\u306bsig/windows\u306e\u30bf\u30b0\u3092\u4ed8\u3051\u3066\u3001SIG-Windows\u30e1\u30f3\u30d0\u30fc\u304c\u6c17\u4ed8\u304f\u3088\u3046\u306b\u3057\u307e\u3059 ## {{% heading \"whatsnext\" %}} We have a lot of features in our roadmap. An abbreviated high level list is included below, but we encourage you to view our [roadmap project](https://github.com/orgs/kubernetes/projects/8) and help us make Windows support better by [contributing](https://github.com/kubernetes/community/blob/master/sig-windows/). \u30ed\u30fc\u30c9\u30de\u30c3\u30d7\u306b\u306f\u591a\u304f\u306e\u6a5f\u80fd\u304c\u3042\u308a\u307e\u3059\u3002\u9ad8\u30ec\u30d9\u30eb\u306e\u7c21\u7565\u30ea\u30b9\u30c8\u3092\u4ee5\u4e0b\u306b\u793a\u3057\u307e\u3059\u304c\u3001[\u30ed\u30fc\u30c9\u30de\u30c3\u30d7\u30d7\u30ed\u30b8\u30a7\u30af\u30c8](https://github.com/orgs/kubernetes/projects/8)\u3092\u898b\u3066\u3001[\u8ca2\u732e\u3059\u308b\u3053\u3068](https://github.com/kubernetes/community/blob/master/sig-windows/)\u306b\u3088\u3063\u3066Windows\u30b5\u30dd\u30fc\u30c8\u3092\u6539\u5584\u3059\u308b\u3053\u3068\u3092\u304a\u52e7\u3081\u3057\u307e\u3059\u3002 ### CRI-ContainerD {{< glossary_tooltip term_id=\"containerd\" >}} is another OCI-compliant runtime that recently graduated as a {{< glossary_tooltip text=\"CNCF\" term_id=\"cncf\" >}} project. It's currently tested on Linux, but 1.3 will bring support for Windows and Hyper-V. [[reference](https://blog.docker.com/2019/02/containerd-graduates-within-the-cncf/)] {{< glossary_tooltip term_id=\"containerd\" >}}\u306f\u3001\u6700\u8fd1{{< glossary_tooltip text=\"CNCF\" term_id=\"cncf\" >}}\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u3068\u3057\u3066\u5352\u696d\u3057\u305f\u3001\u3082\u30461\u3064\u306eOCI\u6e96\u62e0\u30e9\u30f3\u30bf\u30a4\u30e0\u3067\u3059\u3002\u73fe\u5728Linux\u3067\u30c6\u30b9\u30c8\u3055\u308c\u3066\u3044\u307e\u3059\u304c\u30011.3\u306fWindows\u3068Hyper-V\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u307e\u3059\u3002[[\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9](https://blog.docker.com/2019/02/containerd-graduates-within-the-cncf/)] The CRI-ContainerD interface will be able to manage sandboxes based on Hyper-V. This provides a foundation where RuntimeClass could be implemented for new use cases including: CRI-ContainerD\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30a4\u30b9\u306f\u3001Hyper-V\u306b\u57fa\u3065\u3044\u3066\u30b5\u30f3\u30c9\u30dc\u30c3\u30af\u30b9\u3092\u7ba1\u7406\u3067\u304d\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002\u3053\u308c\u306b\u3088\u308a\u3001RuntimeClass\u3092\u6b21\u306e\u3088\u3046\u306a\u65b0\u3057\u3044\u30e6\u30fc\u30b9\u30b1\u30fc\u30b9\u306b\u5b9f\u88c5\u3067\u304d\u308b\u57fa\u76e4\u304c\u63d0\u4f9b\u3055\u308c\u307e\u3059: * Hypervisor-based isolation between pods for additional security * Backwards compatibility allowing a node to run a newer Windows Server version without requiring containers to be rebuilt * Specific CPU/NUMA settings for a pod * Memory isolation and reservations * Pod\u9593\u306e\u30cf\u30a4\u30d1\u30fc\u30d0\u30a4\u30b6\u30fc\u30d9\u30fc\u30b9\u306e\u5206\u96e2\u306b\u3088\u308a\u3001\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u3092\u5f37\u5316 * \u4e0b\u4f4d\u4e92\u63db\u6027\u306b\u3088\u308a\u3001\u30b3\u30f3\u30c6\u30ca\u306e\u518d\u69cb\u7bc9\u3092\u5fc5\u8981\u3068\u305b\u305a\u306b\u30ce\u30fc\u30c9\u3067\u65b0\u3057\u3044Windows Server\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u5b9f\u884c * Pod\u306e\u7279\u5b9a\u306eCPU/NUMA\u8a2d\u5b9a * \u30e1\u30e2\u30ea\u306e\u5206\u96e2\u3068\u4e88\u7d04 ### Hyper-V isolation ### Hyper-V\u5206\u96e2 The existing Hyper-V isolation support, an experimental feature as of v1.10, will be deprecated in the future in favor of the CRI-ContainerD and RuntimeClass features mentioned above. To use the current features and create a Hyper-V isolated container, the kubelet should be started with feature gates `HyperVContainer=true` and the Pod should include the annotation `experimental.windows.kubernetes.io/isolation-type=hyperv`. In the experiemental release, this feature is limited to 1 container per Pod. \u65e2\u5b58\u306eHyper-V\u5206\u96e2\u30b5\u30dd\u30fc\u30c8\u306f\u3001v1.10\u306e\u8a66\u9a13\u7684\u306a\u6a5f\u80fd\u3067\u3042\u308a\u3001\u4e0a\u8a18\u306eCRI-ContainerD\u6a5f\u80fd\u3068RuntimeClass\u6a5f\u80fd\u3092\u512a\u5148\u3057\u3066\u5c06\u6765\u5ec3\u6b62\u3055\u308c\u308b\u4e88\u5b9a\u3067\u3059\u3002\u73fe\u5728\u306e\u6a5f\u80fd\u3092\u4f7f\u7528\u3057\u3066Hyper-V\u5206\u96e2\u30b3\u30f3\u30c6\u30ca\u3092\u4f5c\u6210\u3059\u308b\u306b\u306f\u3001kubelet\u306e\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8\u3092`HyperVContainer=true`\u3067\u958b\u59cb\u3057\u3001Pod\u306b\u30a2\u30ce\u30c6\u30fc\u30b7\u30e7\u30f3`experimental.windows.kubernetes.io/isolation-type=hyperv`\u3092\u542b\u3081\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u5b9f\u9a13\u7684\u30ea\u30ea\u30fc\u30b9\u3067\u306f\u3001\u3053\u306e\u6a5f\u80fd\u306fPod\u3054\u3068\u306b1\u3064\u306e\u30b3\u30f3\u30c6\u30ca\u306b\u5236\u9650\u3055\u308c\u3066\u3044\u307e\u3059\u3002 ```yaml apiVersion: apps/v1", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-9607cb389577466bb19161e8ea9ed17fad2e3696220f80ea4629f2c0cefcb32e", "query": "This is a Feature Request What would you like to be Translate docs/setup/production-environment/windows/intro-windows-in-kubernetes/ into Japanese Why is this needed This page has not been translated. Comments /language ja /assign\n/close\nClosing this issue. ### Deployment with kubeadm and cluster API ### kubeadm\u3068\u30af\u30e9\u30b9\u30bf\u30fcAPI\u3092\u4f7f\u7528\u3057\u305f\u30c7\u30d7\u30ed\u30a4 Kubeadm is becoming the de facto standard for users to deploy a Kubernetes cluster. Windows node support in kubeadm will come in a future release. We are also making investments in cluster API to ensure Windows nodes are properly provisioned. Kubeadm\u306f\u3001\u30e6\u30fc\u30b6\u30fc\u304cKubernetes\u30af\u30e9\u30b9\u30bf\u30fc\u3092\u30c7\u30d7\u30ed\u30a4\u3059\u308b\u305f\u3081\u306e\u4e8b\u5b9f\u4e0a\u306e\u6a19\u6e96\u306b\u306a\u308a\u3064\u3064\u3042\u308a\u307e\u3059\u3002kubeadm\u306eWindows\u30ce\u30fc\u30c9\u306e\u30b5\u30dd\u30fc\u30c8\u306f\u3001\u5c06\u6765\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u63d0\u4f9b\u4e88\u5b9a\u3067\u3059\u3002Windows\u30ce\u30fc\u30c9\u304c\u9069\u5207\u306b\u30d7\u30ed\u30d3\u30b8\u30e7\u30cb\u30f3\u30b0\u3055\u308c\u308b\u3088\u3046\u306b\u3001\u30af\u30e9\u30b9\u30bf\u30fcAPI\u306b\u3082\u6295\u8cc7\u3057\u3066\u3044\u307e\u3059\u3002 ### A few other key features * Beta support for Group Managed Service Accounts * More CNIs * More Storage Plugins ### \u305d\u306e\u4ed6\u306e\u4e3b\u306a\u6a5f\u80fd * \u30b0\u30eb\u30fc\u30d7\u7ba1\u7406\u30b5\u30fc\u30d3\u30b9\u30a2\u30ab\u30a6\u30f3\u30c8\u306e\u30d9\u30fc\u30bf\u30b5\u30dd\u30fc\u30c8 * \u305d\u306e\u4ed6\u306eCNI * \u305d\u306e\u4ed6\u306e\u30b9\u30c8\u30ec\u30fc\u30b8\u30d7\u30e9\u30b0\u30a4\u30f3 ", "commid": "website_pr_22708"}], "negative_passages": []} {"query_id": "q-en-website-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb", "query": "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.\n/language en\nit 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\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:", "positive_passages": [{"docid": "doc-en-website-6e4d622ca28dee8dc9ad3501195eabd05cff4b78a6a30ddf84644e827745dec5", "text": "convert your old configuration files to a newer version. `kubeadm config images list` and `kubeadm config images pull` can be used to list and pull the images that kubeadm requires. For more information navigate to [Using kubeadm init with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file) or [Using kubeadm join with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-join/#config-file). In Kubernetes v1.13.0 and later to list/pull kube-dns images instead of the CoreDNS image the `--config` method described [here](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon) has to be used.", "commid": "website_pr_24076"}], "negative_passages": []} {"query_id": "q-en-website-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb", "query": "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.\n/language en\nit 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\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:", "positive_passages": [{"docid": "doc-en-website-9513b7f0fadec31b929984eeefcde9502f19bbb438beaa2b42c4c579e37b73a0", "text": "It's possible to configure `kubeadm init` with a configuration file instead of command line flags, and some more advanced features may only be available as configuration file options. This file is passed with the `--config` option. configuration file options. This file is passed using the `--config` flag and it must contain a `ClusterConfiguration` structure and optionally more structures separated by `---n` Mixing `--config` with others flags may not be allowed in some cases. The default configuration can be printed out using the [kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. It is **recommended** that you migrate your old `v1beta1` configuration to `v1beta2` using If your configuration is not using the latest version it is **recommended** that you migrate using the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. For more details on each field in the `v1beta2` configuration you can navigate to our [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2). For more information on the fields and usage of the configuration you can navigate to our API reference page and pick a version from [the list](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#pkg-subdirectories). ### Adding kube-proxy parameters {#kube-proxy}", "commid": "website_pr_24076"}], "negative_passages": []} {"query_id": "q-en-website-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb", "query": "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.\n/language en\nit 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\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:", "positive_passages": [{"docid": "doc-en-website-00aa66da7bd6e747d4783005f15f5f1a75641b841a0fa7651cd77fc665499846", "text": "It's possible to configure `kubeadm join` with a configuration file instead of command line flags, and some more advanced features may only be available as configuration file options. This file is passed using the `--config` flag and it must contain a `JoinConfiguration` structure. contain a `JoinConfiguration` structure. Mixing `--config` with others flags may not be allowed in some cases. To print the default values of `JoinConfiguration` run the following command: The default configuration can be printed out using the [kubeadm config print](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. ```shell kubeadm config print join-defaults ``` If your configuration is not using the latest version it is **recommended** that you migrate using the [kubeadm config migrate](/docs/reference/setup-tools/kubeadm/kubeadm-config/) command. For details on individual fields in `JoinConfiguration` see [the godoc](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#JoinConfiguration). For more information on the fields and usage of the configuration you can navigate to our API reference page and pick a version from [the list](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm#pkg-subdirectories). ## {{% heading \"whatsnext\" %}}", "commid": "website_pr_24076"}], "negative_passages": []} {"query_id": "q-en-website-f435a53ad40dbd03e80b0aa9c7bf4f13ebb408c300243b552d0130741c5550bb", "query": "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.\n/language en\nit 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\n. I will keep most of the discussion over there for now.\n/remove-help /assign /lifecycle-active sending a PR with:", "positive_passages": [{"docid": "doc-en-website-b1ff40d596806422812db70a8a3b363c0d90a7a30d68053e4392db33a7a3e784", "text": "For more information about `kubeadm init` arguments, see the [kubeadm reference guide](/docs/reference/setup-tools/kubeadm/kubeadm/). For a complete list of configuration options, see the [configuration file documentation](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file). 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). 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/).", "commid": "website_pr_24076"}], "negative_passages": []} {"query_id": "q-en-website-5a9a940eec7ec3e6b61c02ff80b216559252e70cfa652952117cc031dcc8d3aa", "query": "/language zh\n/sig auth\n/remove-sig auth /assign\nIs this not SIG Auth?\nBy mentioning 'SIG Auth', we mean we want members from that SIG to help review the localization. For one thing, I'm not convinced that will happen. For the other, such mentions are distracting that SIG's attention on PRs which needs their feedback.", "positive_passages": [{"docid": "doc-en-website-c1ac60e6c92845d2b6c78858c7070e6e0b78f5d60ded7c02a1b354daf3c2940a", "text": " --- title: \u7528\u6237\u8ba4\u8bc1 content_type: concept weight: 10 --- \u672c\u9875\u63d0\u4f9b\u8eab\u4efd\u8ba4\u8bc1\u6709\u5173\u7684\u6982\u8ff0\u3002 ## Kubernetes \u4e2d\u7684\u7528\u6237 {#users-in-kubernetes} \u6240\u6709 Kubernetes \u96c6\u7fa4\u90fd\u6709\u4e24\u7c7b\u7528\u6237\uff1a\u7531 Kubernetes \u7ba1\u7406\u7684\u670d\u52a1\u8d26\u53f7\u548c\u666e\u901a\u7528\u6237\u3002 Kuernetes \u5047\u5b9a\u4f7f\u7528\u4ee5\u4e0b\u65b9\u5f0f\u4e4b\u4e00\u6765\u5229\u7528\u4e0e\u96c6\u7fa4\u65e0\u5173\u7684\u670d\u52a1\u6765\u7ba1\u7406\u666e\u901a\u7528\u6237\uff1a - \u8d1f\u8d23\u5206\u53d1\u79c1\u94a5\u7684\u7ba1\u7406\u5458 - \u7c7b\u4f3c Keystone \u6216\u8005 Google Accounts \u8fd9\u7c7b\u7528\u6237\u6570\u636e\u5e93 - \u5305\u542b\u7528\u6237\u540d\u548c\u5bc6\u7801\u5217\u8868\u7684\u6587\u4ef6 \u6709\u9274\u4e8e\u6b64\uff0c_Kubernetes \u5e76\u4e0d\u5305\u542b\u7528\u6765\u4ee3\u8868\u666e\u901a\u7528\u6237\u8d26\u53f7\u7684\u5bf9\u8c61_\u3002 \u666e\u901a\u7528\u6237\u7684\u4fe1\u606f\u65e0\u6cd5\u901a\u8fc7 API \u8c03\u7528\u6dfb\u52a0\u5230\u96c6\u7fa4\u4e2d\u3002 \u5c3d\u7ba1\u65e0\u6cd5\u901a\u8fc7 API \u8c03\u7528\u6765\u6dfb\u52a0\u666e\u901a\u7528\u6237\uff0cKubernetes \u4ecd\u7136\u8ba4\u4e3a\u80fd\u591f\u63d0\u4f9b\u7531\u96c6\u7fa4\u7684\u8bc1\u4e66 \u673a\u6784\u7b7e\u540d\u7684\u5408\u6cd5\u8bc1\u4e66\u7684\u7528\u6237\u662f\u901a\u8fc7\u8eab\u4efd\u8ba4\u8bc1\u7684\u7528\u6237\u3002\u57fa\u4e8e\u8fd9\u6837\u7684\u914d\u7f6e\uff0cKubernetes \u4f7f\u7528\u8bc1\u4e66\u4e2d\u7684 'subject' \u7684\u901a\u7528\u540d\u79f0\uff08Common Name\uff09\u5b57\u6bb5\uff08\u4f8b\u5982\uff0c\"/CN=bob\"\uff09\u6765 \u786e\u5b9a\u7528\u6237\u540d\u3002\u63a5\u4e0b\u6765\uff0c\u57fa\u4e8e\u89d2\u8272\u8bbf\u95ee\u63a7\u5236\uff08RBAC\uff09\u5b50\u7cfb\u7edf\u4f1a\u786e\u5b9a\u7528\u6237\u662f\u5426\u6709\u6743\u9488\u5bf9 \u67d0\u8d44\u6e90\u6267\u884c\u7279\u5b9a\u7684\u64cd\u4f5c\u3002\u8fdb\u4e00\u6b65\u7684\u7ec6\u8282\u53ef\u53c2\u9605 [\u8bc1\u4e66\u8bf7\u6c42](/zh/docs/reference/access-authn-authz/certificate-signing-requests/#normal-user) \u4e0b\u666e\u901a\u7528\u6237\u4e3b\u9898\u3002 \u4e0e\u6b64\u4e0d\u540c\uff0c\u670d\u52a1\u8d26\u53f7\u662f Kubernetes API \u6240\u7ba1\u7406\u7684\u7528\u6237\u3002\u5b83\u4eec\u88ab\u7ed1\u5b9a\u5230\u7279\u5b9a\u7684\u540d\u5b57\u7a7a\u95f4\uff0c \u6216\u8005\u7531 API \u670d\u52a1\u5668\u81ea\u52a8\u521b\u5efa\uff0c\u6216\u8005\u901a\u8fc7 API \u8c03\u7528\u521b\u5efa\u3002\u670d\u52a1\u8d26\u53f7\u4e0e\u4e00\u7ec4\u4ee5 Secret \u4fdd\u5b58 \u7684\u51ed\u636e\u76f8\u5173\uff0c\u8fd9\u4e9b\u51ed\u636e\u4f1a\u88ab\u6302\u8f7d\u5230 Pod \u4e2d\uff0c\u4ece\u800c\u5141\u8bb8\u96c6\u7fa4\u5185\u7684\u8fdb\u7a0b\u8bbf\u95ee Kubernetes API\u3002 API \u8bf7\u6c42\u5219\u6216\u8005\u4e0e\u67d0\u666e\u901a\u7528\u6237\u76f8\u5173\u8054\uff0c\u6216\u8005\u4e0e\u67d0\u670d\u52a1\u8d26\u53f7\u76f8\u5173\u8054\uff0c\u4ea6\u6216\u8005\u88ab\u89c6\u4f5c [\u533f\u540d\u8bf7\u6c42](#anonymous-requests)\u3002\u8fd9\u610f\u5473\u7740\u96c6\u7fa4\u5185\u5916\u7684\u6bcf\u4e2a\u8fdb\u7a0b\u5728\u5411 API \u670d\u52a1\u5668\u53d1\u8d77 \u8bf7\u6c42\u65f6\u90fd\u5fc5\u987b\u901a\u8fc7\u8eab\u4efd\u8ba4\u8bc1\uff0c\u5426\u5219\u4f1a\u88ab\u89c6\u4f5c\u533f\u540d\u7528\u6237\u3002\u8fd9\u91cc\u7684\u8fdb\u7a0b\u53ef\u4ee5\u662f\u5728\u67d0\u5de5\u4f5c\u7ad9\u4e0a \u8f93\u5165 `kubectl` \u547d\u4ee4\u7684\u64cd\u4f5c\u4eba\u5458\uff0c\u4e5f\u53ef\u4ee5\u662f\u8282\u70b9\u4e0a\u7684 `kubelet` \u7ec4\u4ef6\uff0c\u8fd8\u53ef\u4ee5\u662f\u63a7\u5236\u9762 \u7684\u6210\u5458\u3002 ## \u8eab\u4efd\u8ba4\u8bc1\u7b56\u7565 {#authentication-strategies} Kubernetes \u4f7f\u7528\u8eab\u4efd\u8ba4\u8bc1\u63d2\u4ef6\u5229\u7528\u5ba2\u6237\u7aef\u8bc1\u4e66\u3001\u6301\u6709\u8005\u4ee4\u724c\uff08Bearer Token\uff09\u3001\u8eab\u4efd\u8ba4\u8bc1\u4ee3\u7406\uff08Proxy\uff09 \u6216\u8005 HTTP \u57fa\u672c\u8ba4\u8bc1\u673a\u5236\u6765\u8ba4\u8bc1 API \u8bf7\u6c42\u7684\u8eab\u4efd\u3002HTTP \u8bf7\u6c42\u53d1\u7ed9 API \u670d\u52a1\u5668\u65f6\uff0c \u63d2\u4ef6\u4f1a\u5c06\u4ee5\u4e0b\u5c5e\u6027\u5173\u8054\u5230\u8bf7\u6c42\u672c\u8eab\uff1a * \u7528\u6237\u540d\uff1a\u7528\u6765\u8fa9\u8bc6\u6700\u7ec8\u7528\u6237\u7684\u5b57\u7b26\u4e32\u3002\u5e38\u89c1\u7684\u503c\u53ef\u4ee5\u662f `kube-admin` \u6216 `jane@example.com`\u3002 * \u7528\u6237 ID\uff1a\u7528\u6765\u8fa9\u8bc6\u6700\u7ec8\u7528\u6237\u7684\u5b57\u7b26\u4e32\uff0c\u65e8\u5728\u6bd4\u7528\u6237\u540d\u6709\u66f4\u597d\u7684\u4e00\u81f4\u6027\u548c\u552f\u4e00\u6027\u3002 * \u7528\u6237\u7ec4\uff1a\u53d6\u503c\u4e3a\u4e00\u7ec4\u5b57\u7b26\u4e32\uff0c\u5176\u4e2d\u5404\u4e2a\u5b57\u7b26\u4e32\u7528\u6765\u6807\u660e\u7528\u6237\u662f\u67d0\u4e2a\u547d\u540d\u7684\u7528\u6237\u903b\u8f91\u96c6\u5408\u7684\u6210\u5458\u3002 \u5e38\u89c1\u7684\u503c\u53ef\u80fd\u662f `system:masters` \u6216\u8005 `devops-team` \u7b49\u3002 * \u9644\u52a0\u5b57\u6bb5\uff1a\u4e00\u7ec4\u989d\u5916\u7684\u952e-\u503c\u6620\u5c04\uff0c\u952e\u662f\u5b57\u7b26\u4e32\uff0c\u503c\u662f\u4e00\u7ec4\u5b57\u7b26\u4e32\uff1b\u7528\u6765\u4fdd\u5b58\u4e00\u4e9b\u9274\u6743\u7ec4\u4ef6\u53ef\u80fd \u89c9\u5f97\u6709\u7528\u7684\u989d\u5916\u4fe1\u606f\u3002 \u6240\u6709\uff08\u5c5e\u6027\uff09\u503c\u5bf9\u4e8e\u8eab\u4efd\u8ba4\u8bc1\u7cfb\u7edf\u800c\u8a00\u90fd\u662f\u4e0d\u900f\u660e\u7684\uff0c\u53ea\u6709\u88ab [\u9274\u6743\u7ec4\u4ef6](/zh/docs/reference/access-authn-authz/authorization/) \u89e3\u91ca\u8fc7\u4e4b\u540e\u624d\u6709\u610f\u4e49\u3002 \u4f60\u53ef\u4ee5\u540c\u65f6\u542f\u7528\u591a\u79cd\u8eab\u4efd\u8ba4\u8bc1\u65b9\u6cd5\uff0c\u5e76\u4e14\u4f60\u901a\u5e38\u4f1a\u81f3\u5c11\u4f7f\u7528\u4e24\u79cd\u65b9\u6cd5\uff1a - \u9488\u5bf9\u670d\u52a1\u8d26\u53f7\u4f7f\u7528\u670d\u52a1\u8d26\u53f7\u4ee4\u724c - \u81f3\u5c11\u53e6\u5916\u4e00\u79cd\u65b9\u6cd5\u5bf9\u7528\u6237\u7684\u8eab\u4efd\u8fdb\u884c\u8ba4\u8bc1 \u5f53\u96c6\u7fa4\u4e2d\u542f\u7528\u4e86\u591a\u4e2a\u8eab\u4efd\u8ba4\u8bc1\u6a21\u5757\u65f6\uff0c\u7b2c\u4e00\u4e2a\u6210\u529f\u5730\u5bf9\u8bf7\u6c42\u5b8c\u6210\u8eab\u4efd\u8ba4\u8bc1\u7684\u6a21\u5757\u4f1a \u76f4\u63a5\u505a\u51fa\u8bc4\u4f30\u51b3\u5b9a\u3002API \u670d\u52a1\u5668\u5e76\u4e0d\u4fdd\u8bc1\u8eab\u4efd\u8ba4\u8bc1\u6a21\u5757\u7684\u8fd0\u884c\u987a\u5e8f\u3002 \u5bf9\u4e8e\u6240\u6709\u901a\u8fc7\u8eab\u4efd\u8ba4\u8bc1\u7684\u7528\u6237\uff0c`system:authenticated` \u7ec4\u90fd\u4f1a\u88ab\u6dfb\u52a0\u5230\u5176\u7ec4\u5217\u8868\u4e2d\u3002 \u4e0e\u5176\u5b83\u8eab\u4efd\u8ba4\u8bc1\u534f\u8bae\uff08LDAP\u3001SAML\u3001Kerberos\u3001X509 \u7684\u66ff\u4ee3\u6a21\u5f0f\u7b49\u7b49\uff09\u90fd\u53ef\u4ee5\u901a\u8fc7 \u4f7f\u7528\u4e00\u4e2a[\u8eab\u4efd\u8ba4\u8bc1\u4ee3\u7406](#authenticating-proxy)\u6216 [\u8eab\u4efd\u8ba4\u8bc1 Webhoook](#webhook-token-authentication)\u6765\u5b9e\u73b0\u3002 ### X509 \u5ba2\u6237\u8bc1\u4e66 {#x509-client-certs} \u901a\u8fc7\u7ed9 API \u670d\u52a1\u5668\u4f20\u9012 `--client-ca-file=SOMEFILE` \u9009\u9879\uff0c\u5c31\u53ef\u4ee5\u542f\u52a8\u5ba2\u6237\u7aef\u8bc1\u4e66\u8eab\u4efd\u8ba4\u8bc1\u3002 \u6240\u5f15\u7528\u7684\u6587\u4ef6\u5fc5\u987b\u5305\u542b\u4e00\u4e2a\u6216\u8005\u591a\u4e2a\u8bc1\u4e66\u673a\u6784\uff0c\u7528\u6765\u9a8c\u8bc1\u5411 API \u670d\u52a1\u5668\u63d0\u4f9b\u7684\u5ba2\u6237\u7aef\u8bc1\u4e66\u3002 \u5982\u679c\u63d0\u4f9b\u4e86\u5ba2\u6237\u7aef\u8bc1\u4e66\u5e76\u4e14\u8bc1\u4e66\u88ab\u9a8c\u8bc1\u901a\u8fc7\uff0c\u5219 subject \u4e2d\u7684\u516c\u5171\u540d\u79f0\uff08Common Name\uff09\u5c31\u88ab \u4f5c\u4e3a\u8bf7\u6c42\u7684\u7528\u6237\u540d\u3002 \u81ea Kubernetes 1.4 \u5f00\u59cb\uff0c\u5ba2\u6237\u7aef\u8bc1\u4e66\u8fd8\u53ef\u4ee5\u901a\u8fc7\u8bc1\u4e66\u7684 organization \u5b57\u6bb5\u6807\u660e\u7528\u6237\u7684\u7ec4\u6210\u5458\u4fe1\u606f\u3002 \u8981\u5305\u542b\u7528\u6237\u7684\u591a\u4e2a\u7ec4\u6210\u5458\u4fe1\u606f\uff0c\u53ef\u4ee5\u5728\u8bc1\u4e66\u79cd\u5305\u542b\u591a\u4e2a organization \u5b57\u6bb5\u3002 \u4f8b\u5982\uff0c\u4f7f\u7528 `openssl` \u547d\u4ee4\u884c\u5de5\u5177\u751f\u6210\u4e00\u4e2a\u8bc1\u4e66\u7b7e\u540d\u8bf7\u6c42\uff1a ``` bash openssl req -new -key jbeda.pem -out jbeda-csr.pem -subj \"/CN=jbeda/O=app1/O=app2\" ``` \u6b64\u547d\u4ee4\u5c06\u4f7f\u7528\u7528\u6237\u540d `jbeda` \u751f\u6210\u4e00\u4e2a\u8bc1\u4e66\u7b7e\u540d\u8bf7\u6c42\uff08CSR\uff09\uff0c\u4e14\u8be5\u7528\u6237\u5c5e\u4e8e \"app\" \u548c \"app2\" \u4e24\u4e2a\u7528\u6237\u7ec4\u3002 \u53c2\u9605[\u7ba1\u7406\u8bc1\u4e66](/zh/docs/concepts/cluster-administration/certificates/)\u4e86\u89e3\u5982\u4f55\u751f\u6210\u5ba2\u6237\u7aef\u8bc1\u4e66\u3002 ### \u9759\u6001\u4ee4\u724c\u6587\u4ef6 {#static-token-file} \u5f53 API \u670d\u52a1\u5668\u7684\u547d\u4ee4\u884c\u8bbe\u7f6e\u4e86 `--token-auth-file=SOMEFILE` \u9009\u9879\u65f6\uff0c\u4f1a\u4ece\u6587\u4ef6\u4e2d \u8bfb\u53d6\u6301\u6709\u8005\u4ee4\u724c\u3002\u76ee\u524d\uff0c\u4ee4\u724c\u4f1a\u957f\u671f\u6709\u6548\uff0c\u5e76\u4e14\u5728\u4e0d\u91cd\u542f API \u670d\u52a1\u5668\u7684\u60c5\u51b5\u4e0b \u65e0\u6cd5\u66f4\u6539\u4ee4\u724c\u5217\u8868\u3002 \u4ee4\u724c\u6587\u4ef6\u662f\u4e00\u4e2a CSV \u6587\u4ef6\uff0c\u5305\u542b\u81f3\u5c11 3 \u4e2a\u5217\uff1a\u4ee4\u724c\u3001\u7528\u6237\u540d\u548c\u7528\u6237\u7684 UID\u3002 \u5176\u4f59\u5217\u88ab\u89c6\u4e3a\u53ef\u9009\u7684\u7ec4\u540d\u3002 {{< note >}} \u5982\u679c\u8981\u8bbe\u7f6e\u7684\u7ec4\u540d\u4e0d\u6b62\u4e00\u4e2a\uff0c\u5219\u5bf9\u5e94\u7684\u5217\u5fc5\u987b\u7528\u53cc\u5f15\u53f7\u62ec\u8d77\u6765\uff0c\u4f8b\u5982 ```conf token,user,uid,\"group1,group2,group3\" ``` {{< /note >}} #### \u5728\u8bf7\u6c42\u4e2d\u653e\u5165\u6301\u6709\u8005\u4ee4\u724c {#putting-a-bearer-token-in-a-request} \u5f53\u4f7f\u7528\u6301\u6709\u8005\u4ee4\u724c\u6765\u5bf9\u67d0 HTTP \u5ba2\u6237\u7aef\u6267\u884c\u8eab\u4efd\u8ba4\u8bc1\u65f6\uff0cAPI \u670d\u52a1\u5668\u5e0c\u671b\u770b\u5230 \u4e00\u4e2a\u540d\u4e3a `Authorization` \u7684 HTTP \u5934\uff0c\u5176\u503c\u683c\u5f0f\u4e3a `Bearer THETOKEN`\u3002 \u6301\u6709\u8005\u4ee4\u724c\u5fc5\u987b\u662f\u4e00\u4e2a\u53ef\u4ee5\u653e\u5165 HTTP \u5934\u90e8\u503c\u5b57\u6bb5\u7684\u5b57\u7b26\u5e8f\u5217\uff0c\u81f3\u591a\u53ef\u4f7f\u7528 HTTP \u7684\u7f16\u7801\u548c\u5f15\u7528\u673a\u5236\u3002 \u4f8b\u5982\uff1a\u5982\u679c\u6301\u6709\u8005\u4ee4\u724c\u4e3a `31ada4fd-adec-460c-809a-9e56ceb75269`\uff0c\u5219\u5176 \u51fa\u73b0\u5728 HTTP \u5934\u90e8\u65f6\u5982\u4e0b\u6240\u793a\uff1a ```http Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269 ``` ### \u542f\u52a8\u5f15\u5bfc\u4ee4\u724c {#bootstrap-tokens} {{< feature-state for_k8s_version=\"v1.18\" state=\"stable\" >}} \u4e3a\u4e86\u652f\u6301\u5e73\u6ed1\u5730\u542f\u52a8\u5f15\u5bfc\u65b0\u7684\u96c6\u7fa4\uff0cKubernetes \u5305\u542b\u4e86\u4e00\u79cd\u52a8\u6001\u7ba1\u7406\u7684\u6301\u6709\u8005\u4ee4\u724c\u7c7b\u578b\uff0c \u79f0\u4f5c *\u542f\u52a8\u5f15\u5bfc\u4ee4\u724c\uff08Bootstrap Token\uff09*\u3002 \u8fd9\u4e9b\u4ee4\u724c\u4ee5 Secret \u7684\u5f62\u5f0f\u4fdd\u5b58\u5728 `kube-system` \u540d\u5b57\u7a7a\u95f4\u4e2d\uff0c\u53ef\u4ee5\u88ab\u52a8\u6001\u7ba1\u7406\u548c\u521b\u5efa\u3002 \u63a7\u5236\u5668\u7ba1\u7406\u5668\u5305\u542b\u7684 `TokenCleaner` \u63a7\u5236\u5668\u80fd\u591f\u5728\u542f\u52a8\u5f15\u5bfc\u4ee4\u724c\u8fc7\u671f\u65f6\u5c06\u5176\u5220\u9664\u3002 \u8fd9\u4e9b\u4ee4\u724c\u7684\u683c\u5f0f\u4e3a `[a-z0-9]{6}.[a-z0-9]{16}`\u3002\u7b2c\u4e00\u4e2a\u90e8\u5206\u662f\u4ee4\u724c\u7684 ID\uff1b\u7b2c\u4e8c\u4e2a\u90e8\u5206 \u662f\u4ee4\u724c\u7684 Secret\u3002\u4f60\u53ef\u4ee5\u7528\u5982\u4e0b\u6240\u793a\u7684\u65b9\u5f0f\u6765\u5728 HTTP \u5934\u90e8\u8bbe\u7f6e\u4ee4\u724c\uff1a ```http Authorization: Bearer 781292.db7bc3a58fc5f07e ``` \u4f60\u5fc5\u987b\u5728 API \u670d\u52a1\u5668\u4e0a\u8bbe\u7f6e `--enable-bootstrap-token-auth` \u6807\u5fd7\u6765\u542f\u7528\u57fa\u4e8e\u542f\u52a8 \u5f15\u5bfc\u4ee4\u724c\u7684\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6\u3002 \u4f60\u5fc5\u987b\u901a\u8fc7\u63a7\u5236\u5668\u7ba1\u7406\u5668\u7684 `--controllers` \u6807\u5fd7\u6765\u542f\u7528 TokenCleaner \u63a7\u5236\u5668\uff1b \u8fd9\u53ef\u4ee5\u901a\u8fc7\u7c7b\u4f3c `--controllers=*,tokencleaner` \u8fd9\u79cd\u8bbe\u7f6e\u6765\u505a\u5230\u3002 \u5982\u679c\u4f60\u4f7f\u7528 `kubeadm` \u6765\u542f\u52a8\u5f15\u5bfc\u65b0\u7684\u96c6\u7fa4\uff0c\u8be5\u5de5\u5177\u4f1a\u5e2e\u4f60\u5b8c\u6210\u8fd9\u4e9b\u8bbe\u7f6e\u3002 \u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6\u7684\u8ba4\u8bc1\u7ed3\u679c\u4e3a `system:bootstrap:<\u4ee4\u724c ID>`\uff0c\u8be5\u7528\u6237\u5c5e\u4e8e `system:bootstrappers` \u7528\u6237\u7ec4\u3002 \u8fd9\u91cc\u7684\u7528\u6237\u540d\u548c\u7ec4\u8bbe\u7f6e\u90fd\u662f\u6709\u610f\u8bbe\u8ba1\u6210\u8fd9\u6837\uff0c\u5176\u76ee\u7684\u662f\u963b\u6b62\u7528\u6237\u5728\u542f\u52a8\u5f15\u5bfc\u96c6\u7fa4\u4e4b\u540e \u7ee7\u7eed\u4f7f\u7528\u8fd9\u4e9b\u4ee4\u724c\u3002 \u8fd9\u91cc\u7684\u7528\u6237\u540d\u548c\u7ec4\u540d\u53ef\u4ee5\u7528\u6765\uff08\u5e76\u4e14\u5df2\u7ecf\u88ab `kubeadm` \u7528\u6765\uff09\u6784\u9020\u5408\u9002\u7684\u9274\u6743 \u7b56\u7565\uff0c\u4ee5\u5b8c\u6210\u542f\u52a8\u5f15\u5bfc\u65b0\u96c6\u7fa4\u7684\u5de5\u4f5c\u3002 \u8bf7\u53c2\u9605[\u542f\u52a8\u5f15\u5bfc\u4ee4\u724c](/zh/docs/reference/access-authn-authz/bootstrap-tokens/) \u4ee5\u4e86\u89e3\u5173\u4e8e\u542f\u52a8\u5f15\u5bfc\u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6\u4e0e\u63a7\u5236\u5668\u7684\u66f4\u6df1\u5165\u7684\u4fe1\u606f\uff0c\u4ee5\u53ca\u5982\u4f55\u4f7f\u7528 `kubeadm` \u6765\u7ba1\u7406\u8fd9\u4e9b\u4ee4\u724c\u3002 ### Static Password File \u901a\u8fc7\u5411 API \u670d\u52a1\u5668\u4f20\u9012 `--basic-auth-file=SOMEFILE` \u9009\u9879\u53ef\u4ee5\u542f\u7528\u57fa\u672c\u7684 \u8eab\u4efd\u8ba4\u8bc1\u3002\u76ee\u524d\uff0c\u57fa\u672c\u8eab\u4efd\u8ba4\u8bc1\u6240\u6d89\u53ca\u7684\u51ed\u636e\u4fe1\u606f\u4f1a\u957f\u671f\u6709\u6548\uff0c\u5e76\u4e14\u5728\u4e0d\u91cd\u542f API \u670d\u52a1\u5668\u7684\u60c5\u51b5\u4e0b\u65e0\u6cd5\u6539\u53d8\u7528\u6237\u7684\u5bc6\u7801\u3002 \u8981\u6ce8\u610f\u7684\u662f\uff0c\u5bf9\u57fa\u672c\u8eab\u4efd\u8ba4\u8bc1\u7684\u652f\u6301\u76ee\u524d\u4ec5\u662f\u51fa\u4e8e\u65b9\u4fbf\u6027\u8003\u8651\u3002 \u4e0e\u6b64\u540c\u65f6\u6211\u4eec\u6b63\u5728\u589e\u5f3a\u524d\u8ff0\u7684\u3001\u66f4\u4e3a\u5b89\u5168\u7684\u6a21\u5f0f\u7684\u6613\u7528\u6027\u3002 \u57fa\u672c\u8eab\u4efd\u8ba4\u8bc1\u6570\u636e\u6587\u4ef6\u662f\u4e00\u4e2a CSV \u6587\u4ef6\uff0c\u5305\u542b\u81f3\u5c11 3 \u5217\uff1a\u5bc6\u7801\u3001\u7528\u6237\u540d\u548c\u7528\u6237 ID\u3002 \u5728 Kuernetes 1.6 \u53ca\u540e\u7eed\u7248\u672c\u4e2d\uff0c\u4f60\u53ef\u4ee5\u6307\u5b9a\u4e00\u4e2a\u53ef\u9009\u7684\u7b2c 4 \u5217\uff0c\u5728\u5176\u4e2d\u7ed9\u51fa\u7528\u9017\u53f7 \u5206\u9694\u7684\u7528\u6237\u7ec4\u540d\u3002\u5982\u679c\u7528\u6237\u7ec4\u540d\u4e0d\u6b62\u4e00\u4e2a\uff0c\u4f60\u5fc5\u987b\u5c06\u7b2c 4 \u5217\u7684\u503c\u7528\u53cc\u5f15\u53f7\u62ec\u8d77\u6765\u3002 \u53c2\u89c1\u4e0b\u9762\u7684\u4f8b\u5b50\uff1a ```conf password,user,uid,\"group1,group2,group3\" ``` \u5f53\u5728 HTTP \u5ba2\u6237\u7aef\u4f7f\u7528\u57fa\u672c\u8eab\u4efd\u8ba4\u8bc1\u673a\u5236\u65f6\uff0cAPI \u670d\u52a1\u5668\u4f1a\u671f\u671b\u770b\u5230\u540d\u4e3a `Authorization` \u7684 HTTP \u5934\u90e8\uff0c\u5176\u503c\u5f62\u5982 `Basic USER:PASSWORD\u7684Base64\u7f16\u7801\u5b57\u7b26\u4e32` ### \u670d\u52a1\u8d26\u53f7\u4ee4\u724c {#service-account-tokens} \u670d\u52a1\u8d26\u53f7\uff08Service Account\uff09\u662f\u4e00\u79cd\u81ea\u52a8\u88ab\u542f\u7528\u7684\u7528\u6237\u8ba4\u8bc1\u673a\u5236\uff0c\u4f7f\u7528\u7ecf\u8fc7\u7b7e\u540d\u7684 \u6301\u6709\u8005\u4ee4\u724c\u6765\u9a8c\u8bc1\u8bf7\u6c42\u3002\u8be5\u63d2\u4ef6\u53ef\u63a5\u53d7\u4e24\u4e2a\u53ef\u9009\u53c2\u6570\uff1a * `--service-account-key-file` \u4e00\u4e2a\u5305\u542b\u7528\u6765\u4e3a\u6301\u6709\u8005\u4ee4\u724c\u7b7e\u540d\u7684 PEM \u7f16\u7801\u5bc6\u94a5\u3002 \u82e5\u672a\u6307\u5b9a\uff0c\u5219\u4f7f\u7528 API \u670d\u52a1\u5668\u7684 TLS \u79c1\u94a5\u3002 * `--service-account-lookup` \u5982\u679c\u542f\u7528\uff0c\u5219\u4ece API \u5220\u9664\u7684\u4ee4\u724c\u4f1a\u88ab\u56de\u6536\u3002 \u670d\u52a1\u8d26\u53f7\u901a\u5e38\u7531 API \u670d\u52a1\u5668\u81ea\u52a8\u521b\u5efa\u5e76\u901a\u8fc7 `ServiceAccount` [\u51c6\u5165\u63a7\u5236\u5668](/zh/docs/reference/access-authn-authz/admission-controllers/) \u5173\u8054\u5230\u96c6\u7fa4\u4e2d\u8fd0\u884c\u7684 Pod \u4e0a\u3002 \u6301\u6709\u8005\u4ee4\u724c\u4f1a\u6302\u8f7d\u5230 Pod \u4e2d\u53ef\u9884\u77e5\u7684\u4e3a\u4e4b\uff0c\u5141\u8bb8\u96c6\u7fa4\u5185\u8fdb\u7a0b\u4e0e API \u670d\u52a1\u5668\u901a\u4fe1\u3002 \u670d\u52a1\u8d26\u53f7\u4e5f\u53ef\u4ee5\u4f7f\u7528 Pod \u89c4\u7ea6\u7684 `serviceAccountName` \u5b57\u6bb5\u663e\u5f0f\u5730\u5173\u8054\u5230 Pod \u4e0a\u3002 {{< note >}} `serviceAccountName` \u901a\u5e38\u4f1a\u88ab\u5ffd\u7565\uff0c\u56e0\u4e3a\u5173\u8054\u5173\u7cfb\u662f\u81ea\u52a8\u5efa\u7acb\u7684\u3002 {{< /note >}} ```yaml apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment namespace: default spec: replicas: 3 template: metadata: # ... spec: serviceAccountName: bob-the-bot containers: - name: nginx image: nginx:1.14.2 ``` \u5728\u96c6\u7fa4\u5916\u90e8\u4f7f\u7528\u670d\u52a1\u8d26\u53f7\u6301\u6709\u8005\u4ee4\u724c\u4e5f\u662f\u5b8c\u5168\u5408\u6cd5\u7684\uff0c\u4e14\u53ef\u7528\u6765\u4e3a\u957f\u65f6\u95f4\u8fd0\u884c\u7684\u3001\u9700\u8981\u4e0e Kubernetes API \u670d\u52a1\u5668\u901a\u4fe1\u7684\u4efb\u52a1\u521b\u5efa\u6807\u8bc6\u3002\u8981\u624b\u52a8\u521b\u5efa\u670d\u52a1\u8d26\u53f7\uff0c\u53ef\u4ee5\u4f7f\u7528 `kubectl create serviceaccount <\u540d\u79f0>` \u547d\u4ee4\u3002\u6b64\u547d\u4ee4\u4f1a\u5728\u5f53\u524d\u7684\u540d\u5b57\u7a7a\u95f4\u4e2d\u751f\u6210\u4e00\u4e2a \u670d\u52a1\u8d26\u53f7\u548c\u4e00\u4e2a\u4e0e\u4e4b\u5173\u8054\u7684 Secret\u3002 ```bash kubectl create serviceaccount jenkins ``` ``` serviceaccount/jenkins created ``` \u67e5\u9a8c\u76f8\u5173\u8054\u7684 Secret\uff1a ```bash kubectl get serviceaccounts jenkins -o yaml ``` ```yaml apiVersion: v1 kind: ServiceAccount metadata: # ... secrets: - name: jenkins-token-1yvwg ``` \u6240\u521b\u5efa\u7684 Secret \u4e2d\u4f1a\u4fdd\u5b58 API \u670d\u52a1\u5668\u7684\u516c\u5f00\u7684 CA \u8bc1\u4e66\u548c\u4e00\u4e2a\u5df2\u7b7e\u540d\u7684 JSON Web \u4ee4\u724c\uff08JWT\uff09\u3002 ```bash kubectl get secret jenkins-token-1yvwg -o yaml ``` ```yaml apiVersion: v1 data: ca.crt: namespace: ZGVmYXVsdA== token: kind: Secret metadata: # ... type: kubernetes.io/service-account-token ``` {{< note >}} \u5b57\u6bb5\u503c\u662f\u6309 Base64 \u7f16\u7801\u7684\uff0c\u8fd9\u662f\u56e0\u4e3a Secret \u6570\u636e\u603b\u662f\u91c7\u7528 Base64 \u7f16\u7801\u6765\u5b58\u50a8\u3002 {{< /note >}} \u5df2\u7b7e\u540d\u7684 JWT \u53ef\u4ee5\u7528\u4f5c\u6301\u6709\u8005\u4ee4\u724c\uff0c\u5e76\u5c06\u88ab\u8ba4\u8bc1\u4e3a\u6240\u7ed9\u7684\u670d\u52a1\u8d26\u53f7\u3002 \u5173\u4e8e\u5982\u4f55\u5728\u8bf7\u6c42\u4e2d\u5305\u542b\u4ee4\u724c\uff0c\u8bf7\u53c2\u9605[\u524d\u6587](#putting-a-bearer-token-in-a-request)\u3002 \u901a\u5e38\uff0c\u8fd9\u4e9b Secret \u6570\u636e\u4f1a\u88ab\u6302\u8f7d\u5230 Pod \u4e2d\u4ee5\u4fbf\u96c6\u7fa4\u5185\u8bbf\u95ee API \u670d\u52a1\u5668\u65f6\u4f7f\u7528\uff0c \u4e0d\u8fc7\u4e5f\u53ef\u4ee5\u5728\u96c6\u7fa4\u5916\u90e8\u4f7f\u7528\u3002 \u670d\u52a1\u8d26\u53f7\u88ab\u8eab\u4efd\u8ba4\u8bc1\u540e\uff0c\u6240\u786e\u5b9a\u7684\u7528\u6237\u540d\u4e3a `system:serviceaccount:<\u540d\u5b57\u7a7a\u95f4>:<\u670d\u52a1\u8d26\u53f7>`\uff0c \u5e76\u88ab\u5206\u914d\u5230\u7528\u6237\u7ec4 `system:serviceaccounts` \u548c `system:serviceaccounts:<\u540d\u5b57\u7a7a\u95f4>`\u3002 \u8b66\u544a\uff1a\u7531\u4e8e\u670d\u52a1\u8d26\u53f7\u4ee4\u724c\u4fdd\u5b58\u5728 Secret \u5bf9\u8c61\u4e2d\uff0c\u4efb\u4f55\u80fd\u591f\u8bfb\u53d6\u8fd9\u4e9b Secret \u7684\u7528\u6237 \u90fd\u53ef\u4ee5\u88ab\u8ba4\u8bc1\u4e3a\u5bf9\u5e94\u7684\u670d\u52a1\u8d26\u53f7\u3002\u5728\u4e3a\u7528\u6237\u6388\u4e88\u8bbf\u95ee\u670d\u52a1\u8d26\u53f7\u7684\u6743\u9650\u65f6\uff0c\u4ee5\u53ca\u5bf9 Secret \u7684\u8bfb\u6743\u9650\u65f6\uff0c\u8981\u683c\u5916\u5c0f\u5fc3\u3002 ### OpenID Connect\uff08OIDC\uff09\u4ee4\u724c {#openid-connect-tokens} [OpenID Connect](https://openid.net/connect/) \u662f\u4e00\u79cd OAuth2 \u8ba4\u8bc1\u65b9\u5f0f\uff0c \u88ab\u67d0\u4e9b OAuth2 \u63d0\u4f9b\u8005\u652f\u6301\uff0c\u4f8b\u5982 Azure \u6d3b\u52a8\u76ee\u5f55\u3001Salesforce \u548c Google\u3002 \u534f\u8bae\u5bf9 OAuth2 \u7684\u4e3b\u8981\u6269\u5145\u4f53\u73b0\u5728\u6709\u4e00\u4e2a\u9644\u52a0\u5b57\u6bb5\u4f1a\u548c\u8bbf\u95ee\u4ee4\u724c\u4e00\u8d77\u8fd4\u56de\uff0c \u8fd9\u4e00\u5b57\u6bb5\u79f0\u4f5c [ID Token\uff08ID \u4ee4\u724c\uff09](https://openid.net/specs/openid-connect-core-1_0.html#IDToken)\u3002 ID \u4ee4\u724c\u662f\u4e00\u79cd\u7531\u670d\u52a1\u5668\u7b7e\u540d\u7684 JSON Web \u4ee4\u724c\uff08JWT\uff09\uff0c\u5176\u4e2d\u5305\u542b\u4e00\u4e9b\u53ef\u9884\u77e5\u7684\u5b57\u6bb5\uff0c \u4f8b\u5982\u7528\u6237\u7684\u90ae\u7bb1\u5730\u5740\uff0c \u8981\u8bc6\u522b\u7528\u6237\uff0c\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6\u4f7f\u7528 OAuth2 [\u4ee4\u724c\u54cd\u5e94](https://openid.net/specs/openid-connect-core-1_0.html#TokenResponse) \u4e2d\u7684 `id_token`\uff08\u800c\u975e `access_token`\uff09\u4f5c\u4e3a\u6301\u6709\u8005\u4ee4\u724c\u3002 \u5173\u4e8e\u5982\u4f55\u5728\u8bf7\u6c42\u4e2d\u8bbe\u7f6e\u4ee4\u724c\uff0c\u53ef\u53c2\u89c1[\u524d\u6587](#putting-a-bearer-token-in-a-request)\u3002 ![Kubernetes OpenID Connect Flow](/images/docs/admin/k8s_oidc_login.svg) 1. \u767b\u5f55\u5230\u4f60\u7684\u8eab\u4efd\u670d\u52a1\uff08Identity Provider\uff09 2. \u4f60\u7684\u8eab\u4efd\u670d\u52a1\u5c06\u4e3a\u4f60\u63d0\u4f9b `access_token`\u3001`id_token` \u548c `refresh_token` 3. \u5728\u4f7f\u7528 `kubectl` \u65f6\uff0c\u5c06 `id_token` \u8bbe\u7f6e\u4e3a `--token` \u6807\u5fd7\u503c\uff0c\u6216\u8005\u5c06\u5176\u76f4\u63a5\u6dfb\u52a0\u5230 `kubeconfig` \u4e2d 4. `kubectl` \u5c06\u4f60\u7684 `id_token` \u653e\u5230\u4e00\u4e2a\u79f0\u4f5c `Authorization` \u7684\u5934\u90e8\uff0c\u53d1\u9001\u7ed9 API \u670d\u52a1\u5668 5. API \u670d\u52a1\u5668\u5c06\u8d1f\u8d23\u901a\u8fc7\u68c0\u67e5\u914d\u7f6e\u4e2d\u5f15\u7528\u7684\u8bc1\u4e66\u6765\u786e\u8ba4 JWT \u7684\u7b7e\u540d\u662f\u5408\u6cd5\u7684 6. \u68c0\u67e5\u786e\u8ba4 `id_token` \u5c1a\u672a\u8fc7\u671f 7. \u786e\u8ba4\u7528\u6237\u6709\u6743\u9650\u6267\u884c\u64cd\u4f5c 8. \u9274\u6743\u6210\u529f\u4e4b\u540e\uff0cAPI \u670d\u52a1\u5668\u5411 `kubectl` \u8fd4\u56de\u54cd\u5e94 9. `kubectl` \u5411\u7528\u6237\u63d0\u4f9b\u53cd\u9988\u4fe1\u606f \u7531\u4e8e\u7528\u6765\u9a8c\u8bc1\u4f60\u662f\u8c01\u7684\u6240\u6709\u6570\u636e\u90fd\u5728 `id_token` \u4e2d\uff0cKubernetes \u4e0d\u9700\u8981\u518d\u53bb\u8054\u7cfb \u8eab\u4efd\u670d\u52a1\u3002\u5728\u4e00\u4e2a\u6240\u6709\u8bf7\u6c42\u90fd\u662f\u65e0\u72b6\u6001\u8bf7\u6c42\u7684\u6a21\u578b\u4e2d\uff0c\u8fd9\u4e00\u5de5\u4f5c\u65b9\u5f0f\u53ef\u4ee5\u4f7f\u5f97\u8eab\u4efd\u8ba4\u8bc1 \u7684\u89e3\u51b3\u65b9\u6848\u66f4\u5bb9\u6613\u5904\u7406\u5927\u89c4\u6a21\u8bf7\u6c42\u3002\u4e0d\u8fc7\uff0c\u6b64\u8bbf\u95ee\u4e5f\u6709\u4e00\u4e9b\u6311\u6218\uff1a 1. Kubernetes \u6ca1\u6709\u63d0\u4f9b\u7528\u6765\u89e6\u53d1\u8eab\u4efd\u8ba4\u8bc1\u8fc7\u7a0b\u7684 \"Web \u754c\u9762\"\u3002 \u56e0\u4e3a\u4e0d\u5b58\u5728\u7528\u6765\u6536\u96c6\u7528\u6237\u51ed\u636e\u7684\u6d4f\u89c8\u5668\u6216\u7528\u6237\u63a5\u53e3\uff0c\u4f60\u5fc5\u987b\u81ea\u5df1\u5148\u884c\u5b8c\u6210 \u5bf9\u8eab\u4efd\u670d\u52a1\u7684\u8ba4\u8bc1\u8fc7\u7a0b\u3002 2. `id_token` \u4ee4\u724c\u4e0d\u53ef\u6536\u56de\u3002\u56e0\u5176\u5c5e\u6027\u7c7b\u4f3c\u4e8e\u8bc1\u4e66\uff0c\u5176\u751f\u547d\u671f\u4e00\u822c\u5f88\u77ed\uff08\u53ea\u6709\u51e0\u5206\u949f\uff09\uff0c \u6240\u4ee5\uff0c\u6bcf\u9694\u51e0\u5206\u949f\u5c31\u8981\u83b7\u5f97\u4e00\u4e2a\u65b0\u7684\u4ee4\u724c\u8fd9\u4ef6\u4e8b\u53ef\u80fd\u5f88\u8ba9\u4eba\u5934\u75bc\u3002 3. \u5982\u679c\u4e0d\u4f7f\u7528 `kubectl proxy` \u547d\u4ee4\u6216\u8005\u4e00\u4e2a\u80fd\u591f\u6ce8\u5165 `id_token` \u7684\u53cd\u5411\u4ee3\u7406\uff0c \u5411 Kubernetes \u63a7\u5236\u9762\u677f\u6267\u884c\u8eab\u4efd\u8ba4\u8bc1\u662f\u5f88\u56f0\u96be\u7684\u3002 #### \u914d\u7f6e API \u670d\u52a1\u5668 {#configuring-the-api-server} \u8981\u542f\u7528\u6b64\u63d2\u4ef6\uff0c\u987b\u5728 API \u670d\u52a1\u5668\u4e0a\u914d\u7f6e\u4ee5\u4e0b\u6807\u5fd7\uff1a | \u53c2\u6570 | \u63cf\u8ff0 | \u793a\u4f8b | \u5fc5\u9700\uff1f | | --------- | ----------- | ------- | ------- | | `--oidc-issuer-url` | \u5141\u8bb8 API \u670d\u52a1\u5668\u53d1\u73b0\u516c\u5f00\u7684\u7b7e\u540d\u5bc6\u94a5\u7684\u670d\u52a1\u7684 URL\u3002\u53ea\u63a5\u53d7\u6a21\u5f0f\u4e3a `https://` \u7684 URL\u3002\u6b64\u503c\u901a\u5e38\u8bbe\u7f6e\u4e3a\u670d\u52a1\u7684\u53d1\u73b0 URL\uff0c\u4e0d\u542b\u8def\u5f84\u3002\u4f8b\u5982\uff1a\"https://accounts.google.com\" \u6216 \"https://login.salesforce.com\"\u3002\u6b64 URL \u5e94\u6307\u5411 .well-known/openid-configuration \u4e0b\u4e00\u5c42\u7684\u8def\u5f84\u3002 | \u5982\u679c\u53d1\u73b0 URL \u662f `https://accounts.google.com/.well-known/openid-configuration`\uff0c\u5219\u6b64\u503c\u5e94\u4e3a `https://accounts.google.com` | \u662f | | `--oidc-client-id` | \u6240\u6709\u4ee4\u724c\u90fd\u5e94\u53d1\u653e\u7ed9\u6b64\u5ba2\u6237 ID\u3002 | kubernetes | \u662f | | `--oidc-username-claim` | \u7528\u4f5c\u7528\u6237\u540d\u7684 JWT \u7533\u9886\uff08JWT Claim\uff09\u3002\u9ed8\u8ba4\u60c5\u51b5\u4e0b\u4f7f\u7528 `sub` \u503c\uff0c\u5373\u6700\u7ec8\u7528\u6237\u7684\u4e00\u4e2a\u552f\u4e00\u7684\u6807\u8bc6\u7b26\u3002\u7ba1\u7406\u5458\u4e5f\u53ef\u4ee5\u9009\u62e9\u5176\u4ed6\u7533\u9886\uff0c\u4f8b\u5982 `email` \u6216\u8005 `name`\uff0c\u53d6\u51b3\u4e8e\u6240\u7528\u7684\u8eab\u4efd\u670d\u52a1\u3002\u4e0d\u8fc7\uff0c\u9664\u4e86 `email` \u4e4b\u5916\u7684\u7533\u9886\u90fd\u4f1a\u88ab\u6dfb\u52a0\u4ee4\u724c\u53d1\u653e\u8005\u7684 URL \u4f5c\u4e3a\u524d\u7f00\uff0c\u4ee5\u514d\u4e0e\u5176\u4ed6\u63d2\u4ef6\u4ea7\u751f\u547d\u540d\u51b2\u7a81\u3002 | sub | \u5426 | | `--oidc-username-prefix` | \u8981\u6dfb\u52a0\u5230\u7528\u6237\u540d\u7533\u9886\u4e4b\u524d\u7684\u524d\u7f00\uff0c\u7528\u6765\u907f\u514d\u4e0e\u73b0\u6709\u7528\u6237\u540d\u53d1\u751f\u51b2\u7a81\uff08\u4f8b\u5982\uff1a`system:` \u7528\u6237\uff09\u3002\u4f8b\u5982\uff0c\u6b64\u6807\u5fd7\u503c\u4e3a `oidc:` \u65f6\u5c06\u521b\u5efa\u5f62\u5982 `oidc:jane.doe` \u7684\u7528\u6237\u540d\u3002\u5982\u679c\u6b64\u6807\u5fd7\u672a\u8bbe\u7f6e\uff0c\u4e14 `--oidc-username-claim` \u6807\u5fd7\u503c\u4e0d\u662f `email`\uff0c\u5219\u9ed8\u8ba4\u524d\u7f00\u4e3a `<\u4ee4\u724c\u53d1\u653e\u8005\u7684 URL>#`\uff0c\u5176\u4e2d `<\u4ee4\u724c\u53d1\u653e\u8005 URL >` \u7684\u503c\u53d6\u81ea `--oidc-issuer-url` \u6807\u5fd7\u7684\u8bbe\u5b9a\u3002\u6b64\u6807\u5fd7\u503c\u4e3a `-` \u65f6\uff0c\u610f\u5473\u7740\u7981\u6b62\u6dfb\u52a0\u7528\u6237\u540d\u524d\u7f00\u3002 | `oidc:` | \u5426 | | `--oidc-groups-claim` | \u7528\u4f5c\u7528\u6237\u7ec4\u540d\u7684 JWT \u7533\u9886\u3002\u5982\u679c\u6240\u6307\u5b9a\u7684\u7533\u9886\u786e\u5b9e\u5b58\u5728\uff0c\u5219\u5176\u503c\u5fc5\u987b\u662f\u4e00\u4e2a\u5b57\u7b26\u4e32\u6570\u7ec4\u3002 | groups | \u5426 | | `--oidc-groups-prefix` | \u6dfb\u52a0\u5230\u7ec4\u7533\u9886\u7684\u524d\u7f00\uff0c\u7528\u6765\u907f\u514d\u4e0e\u73b0\u6709\u7528\u6237\u7ec4\u540d\uff08\u5982\uff1a`system:` \u7ec4\uff09\u53d1\u751f\u51b2\u7a81\u3002\u4f8b\u5982\uff0c\u6b64\u6807\u5fd7\u503c\u4e3a `oidc:` \u65f6\uff0c\u6240\u5f97\u5230\u7684\u7528\u6237\u7ec4\u540d\u5f62\u5982 `oidc:engineering` \u548c `oidc:infra`\u3002 | `oidc:` | \u5426 | | `--oidc-required-claim` | \u53d6\u503c\u4e3a\u4e00\u4e2a key=value \u5076\u5bf9\uff0c\u610f\u4e3a ID \u4ee4\u724c\u4e2d\u5fc5\u987b\u5b58\u5728\u7684\u7533\u9886\u3002\u5982\u679c\u8bbe\u7f6e\u4e86\u6b64\u6807\u5fd7\uff0c\u5219 ID \u4ee4\u724c\u4f1a\u88ab\u68c0\u67e5\u4ee5\u786e\u5b9a\u662f\u5426\u5305\u542b\u53d6\u503c\u5339\u914d\u7684\u7533\u9886\u3002\u6b64\u6807\u5fd7\u53ef\u591a\u6b21\u91cd\u590d\uff0c\u4ee5\u6307\u5b9a\u591a\u4e2a\u7533\u9886\u3002 | `claim=value` | \u5426 | | `--oidc-ca-file` | \u6307\u5411\u4e00\u4e2a CA \u8bc1\u4e66\u7684\u8def\u5f84\uff0c\u8be5 CA \u8d1f\u8d23\u5bf9\u4f60\u7684\u8eab\u4efd\u670d\u52a1\u7684 Web \u8bc1\u4e66\u63d0\u4f9b\u7b7e\u540d\u3002\u9ed8\u8ba4\u503c\u4e3a\u5bbf\u4e3b\u7cfb\u7edf\u7684\u6839 CA\u3002 | `/etc/kubernetes/ssl/kc-ca.pem` | \u5426 | \u5f88\u91cd\u8981\u7684\u4e00\u70b9\u662f\uff0cAPI \u670d\u52a1\u5668\u5e76\u975e\u4e00\u4e2a OAuth2 \u5ba2\u6237\u7aef\uff0c\u76f8\u53cd\uff0c\u5b83\u53ea\u80fd\u88ab\u914d\u7f6e\u4e3a \u4fe1\u4efb\u67d0\u4e00\u4e2a\u4ee4\u724c\u53d1\u653e\u8005\u3002\u8fd9\u4f7f\u5f97\u4f7f\u7528\u516c\u5171\u670d\u52a1\uff08\u5982 Google\uff09\u7684\u7528\u6237\u53ef\u4ee5\u4e0d\u4fe1\u4efb\u53d1\u653e\u7ed9 \u7b2c\u4e09\u65b9\u7684\u51ed\u636e\u3002 \u5982\u679c\u7ba1\u7406\u5458\u5e0c\u671b\u4f7f\u7528\u591a\u4e2a OAuth \u5ba2\u6237\u7aef\uff0c\u4ed6\u4eec\u5e94\u8be5\u7814\u7a76\u4e00\u4e0b\u90a3\u4e9b\u652f\u6301 `azp` \uff08Authorized Party\uff0c\u88ab\u6388\u6743\u65b9\uff09\u7533\u9886\u7684\u670d\u52a1\u3002 `azp` \u662f\u4e00\u79cd\u5141\u8bb8\u67d0\u5ba2\u6237\u7aef\u4ee3\u66ff\u53e6\u4e00\u5ba2\u6237\u7aef\u53d1\u653e\u4ee4\u724c\u7684\u673a\u5236\u3002 Kubernetes \u5e76\u672a\u63d0\u4f9b OpenID Connect \u7684\u8eab\u4efd\u670d\u52a1\u3002 \u4f60\u53ef\u4ee5\u4f7f\u7528\u73b0\u6709\u7684\u516c\u5171\u7684 OpenID Connect \u8eab\u4efd\u670d\u52a1\uff08\u4f8b\u5982 Google \u6216\u8005 [\u5176\u4ed6\u670d\u52a1](https://connect2id.com/products/nimbus-oauth-openid-connect-sdk/openid-connect-providers)\uff09\u3002 \u6216\u8005\uff0c\u4f60\u4e5f\u53ef\u4ee5\u9009\u62e9\u81ea\u5df1\u8fd0\u884c\u4e00\u4e2a\u8eab\u4efd\u670d\u52a1\uff0c\u4f8b\u5982 CoreOS [dex](https://github.com/coreos/dex)\u3001 [Keycloak](https://github.com/keycloak/keycloak)\u3001 CloudFoundry [UAA](https://github.com/cloudfoundry/uaa) \u6216\u8005 Tremolo Security \u7684 [OpenUnison](https://github.com/tremolosecurity/openunison)\u3002 \u8981\u5728 Kubernetes \u73af\u5883\u4e2d\u4f7f\u7528\u67d0\u8eab\u4efd\u670d\u52a1\uff0c\u8be5\u670d\u52a1\u5fc5\u987b\uff1a 1. \u652f\u6301 [OpenID connect \u53d1\u73b0](https://openid.net/specs/openid-connect-discovery-1_0.html)\uff1b \u4f46\u4e8b\u5b9e\u4e0a\u5e76\u975e\u6240\u6709\u670d\u52a1\u90fd\u5177\u5907\u6b64\u80fd\u529b 2. \u8fd0\u884c TLS \u534f\u8bae\u4e14\u6240\u4f7f\u7528\u7684\u52a0\u5bc6\u7ec4\u4ef6\u90fd\u672a\u8fc7\u65f6 3. \u62e5\u6709\u7531 CA \u7b7e\u540d\u7684\u8bc1\u4e66\uff08\u5373\u4f7f CA \u4e0d\u662f\u5546\u4e1a CA \u6216\u8005\u662f\u81ea\u7b7e\u540d\u7684 CA \u4e5f\u53ef\u4ee5\uff09 \u5173\u4e8e\u4e0a\u8ff0\u7b2c\u4e09\u6761\u9700\u6c42\uff0c\u5373\u8981\u6c42\u5177\u5907 CA \u7b7e\u540d\u7684\u8bc1\u4e66\uff0c\u6709\u4e00\u4e9b\u989d\u5916\u7684\u6ce8\u610f\u4e8b\u9879\u3002 \u5982\u679c\u4f60\u90e8\u7f72\u4e86\u81ea\u5df1\u7684\u8eab\u4efd\u670d\u52a1\uff0c\u800c\u4e0d\u662f\u4f7f\u7528\u4e91\u5382\u5546\uff08\u5982 Google \u6216 Microsoft\uff09\u6240\u63d0\u4f9b\u7684\u670d\u52a1\uff0c \u4f60\u5fc5\u987b\u5bf9\u8eab\u4efd\u670d\u52a1\u7684 Web \u670d\u52a1\u5668\u8bc1\u4e66\u8fdb\u884c\u7b7e\u540d\uff0c\u7b7e\u540d\u6240\u7528\u8bc1\u4e66\u7684 `CA` \u6807\u5fd7\u8981\u8bbe\u7f6e\u4e3a `TRUE`\uff0c\u5373\u4f7f\u7528\u7684\u662f\u81ea\u7b7e\u540d\u8bc1\u4e66\u3002\u8fd9\u662f\u56e0\u4e3a GoLang \u7684 TLS \u5ba2\u6237\u7aef\u5b9e\u73b0\u5bf9\u8bc1\u4e66\u9a8c\u8bc1 \u6807\u51c6\u65b9\u9762\u6709\u975e\u5e38\u4e25\u683c\u7684\u8981\u6c42\u3002\u5982\u679c\u4f60\u624b\u5934\u6ca1\u6709\u73b0\u6210\u7684 CA \u8bc1\u4e66\uff0c\u53ef\u4ee5\u4f7f\u7528 CoreOS \u56e2\u961f\u6240\u5f00\u53d1\u7684[\u8fd9\u4e2a\u811a\u672c](https://github.com/coreos/dex/blob/1ee5920c54f5926d6468d2607c728b71cfe98092/examples/k8s/gencert.sh)\u6765\u521b\u5efa\u4e00\u4e2a\u7b80\u5355\u7684 CA \u548c\u88ab\u7b7e\u4e86\u540d\u7684\u8bc1\u4e66\u4e0e\u5bc6\u94a5\u5bf9\u3002 \u6216\u8005\u4f60\u4e5f\u53ef\u4ee5\u4f7f\u7528[\u8fd9\u4e2a\u7c7b\u4f3c\u7684\u811a\u672c](https://raw.githubusercontent.com/TremoloSecurity/openunison-qs-kubernetes/master/src/main/bash/makessl.sh)\uff0c\u751f\u6210\u4e00\u4e2a\u5408\u6cd5\u671f\u66f4\u957f\u3001\u5bc6\u94a5\u5c3a\u5bf8\u66f4\u5927\u7684 SHA256 \u8bc1\u4e66\u3002 \u7279\u5b9a\u7cfb\u7edf\u7684\u5b89\u88c5\u6307\u4ee4\uff1a - [UAA](https://docs.cloudfoundry.org/concepts/architecture/uaa.html) - [Dex](https://github.com/dexidp/dex/blob/master/Documentation/kubernetes.md) - [OpenUnison](https://www.tremolosecurity.com/orchestra-k8s/) #### \u4f7f\u7528 kubectl {#using-kubectl} ##### \u9009\u9879\u4e00 - OIDC \u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6 \u7b2c\u4e00\u79cd\u65b9\u6848\u662f\u4f7f\u7528 kubectl \u7684 `oidc` \u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6\uff0c\u8be5\u7ec4\u4ef6\u5c06 `id_token` \u8bbe\u7f6e \u4e3a\u6240\u6709\u8bf7\u6c42\u7684\u6301\u6709\u8005\u4ee4\u724c\uff0c\u5e76\u4e14\u5728\u4ee4\u724c\u8fc7\u671f\u65f6\u81ea\u52a8\u5237\u65b0\u3002\u5728\u4f60\u767b\u5f55\u5230\u4f60\u7684\u8eab\u4efd\u670d\u52a1\u4e4b\u540e\uff0c \u53ef\u4ee5\u4f7f\u7528 kubectl \u6765\u6dfb\u52a0\u4f60\u7684 `id_token`\u3001`refresh_token`\u3001`client_id` \u548c `client_secret`\uff0c\u4ee5\u914d\u7f6e\u8be5\u63d2\u4ef6\u3002 \u5982\u679c\u670d\u52a1\u5728\u5176\u5237\u65b0\u4ee4\u724c\u54cd\u5e94\u4e2d\u4e0d\u5305\u542b `id_token`\uff0c\u5219\u6b64\u63d2\u4ef6\u65e0\u6cd5\u652f\u6301\u8be5\u670d\u52a1\u3002 \u8fd9\u65f6\u4f60\u5e94\u8be5\u8003\u8651\u4e0b\u9762\u7684\u9009\u9879\u4e8c\u3002 ```bash kubectl config set-credentials USER_NAME --auth-provider=oidc --auth-provider-arg=idp-issuer-url=( issuer url ) --auth-provider-arg=client-id=( your client id ) --auth-provider-arg=client-secret=( your client secret ) --auth-provider-arg=refresh-token=( your refresh token ) --auth-provider-arg=idp-certificate-authority=( path to your ca certificate ) --auth-provider-arg=id-token=( your id_token ) ``` \u4f5c\u4e3a\u793a\u4f8b\uff0c\u5728\u5b8c\u6210\u5bf9\u4f60\u7684\u8eab\u4efd\u670d\u52a1\u7684\u8eab\u4efd\u8ba4\u8bc1\u4e4b\u540e\uff0c\u8fd0\u884c\u4e0b\u9762\u7684\u547d\u4ee4\uff1a ```bash kubectl config set-credentials mmosley --auth-provider=oidc --auth-provider-arg=idp-issuer-url=https://oidcidp.tremolo.lan:8443/auth/idp/OidcIdP --auth-provider-arg=client-id=kubernetes --auth-provider-arg=client-secret=1db158f6-177d-4d9c-8a8b-d36869918ec5 --auth-provider-arg=refresh-token=q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXqHega4GAXlF+ma+vmYpFcHe5eZR+slBFpZKtQA= --auth-provider-arg=idp-certificate-authority=/root/ca.pem --auth-provider-arg=id-token=eyJraWQiOiJDTj1vaWRjaWRwLnRyZW1vbG8ubGFuLCBPVT1EZW1vLCBPPVRybWVvbG8gU2VjdXJpdHksIEw9QXJsaW5ndG9uLCBTVD1WaXJnaW5pYSwgQz1VUy1DTj1rdWJlLWNhLTEyMDIxNDc5MjEwMzYwNzMyMTUyIiwiYWxnIjoiUlMyNTYifQ.eyJpc3MiOiJodHRwczovL29pZGNpZHAudHJlbW9sby5sYW46ODQ0My9hdXRoL2lkcC9PaWRjSWRQIiwiYXVkIjoia3ViZXJuZXRlcyIsImV4cCI6MTQ4MzU0OTUxMSwianRpIjoiMm96US15TXdFcHV4WDlHZUhQdy1hZyIsImlhdCI6MTQ4MzU0OTQ1MSwibmJmIjoxNDgzNTQ5MzMxLCJzdWIiOiI0YWViMzdiYS1iNjQ1LTQ4ZmQtYWIzMC0xYTAxZWU0MWUyMTgifQ.w6p4J_6qQ1HzTG9nrEOrubxIMb9K5hzcMPxc9IxPx2K4xO9l-oFiUw93daH3m5pluP6K7eOE6txBuRVfEcpJSwlelsOsW8gb8VJcnzMS9EnZpeA0tW_p-mnkFc3VcfyXuhe5R3G7aa5d8uHv70yJ9Y3-UhjiN9EhpMdfPAoEB9fYKKkJRzF7utTTIPGrSaSU6d2pcpfYKaxIwePzEkT4DfcQthoZdy9ucNvvLoi1DIC-UocFD8HLs8LYKEqSxQvOcvnThbObJ9af71EwmuE21fO5KzMW20KtAeget1gnldOosPtz1G5EwvaQ401-RPQzPGMVBld0_zMCAwZttJ4knw ``` \u6b64\u64cd\u4f5c\u4f1a\u751f\u6210\u4ee5\u4e0b\u914d\u7f6e\uff1a ```yaml users: - name: mmosley user: auth-provider: config: client-id: kubernetes client-secret: 1db158f6-177d-4d9c-8a8b-d36869918ec5 id-token: eyJraWQiOiJDTj1vaWRjaWRwLnRyZW1vbG8ubGFuLCBPVT1EZW1vLCBPPVRybWVvbG8gU2VjdXJpdHksIEw9QXJsaW5ndG9uLCBTVD1WaXJnaW5pYSwgQz1VUy1DTj1rdWJlLWNhLTEyMDIxNDc5MjEwMzYwNzMyMTUyIiwiYWxnIjoiUlMyNTYifQ.eyJpc3MiOiJodHRwczovL29pZGNpZHAudHJlbW9sby5sYW46ODQ0My9hdXRoL2lkcC9PaWRjSWRQIiwiYXVkIjoia3ViZXJuZXRlcyIsImV4cCI6MTQ4MzU0OTUxMSwianRpIjoiMm96US15TXdFcHV4WDlHZUhQdy1hZyIsImlhdCI6MTQ4MzU0OTQ1MSwibmJmIjoxNDgzNTQ5MzMxLCJzdWIiOiI0YWViMzdiYS1iNjQ1LTQ4ZmQtYWIzMC0xYTAxZWU0MWUyMTgifQ.w6p4J_6qQ1HzTG9nrEOrubxIMb9K5hzcMPxc9IxPx2K4xO9l-oFiUw93daH3m5pluP6K7eOE6txBuRVfEcpJSwlelsOsW8gb8VJcnzMS9EnZpeA0tW_p-mnkFc3VcfyXuhe5R3G7aa5d8uHv70yJ9Y3-UhjiN9EhpMdfPAoEB9fYKKkJRzF7utTTIPGrSaSU6d2pcpfYKaxIwePzEkT4DfcQthoZdy9ucNvvLoi1DIC-UocFD8HLs8LYKEqSxQvOcvnThbObJ9af71EwmuE21fO5KzMW20KtAeget1gnldOosPtz1G5EwvaQ401-RPQzPGMVBld0_zMCAwZttJ4knw idp-certificate-authority: /root/ca.pem idp-issuer-url: https://oidcidp.tremolo.lan:8443/auth/idp/OidcIdP refresh-token: q1bKLFOyUiosTfawzA93TzZIDzH2TNa2SMm0zEiPKTUwME6BkEo6Sql5yUWVBSWpKUGphaWpxSVAfekBOZbBhaEW+VlFUeVRGcluyVF5JT4+haZmPsluFoFu5XkpXk5BXq name: oidc ``` \u5f53\u4f60\u7684 `id_token` \u8fc7\u671f\u65f6\uff0c`kubectl` \u4f1a\u5c1d\u8bd5\u4f7f\u7528\u4f60\u7684 `refresh_token` \u6765\u5237\u65b0\u4f60\u7684 `id_token`\uff0c\u5e76\u4e14\u5728 `client_secret` \u4e2d\u5b58\u653e `refresh_token` \u7684\u65b0\u503c\uff0c\u540c\u65f6\u628a `id_token` \u7684\u65b0\u503c\u5199\u5165\u5230 `.kube/config` \u6587\u4ef6\u4e2d\u3002 ##### \u9009\u9879\u4e8c - \u4f7f\u7528 `--token` \u9009\u9879 `kubectl` \u547d\u4ee4\u5141\u8bb8\u4f60\u4f7f\u7528 `--token` \u9009\u9879\u4f20\u9012\u4e00\u4e2a\u4ee4\u724c\u3002 \u4f60\u53ef\u4ee5\u5c06 `id_token` \u7684\u5185\u5bb9\u590d\u5236\u7c98\u8d34\u8fc7\u6765\uff0c\u4f5c\u4e3a\u6b64\u6807\u5fd7\u7684\u53d6\u503c\uff1a ```bash kubectl --token=eyJhbGciOiJSUzI1NiJ9.eyJpc3MiOiJodHRwczovL21sYi50cmVtb2xvLmxhbjo4MDQzL2F1dGgvaWRwL29pZGMiLCJhdWQiOiJrdWJlcm5ldGVzIiwiZXhwIjoxNDc0NTk2NjY5LCJqdGkiOiI2RDUzNXoxUEpFNjJOR3QxaWVyYm9RIiwiaWF0IjoxNDc0NTk2MzY5LCJuYmYiOjE0NzQ1OTYyNDksInN1YiI6Im13aW5kdSIsInVzZXJfcm9sZSI6WyJ1c2VycyIsIm5ldy1uYW1lc3BhY2Utdmlld2VyIl0sImVtYWlsIjoibXdpbmR1QG5vbW9yZWplZGkuY29tIn0.f2As579n9VNoaKzoF-dOQGmXkFKf1FMyNV0-va_B63jn-_n9LGSCca_6IVMP8pO-Zb4KvRqGyTP0r3HkHxYy5c81AnIh8ijarruczl-TK_yF5akjSTHFZD-0gRzlevBDiH8Q79NAr-ky0P4iIXS8lY9Vnjch5MF74Zx0c3alKJHJUnnpjIACByfF2SCaYzbWFMUNat-K1PaUk5-ujMBG7yYnr95xD-63n8CO8teGUAAEMx6zRjzfhnhbzX-ajwZLGwGUBT4WqjMs70-6a7_8gZmLZb2az1cZynkFRj2BaCkVT3A2RrjeEwZEtGXlMqKJ1_I2ulrOVsYx01_yD35-rw get nodes ``` ### Webhook \u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1 {#webhook-token-authentication} Webhook \u8eab\u4efd\u8ba4\u8bc1\u662f\u4e00\u79cd\u7528\u6765\u9a8c\u8bc1\u6301\u6709\u8005\u4ee4\u724c\u7684\u56de\u8c03\u673a\u5236\u3002 * `--authentication-token-webhook-config-file` \u6307\u5411\u4e00\u4e2a\u914d\u7f6e\u6587\u4ef6\uff0c\u5176\u4e2d\u63cf\u8ff0 \u5982\u4f55\u8bbf\u95ee\u8fdc\u7a0b\u7684 Webhook \u670d\u52a1\u3002 * `--authentication-token-webhook-cache-ttl` \u7528\u6765\u8bbe\u5b9a\u8eab\u4efd\u8ba4\u8bc1\u51b3\u5b9a\u7684\u7f13\u5b58\u65f6\u95f4\u3002 \u9ed8\u8ba4\u65f6\u957f\u4e3a 2 \u5206\u949f\u3002 \u914d\u7f6e\u6587\u4ef6\u4f7f\u7528 [kubeconfig](/docs/concepts/configuration/organize-cluster-access-kubeconfig/) \u6587\u4ef6\u7684\u683c\u5f0f\u3002\u6587\u4ef6\u4e2d\uff0c`clusters` \u6307\u4ee3\u8fdc\u7a0b\u670d\u52a1\uff0c`users` \u6307\u4ee3\u8fdc\u7a0b API \u670d\u52a1 Webhook\u3002\u4e0b\u9762\u662f\u4e00\u4e2a\u4f8b\u5b50\uff1a ```yaml # Kubernetes API \u7248\u672c apiVersion: v1 # API \u5bf9\u8c61\u7c7b\u522b kind: Config # clusters \u6307\u4ee3\u8fdc\u7a0b\u670d\u52a1 clusters: - name: name-of-remote-authn-service cluster: certificate-authority: /path/to/ca.pem # \u7528\u6765\u9a8c\u8bc1\u8fdc\u7a0b\u670d\u52a1\u7684 CA server: https://authn.example.com/authenticate # \u8981\u67e5\u8be2\u7684\u8fdc\u7a0b\u670d\u52a1 URL\u3002\u5fc5\u987b\u4f7f\u7528 'https'\u3002 # users \u6307\u4ee3 API \u670d\u52a1\u7684 Webhook \u914d\u7f6e users: - name: name-of-api-server user: client-certificate: /path/to/cert.pem # Webhook \u63d2\u4ef6\u8981\u4f7f\u7528\u7684\u8bc1\u4e66 client-key: /path/to/key.pem # \u4e0e\u8bc1\u4e66\u5339\u914d\u7684\u5bc6\u94a5 # kubeconfig \u6587\u4ef6\u9700\u8981\u4e00\u4e2a\u4e0a\u4e0b\u6587\uff08Context\uff09\uff0c\u6b64\u4e0a\u4e0b\u6587\u7528\u4e8e\u672c API \u670d\u52a1\u5668 current-context: webhook contexts: - context: cluster: name-of-remote-authn-service user: name-of-api-sever name: webhook ``` \u5f53\u5ba2\u6237\u7aef\u5c1d\u8bd5\u5728 API \u670d\u52a1\u5668\u4e0a\u4f7f\u7528\u6301\u6709\u8005\u4ee4\u724c\u5b8c\u6210\u8eab\u4efd\u8ba4\u8bc1\uff08 \u5982[\u524d](#putting-a-bearer-token-in-a-request)\u6240\u8ff0\uff09\u65f6\uff0c \u8eab\u4efd\u8ba4\u8bc1 Webhook \u4f1a\u7528 POST \u8bf7\u6c42\u53d1\u9001\u4e00\u4e2a JSON \u5e8f\u5217\u5316\u7684\u5bf9\u8c61\u5230\u8fdc\u7a0b\u670d\u52a1\u3002 \u8be5\u5bf9\u8c61\u662f `authentication.k8s.io/v1beta1` \u7ec4\u7684 `TokenReview` \u5bf9\u8c61\uff0c \u5176\u4e2d\u5305\u542b\u6301\u6709\u8005\u4ee4\u724c\u3002 Kubernetes \u4e0d\u4f1a\u5f3a\u5236\u8bf7\u6c42\u63d0\u4f9b\u6b64 HTTP \u5934\u90e8\u3002 \u8981\u6ce8\u610f\u7684\u662f\uff0cWebhook API \u5bf9\u8c61\u548c\u5176\u4ed6 Kubernetes API \u5bf9\u8c61\u4e00\u6837\uff0c\u4e5f\u8981\u53d7\u5230\u540c\u4e00 [\u7248\u672c\u517c\u5bb9\u89c4\u5219](/zh/docs/concepts/overview/kubernetes-api/)\u7ea6\u675f\u3002 \u5b9e\u73b0\u8005\u8981\u4e86\u89e3\u5bf9 Beta \u9636\u6bb5\u5bf9\u8c61\u7684\u517c\u5bb9\u6027\u627f\u8bfa\uff0c\u5e76\u68c0\u67e5\u8bf7\u6c42\u7684 `apiVersion` \u5b57\u6bb5\uff0c \u4ee5\u786e\u4fdd\u6570\u636e\u7ed3\u6784\u80fd\u591f\u6b63\u5e38\u53cd\u5e8f\u5217\u5316\u89e3\u6790\u3002\u6b64\u5916\uff0cAPI \u670d\u52a1\u5668\u5fc5\u987b\u542f\u7528 `authentication.k8s.io/v1beta1` API \u6269\u5c55\u7ec4 \uff08`--runtime-config=authentication.k8s.io/v1beta1=true`\uff09\u3002 POST \u8bf7\u6c42\u7684 Body \u90e8\u5206\u5c06\u662f\u5982\u4e0b\u683c\u5f0f\uff1a ```json { \"apiVersion\": \"authentication.k8s.io/v1beta1\", \"kind\": \"TokenReview\", \"spec\": { \"token\": \"<\u6301\u6709\u8005\u4ee4\u724c>\" } } ``` \u8fdc\u7a0b\u670d\u52a1\u5e94\u8be5\u4f1a\u586b\u5145\u8bf7\u6c42\u7684 `status` \u5b57\u6bb5\uff0c\u4ee5\u6807\u660e\u767b\u5f55\u64cd\u4f5c\u662f\u5426\u6210\u529f\u3002 \u54cd\u5e94\u7684 Body \u4e2d\u7684 `spec` \u5b57\u6bb5\u4f1a\u88ab\u5ffd\u7565\uff0c\u56e0\u6b64\u53ef\u4ee5\u7701\u7565\u3002 \u5982\u679c\u6301\u6709\u8005\u4ee4\u724c\u9a8c\u8bc1\u6210\u529f\uff0c\u5e94\u8be5\u8fd4\u56de\u5982\u4e0b\u6240\u793a\u7684\u54cd\u5e94\uff1a ```json { \"apiVersion\": \"authentication.k8s.io/v1beta1\", \"kind\": \"TokenReview\", \"status\": { \"authenticated\": true, \"user\": { \"username\": \"janedoe@example.com\", \"uid\": \"42\", \"groups\": [ \"developers\", \"qa\" ], \"extra\": { \"extrafield1\": [ \"extravalue1\", \"extravalue2\" ] } } } } ``` \u800c\u4e0d\u6210\u529f\u7684\u8bf7\u6c42\u4f1a\u8fd4\u56de\uff1a ```json { \"apiVersion\": \"authentication.k8s.io/v1beta1\", \"kind\": \"TokenReview\", \"status\": { \"authenticated\": false } } ``` HTTP \u72b6\u6001\u7801\u53ef\u7528\u6765\u63d0\u4f9b\u8fdb\u4e00\u6b65\u7684\u9519\u8bef\u8bed\u5883\u4fe1\u606f\u3002 ### \u8eab\u4efd\u8ba4\u8bc1\u4ee3\u7406 {#authenticating-proxy} API \u670d\u52a1\u5668\u53ef\u4ee5\u914d\u7f6e\u6210\u4ece\u8bf7\u6c42\u7684\u5934\u90e8\u5b57\u6bb5\u503c\uff08\u5982 `X-Remote-User`\uff09\u4e2d\u8fa9\u8bc6\u7528\u6237\u3002 \u8fd9\u4e00\u8bbe\u8ba1\u662f\u7528\u6765\u4e0e\u67d0\u8eab\u4efd\u8ba4\u8bc1\u4ee3\u7406\u4e00\u8d77\u4f7f\u7528 API \u670d\u52a1\u5668\uff0c\u4ee3\u7406\u8d1f\u8d23\u8bbe\u7f6e\u8bf7\u6c42\u7684\u5934\u90e8\u5b57\u6bb5\u503c\u3002 * `--requestheader-username-headers` \u5fc5\u9700\u5b57\u6bb5\uff0c\u5927\u5c0f\u5199\u4e0d\u654f\u611f\u3002\u7528\u6765\u8bbe\u7f6e\u8981\u83b7\u5f97\u7528\u6237\u8eab\u4efd\u6240\u8981\u68c0\u67e5\u7684\u5934\u90e8\u5b57\u6bb5\u540d\u79f0\u5217\u8868\uff08\u6709\u5e8f\uff09\u3002\u7b2c\u4e00\u4e2a\u5305\u542b\u6570\u503c\u7684\u5b57\u6bb5\u4f1a\u88ab\u7528\u6765\u63d0\u53d6\u7528\u6237\u540d\u3002 * `--requestheader-group-headers` \u53ef\u9009\u5b57\u6bb5\uff0c\u5728 Kubernetes 1.6 \u7248\u672c\u4ee5\u540e\u652f\u6301\uff0c\u5927\u5c0f\u5199\u4e0d\u654f\u611f\u3002 \u5efa\u8bae\u8bbe\u7f6e\u4e3a \"X-Remote-Group\"\u3002\u7528\u6765\u6307\u5b9a\u4e00\u7ec4\u5934\u90e8\u5b57\u6bb5\u540d\u79f0\u5217\u8868\uff0c\u4ee5\u4f9b\u68c0\u67e5\u7528\u6237\u6240\u5c5e\u7684\u7ec4\u540d\u79f0\u3002 \u6240\u627e\u5230\u7684\u5168\u90e8\u5934\u90e8\u5b57\u6bb5\u7684\u53d6\u503c\u90fd\u4f1a\u88ab\u7528\u4f5c\u7528\u6237\u7ec4\u540d\u3002 * `--requestheader-extra-headers-prefix` \u53ef\u9009\u5b57\u6bb5\uff0c\u5728 Kubernetes 1.6 \u7248\u672c\u4ee5\u540e\u652f\u6301\uff0c\u5927\u5c0f\u5199\u4e0d\u654f\u611f\u3002 \u5efa\u8bae\u8bbe\u7f6e\u4e3a \"X-Remote-Extra-\"\u3002\u7528\u6765\u8bbe\u7f6e\u4e00\u4e2a\u5934\u90e8\u5b57\u6bb5\u7684\u524d\u7f00\u5b57\u7b26\u4e32\uff0cAPI \u670d\u52a1\u5668\u4f1a\u57fa\u4e8e\u6240\u7ed9 \u524d\u7f00\u6765\u67e5\u627e\u4e0e\u7528\u6237\u6709\u5173\u7684\u4e00\u4e9b\u989d\u5916\u4fe1\u606f\u3002\u8fd9\u4e9b\u989d\u5916\u4fe1\u606f\u901a\u5e38\u7528\u4e8e\u6240\u914d\u7f6e\u7684\u9274\u6743\u63d2\u4ef6\u3002 API \u670d\u52a1\u5668\u4f1a\u5c06\u4e0e\u6240\u7ed9\u524d\u7f00\u5339\u914d\u7684\u5934\u90e8\u5b57\u6bb5\u8fc7\u6ee4\u51fa\u6765\uff0c\u53bb\u6389\u5176\u524d\u7f00\u90e8\u5206\uff0c\u5c06\u5269\u4f59\u90e8\u5206 \u8f6c\u6362\u4e3a\u5c0f\u5199\u5b57\u7b26\u4e32\u5e76\u5728\u5fc5\u8981\u65f6\u6267\u884c[\u767e\u5206\u53f7\u89e3\u7801](https://tools.ietf.org/html/rfc3986#section-2.1) \u540e\uff0c\u6784\u9020\u65b0\u7684\u9644\u52a0\u4fe1\u606f\u5b57\u6bb5\u952e\u540d\u3002\u539f\u6765\u7684\u5934\u90e8\u5b57\u6bb5\u503c\u76f4\u63a5\u4f5c\u4e3a\u9644\u52a0\u4fe1\u606f\u5b57\u6bb5\u7684\u503c\u3002 {{< note >}} \u5728 1.13.3 \u7248\u672c\u4e4b\u524d\uff08\u5305\u62ec 1.10.7\u30011.9.11\uff09\uff0c\u9644\u52a0\u5b57\u6bb5\u7684\u952e\u540d\u53ea\u80fd\u5305\u542b [HTTP \u5934\u90e8\u6807\u7b7e\u7684\u5408\u6cd5\u5b57\u7b26](https://tools.ietf.org/html/rfc7230#section-3.2.6)\u3002 {{< /note >}} \u4f8b\u5982\uff0c\u4f7f\u7528\u4e0b\u9762\u7684\u914d\u7f6e\uff1a ``` --requestheader-username-headers=X-Remote-User --requestheader-group-headers=X-Remote-Group --requestheader-extra-headers-prefix=X-Remote-Extra- ``` \u9488\u5bf9\u6240\u6536\u5230\u7684\u5982\u4e0b\u8bf7\u6c42\uff1a ```http GET / HTTP/1.1 X-Remote-User: fido X-Remote-Group: dogs X-Remote-Group: dachshunds X-Remote-Extra-Acme.com%2Fproject: some-project X-Remote-Extra-Scopes: openid X-Remote-Extra-Scopes: profile ``` \u4f1a\u751f\u6210\u4e0b\u9762\u7684\u7528\u6237\u4fe1\u606f\uff1a ```yaml name: fido groups: - dogs - dachshunds extra: acme.com/project: - some-project scopes: - openid - profile ``` \u4e3a\u4e86\u9632\u8303\u5934\u90e8\u4fe1\u606f\u4fa6\u542c\uff0c\u5728\u8bf7\u6c42\u4e2d\u7684\u5934\u90e8\u5b57\u6bb5\u88ab\u68c0\u89c6\u4e4b\u524d\uff0c \u8eab\u4efd\u8ba4\u8bc1\u4ee3\u7406\u9700\u8981\u5411 API \u670d\u52a1\u5668\u63d0\u4f9b\u4e00\u4efd\u5408\u6cd5\u7684\u5ba2\u6237\u7aef\u8bc1\u4e66\uff0c \u4f9b\u540e\u8005\u4f7f\u7528\u6240\u7ed9\u7684 CA \u6765\u6267\u884c\u9a8c\u8bc1\u3002 \u8b66\u544a\uff1a*\u4e0d\u8981* \u5728\u4e0d\u540c\u7684\u4e0a\u4e0b\u6587\u4e2d\u590d\u7528 CA \u8bc1\u4e66\uff0c\u9664\u975e\u4f60\u6e05\u695a\u8fd9\u6837\u505a\u7684\u98ce\u9669\u662f\u4ec0\u4e48\u4ee5\u53ca \u5e94\u5982\u4f55\u4fdd\u62a4 CA \u7528\u6cd5\u7684\u673a\u5236\u3002 * `--requestheader-client-ca-file` \u5fc5\u9700\u5b57\u6bb5\uff0c\u7ed9\u51fa PEM \u7f16\u7801\u7684\u8bc1\u4e66\u5305\u3002 \u5728\u68c0\u67e5\u8bf7\u6c42\u7684\u5934\u90e8\u5b57\u6bb5\u4ee5\u63d0\u53d6\u7528\u6237\u540d\u4fe1\u606f\u4e4b\u524d\uff0c\u5fc5\u987b\u63d0\u4f9b\u4e00\u4e2a\u5408\u6cd5\u7684\u5ba2\u6237\u7aef\u8bc1\u4e66\uff0c \u4e14\u8be5\u8bc1\u4e66\u8981\u80fd\u591f\u88ab\u6240\u7ed9\u6587\u4ef6\u4e2d\u7684\u673a\u6784\u6240\u9a8c\u8bc1\u3002 * `--requestheader-allowed-names` \u53ef\u9009\u5b57\u6bb5\uff0c\u7528\u6765\u7ed9\u51fa\u4e00\u7ec4\u516c\u5171\u540d\u79f0\uff08CN\uff09\u3002 \u5982\u679c\u6b64\u6807\u5fd7\u88ab\u8bbe\u7f6e\uff0c\u5219\u5728\u68c0\u89c6\u8bf7\u6c42\u4e2d\u7684\u5934\u90e8\u4ee5\u63d0\u53d6\u7528\u6237\u4fe1\u606f\u4e4b\u524d\uff0c\u5fc5\u987b\u63d0\u4f9b \u5305\u542b\u6b64\u5217\u8868\u4e2d\u6240\u7ed9\u7684 CN \u540d\u7684\u3001\u5408\u6cd5\u7684\u5ba2\u6237\u7aef\u8bc1\u4e66\u3002 ## \u533f\u540d\u8bf7\u6c42 {#anonymous-requests} \u542f\u7528\u533f\u540d\u8bf7\u6c42\u652f\u6301\u4e4b\u540e\uff0c\u5982\u679c\u8bf7\u6c42\u6ca1\u6709\u88ab\u5df2\u914d\u7f6e\u7684\u5176\u4ed6\u8eab\u4efd\u8ba4\u8bc1\u65b9\u6cd5\u62d2\u7edd\uff0c\u5219\u88ab\u89c6\u4f5c \u533f\u540d\u8bf7\u6c42\uff08Anonymous Requests\uff09\u3002\u8fd9\u7c7b\u8bf7\u6c42\u83b7\u5f97\u7528\u6237\u540d `system:anonymous` \u548c \u5bf9\u5e94\u7684\u7528\u6237\u7ec4 `system:unauthenticated`\u3002 \u4f8b\u5982\uff0c\u5728\u4e00\u4e2a\u914d\u7f6e\u4e86\u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1\u4e14\u542f\u7528\u4e86\u533f\u540d\u8bbf\u95ee\u7684\u670d\u52a1\u5668\u4e0a\uff0c\u5982\u679c\u8bf7\u6c42\u63d0\u4f9b\u4e86\u975e\u6cd5\u7684 \u6301\u6709\u8005\u4ee4\u724c\uff0c\u5219\u4f1a\u8fd4\u56de `401 Unauthorized` \u9519\u8bef\u3002 \u5982\u679c\u8bf7\u6c42\u6ca1\u6709\u63d0\u4f9b\u6301\u6709\u8005\u4ee4\u724c\uff0c\u5219\u88ab\u89c6\u4e3a\u533f\u540d\u8bf7\u6c42\u3002 \u5728 1.5.1-1.5.x \u7248\u672c\u4e2d\uff0c\u533f\u540d\u8bbf\u95ee\u9ed8\u8ba4\u60c5\u51b5\u4e0b\u662f\u88ab\u7981\u7528\u7684\uff0c\u53ef\u4ee5\u901a\u8fc7\u4e3a API \u670d\u52a1\u5668\u8bbe\u5b9a `--anonymous-auth=true` \u6765\u542f\u7528\u3002 \u5728 1.6 \u53ca\u4e4b\u540e\u7248\u672c\u4e2d\uff0c\u5982\u679c\u6240\u4f7f\u7528\u7684\u9274\u6743\u6a21\u5f0f\u4e0d\u662f `AlwaysAllow`\uff0c\u5219\u533f\u540d\u8bbf\u95ee\u9ed8\u8ba4\u662f\u88ab\u542f\u7528\u7684\u3002 \u4ece 1.6 \u7248\u672c\u5f00\u59cb\uff0cABAC \u548c RBAC \u9274\u6743\u6a21\u5757\u8981\u6c42\u5bf9 `system:anonymous` \u7528\u6237\u6216\u8005 `system:unauthenticated` \u7528\u6237\u7ec4\u6267\u884c\u663e\u5f0f\u7684\u6743\u9650\u5224\u5b9a\uff0c\u6240\u4ee5\u4e4b\u524d\u7684\u4e3a `*` \u7528\u6237\u6216 `*` \u7528\u6237\u7ec4\u8d4b\u4e88\u8bbf\u95ee\u6743\u9650\u7684\u7b56\u7565\u89c4\u5219\u90fd\u4e0d\u518d\u5305\u542b\u533f\u540d\u7528\u6237\u3002 ## \u7528\u6237\u4f2a\u88c5 {#user-impersonation} \u4e00\u4e2a\u7528\u6237\u53ef\u4ee5\u901a\u8fc7\u4f2a\u88c5\uff08Impersonation\uff09\u5934\u90e8\u5b57\u6bb5\u6765\u4ee5\u53e6\u4e00\u4e2a\u7528\u6237\u7684\u8eab\u4efd\u6267\u884c\u64cd\u4f5c\u3002 \u4f7f\u7528\u8fd9\u4e00\u80fd\u529b\uff0c\u4f60\u53ef\u4ee5\u624b\u52a8\u91cd\u8f7d\u8bf7\u6c42\u88ab\u8eab\u4efd\u8ba4\u8bc1\u6240\u8bc6\u522b\u51fa\u6765\u7684\u7528\u6237\u4fe1\u606f\u3002 \u4f8b\u5982\uff0c\u7ba1\u7406\u5458\u53ef\u4ee5\u4f7f\u7528\u8fd9\u4e00\u529f\u80fd\u7279\u6027\u6765\u4e34\u65f6\u4f2a\u88c5\u6210\u53e6\u4e00\u4e2a\u7528\u6237\uff0c\u67e5\u770b\u8bf7\u6c42\u662f\u5426\u88ab\u62d2\u7edd\uff0c \u4ece\u800c\u8c03\u8bd5\u9274\u6743\u7b56\u7565\u4e2d\u7684\u95ee\u9898\uff0c \u5e26\u4f2a\u88c5\u7684\u8bf7\u6c42\u9996\u5148\u4f1a\u88ab\u8eab\u4efd\u8ba4\u8bc1\u8bc6\u522b\u4e3a\u53d1\u51fa\u8bf7\u6c42\u7684\u7528\u6237\uff0c\u4e4b\u540e\u4f1a\u5207\u6362\u5230\u4f7f\u7528\u88ab\u4f2a\u88c5\u7684\u7528\u6237 \u7684\u7528\u6237\u4fe1\u606f\u3002 * \u7528\u6237\u53d1\u8d77 API \u8c03\u7528\u65f6 _\u540c\u65f6_ \u63d0\u4f9b\u81ea\u8eab\u7684\u51ed\u636e\u548c\u4f2a\u88c5\u5934\u90e8\u5b57\u6bb5\u4fe1\u606f * API \u670d\u52a1\u5668\u5bf9\u7528\u6237\u6267\u884c\u8eab\u4efd\u8ba4\u8bc1 * API \u670d\u52a1\u5668\u786e\u8ba4\u901a\u8fc7\u8ba4\u8bc1\u7684\u7528\u6237\u5177\u6709\u4f2a\u88c5\u7279\u6743 * \u8bf7\u6c42\u7528\u6237\u7684\u4fe1\u606f\u88ab\u66ff\u6362\u6210\u4f2a\u88c5\u5b57\u6bb5\u7684\u503c * \u8bc4\u4f30\u8bf7\u6c42\uff0c\u9274\u6743\u7ec4\u4ef6\u9488\u5bf9\u6240\u4f2a\u88c5\u7684\u7528\u6237\u4fe1\u606f\u6267\u884c\u64cd\u4f5c \u4ee5\u4e0b HTTP \u5934\u90e8\u5b57\u6bb5\u53ef\u7528\u6765\u6267\u884c\u4f2a\u88c5\u8bf7\u6c42\uff1a * `Impersonate-User`\uff1a\u8981\u4f2a\u88c5\u6210\u7684\u7528\u6237\u540d * `Impersonate-Group`\uff1a\u8981\u4f2a\u88c5\u6210\u7684\u7528\u6237\u7ec4\u540d\u3002\u53ef\u4ee5\u591a\u6b21\u6307\u5b9a\u4ee5\u8bbe\u7f6e\u591a\u4e2a\u7528\u6237\u7ec4\u3002 \u53ef\u9009\u5b57\u6bb5\uff1b\u8981\u6c42 \"Impersonate-User\" \u5fc5\u987b\u88ab\u8bbe\u7f6e\u3002 * `Impersonate-Extra-<\u9644\u52a0\u540d\u79f0>`\uff1a\u4e00\u4e2a\u52a8\u6001\u7684\u5934\u90e8\u5b57\u6bb5\uff0c\u7528\u6765\u8bbe\u7f6e\u4e0e\u7528\u6237\u76f8\u5173\u7684\u9644\u52a0\u5b57\u6bb5\u3002 \u6b64\u5b57\u6bb5\u53ef\u9009\uff1b\u8981\u6c42 \"Impersonate-User\" \u88ab\u8bbe\u7f6e\u3002\u4e3a\u4e86\u80fd\u591f\u4ee5\u4e00\u81f4\u7684\u5f62\u5f0f\u4fdd\u7559\uff0c `<\u9644\u52a0\u540d\u79f0>`\u90e8\u5206\u5fc5\u987b\u662f\u5c0f\u5199\u5b57\u7b26\uff0c\u5982\u679c\u6709\u4efb\u4f55\u5b57\u7b26\u4e0d\u662f [\u5408\u6cd5\u7684 HTTP \u5934\u90e8\u6807\u7b7e\u5b57\u7b26](https://tools.ietf.org/html/rfc7230#section-3.2.6)\uff0c \u5219\u5fc5\u987b\u662f utf8 \u5b57\u7b26\uff0c\u4e14\u8f6c\u6362\u4e3a[\u767e\u5206\u53f7\u7f16\u7801](https://tools.ietf.org/html/rfc3986#section-2.1)\u3002 {{< note >}} \u5728 1.11.3 \u7248\u672c\u4e4b\u524d\uff08\u4ee5\u53ca 1.10.7\u30011.9.11\uff09\uff0c`<\u9644\u52a0\u540d\u79f0>` \u53ea\u80fd\u5305\u542b \u5408\u6cd5\u7684 HTTP \u6807\u7b7e\u5b57\u7b26\u3002 {{< /note >}} \u5934\u90e8\u5b57\u6bb5\u96c6\u5408\u7684\u793a\u4f8b\uff1a ```http Impersonate-User: jane.doe@example.com Impersonate-Group: developers Impersonate-Group: admins Impersonate-Extra-dn: cn=jane,ou=engineers,dc=example,dc=com Impersonate-Extra-acme.com%2Fproject: some-project Impersonate-Extra-scopes: view Impersonate-Extra-scopes: development ``` \u5728\u4f7f\u7528 `kubectl` \u65f6\uff0c\u53ef\u4ee5\u4f7f\u7528 `--as` \u6807\u5fd7\u6765\u914d\u7f6e `Impersonate-User` \u5934\u90e8\u5b57\u6bb5\u503c\uff0c \u4f7f\u7528 `--as-group` \u6807\u5fd7\u914d\u7f6e `Impersonate-Group` \u5934\u90e8\u5b57\u6bb5\u503c\u3002 ```bash kubectl drain mynode ``` ```none Error from server (Forbidden): User \"clark\" cannot get nodes at the cluster scope. (get nodes mynode) ``` \u8bbe\u7f6e `--as` \u548c `--as-group` \u6807\u5fd7\uff1a ```bash kubectl drain mynode --as=superman --as-group=system:masters ``` ```none node/mynode cordoned node/mynode drained ``` \u8981\u4f2a\u88c5\u6210\u67d0\u4e2a\u7528\u6237\u3001\u67d0\u4e2a\u7ec4\u6216\u8005\u8bbe\u7f6e\u9644\u52a0\u5b57\u6bb5\uff0c\u6267\u884c\u4f2a\u88c5\u64cd\u4f5c\u7684\u7528\u6237\u5fc5\u987b\u5177\u6709\u5bf9\u6240\u4f2a\u88c5\u7684 \u7c7b\u522b\uff08\u201cuser\u201d\u3001\u201cgroup\u201d \u7b49\uff09\u6267\u884c \u201cimpersonate\u201d \u52a8\u8bcd\u64cd\u4f5c\u7684\u80fd\u529b\u3002 \u5bf9\u4e8e\u542f\u7528\u4e86 RBAC \u9274\u6743\u63d2\u4ef6\u7684\u96c6\u7fa4\uff0c\u4e0b\u9762\u7684 ClusterRole \u5c01\u88c5\u4e86\u8bbe\u7f6e\u7528\u6237\u548c\u7ec4\u4f2a\u88c5\u5b57\u6bb5 \u6240\u9700\u7684\u89c4\u5219\uff1a ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: impersonator rules: - apiGroups: [\"\"] resources: [\"users\", \"groups\", \"serviceaccounts\"] verbs: [\"impersonate\"] ``` \u9644\u52a0\u5b57\u6bb5\u4f1a\u88ab\u4f5c\u4e3a `userextras` \u8d44\u6e90\u7684\u5b50\u8d44\u6e90\u6765\u6267\u884c\u6743\u9650\u8bc4\u4f30\u3002 \u5982\u679c\u8981\u5141\u8bb8\u7528\u6237\u4e3a\u9644\u52a0\u5b57\u6bb5 \u201cscopes\u201d \u8bbe\u7f6e\u4f2a\u88c5\u5934\u90e8\uff0c\u8be5\u7528\u6237\u9700\u8981\u88ab\u6388\u4e88\u4ee5\u4e0b\u89c4\u5219\uff1a ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: scopes-impersonator rules: # \u53ef\u4ee5\u8bbe\u7f6e \"Impersonate-Extra-scopes\" \u5934\u90e8 - apiGroups: [\"authentication.k8s.io\"] resources: [\"userextras/scopes\"] verbs: [\"impersonate\"] ``` \u4f60\u4e5f\u53ef\u4ee5\u901a\u8fc7\u7ea6\u675f\u8d44\u6e90\u53ef\u80fd\u5bf9\u5e94\u7684 `resourceNames` \u9650\u5236\u4f2a\u88c5\u5934\u90e8\u7684\u53d6\u503c\uff1a ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: limited-impersonator rules: # \u53ef\u4ee5\u4f2a\u88c5\u6210\u7528\u6237 \"jane.doe@example.com\" - apiGroups: [\"\"] resources: [\"users\"] verbs: [\"impersonate\"] resourceNames: [\"jane.doe@example.com\"] # \u53ef\u4ee5\u4f2a\u88c5\u6210\u7528\u6237\u7ec4 \"developers\" \u548c \"admins\" - apiGroups: [\"\"] resources: [\"groups\"] verbs: [\"impersonate\"] resourceNames: [\"developers\",\"admins\"] # \u53ef\u4ee5\u5c06\u9644\u52a0\u5b57\u6bb5 \"scopes\" \u4f2a\u88c5\u6210 \"view\" \u548c \"development\" - apiGroups: [\"authentication.k8s.io\"] resources: [\"userextras/scopes\"] verbs: [\"impersonate\"] resourceNames: [\"view\", \"development\"] ``` ## client-go \u51ed\u636e\u63d2\u4ef6 {#client-go-credential-plugins} {{< feature-state for_k8s_version=\"v1.11\" state=\"beta\" >}} `k8s.io/client-go` \u53ca\u4f7f\u7528\u5b83\u7684\u5de5\u5177\uff08\u5982 `kubectl` \u548c `kubelet`\uff09\u53ef\u4ee5\u6267\u884c\u67d0\u4e2a\u5916\u90e8 \u547d\u4ee4\u6765\u83b7\u5f97\u7528\u6237\u7684\u51ed\u636e\u4fe1\u606f\u3002 \u8fd9\u4e00\u7279\u6027\u7684\u76ee\u7684\u662f\u4fbf\u4e8e\u5ba2\u6237\u7aef\u4e0e `k8s.io/client-go` \u5e76\u4e0d\u652f\u6301\u7684\u8eab\u4efd\u8ba4\u8bc1\u534f\u8bae\uff08LDAP\u3001 Kerberos\u3001OAuth2\u3001SAML \u7b49\uff09\u7ee7\u627f\u3002 \u63d2\u4ef6\u5b9e\u73b0\u7279\u5b9a\u4e8e\u534f\u8bae\u7684\u903b\u8f91\uff0c\u4e4b\u540e\u8fd4\u56de\u4e0d\u900f\u660e\u7684\u51ed\u636e\u4ee5\u4f9b\u4f7f\u7528\u3002 \u51e0\u4e4e\u6240\u6709\u7684\u51ed\u636e\u63d2\u4ef6\u4f7f\u7528\u573a\u666f\u4e2d\u90fd\u9700\u8981\u5728\u670d\u52a1\u5668\u7aef\u5b58\u5728\u4e00\u4e2a\u652f\u6301 [Webhook \u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6](#webhook-token-authentication)\u7684\u6a21\u5757\uff0c \u8d1f\u8d23\u89e3\u6790\u5ba2\u6237\u7aef\u63d2\u4ef6\u6240\u751f\u6210\u7684\u51ed\u636e\u683c\u5f0f\u3002 ### \u793a\u4f8b\u5e94\u7528\u573a\u666f {#example-use-case} \u5728\u4e00\u4e2a\u5047\u60f3\u7684\u5e94\u7528\u573a\u666f\u4e2d\uff0c\u67d0\u7ec4\u7ec7\u8fd0\u884c\u8fd9\u4e00\u4e2a\u5916\u90e8\u7684\u670d\u52a1\uff0c\u80fd\u591f\u5c06\u7279\u5b9a\u7528\u6237\u7684\u5df2\u7b7e\u540d\u7684 \u4ee4\u724c\u8f6c\u6362\u6210 LDAP \u51ed\u636e\u3002\u6b64\u670d\u52a1\u8fd8\u80fd\u591f\u5bf9 [Webhook \u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6](#webhook-token-authentication)\u7684\u8bf7\u6c42\u505a\u51fa\u54cd\u5e94\u4ee5 \u9a8c\u8bc1\u6240\u63d0\u4f9b\u7684\u4ee4\u724c\u3002\u7528\u6237\u9700\u8981\u5728\u81ea\u5df1\u7684\u5de5\u4f5c\u7ad9\u4e0a\u5b89\u88c5\u4e00\u4e2a\u51ed\u636e\u63d2\u4ef6\u3002 \u8981\u5bf9 API \u670d\u52a1\u5668\u8ba4\u8bc1\u8eab\u4efd\u65f6\uff1a * \u7528\u6237\u53d1\u51fa `kubectl` \u547d\u4ee4\u3002 * \u51ed\u636e\u63d2\u4ef6\u63d0\u793a\u7528\u6237\u8f93\u5165 LDAP \u51ed\u636e\uff0c\u5e76\u4e0e\u5916\u90e8\u670d\u52a1\u4ea4\u4e92\uff0c\u83b7\u5f97\u4ee4\u724c\u3002 * \u51ed\u636e\u63d2\u4ef6\u5c06\u4ee4\u724c\u8fd4\u56de\u8be5 client-go\uff0c\u540e\u8005\u5c06\u5176\u7528\u4f5c\u6301\u6709\u8005\u4ee4\u724c\u63d0\u4ea4\u7ed9 API \u670d\u52a1\u5668\u3002 * API \u670d\u52a1\u5668\u4f7f\u7528[Webhook \u4ee4\u724c\u8eab\u4efd\u8ba4\u8bc1\u7ec4\u4ef6](#webhook-token-authentication)\u5411 \u5916\u90e8\u670d\u52a1\u53d1\u51fa `TokenReview` \u8bf7\u6c42\u3002 * \u5916\u90e8\u670d\u52a1\u68c0\u67e5\u4ee4\u724c\u4e0a\u7684\u7b7e\u540d\uff0c\u8fd4\u56de\u7528\u6237\u7684\u7528\u6237\u540d\u548c\u7528\u6237\u7ec4\u4fe1\u606f\u3002 ### \u914d\u7f6e {#configuration} \u51ed\u636e\u63d2\u4ef6\u901a\u8fc7 [kubectl \u914d\u7f6e\u6587\u4ef6](/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) \u6765\u4f5c\u4e3a user \u5b57\u6bb5\u7684\u4e00\u90e8\u5206\u8bbe\u7f6e\u3002 ```yaml apiVersion: v1 kind: Config users: - name: my-user user: exec: # \u8981\u6267\u884c\u7684\u547d\u4ee4\u3002\u5fc5\u9700\u3002 command: \"example-client-go-exec-plugin\" # \u89e3\u6790 ExecCredentials \u8d44\u6e90\u65f6\u4f7f\u7528\u7684 API \u7248\u672c\u3002\u5fc5\u9700\u3002 # # \u63d2\u4ef6\u8fd4\u56de\u7684 API \u7248\u672c\u5fc5\u9700\u4e0e\u8fd9\u91cc\u5217\u51fa\u7684\u7248\u672c\u5339\u914d\u3002 # # \u8981\u4e0e\u652f\u6301\u591a\u4e2a\u7248\u672c\u7684\u5de5\u5177\uff08\u5982 client.authentication.k8sio/v1alpha1\uff09\u96c6\u6210\uff0c # \u53ef\u4ee5\u8bbe\u7f6e\u4e00\u4e2a\u73af\u5883\u53d8\u91cf\u6216\u8005\u5411\u5de5\u5177\u4f20\u9012\u4e00\u4e2a\u53c2\u6570\u6807\u660e exec \u63d2\u4ef6\u6240\u671f\u671b\u7684\u7248\u672c\u3002 apiVersion: \"client.authentication.k8s.io/v1beta1\" # \u6267\u884c\u6b64\u63d2\u4ef6\u65f6\u8981\u8bbe\u7f6e\u7684\u73af\u5883\u53d8\u91cf\u3002\u53ef\u9009\u5b57\u6bb5\u3002 env: - name: \"FOO\" value: \"bar\" # \u6267\u884c\u63d2\u4ef6\u65f6\u8981\u4f20\u9012\u7684\u53c2\u6570\u3002\u53ef\u9009\u5b57\u6bb5\u3002 args: - \"arg1\" - \"arg2\" clusters: - name: my-cluster cluster: server: \"https://172.17.4.100:6443\" certificate-authority: \"/etc/kubernetes/ca.pem\" contexts: - name: my-cluster context: cluster: my-cluster user: my-user current-context: my-cluster ``` \u89e3\u6790\u76f8\u5bf9\u547d\u4ee4\u8def\u5f84\u65f6\uff0ckubectl \u5c06\u5176\u89c6\u4e3a\u4e0e\u914d\u7f6e\u6587\u4ef6\u6bd4\u8f83\u800c\u8a00\u7684\u76f8\u5bf9\u8def\u5f84\u3002 \u5982\u679c KUBECONFIG \u88ab\u8bbe\u7f6e\u4e3a `/home/jane/kubeconfig`\uff0c\u800c exec \u547d\u4ee4\u4e3a `./bin/example-client-go-exec-plugin`\uff0c\u5219\u8981\u6267\u884c\u7684\u53ef\u6267\u884c\u6587\u4ef6\u4e3a `/home/jane/bin/example-client-go-exec-plugin`\u3002 ```yaml - name: my-user user: exec: # \u5bf9 kubeconfig \u76ee\u5f55\u800c\u8a00\u7684\u76f8\u5bf9\u8def\u5f84 command: \"./bin/example-client-go-exec-plugin\" apiVersion: \"client.authentication.k8s.io/v1beta1\" ``` ### \u8f93\u51fa\u548c\u8f93\u51fa\u683c\u5f0f {#input-and-output-formats} \u6240\u6267\u884c\u7684\u547d\u4ee4\u4f1a\u5728 `stdout` \u6253\u5370 `ExecCredential` \u5bf9\u8c61\u3002 `k8s.io/client-go` \u4f7f\u7528 `status` \u4e2d\u8fd4\u56de\u7684\u51ed\u636e\u4fe1\u606f\u5411 Kubernetes API \u670d\u52a1\u5668 \u6267\u884c\u8eab\u4efd\u8ba4\u8bc1\u3002 \u5728\u4ea4\u4e92\u5f0f\u4f1a\u8bdd\u4e2d\u8fd0\u884c\u65f6\uff0c`stdin` \u662f\u76f4\u63a5\u66b4\u9732\u7ed9\u63d2\u4ef6\u4f7f\u7528\u7684\u3002 \u63d2\u4ef6\u5e94\u8be5\u4f7f\u7528 [TTY check](https://godoc.org/golang.org/x/crypto/ssh/terminal#IsTerminal) \u6765\u786e\u5b9a\u662f\u5426\u9002\u5408\u7528\u4ea4\u4e92\u65b9\u5f0f\u8bf7\u6c42\u7528\u6237\u8f93\u5165\u3002 \u4e0e\u4f7f\u7528\u6301\u6709\u8005\u4ee4\u724c\u51ed\u636e\uff0c\u63d2\u4ef6\u5728 `ExecCredential` \u7684\u72b6\u6001\u4e2d\u8fd4\u56de\u4e00\u4e2a\u4ee4\u724c\uff1a ```json { \"apiVersion\": \"client.authentication.k8s.io/v1beta1\", \"kind\": \"ExecCredential\", \"status\": { \"token\": \"my-bearer-token\" } } ``` \u53e6\u4e00\u79cd\u65b9\u6848\u662f\uff0c\u8fd4\u56de PEM \u7f16\u7801\u7684\u5ba2\u6237\u7aef\u8bc1\u4e66\u548c\u5bc6\u94a5\uff0c\u4ee5\u4fbf\u6267\u884c TLS \u5ba2\u6237\u7aef\u8eab\u4efd\u8ba4\u8bc1\u3002 \u5982\u679c\u63d2\u4ef6\u5728\u540e\u7eed\u8c03\u7528\u4e2d\u8fd4\u56de\u4e86\u4e0d\u540c\u7684\u8bc1\u4e66\u6216\u5bc6\u94a5\uff0c`k8s.io/client-go` \u4f1a\u7ec8\u6b62\u5176\u4e0e\u670d\u52a1\u5668\u7684\u8fde\u63a5\uff0c\u4ece\u800c\u5f3a\u5236\u6267\u884c\u65b0\u7684 TLS \u63e1\u624b\u8fc7\u7a0b\u3002 \u5982\u679c\u6307\u5b9a\u4e86\u8fd9\u79cd\u65b9\u5f0f\uff0c\u5219 `clientKeyData` \u548c `clientCertificateData` \u5b57\u6bb5\u90fd\u5fc5\u9700\u5b58\u5728\u3002 `clientCertificateData` \u5b57\u6bb5\u53ef\u80fd\u5305\u542b\u4e00\u4e9b\u8981\u53d1\u9001\u7ed9\u670d\u52a1\u5668\u7684\u4e2d\u95f4\u8bc1\u4e66\uff08Intermediate Certificates\uff09\u3002 ```json { \"apiVersion\": \"client.authentication.k8s.io/v1beta1\", \"kind\": \"ExecCredential\", \"status\": { \"clientCertificateData\": \"-----BEGIN CERTIFICATE-----n...n-----END CERTIFICATE-----\", \"clientKeyData\": \"-----BEGIN RSA PRIVATE KEY-----n...n-----END RSA PRIVATE KEY-----\" } } ``` \u4f5c\u4e3a\u4e00\u79cd\u53ef\u9009\u65b9\u6848\uff0c\u54cd\u5e94\u4e2d\u8fd8\u53ef\u4ee5\u5305\u542b\u4ee5 RFC3339 \u65f6\u95f4\u6233\u683c\u5f0f\u7ed9\u51fa\u7684\u8bc1\u4e66\u5230\u671f\u65f6\u95f4\u3002 \u8bc1\u4e66\u5230\u671f\u65f6\u95f4\u7684\u6709\u65e0\u4f1a\u6709\u5982\u4e0b\u5f71\u54cd\uff1a - \u5982\u679c\u54cd\u5e94\u4e2d\u5305\u542b\u4e86\u5230\u671f\u65f6\u95f4\uff0c\u6301\u6709\u8005\u4ee4\u724c\u548c TLS \u51ed\u636e\u4f1a\u88ab\u7f13\u5b58\uff0c\u76f4\u5230\u5230\u671f\u671f\u9650\u5230\u6765\u3001 \u6216\u8005\u670d\u52a1\u5668\u8fd4\u56de 401 HTTP \u72b6\u6001\u7801\uff0c\u6216\u8005\u8fdb\u7a0b\u9000\u51fa\u3002 - \u5982\u679c\u672a\u6307\u5b9a\u5230\u671f\u65f6\u95f4\uff0c\u5219\u6301\u6709\u8005\u4ee4\u724c\u548c TLS \u51ed\u636e\u4f1a\u88ab\u7f13\u5b58\uff0c\u76f4\u5230\u670d\u52a1\u5668\u8fd4\u56de 401 HTTP \u72b6\u6001\u7801\u6216\u8005\u8fdb\u7a0b\u9000\u51fa\u3002 ```json { \"apiVersion\": \"client.authentication.k8s.io/v1beta1\", \"kind\": \"ExecCredential\", \"status\": { \"token\": \"my-bearer-token\", \"expirationTimestamp\": \"2018-03-05T17:30:20-08:00\" } } ``` ", "commid": "website_pr_23467"}], "negative_passages": []} {"query_id": "q-en-website-7ae92f761b610feaedf70a069ceb4cb507422b24300789180ed26f65662c8a47", "query": "This is a Feature Request \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u306f\u3001{{< glossary_tooltip text=\"Pod\" term_id=\"pod\">}}\u306e\u30b0\u30eb\u30fc\u30d7\u304c\u3001Pod\u76f8\u4e92\u3084\u4ed6\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a8\u30f3\u30c9\u30dd\u30a4\u30f3\u30c8\u3068\u901a\u4fe1\u3059\u308b\u5834\u5408\u306b\u8a31\u53ef\u3092\u4e0e\u3048\u308b\u65b9\u6cd5\u3092\u6307\u5b9a\u3059\u308b\u305f\u3081\u306e\u4ed5\u69d8\u3067\u3059\u3002 NetworkPolicy\u30ea\u30bd\u30fc\u30b9\u306f\u3001{{< glossary_tooltip text=\"\u30e9\u30d9\u30eb\" term_id=\"label\">}}\u3092\u4f7f\u7528\u3057\u3066Pod\u3092\u9078\u629e\u3057\u3001\u9078\u629e\u3057\u305fPod\u306b\u5bfe\u3057\u3066\u3069\u3093\u306a\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3059\u308b\u304b\u3092\u6307\u5b9a\u3059\u308b\u30eb\u30fc\u30eb\u3092\u5b9a\u7fa9\u3057\u307e\u3059\u3002 ## \u524d\u63d0\u6761\u4ef6 \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u306f\u3001[\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/)\u306b\u3088\u308a\u5b9f\u88c5\u3055\u308c\u307e\u3059\u3002\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u4f7f\u7528\u3059\u308b\u306b\u306f\u3001NetworkPolicy\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3092\u4f7f\u7528\u3057\u306a\u3051\u308c\u3070\u306a\u308a\u307e\u305b\u3093\u3002\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u5b9f\u88c5\u3057\u305f\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u3092\u4f7f\u7528\u305b\u305a\u306bNetworkPolicy\u30ea\u30bd\u30fc\u30b9\u3092\u4f5c\u6210\u3057\u305f\u5834\u5408\u306f\u3001\u4f55\u3082\u52b9\u679c\u306f\u3042\u308a\u307e\u305b\u3093\u3002 ## \u5206\u96e2\u3055\u308c\u305fPod\u3068\u5206\u96e2\u3055\u308c\u3066\u3044\u306a\u3044Pod \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u306f\u3001Pod\u306f\u5206\u96e2\u3055\u308c\u3066\u3044\u306a\u3044\u72b6\u614b(non-isolated)\u3068\u306a\u308b\u305f\u3081\u3001\u3059\u3079\u3066\u306e\u30bd\u30fc\u30b9\u304b\u3089\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u53d7\u4fe1\u3057\u307e\u3059\u3002 Pod\u3092\u9078\u629e\u3059\u308bNetworkPolicy\u304c\u5b58\u5728\u3059\u308b\u3068\u3001Pod\u306f\u5206\u96e2\u3055\u308c\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002\u540d\u524d\u7a7a\u9593\u5185\u306b\u7279\u5b9a\u306ePod\u3092\u9078\u629e\u3059\u308bNetworkPolicy\u304c1\u3064\u3067\u3082\u5b58\u5728\u3059\u308b\u3068\u3001\u305d\u306ePod\u306f\u3044\u305a\u308c\u304b\u306eNetworkPolicy\u3067\u8a31\u53ef\u3055\u308c\u3066\u3044\u306a\u3044\u3059\u3079\u3066\u306e\u63a5\u7d9a\u3092\u62d2\u5426\u3059\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002(\u540c\u3058\u540d\u524d\u7a7a\u9593\u5185\u306ePod\u3067\u3082\u3001\u3069\u306eNetworkPolicy\u306b\u3082\u9078\u629e\u3055\u308c\u306a\u304b\u3063\u305f\u4ed6\u306ePod\u306f\u3001\u5f15\u304d\u7d9a\u304d\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002) \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u306f\u8ffd\u52a0\u5f0f\u3067\u3042\u308b\u305f\u3081\u3001\u7af6\u5408\u3059\u308b\u3053\u3068\u306f\u3042\u308a\u307e\u305b\u3093\u3002\u8907\u6570\u306e\u30dd\u30ea\u30b7\u30fc\u304cPod\u3092\u9078\u629e\u3059\u308b\u5834\u5408\u3001\u305d\u306ePod\u306b\u8a31\u53ef\u3055\u308c\u308b\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306f\u3001\u305d\u308c\u3089\u306e\u30dd\u30ea\u30b7\u30fc\u306eingress/egress\u30eb\u30fc\u30eb\u306e\u548c\u96c6\u5408\u3067\u5236\u9650\u3055\u308c\u307e\u3059\u3002\u3057\u305f\u304c\u3063\u3066\u3001\u8a55\u4fa1\u306e\u9806\u5e8f\u306f\u30dd\u30ea\u30b7\u30fc\u306e\u7d50\u679c\u306b\u306f\u5f71\u97ff\u304c\u3042\u308a\u307e\u305b\u3093\u3002 ## NetworkPolicy\u30ea\u30bd\u30fc\u30b9 {#networkpolicy-resource} \u30ea\u30bd\u30fc\u30b9\u306e\u5b8c\u5168\u306a\u5b9a\u7fa9\u306b\u3064\u3044\u3066\u306f\u3001\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u306e[NetworkPolicy](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#networkpolicy-v1-networking-k8s-io)\u306e\u30bb\u30af\u30b7\u30e7\u30f3\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 \u4ee5\u4e0b\u306f\u3001NetworkPolicy\u306e\u4e00\u4f8b\u3067\u3059\u3002 ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: test-network-policy namespace: default spec: podSelector: matchLabels: role: db policyTypes: - Ingress - Egress ingress: - from: - ipBlock: cidr: 172.17.0.0/16 except: - 172.17.1.0/24 - namespaceSelector: matchLabels: project: myproject - podSelector: matchLabels: role: frontend ports: - protocol: TCP port: 6379 egress: - to: - ipBlock: cidr: 10.0.0.0/24 ports: - protocol: TCP port: 5978 ``` {{< note >}} \u9078\u629e\u3057\u305f\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u304c\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u306a\u3044\u5834\u5408\u306b\u306f\u3001\u3053\u308c\u3092\u30af\u30e9\u30b9\u30bf\u30fc\u306eAPI\u30b5\u30fc\u30d0\u30fc\u306bPOST\u3057\u3066\u3082\u52b9\u679c\u306f\u3042\u308a\u307e\u305b\u3093\u3002 {{< /note >}} __\u5fc5\u9808\u30d5\u30a3\u30fc\u30eb\u30c9__: \u4ed6\u306eKubernetes\u306e\u8a2d\u5b9a\u3068\u540c\u69d8\u306b\u3001NetworkPolicy\u306b\u3082`apiVersion`\u3001`kind`\u3001`metadata`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u5fc5\u9808\u3067\u3059\u3002\u8a2d\u5b9a\u30d5\u30a1\u30a4\u30eb\u306e\u6271\u3044\u65b9\u306b\u95a2\u3059\u308b\u4e00\u822c\u7684\u306a\u60c5\u5831\u306b\u3064\u3044\u3066\u306f\u3001[ConfigMap\u3092\u4f7f\u7528\u3057\u3066\u30b3\u30f3\u30c6\u30ca\u3092\u69cb\u6210\u3059\u308b](/ja/docs/tasks/configure-pod-container/configure-pod-configmap/)\u3068[\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u7ba1\u7406](/ja/docs/concepts/overview/working-with-objects/object-management)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 __spec__: NetworkPolicy\u306e[spec](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)\u3092\u898b\u308b\u3068\u3001\u6307\u5b9a\u3057\u305f\u540d\u524d\u7a7a\u9593\u5185\u3067\u7279\u5b9a\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u5b9a\u7fa9\u3059\u308b\u306e\u306b\u5fc5\u8981\u306a\u3059\u3079\u3066\u306e\u60c5\u5831\u304c\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 __podSelector__: \u5404NetworkPolicy\u306b\u306f\u3001\u30dd\u30ea\u30b7\u30fc\u3092\u9069\u7528\u3059\u308bPod\u306e\u30b0\u30eb\u30fc\u30d7\u3092\u9078\u629e\u3059\u308b`podSelector`\u304c\u542b\u307e\u308c\u307e\u3059\u3002\u30dd\u30ea\u30b7\u30fc\u306e\u4f8b\u3067\u306f\u3001\u30e9\u30d9\u30eb\"role=db\"\u3092\u6301\u3064Pod\u3092\u9078\u629e\u3057\u3066\u3044\u307e\u3059\u3002`podSelector`\u3092\u7a7a\u306b\u3059\u308b\u3068\u3001\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod\u304c\u9078\u629e\u3055\u308c\u307e\u3059\u3002 __policyTypes__: \u5404NetworkPolicy\u306b\u306f\u3001`policyTypes`\u3068\u3057\u3066\u3001`Ingress`\u3001`Egress`\u3001\u307e\u305f\u306f\u305d\u306e\u4e21\u65b9\u304b\u3089\u306a\u308b\u30ea\u30b9\u30c8\u304c\u542b\u307e\u308c\u307e\u3059\u3002`policyTypes`\u30d5\u30a3\u30fc\u30eb\u30c9\u3067\u306f\u3001\u6307\u5b9a\u3057\u305f\u30dd\u30ea\u30b7\u30fc\u304c\u3069\u306e\u7a2e\u985e\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306b\u9069\u7528\u3055\u308c\u308b\u304b\u3092\u5b9a\u3081\u307e\u3059\u3002\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306e\u7a2e\u985e\u3068\u3057\u3066\u306f\u3001\u9078\u629e\u3057\u305fPod\u3078\u306e\u5185\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af(Ingress)\u3001\u9078\u629e\u3057\u305fPod\u304b\u3089\u306e\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af(Egress)\u3001\u307e\u305f\u306f\u305d\u306e\u4e21\u65b9\u3092\u6307\u5b9a\u3057\u307e\u3059\u3002`policyTypes`\u3092\u6307\u5b9a\u3057\u306a\u304b\u3063\u305f\u5834\u5408\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u5e38\u306b `Ingress`\u304c\u6307\u5b9a\u3055\u308c\u3001NetworkPolicy\u306begress\u30eb\u30fc\u30eb\u304c1\u3064\u3067\u3082\u3042\u308c\u3070`Egress`\u3082\u8a2d\u5b9a\u3055\u308c\u307e\u3059\u3002 __ingress__: \u5404NetworkPolicy\u306b\u306f\u3001\u8a31\u53ef\u3059\u308b`ingress`\u30eb\u30fc\u30eb\u306e\u30ea\u30b9\u30c8\u3092\u6307\u5b9a\u3067\u304d\u307e\u3059\u3002\u5404\u30eb\u30fc\u30eb\u306f\u3001`from`\u304a\u3088\u3073`ports`\u30bb\u30af\u30b7\u30e7\u30f3\u306e\u4e21\u65b9\u306b\u4e00\u81f4\u3059\u308b\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002\u30dd\u30ea\u30b7\u30fc\u306e\u4f8b\u306b\u306f1\u3064\u306e\u30eb\u30fc\u30eb\u304c\u542b\u307e\u308c\u3001\u3053\u306e\u30eb\u30fc\u30eb\u306f\u30013\u3064\u306e\u30bd\u30fc\u30b9\u306e\u3044\u305a\u308c\u304b\u304b\u3089\u9001\u4fe1\u3055\u308c\u305f1\u3064\u306e\u30dd\u30fc\u30c8\u4e0a\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306b\u4e00\u81f4\u3057\u307e\u3059\u30021\u3064\u76ee\u306e\u30bd\u30fc\u30b9\u306f`ipBlock`\u3067\u30012\u3064\u76ee\u306e\u30bd\u30fc\u30b9\u306f`namespaceSelector`\u3067\u30013\u3064\u76ee\u306e\u30bd\u30fc\u30b9\u306f`podSelector`\u3067\u305d\u308c\u305e\u308c\u5b9a\u3081\u3089\u308c\u307e\u3059\u3002 __egress__: \u5404NetworkPolicy\u306b\u306f\u3001\u8a31\u53ef\u3059\u308b`egress`\u30eb\u30fc\u30eb\u306e\u30ea\u30b9\u30c8\u3092\u6307\u5b9a\u3067\u304d\u307e\u3059\u3002\u5404\u30eb\u30fc\u30eb\u306f\u3001`to`\u304a\u3088\u3073`ports`\u30bb\u30af\u30b7\u30e7\u30f3\u306e\u4e21\u65b9\u306b\u4e00\u81f4\u3059\u308b\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002\u30dd\u30ea\u30b7\u30fc\u306e\u4f8b\u306b\u306f1\u3064\u306e\u30eb\u30fc\u30eb\u304c\u542b\u307e\u308c\u3001\u3053\u306e\u30eb\u30fc\u30eb\u306f\u30011\u3064\u306e\u30dd\u30fc\u30c8\u4e0a\u3067`10.0.0.0/24`\u306e\u7bc4\u56f2\u5185\u306e\u4efb\u610f\u306e\u9001\u4fe1\u5148\u3078\u9001\u3089\u308c\u308b\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306b\u4e00\u81f4\u3057\u307e\u3059\u3002 \u3057\u305f\u304c\u3063\u3066\u3001\u4e0a\u306eNetworkPolicy\u306e\u4f8b\u3067\u306f\u3001\u6b21\u306e\u3088\u3046\u306b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u9069\u7528\u3057\u307e\u3059\u3002 1. \"default\"\u540d\u524d\u7a7a\u9593\u5185\u306b\u3042\u308b\"role=db\"\u306ePod\u3092\u3001\u5185\u5411\u304d\u3068\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306b\u5bfe\u3057\u3066\u5206\u96e2\u3059\u308b(\u307e\u3060\u5206\u96e2\u3055\u308c\u3066\u3044\u306a\u3044\u5834\u5408) 2. (Ingress\u30eb\u30fc\u30eb) \"default\"\u540d\u524d\u7a7a\u9593\u5185\u306e\"role=db\"\u30e9\u30d9\u30eb\u304c\u4ed8\u3044\u305f\u3059\u3079\u3066\u306ePod\u306eTCP\u306e6379\u756a\u30dd\u30fc\u30c8\u3078\u306e\u63a5\u7d9a\u306e\u3046\u3061\u3001\u6b21\u306e\u9001\u4fe1\u5143\u304b\u3089\u306e\u3082\u306e\u3092\u8a31\u53ef\u3059\u308b * \"default\"\u540d\u524d\u7a7a\u9593\u5185\u306e\u30e9\u30d9\u30eb\"role=frontend\"\u304c\u4ed8\u3044\u305f\u3059\u3079\u3066\u306ePod * \u30e9\u30d9\u30eb\"project=myproject\"\u304c\u4ed8\u3044\u305f\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod * 172.17.0.0\u2013172.17.0.255\u304a\u3088\u3073172.17.2.0\u2013172.17.255.255(\u8a00\u3044\u63db\u3048\u308c\u3070\u3001172.17.1.0/24\u306e\u7bc4\u56f2\u3092\u9664\u304f172.17.0.0/16)\u306e\u7bc4\u56f2\u5185\u306e\u3059\u3079\u3066\u306eIP\u30a2\u30c9\u30ec\u30b9 3. (Egress\u30eb\u30fc\u30eb) \"role=db\"\u3068\u3044\u3046\u30e9\u30d9\u30eb\u304c\u4ed8\u3044\u305f\"default\"\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod\u304b\u3089\u306e\u3001TCP\u306e5978\u756a\u30dd\u30fc\u30c8\u4e0a\u3067\u306eCIDR 10.0.0.0/24\u3078\u306e\u63a5\u7d9a\u3092\u8a31\u53ef\u3059\u308b \u8ffd\u52a0\u306e\u4f8b\u306b\u3064\u3044\u3066\u306f\u3001[\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u5ba3\u8a00\u3059\u308b](/ja/docs/tasks/administer-cluster/declare-network-policy/)\u306e\u8aac\u660e\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ## `to`\u3068`from`\u306e\u30bb\u30ec\u30af\u30bf\u30fc\u306e\u632f\u308b\u821e\u3044 `ingress`\u306e`from`\u30bb\u30af\u30b7\u30e7\u30f3\u307e\u305f\u306f`egress`\u306e`to`\u30bb\u30af\u30b7\u30e7\u30f3\u306b\u6307\u5b9a\u3067\u304d\u308b\u30bb\u30ec\u30af\u30bf\u30fc\u306f4\u7a2e\u985e\u3042\u308a\u307e\u3059\u3002 __podSelector__: NetworkPolicy\u3068\u540c\u3058\u540d\u524d\u7a7a\u9593\u5185\u306e\u7279\u5b9a\u306ePod\u3092\u9078\u629e\u3057\u3066\u3001ingress\u306e\u9001\u4fe1\u5143\u307e\u305f\u306fegress\u306e\u9001\u4fe1\u5148\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002 __namespaceSelector__: \u7279\u5b9a\u306e\u540d\u524d\u7a7a\u9593\u3092\u9078\u629e\u3057\u3066\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod\u306b\u3064\u3044\u3066\u3001ingress\u306e\u9001\u4fe1\u5143\u307e\u305f\u306fegress\u306e\u9001\u4fe1\u5148\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002 __namespaceSelector__ *\u304a\u3088\u3073* __podSelector__: 1\u3064\u306e`to`\u307e\u305f\u306f`from`\u30a8\u30f3\u30c8\u30ea\u30fc\u3067`namespaceSelector`\u3068`podSelector`\u306e\u4e21\u65b9\u3092\u6307\u5b9a\u3057\u3066\u3001\u7279\u5b9a\u306e\u540d\u524d\u7a7a\u9593\u5185\u306e\u7279\u5b9a\u306ePod\u3092\u9078\u629e\u3057\u307e\u3059\u3002\u6b63\u3057\u3044YAML\u306e\u69cb\u6587\u3092\u4f7f\u3046\u3088\u3046\u306b\u6c17\u3092\u3064\u3051\u3066\u304f\u3060\u3055\u3044\u3002\u3053\u306e\u30dd\u30ea\u30b7\u30fc\u306e\u4f8b\u3092\u4ee5\u4e0b\u306b\u793a\u3057\u307e\u3059\u3002 ```yaml ... ingress: - from: - namespaceSelector: matchLabels: user: alice podSelector: matchLabels: role: client ... ``` \u3053\u306e\u30dd\u30ea\u30b7\u30fc\u306b\u306f\u30011\u3064\u306e`from`\u8981\u7d20\u304c\u3042\u308a\u3001\u30e9\u30d9\u30eb`user=alice`\u306e\u4ed8\u3044\u305f\u540d\u524d\u7a7a\u9593\u5185\u306b\u3042\u308b\u3001\u30e9\u30d9\u30eb`role=client`\u306e\u4ed8\u3044\u305fPod\u304b\u3089\u306e\u63a5\u7d9a\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002\u3057\u304b\u3057\u3001*\u4ee5\u4e0b\u306e*\u30dd\u30ea\u30b7\u30fc\u306b\u306f\u6ce8\u610f\u304c\u5fc5\u8981\u3067\u3059\u3002 ```yaml ... ingress: - from: - namespaceSelector: matchLabels: user: alice - podSelector: matchLabels: role: client ... ``` \u3053\u306e\u30dd\u30ea\u30b7\u30fc\u306b\u306f\u3001`from`\u914d\u5217\u306e\u4e2d\u306b2\u3064\u306e\u8981\u7d20\u304c\u3042\u308a\u307e\u3059\u3002\u305d\u306e\u305f\u3081\u3001\u30e9\u30d9\u30eb`role=client`\u306e\u4ed8\u3044\u305f\u540d\u524d\u7a7a\u9593\u5185\u306b\u3042\u308b\u3059\u3079\u3066\u306ePod\u304b\u3089\u306e\u63a5\u7d9a\u3001*\u307e\u305f\u306f*\u3001\u4efb\u610f\u306e\u540d\u524d\u7a7a\u9593\u5185\u306b\u3042\u308b\u30e9\u30d9\u30eb`user=alice`\u306e\u4ed8\u3044\u305f\u3059\u3079\u3066\u306ePod\u304b\u3089\u306e\u63a5\u7d9a\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002 \u6b63\u3057\u3044\u30eb\u30fc\u30eb\u306b\u306a\u3063\u3066\u3044\u308b\u304b\u81ea\u4fe1\u304c\u306a\u3044\u3068\u304d\u306f\u3001`kubectl describe`\u3092\u4f7f\u7528\u3059\u308b\u3068\u3001Kubernetes\u304c\u3069\u306e\u3088\u3046\u306b\u30dd\u30ea\u30b7\u30fc\u3092\u89e3\u91c8\u3057\u305f\u306e\u304b\u3092\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 __ipBlock__: \u7279\u5b9a\u306eIP\u306eCIDR\u306e\u7bc4\u56f2\u3092\u9078\u629e\u3057\u3066\u3001ingress\u306e\u9001\u4fe1\u5143\u307e\u305f\u306fegress\u306e\u9001\u4fe1\u5148\u3092\u8a31\u53ef\u3057\u307e\u3059\u3002Pod\u306eIP\u306f\u4e00\u6642\u7684\u306a\u3082\u306e\u3067\u4e88\u6e2c\u3067\u304d\u306a\u3044\u305f\u3081\u3001\u3053\u3053\u306b\u306f\u30af\u30e9\u30b9\u30bf\u30fc\u5916\u306eIP\u3092\u6307\u5b9a\u3059\u308b\u3079\u304d\u3067\u3059\u3002 \u30af\u30e9\u30b9\u30bf\u30fc\u306eingress\u3068egress\u306e\u4ed5\u7d44\u307f\u306f\u30d1\u30b1\u30c3\u30c8\u306e\u9001\u4fe1\u5143IP\u3084\u9001\u4fe1\u5148IP\u306e\u66f8\u304d\u63db\u3048\u3092\u5fc5\u8981\u3068\u3059\u308b\u3053\u3068\u304c\u3088\u304f\u3042\u308a\u307e\u3059\u3002\u305d\u306e\u5834\u5408\u3001NetworkPolicy\u306e\u51e6\u7406\u304cIP\u306e\u66f8\u304d\u63db\u3048\u306e\u524d\u5f8c\u3069\u3061\u3089\u3067\u884c\u308f\u308c\u308b\u306e\u304b\u306f\u5b9a\u7fa9\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002\u305d\u306e\u305f\u3081\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30e9\u30b0\u30a4\u30f3\u3001\u30af\u30e9\u30a6\u30c9\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3001`Service`\u306e\u5b9f\u88c5\u306a\u3069\u306e\u7d44\u307f\u5408\u308f\u305b\u306b\u3088\u3063\u3066\u306f\u3001\u52d5\u4f5c\u304c\u7570\u306a\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002 \u5185\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306e\u5834\u5408\u306f\u3001\u5b9f\u969b\u306e\u30aa\u30ea\u30b8\u30ca\u30eb\u306e\u9001\u4fe1\u5143IP\u306b\u57fa\u3065\u3044\u3066\u30d1\u30b1\u30c3\u30c8\u3092\u30d5\u30a3\u30eb\u30bf\u30ea\u30f3\u30b0\u3067\u304d\u308b\u53ef\u80fd\u6027\u3082\u3042\u308c\u3070\u3001NetworkPolicy\u304c\u5bfe\u8c61\u3068\u3059\u308b\u300c\u9001\u4fe1\u5143IP\u300d\u304c`LoadBalancer`\u3084Pod\u306e\u30ce\u30fc\u30c9\u306a\u3069\u306eIP\u306b\u306a\u3063\u3066\u3057\u307e\u3063\u3066\u3044\u308b\u53ef\u80fd\u6027\u3082\u3042\u308b\u3053\u3068\u306b\u306a\u308a\u307e\u3059\u3002 \u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306e\u5834\u5408\u306f\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u5916\u306eIP\u306b\u66f8\u304d\u63db\u3048\u3089\u308c\u305fPod\u304b\u3089`Service`\u306eIP\u3078\u306e\u63a5\u7d9a\u306f\u3001`ipBlock`\u30d9\u30fc\u30b9\u306e\u30dd\u30ea\u30b7\u30fc\u306e\u5bfe\u8c61\u306b\u306a\u308b\u5834\u5408\u3068\u306a\u3089\u306a\u3044\u5834\u5408\u304c\u3042\u308b\u3053\u3068\u306b\u306a\u308a\u307e\u3059\u3002 ## \u30c7\u30d5\u30a9\u30eb\u30c8\u306e\u30dd\u30ea\u30b7\u30fc \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u306f\u3001\u540d\u524d\u7a7a\u9593\u306b\u30dd\u30ea\u30b7\u30fc\u304c\u5b58\u5728\u3057\u306a\u3044\u5834\u5408\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u5185\u306ePod\u306e\u5185\u5411\u304d\u3068\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u306f\u3059\u3079\u3066\u8a31\u53ef\u3055\u308c\u307e\u3059\u3002\u4ee5\u4e0b\u306e\u4f8b\u3092\u5229\u7528\u3059\u308b\u3068\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u5185\u3067\u306e\u30c7\u30d5\u30a9\u30eb\u30c8\u306e\u632f\u308b\u821e\u3044\u3092\u5909\u66f4\u3067\u304d\u307e\u3059\u3002 ### \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u3059\u3079\u3066\u306e\u5185\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u62d2\u5426\u3059\u308b \u3059\u3079\u3066\u306ePod\u3092\u9078\u629e\u3057\u3066\u3001\u305d\u306ePod\u3078\u306e\u3059\u3079\u3066\u306e\u5185\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u306a\u3044NetworkPolicy\u3092\u4f5c\u6210\u3059\u308b\u3068\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u306b\u5bfe\u3059\u308b\u300c\u30c7\u30d5\u30a9\u30eb\u30c8\u300d\u306e\u5206\u96e2\u30dd\u30ea\u30b7\u30fc\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002 {{< codenew file=\"service/networking/network-policy-default-deny-ingress.yaml\" >}} \u3053\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u5229\u7528\u3059\u308c\u3070\u3001\u4ed6\u306e\u3044\u304b\u306a\u308bNetworkPolicy\u306b\u3082\u9078\u629e\u3055\u308c\u306a\u304b\u3063\u305fPod\u3067\u3082\u5206\u96e2\u3055\u308c\u308b\u3053\u3068\u3092\u4fdd\u8a3c\u3067\u304d\u307e\u3059\u3002\u3053\u306e\u30dd\u30ea\u30b7\u30fc\u306f\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u306e\u5916\u5411\u304d\u306e\u5206\u96e2\u306e\u632f\u308b\u821e\u3044\u3092\u5909\u66f4\u3057\u307e\u305b\u3093\u3002 ### \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u5185\u5411\u304d\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3059\u308b (\u305f\u3068\u3048Pod\u3092\u300c\u5206\u96e2\u3055\u308c\u305f\u3082\u306e\u300d\u3068\u3057\u3066\u6271\u3046\u30dd\u30ea\u30b7\u30fc\u304c\u8ffd\u52a0\u3055\u308c\u305f\u5834\u5408\u3067\u3082)\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod\u3078\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u305f\u3044\u5834\u5408\u306b\u306f\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u660e\u793a\u7684\u306b\u8a31\u53ef\u3059\u308b\u30dd\u30ea\u30b7\u30fc\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002 {{< codenew file=\"service/networking/network-policy-allow-all-ingress.yaml\" >}} ### \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u5916\u5411\u304d\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u62d2\u5426\u3059\u308b \u3059\u3079\u3066\u306ePod\u3092\u9078\u629e\u3057\u3066\u3001\u305d\u306ePod\u304b\u3089\u306e\u3059\u3079\u3066\u306e\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u306a\u3044NetworkPolicy\u3092\u4f5c\u6210\u3059\u308b\u3068\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u306b\u5bfe\u3059\u308b\u300c\u30c7\u30d5\u30a9\u30eb\u30c8\u300d\u306e\u5916\u5411\u304d\u306e\u5206\u96e2\u30dd\u30ea\u30b7\u30fc\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002 {{< codenew file=\"service/networking/network-policy-default-deny-egress.yaml\" >}} \u3053\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u5229\u7528\u3059\u308c\u3070\u3001\u4ed6\u306e\u3044\u304b\u306a\u308bNetworkPolicy\u306b\u3082\u9078\u629e\u3055\u308c\u306a\u304b\u3063\u305fPod\u3067\u3082\u3001\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u304c\u8a31\u53ef\u3055\u308c\u306a\u3044\u3053\u3068\u3092\u4fdd\u8a3c\u3067\u304d\u307e\u3059\u3002\u3053\u306e\u30dd\u30ea\u30b7\u30fc\u306f\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u306e\u5185\u5411\u304d\u306e\u5206\u96e2\u306e\u632f\u308b\u821e\u3044\u3092\u5909\u66f4\u3057\u307e\u305b\u3093\u3002 ### \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u5916\u5411\u304d\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3059\u308b (\u305f\u3068\u3048Pod\u3092\u300c\u5206\u96e2\u3055\u308c\u305f\u3082\u306e\u300d\u3068\u3057\u3066\u6271\u3046\u30dd\u30ea\u30b7\u30fc\u304c\u8ffd\u52a0\u3055\u308c\u305f\u5834\u5408\u3067\u3082)\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306ePod\u304b\u3089\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u8a31\u53ef\u3057\u305f\u3044\u5834\u5408\u306b\u306f\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u5185\u306e\u3059\u3079\u3066\u306e\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u660e\u793a\u7684\u306b\u8a31\u53ef\u3059\u308b\u30dd\u30ea\u30b7\u30fc\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002 {{< codenew file=\"service/networking/network-policy-allow-all-egress.yaml\" >}} ### \u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u5185\u5411\u304d\u3068\u5916\u5411\u304d\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u62d2\u5426\u3059\u308b \u540d\u524d\u7a7a\u9593\u5185\u306b\u4ee5\u4e0b\u306eNetworkPolicy\u3092\u4f5c\u6210\u3059\u308b\u3068\u3001\u305d\u306e\u540d\u524d\u7a7a\u9593\u3067\u5185\u5411\u304d\u3068\u5916\u5411\u304d\u306e\u3059\u3079\u3066\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u62d2\u5426\u3059\u308b\u300c\u30c7\u30d5\u30a9\u30eb\u30c8\u300d\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002 {{< codenew file=\"service/networking/network-policy-default-deny-all.yaml\" >}} \u3053\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u5229\u7528\u3059\u308c\u3070\u3001\u4ed6\u306e\u3044\u304b\u306a\u308bNetworkPolicy\u306b\u3082\u9078\u629e\u3055\u308c\u306a\u304b\u3063\u305fPod\u3067\u3082\u3001\u5185\u5411\u304d\u3068\u5916\u5411\u304d\u306e\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u304c\u8a31\u53ef\u3055\u308c\u306a\u3044\u3053\u3068\u3092\u4fdd\u8a3c\u3067\u304d\u307e\u3059\u3002 ## SCTP\u306e\u30b5\u30dd\u30fc\u30c8 {{< feature-state for_k8s_version=\"v1.12\" state=\"alpha\" >}} \u3053\u306e\u6a5f\u80fd\u3092\u5229\u7528\u3059\u308b\u306b\u306f\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u7ba1\u7406\u8005\u304cAPI\u30b5\u30fc\u30d0\u30fc\u3067`--feature-gates=SCTPSupport=true,\u2026`\u3068\u6307\u5b9a\u3057\u3066\u3001`SCTPSupport`[\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8](/ja/docs/reference/command-line-tools-reference/feature-gates/)\u3092\u6709\u52b9\u306b\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8\u304c\u6709\u52b9\u306b\u306a\u308c\u3070\u3001NetworkPolicy\u306e`protocol`\u30d5\u30a3\u30fc\u30eb\u30c9\u306b`SCTP`\u304c\u6307\u5b9a\u3067\u304d\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002 {{< note >}} SCTP\u30d7\u30ed\u30c8\u30b3\u30eb\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b{{< glossary_tooltip text=\"CNI\" term_id=\"cni\" >}}\u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 {{< /note >}} ## {{% heading \"whatsnext\" %}} - [\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u5ba3\u8a00\u3059\u308b](/ja/docs/tasks/administer-cluster/declare-network-policy/)\u3067\u8ffd\u52a0\u306e\u4f8b\u306e\u8aac\u660e\u3092\u8aad\u3080\u3002 - NetworkPolicy\u30ea\u30bd\u30fc\u30b9\u3067\u5b9f\u73fe\u3067\u304d\u308b\u3088\u304f\u3042\u308b\u30b7\u30ca\u30ea\u30aa\u306e\u305f\u3081\u306e\u3055\u307e\u3056\u307e\u306a[\u30ec\u30b7\u30d4](https://github.com/ahmetb/kubernetes-network-policy-recipes)\u3092\u78ba\u8a8d\u3059\u308b\u3002 ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350", "query": "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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale", "positive_passages": [{"docid": "doc-en-website-f58b916b792edcc3e8334c28f7b35cbcc3bbc22434f5d976a2ac90cd94ba3d80", "text": " --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-all-egress spec: podSelector: {} egress: - {} policyTypes: - Egress ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350", "query": "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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale", "positive_passages": [{"docid": "doc-en-website-8dc2afd63988141a5d13a514eb7d2afe6ce7faebcb6266f861c02adb73d42df1", "text": " --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: allow-all-ingress spec: podSelector: {} ingress: - {} policyTypes: - Ingress ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350", "query": "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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale", "positive_passages": [{"docid": "doc-en-website-f13d982f83614bd85070e08af8512f1bf6f9ca95ea76212f42a22ed9226a6754", "text": " --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-all spec: podSelector: {} policyTypes: - Ingress - Egress ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350", "query": "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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale", "positive_passages": [{"docid": "doc-en-website-203f37b200db88b91a4eaa11287ab731a304e7e130d4cc61e721bad6ae63d95a", "text": " --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-egress spec: podSelector: {} policyTypes: - Egress ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c8edf2ccf50910d63915304f774a4c37702d6a96bfeb247ab3d91e266dc08350", "query": "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\nIssues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale", "positive_passages": [{"docid": "doc-en-website-a3a019c74ffd026c879a8bdfb18ba45ae980fc7a9eac9cf425ffef3992796d7e", "text": " --- apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: default-deny-ingress spec: podSelector: {} policyTypes: - Ingress ", "commid": "website_pr_23235"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-c3b1cc61b2743ad79d4eaa483e4ed200980ad4cdd23e8794459979056b8d2c9e", "query": "This is an enhancement Request ", "commid": "website_pr_23054"}], "negative_passages": []} {"query_id": "q-en-website-01010a6817889a9d5adf5c2a2d5762fd31162dac42b2962e212a1b80985f4eca", "query": "This is a Bug Report {{< feature-state for_k8s_version=\"v1.18\" state=\"beta\" >}} Kubernetes\u3092\u4f7f\u7528\u3057\u3066Linux\u30ce\u30fc\u30c9\u3068Windows\u30ce\u30fc\u30c9\u3092\u6df7\u5728\u3055\u305b\u3066\u5b9f\u884c\u3067\u304d\u308b\u305f\u3081\u3001Linux\u3067\u5b9f\u884c\u3059\u308bPod\u3068Windows\u3067\u5b9f\u884c\u3059\u308bPod\u3092\u6df7\u5728\u3055\u305b\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002\u3053\u306e\u30da\u30fc\u30b8\u3067\u306f\u3001Windows\u30ce\u30fc\u30c9\u3092\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u767b\u9332\u3059\u308b\u65b9\u6cd5\u3092\u793a\u3057\u307e\u3059\u3002 ## {{% heading \"prerequisites\" %}} {{< version-check >}} * Windows\u30b3\u30f3\u30c6\u30ca\u3092\u30db\u30b9\u30c8\u3059\u308bWindows\u30ce\u30fc\u30c9\u3092\u69cb\u6210\u3059\u308b\u306b\u306f\u3001[Windows Server 2019\u30e9\u30a4\u30bb\u30f3\u30b9](https://www.microsoft.com/en-us/cloud-platform/windows-server-pricing)(\u307e\u305f\u306f\u305d\u308c\u4ee5\u4e0a)\u3092\u53d6\u5f97\u3057\u307e\u3059\u3002 VXLAN/\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306f\u3001[KB4489899](https://support.microsoft.com/help/4489899)\u3082\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3055\u308c\u3066\u3044\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 * \u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u306b\u30a2\u30af\u30bb\u30b9\u3067\u304d\u308bLinux\u30d9\u30fc\u30b9\u306eKubernetes kubeadm\u30af\u30e9\u30b9\u30bf\u30fc([kubeadm\u3092\u4f7f\u7528\u3057\u305f\u5358\u4e00\u306e\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u30af\u30e9\u30b9\u30bf\u30fc\u306e\u4f5c\u6210](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)\u3092\u53c2\u7167) ## {{% heading \"objectives\" %}} * Windows\u30ce\u30fc\u30c9\u3092\u30af\u30e9\u30b9\u30bf\u30fc\u306b\u767b\u9332\u3059\u308b * Linux\u3068Windows\u306ePod\u3068Service\u304c\u76f8\u4e92\u306b\u901a\u4fe1\u3067\u304d\u308b\u3088\u3046\u306b\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u69cb\u6210\u3059\u308b ## \u306f\u3058\u3081\u306b: \u30af\u30e9\u30b9\u30bf\u3078\u306eWindows\u30ce\u30fc\u30c9\u306e\u8ffd\u52a0 ### \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u69cb\u6210 Linux\u30d9\u30fc\u30b9\u306eKubernetes\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u30ce\u30fc\u30c9\u3092\u53d6\u5f97\u3057\u305f\u3089\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30ad\u30f3\u30b0\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3092\u9078\u629e\u3067\u304d\u307e\u3059\u3002\u3053\u306e\u30ac\u30a4\u30c9\u3067\u306f\u3001\u7c21\u5358\u306b\u3059\u308b\u305f\u3081\u306bVXLAN\u30e2\u30fc\u30c9\u3067\u306eFlannel\u306e\u4f7f\u7528\u306b\u3064\u3044\u3066\u8aac\u660e\u3057\u307e\u3059\u3002 #### Flannel\u69cb\u6210 1. Flannel\u306e\u305f\u3081\u306bKubernetes\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u3092\u6e96\u5099\u3059\u308b \u30af\u30e9\u30b9\u30bf\u30fc\u5185\u306eKubernetes\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u3067\u306f\u3001\u591a\u5c11\u306e\u6e96\u5099\u304c\u63a8\u5968\u3055\u308c\u307e\u3059\u3002Flannel\u3092\u4f7f\u7528\u3059\u308b\u5834\u5408\u306f\u3001iptables\u30c1\u30a7\u30fc\u30f3\u3078\u306e\u30d6\u30ea\u30c3\u30b8IPv4\u30c8\u30e9\u30d5\u30a3\u30c3\u30af\u3092\u6709\u52b9\u306b\u3059\u308b\u3053\u3068\u3092\u304a\u52e7\u3081\u3057\u307e\u3059\u3002\u3059\u3079\u3066\u306eLinux\u30ce\u30fc\u30c9\u3067\u6b21\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059: ```bash sudo sysctl net.bridge.bridge-nf-call-iptables=1 ``` 1. Linux\u7528\u306eFlannel\u3092\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9\u3057\u3066\u69cb\u6210\u3059\u308b \u6700\u65b0\u306eFlannel\u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u3092\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9: ```bash wget https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml ``` VNI\u30924096\u3001\u30dd\u30fc\u30c8\u30924789\u306b\u8a2d\u5b9a\u3059\u308b\u305f\u3081\u306b\u3001flannel\u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u306e`net-conf.json`\u30bb\u30af\u30b7\u30e7\u30f3\u3092\u5909\u66f4\u3057\u307e\u3059\u3002\u6b21\u306e\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002: ```json net-conf.json: | { \"Network\": \"10.244.0.0/16\", \"Backend\": { \"Type\": \"vxlan\", \"VNI\" : 4096, \"Port\": 4789 } } ``` {{< note >}}Linux\u4e0a\u306eFlannel\u304cWindows\u4e0a\u306eFlannel\u3068\u76f8\u4e92\u904b\u7528\u3059\u308b\u306b\u306f\u3001VNI\u30924096\u304a\u3088\u3073\u30dd\u30fc\u30c84789\u306b\u8a2d\u5b9a\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u30d5\u30a3\u30fc\u30eb\u30c9\u306e\u8aac\u660e\u306b\u3064\u3044\u3066\u306f\u3001[VXLAN\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002{{< /note >}} {{< note >}}L2Bridge/Host-gateway\u30e2\u30fc\u30c9\u3092\u4f7f\u7528\u3059\u308b\u306b\u306f\u3001\u4ee3\u308f\u308a\u306b`Type`\u306e\u5024\u3092`\"host-gw\"`\u306b\u5909\u66f4\u3057\u3001`VNI`\u3068`Port`\u3092\u7701\u7565\u3057\u307e\u3059\u3002{{< /note >}} 1. Flannel\u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u3092\u9069\u7528\u3057\u3066\u691c\u8a3c\u3059\u308b Flannel\u306e\u69cb\u6210\u3092\u9069\u7528\u3057\u307e\u3057\u3087\u3046: ```bash kubectl apply -f kube-flannel.yml ``` \u6570\u5206\u5f8c\u3001Flannel Pod\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u304c\u30c7\u30d7\u30ed\u30a4\u3055\u308c\u3066\u3044\u308c\u3070\u3001\u3059\u3079\u3066\u306ePod\u304c\u5b9f\u884c\u3055\u308c\u3066\u3044\u308b\u3053\u3068\u304c\u308f\u304b\u308a\u307e\u3059\u3002 ```bash kubectl get pods -n kube-system ``` \u51fa\u529b\u7d50\u679c\u306b\u306f\u3001\u5b9f\u884c\u4e2d\u306eLinux flannel DaemonSet\u304c\u542b\u307e\u308c\u3066\u3044\u308b\u306f\u305a\u3067\u3059: ``` NAMESPACE NAME READY STATUS RESTARTS AGE ... kube-system kube-flannel-ds-54954 1/1 Running 0 1m ``` 1. Windows Flannel\u3068kube-proxy DaemonSet\u3092\u8ffd\u52a0\u3059\u308b \u3053\u308c\u3067\u3001Windows\u4e92\u63db\u30d0\u30fc\u30b8\u30e7\u30f3\u306eFlannel\u304a\u3088\u3073kube-proxy\u3092\u8ffd\u52a0\u3067\u304d\u307e\u3059\u3002 \u9806\u756a\u306b\u4e92\u63db\u6027\u306e\u3042\u308b\u30d0\u30fc\u30b8\u30e7\u30f3\u306ekube-proxy\u3092\u78ba\u5b9f\u306b\u5165\u624b\u3059\u308b\u306b\u306f\u3001\u30a4\u30e1\u30fc\u30b8\u306e\u30bf\u30b0\u3092\u4ee3\u7528\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 \u6b21\u306e\u4f8b\u306f\u3001Kubernetes{{< param \"fullversion\" >}}\u306e\u4f7f\u7528\u65b9\u6cd5\u3092\u793a\u3057\u3066\u3044\u307e\u3059\u304c\u3001 \u72ec\u81ea\u306edeployment\u306b\u5408\u308f\u305b\u3066\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u8abf\u6574\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 ```bash curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed 's/VERSION/{{< param \"fullversion\" >}}/g' | kubectl apply -f - kubectl apply -f https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-overlay.yml ``` {{< note >}} \u30db\u30b9\u30c8\u30b2\u30fc\u30c8\u30a6\u30a7\u30a4\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306f\u3001\u4ee3\u308f\u308a\u306bhttps://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-host-gw.yml\u3092\u4f7f\u7528\u3057\u3066\u304f\u3060\u3055\u3044\u3002 {{< /note >}} {{< note >}} Windows\u30ce\u30fc\u30c9\u3067\u30a4\u30fc\u30b5\u30cd\u30c3\u30c8(\u300cEthernet0 2\u300d\u306a\u3069)\u3067\u306f\u306a\u304f\u5225\u306e\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30fc\u30b9\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306f\u3001\u6b21\u306e\u884c\u3092\u5909\u66f4\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002: ```powershell wins cli process run --path /k/flannel/setup.exe --args \"--mode=overlay --interface=Ethernet\" ``` `flannel-host-gw.yml`\u307e\u305f\u306f`flannel-overlay.yml`\u30d5\u30a1\u30a4\u30eb\u3067\u3001\u305d\u308c\u306b\u5fdc\u3058\u3066\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30fc\u30b9\u3092\u6307\u5b9a\u3057\u307e\u3059\u3002 ```bash # \u4f8b curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/flannel-overlay.yml | sed 's/Ethernet/Ethernet0 2/g' | kubectl apply -f - ``` {{< /note >}} ### Windows\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306e\u53c2\u52a0 {{< note >}} `Containers`\u6a5f\u80fd\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u3001Docker\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 \u884c\u3046\u305f\u3081\u306e\u6307\u793a\u3068\u3057\u3066\u306f\u3001[Docker\u30a8\u30f3\u30b8\u30f3\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb - Windows\u30b5\u30fc\u30d0\u30fc\u4e0a\u306e\u30a8\u30f3\u30bf\u30fc\u30d7\u30e9\u30a4\u30ba](https://docs.mirantis.com/docker-enterprise/v3.1/dockeree-products/docker-engine-enterprise/dee-windows.html)\u3092\u5229\u7528\u3067\u304d\u307e\u3059\u3002 {{< /note >}} {{< note >}} Windows\u30bb\u30af\u30b7\u30e7\u30f3\u306e\u3059\u3079\u3066\u306e\u30b3\u30fc\u30c9\u30b9\u30cb\u30da\u30c3\u30c8\u306f\u3001 Windows\u30ef\u30fc\u30ab\u30fc\u30ce\u30fc\u30c9\u306e(\u7ba1\u7406\u8005)\u6a29\u9650\u3092\u6301\u3064PowerShell\u74b0\u5883\u3067\u5b9f\u884c\u3055\u308c\u307e\u3059\u3002 {{< /note >}} 1. wins\u3001kubelet\u3001kubeadm\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3057\u307e\u3059\u3002 ```PowerShell curl.exe -LO https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/PrepareNode.ps1 .PrepareNode.ps1 -KubernetesVersion {{< param \"fullversion\" >}} ``` 1. `kubeadm`\u3092\u5b9f\u884c\u3057\u3066\u30ce\u30fc\u30c9\u306b\u53c2\u52a0\u3057\u307e\u3059 \u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u30db\u30b9\u30c8\u3067`kubeadm init`\u3092\u5b9f\u884c\u3057\u305f\u3068\u304d\u306b\u63d0\u4f9b\u3055\u308c\u305f\u30b3\u30de\u30f3\u30c9\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002 \u3053\u306e\u30b3\u30de\u30f3\u30c9\u304c\u306a\u304f\u306a\u3063\u305f\u5834\u5408\u3001\u307e\u305f\u306f\u30c8\u30fc\u30af\u30f3\u306e\u6709\u52b9\u671f\u9650\u304c\u5207\u308c\u3066\u3044\u308b\u5834\u5408\u306f\u3001`kubeadm token create --print-join-command` (\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u30db\u30b9\u30c8\u4e0a\u3067)\u3092\u5b9f\u884c\u3057\u3066\u65b0\u3057\u3044\u30c8\u30fc\u30af\u30f3\u3092\u751f\u6210\u3057\u307e\u3059\u3002 #### \u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u306e\u78ba\u8a8d \u6b21\u306e\u30b3\u30de\u30f3\u30c9\u3092\u5b9f\u884c\u3057\u3066\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u5185\u306eWindows\u30ce\u30fc\u30c9\u3092\u8868\u793a\u3067\u304d\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059: ```bash kubectl get nodes -o wide ``` \u65b0\u3057\u3044\u30ce\u30fc\u30c9\u304c`NotReady`\u72b6\u614b\u306e\u5834\u5408\u306f\u3001flannel\u30a4\u30e1\u30fc\u30b8\u304c\u307e\u3060\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9\u3055\u308c\u3066\u3044\u308b\u53ef\u80fd\u6027\u304c\u3042\u308a\u307e\u3059\u3002 `kube-system`\u540d\u524d\u7a7a\u9593\u306eflannel Pod\u3092\u78ba\u8a8d\u3059\u308b\u3053\u3068\u3067\u3001\u4ee5\u524d\u3068\u540c\u69d8\u306b\u9032\u884c\u72b6\u6cc1\u3092\u78ba\u8a8d\u3067\u304d\u307e\u3059: ```shell kubectl -n kube-system get pods -l app=flannel ``` flannel Pod\u304c\u5b9f\u884c\u3055\u308c\u308b\u3068\u3001\u30ce\u30fc\u30c9\u306f`Ready`\u72b6\u614b\u306b\u306a\u308a\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3092\u51e6\u7406\u3067\u304d\u308b\u3088\u3046\u306b\u306a\u308a\u307e\u3059\u3002 ## {{% heading \"whatsnext\" %}} - [Windows kubeadm\u30ce\u30fc\u30c9\u306e\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9](/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes) ", "commid": "website_pr_23495"}], "negative_passages": []} {"query_id": "q-en-website-f75f3e286dd9913351f125cba4a923934d4fc31a459f4212e057e685142d01b5", "query": "This is a Bug Report Kubernetes\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306b\u4f55\u304b\u554f\u984c\u3092\u898b\u3064\u3051\u305f\u308a\u3001\u65b0\u3057\u3044\u30b3\u30f3\u30c6\u30f3\u30c4\u306b\u95a2\u3057\u3066\u30a2\u30a4\u30c7\u30a2\u3092\u601d\u3044\u4ed8\u3044\u305f\u3068\u304d\u306f\u3001issue\u3092\u4f5c\u3063\u3066\u304f\u3060\u3055\u3044\u3002\u5fc5\u8981\u306a\u3082\u306e\u306f\u3001[GitHub\u30a2\u30ab\u30a6\u30f3\u30c8](https://github.com/join)\u3068\u30a6\u30a7\u30d6\u30d6\u30e9\u30a6\u30b6\u30fc\u3060\u3051\u3067\u3059\u3002 Kubernetes\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u4e0a\u306e\u65b0\u3057\u3044\u4f5c\u696d\u306f\u3001\u307b\u3068\u3093\u3069\u306e\u5834\u5408\u3001GitHub\u306eissue\u304b\u3089\u59cb\u307e\u308a\u307e\u3059\u3002Kubernetes\u306e\u30b3\u30f3\u30c8\u30ea\u30d3\u30e5\u30fc\u30bf\u30fc\u306f\u3001\u5fc5\u8981\u306b\u5fdc\u3058\u3066\u30ec\u30d3\u30e5\u30fc\u3001\u5206\u985e\u3001\u30bf\u30b0\u4ed8\u3051\u3092\u884c\u3044\u307e\u3059\u3002\u6b21\u306b\u3001\u3042\u306a\u305f\u3084Kubernetes\u30b3\u30df\u30e5\u30cb\u30c6\u30a3\u306e\u4ed6\u306e\u30e1\u30f3\u30d0\u30fc\u304c\u3001\u305d\u306eissue\u3092\u89e3\u6c7a\u3059\u308b\u305f\u3081\u306e\u5909\u66f4\u3092\u52a0\u3048\u308bpull request\u3092\u958b\u304d\u307e\u3059\u3002 ## issue\u3092\u4f5c\u308b \u65e2\u5b58\u306e\u30b3\u30f3\u30c6\u30f3\u30c4\u306b\u5bfe\u3057\u3066\u6539\u5584\u3092\u63d0\u6848\u3057\u305f\u3044\u5834\u5408\u3084\u3001\u9593\u9055\u3044\u3092\u767a\u898b\u3057\u305f\u5834\u5408\u306f\u3001issue\u3092\u4f5c\u3063\u3066\u304f\u3060\u3055\u3044\u3002 1. \u30da\u30fc\u30b8\u306e\u53f3\u5074\u306e\u30b5\u30a4\u30c9\u30d0\u30fc\u306b\u3042\u308b**\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306eissue\u3092\u4f5c\u6210**\u30dc\u30bf\u30f3\u3092\u30af\u30ea\u30c3\u30af\u3057\u307e\u3059\u3002GitHub\u306eissue\u30da\u30fc\u30b8\u306b\u30ea\u30c0\u30a4\u30ec\u30af\u30c8\u3057\u3001\u4e00\u90e8\u306e\u30d8\u30c3\u30c0\u30fc\u304c\u81ea\u52d5\u7684\u306b\u633f\u5165\u3055\u308c\u307e\u3059\u3002 2. \u554f\u984c\u3084\u6539\u5584\u306e\u63d0\u6848\u306b\u3064\u3044\u3066\u66f8\u304d\u307e\u3059\u3002\u3067\u304d\u308b\u9650\u308a\u591a\u304f\u306e\u8a73\u7d30\u60c5\u5831\u3092\u63d0\u4f9b\u3059\u308b\u3088\u3046\u306b\u3057\u3066\u304f\u3060\u3055\u3044\u3002 3. **Submit new issue**\u30dc\u30bf\u30f3\u3092\u30af\u30ea\u30c3\u30af\u3057\u307e\u3059\u3002 \u9001\u4fe1\u5f8c\u3001\u5b9a\u671f\u7684\u306bissue\u3092\u78ba\u8a8d\u3059\u308b\u304b\u3001GitHub\u306e\u901a\u77e5\u3092\u8a2d\u5b9a\u3057\u3066\u304f\u3060\u3055\u3044\u3002\u30ec\u30d3\u30e5\u30a2\u3084\u4ed6\u306e\u30b3\u30df\u30e5\u30cb\u30c6\u30a3\u30e1\u30f3\u30d0\u30fc\u304c\u3001issue\u306b\u5bfe\u3057\u3066\u4f5c\u696d\u3092\u884c\u3046\u305f\u3081\u306b\u3001\u3042\u306a\u305f\u306b\u4f55\u304b\u8cea\u554f\u3092\u3059\u308b\u304b\u3082\u3057\u308c\u307e\u305b\u3093\u3002 ## \u65b0\u3057\u3044\u30b3\u30f3\u30c6\u30f3\u30c4\u306e\u63d0\u6848 \u65b0\u3057\u3044\u30b3\u30f3\u30c6\u30f3\u30c4\u306b\u95a2\u3059\u308b\u30a2\u30a4\u30c7\u30a2\u304c\u3042\u308b\u3082\u306e\u306e\u3001\u3069\u306e\u5834\u6240\u306b\u8ffd\u52a0\u3059\u308c\u3070\u308f\u304b\u3089\u306a\u3044\u3068\u304d\u3067\u3082\u3001issue\u3092\u4f5c\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002\u6b21\u306e\u3044\u305a\u308c\u304b\u3092\u9078\u629e\u3057\u3066\u884c\u3063\u3066\u304f\u3060\u3055\u3044\u3002 - \u30b3\u30f3\u30c6\u30f3\u30c4\u304c\u8ffd\u52a0\u3055\u308c\u308b\u3079\u304d\u3060\u3068\u601d\u3046\u65e2\u5b58\u306e\u30da\u30fc\u30b8\u3092\u9078\u629e\u3057\u3001**\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306eissue\u3092\u4f5c\u6210**\u30dc\u30bf\u30f3\u3092\u30af\u30ea\u30c3\u30af\u3059\u308b\u3002 - [GitHub](https://github.com/kubernetes/website/issues/new/)\u306b\u79fb\u52d5\u3057\u3001\u76f4\u63a5issue\u3092\u4f5c\u308b\u3002 ## \u3088\u3044issue\u3092\u4f5c\u308b\u306b\u306f issue\u3092\u4f5c\u308b\u3068\u304d\u306f\u3001\u4ee5\u4e0b\u306e\u3053\u3068\u3092\u5fc3\u306b\u7559\u3081\u3066\u304f\u3060\u3055\u3044\u3002 - \u660e\u78ba\u306aissue\u306e\u8aac\u660e\u3092\u66f8\u304f\u3002\u4e0d\u8db3\u3057\u3066\u3044\u308b\u70b9\u3001\u53e4\u304f\u306a\u3063\u3066\u3044\u308b\u70b9\u3001\u8aa4\u3063\u3066\u3044\u308b\u70b9\u3001\u6539\u5584\u304c\u5fc5\u8981\u306a\u70b9\u306a\u3069\u3001\u3069\u306e\u70b9\u304c\u305d\u3046\u3067\u3042\u308b\u304b\u660e\u78ba\u306b\u66f8\u304f\u3002 - issue\u304c\u30e6\u30fc\u30b6\u30fc\u306b\u4e0e\u3048\u308b\u5177\u4f53\u7684\u306a\u5f71\u97ff\u3092\u8aac\u660e\u3059\u308b\u3002 - \u5408\u7406\u7684\u306a\u4f5c\u696d\u5358\u4f4d\u306b\u306a\u308b\u3088\u3046\u306b\u3001\u7279\u5b9a\u306eissue\u306e\u30b9\u30b3\u30fc\u30d7\u3092\u5236\u9650\u3059\u308b\u3002\u30b9\u30b3\u30fc\u30d7\u306e\u5927\u304d\u306a\u554f\u984c\u306b\u3064\u3044\u3066\u306f\u3001\u5c0f\u3055\u306a\u8907\u6570\u306eissue\u306b\u5206\u5272\u3059\u308b\u3002\u305f\u3068\u3048\u3070\u3001\"Fix the security docs\"(\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3092\u4fee\u6b63\u3059\u308b)\u3068\u3044\u3046\u306e\u306f\u30b9\u30b3\u30fc\u30d7\u304c\u5927\u304d\u3059\u304e\u307e\u3059\u304c\u3001\"Add details to the 'Restricting network access' topic\"(\u30c8\u30d4\u30c3\u30af\u300c\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a2\u30af\u30bb\u30b9\u306e\u5236\u9650\u300d\u306b\u8a73\u7d30\u60c5\u5831\u3092\u8ffd\u52a0\u3059\u308b)\u3067\u3042\u308c\u3070\u5341\u5206\u306b\u4f5c\u696d\u53ef\u80fd\u306a\u5927\u304d\u3055\u3067\u3059\u3002 - \u3059\u3067\u306b\u3042\u308bissue\u3092\u691c\u7d22\u3057\u3001\u95a2\u9023\u307e\u305f\u306f\u540c\u69d8\u306eissue\u304c\u306a\u3044\u304b\u3069\u3046\u304b\u78ba\u8a8d\u3059\u308b\u3002 - \u65b0\u3057\u3044issue\u304c\u307b\u304b\u306eissue\u3084pull request\u3068\u95a2\u4fc2\u3059\u308b\u5834\u5408\u306f\u3001\u5b8c\u5168\u306aURL\u3092\u53c2\u7167\u3059\u308b\u304b\u3001issue\u3084pull request\u306e\u6570\u5b57\u306e\u524d\u306b`#`\u306e\u6587\u5b57\u3092\u4ed8\u3051\u3066\u53c2\u7167\u3059\u308b\u3002\u4f8b\u3048\u3070\u3001`Introduced by #987654`\u306e\u3088\u3046\u306b\u66f8\u304d\u307e\u3059\u3002 - [\u884c\u52d5\u898f\u7bc4](/ja/community/code-of-conduct/)\u306b\u5f93\u3063\u3066\u3001\u4ef2\u9593\u306e\u30b3\u30f3\u30c8\u30ea\u30d3\u30e5\u30fc\u30bf\u30fc\u306b\u656c\u610f\u3092\u6255\u3044\u307e\u3057\u3087\u3046\u3002\u305f\u3068\u3048\u3070\u3001\"The docs are terrible\"(\u3053\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306f\u6700\u60aa\u3060)\u306e\u3088\u3046\u306a\u30b3\u30e1\u30f3\u30c8\u306f\u3001\u5f79\u306b\u7acb\u3064\u656c\u610f\u306e\u3042\u308b\u30d5\u30a3\u30fc\u30c9\u30d0\u30c3\u30af\u3067\u306f\u3042\u308a\u307e\u305b\u3093\u3002 ", "commid": "website_pr_23891"}], "negative_passages": []} {"query_id": "q-en-website-5e853c722cb5be1f3f49920c218f61ec7d946ba811cae76193f24d9e8f33ad75", "query": "A page just to provide a link another page? My be you are planning more links on this page. If not this page it self can point to target page.\nHi in this there is another link reference to kubectl commands refrence , so far i am understanding is that you want to replace reference Link for kubectl command to be in this ?\nTo fix this, edit so that it redirects to /good-first-issue /language en\n/triage accepted\n/retitle No page content for\n/assign\nhi could you help to review the PR? Thanks\n~reviewers~ approvers for the English localization (who are mainly volunteers) pick up that task on a . I can take a look though.\n/remove-good-first-issue\n/assign\nI the redirect () but it doesn't seem to be working on the deploy preview or locally. Any advice would be appreciated:", "positive_passages": [{"docid": "doc-en-website-412b6408b600d4afc4fefdefe1276c75a37aadf2c3aca487971d27c2f35efea6", "text": "/docs/reference/glossary/maintainer/ /docs/reference/glossary/approver/ 301 /docs/reference/kubectl/kubectl-cmds/ /docs/reference/generated/kubectl/kubectl-commands/ 301! /docs/reference/kubectl/kubectl/kubectl_*.md /docs/reference/generated/kubectl/kubectl-commands#:splat 301 /docs/reference/scheduling/profiles/ /docs/reference/scheduling/config/#profiles 301", "commid": "website_pr_27904"}], "negative_passages": []} {"query_id": "q-en-website-6b73162eaa6e8a5d74c0e5c4b16ce18491508ee547cf7dd90a96da5771dd6e73", "query": "/language zh /help\nThis 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. --- title: \u5347\u7ea7 Windows \u8282\u70b9 min-kubernetes-server-version: 1.17 content_type: task weight: 40 --- {{< feature-state for_k8s_version=\"v1.18\" state=\"beta\" >}} \u672c\u9875\u89e3\u91ca\u5982\u4f55\u5347\u7ea7[\u7528 kubeadm \u521b\u5efa\u7684](/zh/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes) Windows \u8282\u70b9\u3002 ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} * \u719f\u6089[\u66f4\u65b0 kubeadm \u96c6\u7fa4\u4e2d\u7684\u5176\u4f59\u7ec4\u4ef6](/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade)\u3002 \u5728\u5347\u7ea7\u4f60\u7684 Windows \u8282\u70b9\u4e4b\u524d\u4f60\u4f1a\u60f3\u8981\u5347\u7ea7\u63a7\u5236\u9762\u8282\u70b9\u3002 ## \u5347\u7ea7\u5de5\u4f5c\u8282\u70b9 {#upgrading-worker-nodes} ### \u5347\u7ea7 kubeadm {#upgrade-kubeadm} 1. \u5728 Windows \u8282\u70b9\u4e0a\u5347\u7ea7 kubeadm\uff1a ```powershell # \u5c06 {{< param \"fullversion\" >}} \u66ff\u6362\u4e3a\u4f60\u5e0c\u671b\u7684\u7248\u672c curl.exe -Lo C:kkubeadm.exe https://dl.k8s.io/{{< param \"fullversion\" >}}/bin/windows/amd64/kubeadm.exe ``` ### \u817e\u7a7a\u8282\u70b9 {#drain-the-node} 1. \u5728\u4e00\u4e2a\u80fd\u8bbf\u95ee\u5230 Kubernetes API \u7684\u673a\u5668\u4e0a\uff0c\u5c06 Windows \u8282\u70b9\u6807\u8bb0\u4e3a\u4e0d\u53ef\u8c03\u5ea6\u5e76 \u9a71\u9010\u5176\u4e0a\u7684\u6240\u6709\u8d1f\u8f7d\uff0c\u4ee5\u4fbf\u51c6\u5907\u8282\u70b9\u7ef4\u62a4\u64cd\u4f5c\uff1a ```shell # \u5c06 <\u8981\u817e\u7a7a\u7684\u8282\u70b9> \u66ff\u6362\u4e3a\u4f60\u8981\u817e\u7a7a\u7684\u8282\u70b9\u7684\u540d\u79f0 kubectl drain <\u8981\u817e\u7a7a\u7684\u8282\u70b9> -ignore-daemonsets ``` \u4f60\u5e94\u8be5\u4f1a\u770b\u5230\u7c7b\u4f3c\u4e0b\u9762\u7684\u8f93\u51fa\uff1a ``` node/ip-172-31-85-18 cordoned node/ip-172-31-85-18 drained ``` ### \u5347\u7ea7 kubelet \u914d\u7f6e {#upgrade-the-kubelet-configuration} 1. \u5728 Windows \u8282\u70b9\u4e0a\uff0c\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\u6765\u540c\u6b65\u65b0\u7684 kubelet \u914d\u7f6e\uff1a ```powershell kubeadm upgrade node ``` ### \u5347\u7ea7 kubelet {#upgrade-kubelet} 1. \u5728 Windows \u8282\u70b9\u4e0a\u5347\u7ea7\u5e76\u91cd\u542f kubelet\uff1a ```powershell stop-service kubelet curl.exe -Lo C:kkubelet.exe https://dl.k8s.io/{{< param \"fullversion\" >}}/bin/windows/amd64/kubelet.exe restart-service kubelet ``` ### \u5bf9\u8282\u70b9\u6267\u884c uncordon \u64cd\u4f5c {#uncordon-the-node} 1. \u4ece\u4e00\u53f0\u80fd\u591f\u8bbf\u95ee\u5230 Kubernetes API \u7684\u673a\u5668\u4e0a\uff0c\u901a\u8fc7\u5c06\u8282\u70b9\u6807\u8bb0\u4e3a\u53ef\u8c03\u5ea6\uff0c\u4f7f\u4e4b \u91cd\u65b0\u4e0a\u7ebf\uff1a ```shell # \u5c06 <\u8981\u817e\u7a7a\u7684\u8282\u70b9> \u66ff\u6362\u4e3a\u4f60\u7684\u8282\u70b9\u540d\u79f0 kubectl uncordon <\u8981\u817e\u7a7a\u7684\u8282\u70b9> ``` ### \u5347\u7ea7 kube-proxy {#upgrade-kube-proxy} 1. \u5728\u4e00\u53f0\u53ef\u8bbf\u95ee Kubernetes API \u7684\u673a\u5668\u4e0a\u548c\uff0c\u5c06 {{< param \"fullversion\" >}} \u66ff\u6362\u6210\u4f60 \u671f\u671b\u7684\u7248\u672c\u540e\u518d\u6b21\u6267\u884c\u4e0b\u9762\u7684\u547d\u4ee4\uff1a ```shell curl -L https://github.com/kubernetes-sigs/sig-windows-tools/releases/latest/download/kube-proxy.yml | sed 's/VERSION/{{< param \"fullversion\" >}}/g' | kubectl apply -f - ``` ", "commid": "website_pr_24631"}], "negative_passages": []} {"query_id": "q-en-website-4321a1db43bbaf244c2de3212770e68af14b179c6edc9df7569804a6965ed9e3", "query": "/language zh /help\nThis 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. --- title: \u4e3a Windows Pod \u548c\u5bb9\u5668\u914d\u7f6e GMSA content_type: task weight: 20 --- {{< feature-state for_k8s_version=\"v1.18\" state=\"stable\" >}} \u672c\u9875\u5c55\u793a\u5982\u4f55\u4e3a\u5c06\u8fd0\u884c\u5728 Windows \u8282\u70b9\u4e0a\u7684 Pod \u548c\u5bb9\u5668\u914d\u7f6e [\u7ec4\u7ba1\u7406\u7684\u670d\u52a1\u8d26\u53f7\uff08Group Managed Service Accounts\uff0cGMSA\uff09](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)\u3002 \u7ec4\u7ba1\u7406\u7684\u670d\u52a1\u8d26\u53f7\u662f\u6d3b\u52a8\u76ee\u5f55\uff08Active Directory\uff09\u7684\u4e00\u79cd\u7279\u6b8a\u7c7b\u578b\uff0c\u63d0\u4f9b\u81ea\u52a8\u5316\u7684 \u5bc6\u7801\u7ba1\u7406\u3001\u7b80\u5316\u7684\u670d\u52a1\u4e3b\u4f53\u540d\u79f0\uff08Service Principal Name\uff0cSPN\uff09\u7ba1\u7406\u4ee5\u53ca\u8de8\u591a\u4e2a \u670d\u52a1\u5668\u5c06\u7ba1\u7406\u64cd\u4f5c\u59d4\u6d3e\u7ed9\u5176\u4ed6\u7ba1\u7406\u5458\u7b49\u80fd\u529b\u3002 \u5728 Kubernetes \u73af\u5883\u4e2d\uff0cGMSA \u51ed\u636e\u89c4\u7ea6\u914d\u7f6e\u4e3a Kubernetes \u96c6\u7fa4\u8303\u56f4\u7684\u81ea\u5b9a\u4e49\u8d44\u6e90 \uff08Custom Resources\uff09\u5f62\u5f0f\u3002Windows Pod \u4ee5\u53ca\u5404 Pod \u4e2d\u7684\u6bcf\u4e2a\u5bb9\u5668\u53ef\u4ee5\u914d\u7f6e\u4e3a \u4f7f\u7528 GMSA \u6765\u5b8c\u6210\u57fa\u4e8e\u57df\uff08Domain\uff09\u7684\u64cd\u4f5c\uff08\u4f8b\u5982\uff0cKerberos \u8eab\u4efd\u8ba4\u8bc1\uff09\uff0c\u4ee5\u4fbf \u4e0e\u5176\u4ed6 Windows \u670d\u52a1\u76f8\u4ea4\u4e92\u3002\u81ea Kubernetes 1.16 \u7248\u672c\u8d77\uff0cDocker \u8fd0\u884c\u65f6\u4e3a Windows \u8d1f\u8f7d\u652f\u6301 GMSA\u3002 ## {{% heading \"prerequisites\" %}} \u4f60\u9700\u8981\u4e00\u4e2a Kubernetes \u96c6\u7fa4\uff0c\u4ee5\u53ca `kubectl` \u547d\u4ee4\u884c\u5de5\u5177\uff0c\u4e14\u5de5\u5177\u5fc5\u987b\u5df2\u914d\u7f6e \u4e3a\u80fd\u591f\u4e0e\u4f60\u7684\u96c6\u7fa4\u901a\u4fe1\u3002\u96c6\u7fa4\u9884\u671f\u5305\u542b Windows \u5de5\u4f5c\u8282\u70b9\u3002 \u672c\u8282\u8ba8\u8bba\u9700\u8981\u4e3a\u6bcf\u4e2a\u96c6\u7fa4\u6267\u884c\u4e00\u6b21\u7684\u521d\u59cb\u64cd\u4f5c\u3002 ### \u5b89\u88c5 GMSACredentialSpec CRD \u4f60\u9700\u8981\u5728\u96c6\u7fa4\u4e0a\u914d\u7f6e\u4e00\u4e2a\u7528\u4e8e GMSA \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u7684 [CustomResourceDefinition](/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/)(CRD)\uff0c \u4ee5\u4fbf\u5b9a\u4e49\u7c7b\u578b\u4e3a `GMSACredentialSpec` \u7684\u81ea\u5b9a\u4e49\u8d44\u6e90\u3002 \u9996\u5148\u4e0b\u8f7d GMSA CRD [YAML](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/gmsa-crd.yml) \u5e76\u5c06\u5176\u4fdd\u5b58\u4e3a `gmsa-crd.yaml`\u3002\u63a5\u4e0b\u6765\u6267\u884c `kubectl apply -f gmsa-crd.yaml` \u5b89\u88c5 CRD\u3002 ### \u5b89\u88c5 Webhook \u6765\u9a8c\u8bc1 GMSA \u7528\u6237 \u4f60\u9700\u8981\u4e3a Kubernetes \u96c6\u7fa4\u914d\u7f6e\u4e24\u4e2a Webhook\uff0c\u5728 Pod \u6216\u5bb9\u5668\u7ea7\u522b\u586b\u5145\u548c\u68c0\u67e5 GMSA \u51ed\u636e\u89c4\u7ea6\u5f15\u7528\u3002 1. \u4e00\u4e2a\u4fee\u6539\u6a21\u5f0f\uff08Mutating\uff09\u7684 Webhook\uff0c\u5c06\u5bf9 GMSA \u7684\u5f15\u7528\uff08\u5728 Pod \u89c4\u7ea6\u4e2d\u4f53\u73b0\u4e3a\u540d\u5b57\uff09 \u5c55\u5f00\u4e3a\u5b8c\u6574\u51ed\u636e\u89c4\u7ea6\u7684 JSON \u5f62\u5f0f\uff0c\u5e76\u4fdd\u5b58\u56de Pod \u89c4\u7ea6\u4e2d\u3002 1. \u4e00\u4e2a\u9a8c\u8bc1\u6a21\u5f0f\uff08Validating\uff09\u7684 Webhook\uff0c\u786e\u4fdd\u5bf9 GMSA \u7684\u6240\u6709\u5f15\u7528\u90fd\u662f\u5df2\u7ecf\u6388\u6743 \u7ed9 Pod \u7684\u670d\u52a1\u8d26\u53f7\u4f7f\u7528\u7684\u3002 \u5b89\u88c5\u4ee5\u4e0a Webhook \u53ca\u5176\u76f8\u5173\u8054\u7684\u5bf9\u8c61\u9700\u8981\u6267\u884c\u4ee5\u4e0b\u6b65\u9aa4\uff1a 1. \u521b\u5efa\u4e00\u4e2a\u8bc1\u4e66\u5bc6\u94a5\u5bf9\uff08\u7528\u4e8e\u5141\u8bb8 Webhook \u5bb9\u5668\u4e0e\u96c6\u7fa4\u901a\u4fe1\uff09 1. \u5b89\u88c5\u4e00\u4e2a\u5305\u542b\u5982\u4e0a\u8bc1\u4e66\u7684 Secret 1. \u521b\u5efa\u4e00\u4e2a\u5305\u542b\u6838\u5fc3 Webhook \u903b\u8f91\u7684 Deployment 1. \u521b\u5efa\u5f15\u7528\u8be5 Deployment \u7684 Validating Webhook \u548c Mutating Webhook \u914d\u7f6e \u4f60\u53ef\u4ee5\u4f7f\u7528[\u8fd9\u4e2a\u811a\u672c](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/deploy-gmsa-webhook.sh) \u6765\u90e8\u7f72\u548c\u914d\u7f6e\u4e0a\u8ff0 GMSA Webhook \u53ca\u76f8\u5173\u8054\u7684\u5bf9\u8c61\u3002\u4f60\u8fd8\u53ef\u4ee5\u5728\u8fd0\u884c\u811a\u672c\u65f6\u8bbe\u7f6e `--dry-run=server` \u9009\u9879\u4ee5\u4fbf\u5ba1\u67e5\u811a\u672c\u5c06\u4f1a\u5bf9\u96c6\u7fa4\u505a\u51fa\u7684\u53d8\u66f4\u3002 \u811a\u672c\u6240\u4f7f\u7528\u7684[YAML \u6a21\u677f](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/gmsa-webhook.yml.tpl) \u4e5f\u53ef\u7528\u4e8e\u624b\u52a8\u90e8\u7f72 Webhook \u53ca\u76f8\u5173\u8054\u7684\u5bf9\u8c61\uff0c\u4e0d\u8fc7\u9700\u8981\u5bf9\u5176\u4e2d\u7684\u53c2\u6570\u4f5c\u9002\u5f53\u66ff\u6362\u3002 ## \u5728\u6d3b\u52a8\u76ee\u5f55\u4e2d\u914d\u7f6e GMSA \u548c Windows \u8282\u70b9 \u5728\u914d\u7f6e Kubernetes \u4e2d\u7684 Pod \u4ee5\u4f7f\u7528 GMSA \u4e4b\u524d\uff0c\u9700\u8981\u6309 [Windows GMSA \u6587\u6863](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#BKMK_Step1) \u4e2d\u63cf\u8ff0\u7684\u90a3\u6837\u5148\u5728\u6d3b\u52a8\u76ee\u5f55\u4e2d\u51c6\u5907\u597d\u671f\u671b\u7684 GMSA\u3002 Windows \u5de5\u4f5c\u8282\u70b9\uff08\u4f5c\u4e3a Kubernetes \u96c6\u7fa4\u7684\u4e00\u90e8\u5206\uff09\u9700\u8981\u88ab\u914d\u7f6e\u5230\u6d3b\u52a8\u76ee\u5f55\u4e2d\uff0c\u4ee5\u4fbf \u8bbf\u95ee\u4e0e\u671f\u671b\u7684 GSMA \u76f8\u5173\u8054\u7684\u79d8\u5bc6\u51ed\u636e\u6570\u636e\u3002\u8fd9\u4e00\u64cd\u4f5c\u7684\u63cf\u8ff0\u4f4d\u4e8e [Windows GMSA \u6587\u6863](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#to-add-member-hosts-using-the-set-adserviceaccount-cmdlet) \u4e2d\u3002 ## \u521b\u5efa GMSA \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90 \u5f53\uff08\u5982\u524d\u6240\u8ff0\uff09\u5b89\u88c5\u4e86 GMSACredentialSpec CRD \u4e4b\u540e\uff0c\u4f60\u5c31\u53ef\u4ee5\u914d\u7f6e\u5305\u542b GMSA \u51ed\u636e \u89c4\u7ea6\u7684\u81ea\u5b9a\u4e49\u8d44\u6e90\u4e86\u3002GMSA \u51ed\u636e\u89c4\u7ea6\u4e2d\u5e76\u4e0d\u5305\u542b\u79d8\u5bc6\u6216\u654f\u611f\u6570\u636e\u3002 \u5176\u4e2d\u5305\u542b\u7684\u4fe1\u606f\u4e3b\u8981\u7528\u4e8e\u5bb9\u5668\u8fd0\u884c\u65f6\uff0c\u4fbf\u4e8e\u540e\u8005\u5411 Windows \u63cf\u8ff0\u5bb9\u5668\u6240\u671f\u671b\u7684 GMSA\u3002 GMSA \u51ed\u636e\u89c4\u7ea6\u53ef\u4ee5\u4f7f\u7528 [PowerShell \u811a\u672c](https://github.com/kubernetes-sigs/windows-gmsa/tree/master/scripts/GenerateCredentialSpecResource.ps1) \u4ee5 YAML \u683c\u5f0f\u751f\u6210\u3002 \u4e0b\u9762\u662f\u624b\u52a8\u4ee5 JSON \u683c\u5f0f\u751f\u6210 GMSA \u51ed\u636e\u89c4\u7ea6\u5e76\u5bf9\u5176\u8fdb\u884c YAML \u8f6c\u6362\u7684\u6b65\u9aa4\uff1a 1. \u5bfc\u5165 CredentialSpec [\u6a21\u5757](https://github.com/MicrosoftDocs/Virtualization-Documentation/blob/live/windows-server-container-tools/ServiceAccounts/CredentialSpec.psm1): `ipmo CredentialSpec.psm1` 1. \u4f7f\u7528 `New-CredentialSpec` \u6765\u521b\u5efa\u4e00\u4e2a JSON \u683c\u5f0f\u7684\u51ed\u636e\u89c4\u7ea6\u3002 \u8981\u521b\u5efa\u540d\u4e3a `WebApp1` \u7684 GMSA \u51ed\u636e\u89c4\u7ea6\uff0c\u8c03\u7528 `New-CredentialSpec -Name WebApp1 -AccountName WebApp1 -Domain $(Get-ADDomain -Current LocalComputer)`\u3002 1. \u4f7f\u7528 `Get-CredentialSpec` \u6765\u663e\u793a JSON \u6587\u4ef6\u7684\u8def\u5f84\u3002 1. \u5c06\u51ed\u636e\u89c4\u7ea6\u4ece JSON \u683c\u5f0f\u8f6c\u6362\u4e3a YAML \u683c\u5f0f\uff0c\u5e76\u6dfb\u52a0\u5fc5\u8981\u7684\u5934\u90e8\u5b57\u6bb5 `apiVersion`\u3001`kind`\u3001`metadata` \u548c `credspec`\uff0c\u4f7f\u5176\u6210\u4e3a\u4e00\u4e2a\u53ef\u4ee5\u5728 Kubernetes \u4e2d\u914d\u7f6e\u7684 GMSACredentialSpec \u81ea\u5b9a\u4e49\u8d44\u6e90\u3002 \u4e0b\u9762\u7684 YAML \u914d\u7f6e\u63cf\u8ff0\u7684\u662f\u4e00\u4e2a\u540d\u4e3a `gmsa-WebApp1` \u7684 GMSA \u51ed\u636e\u89c4\u7ea6\uff1a ```yaml apiVersion: windows.k8s.io/v1alpha1 kind: GMSACredentialSpec metadata: name: gmsa-WebApp1 # \u8fd9\u662f\u968f\u610f\u8d77\u7684\u4e00\u4e2a\u540d\u5b57\uff0c\u5c06\u7528\u4f5c\u5f15\u7528 credspec: ActiveDirectoryConfig: GroupManagedServiceAccounts: - Name: WebApp1 # GMSA \u8d26\u53f7\u7684\u7528\u6237\u540d Scope: CONTOSO # NETBIOS \u57df\u540d - Name: WebApp1 # GMSA \u8d26\u53f7\u7684\u7528\u6237\u540d Scope: contoso.com # DNS \u57df\u540d CmsPlugins: - ActiveDirectory DomainJoinConfig: DnsName: contoso.com # DNS \u57df\u540d DnsTreeName: contoso.com # DNS \u57df\u540d\u6839 Guid: 244818ae-87ac-4fcd-92ec-e79e5252348a # GUID MachineAccountName: WebApp1 # GMSA \u8d26\u53f7\u7684\u7528\u6237\u540d NetBiosName: CONTOSO # NETBIOS \u57df\u540d Sid: S-1-5-21-2126449477-2524075714-3094792973 # GMSA \u7684 SID ``` \u4e0a\u9762\u7684\u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u53ef\u4ee5\u4fdd\u5b58\u4e3a `gmsa-Webapp1-credspec.yaml`\uff0c\u4e4b\u540e\u4f7f\u7528 `kubectl apply -f gmsa-Webapp1-credspec.yml` \u5e94\u7528\u5230\u96c6\u7fa4\u4e0a\u3002 ## \u914d\u7f6e\u96c6\u7fa4\u89d2\u8272\u4ee5\u542f\u7528\u5bf9\u7279\u5b9a GMSA \u51ed\u636e\u89c4\u7ea6\u7684 RBAC \u4f60\u9700\u8981\u4e3a\u6bcf\u4e2a GMSA \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u5b9a\u4e49\u96c6\u7fa4\u89d2\u8272\u3002 \u8be5\u96c6\u7fa4\u89d2\u8272\u6388\u6743\u67d0\u4e3b\u4f53\uff08\u901a\u5e38\u662f\u4e00\u4e2a\u670d\u52a1\u8d26\u53f7\uff09\u5bf9\u7279\u5b9a\u7684 GMSA \u8d44\u6e90\u6267\u884c `use` \u52a8\u4f5c\u3002 \u4e0b\u9762\u7684\u793a\u4f8b\u663e\u793a\u7684\u662f\u4e00\u4e2a\u96c6\u7fa4\u89d2\u8272\uff0c\u5bf9\u524d\u6587\u521b\u5efa\u7684\u51ed\u636e\u89c4\u7ea6 `gmsa-WebApp1` \u6267\u884c\u9274\u6743\u3002 \u5c06\u6b64\u6587\u4ef6\u4fdd\u5b58\u4e3a `gmsa-webapp1-role.yaml` \u5e76\u6267\u884c `kubectl apply -f gmsa-webapp1-role.yaml`\u3002 ```yaml # \u521b\u5efa\u96c6\u7fa4\u89d2\u8272\u8bfb\u53d6\u51ed\u636e\u89c4\u7ea6 apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: webapp1-role rules: - apiGroups: [\"windows.k8s.io\"] resources: [\"gmsacredentialspecs\"] verbs: [\"use\"] resourceNames: [\"gmsa-WebApp1\"] ``` ## \u5c06\u89d2\u8272\u6307\u6d3e\u7ed9\u8981\u4f7f\u7528\u7279\u5b9a GMSA \u51ed\u636e\u89c4\u7ea6\u7684\u670d\u52a1\u8d26\u53f7 \u4f60\u9700\u8981\u5c06\u67d0\u4e2a\u670d\u52a1\u8d26\u53f7\uff08Pod \u914d\u7f6e\u6240\u5bf9\u5e94\u7684\u90a3\u4e2a\uff09\u7ed1\u5b9a\u5230\u524d\u6587\u521b\u5efa\u7684\u96c6\u7fa4\u89d2\u8272\u4e0a\u3002 \u8fd9\u4e00\u7ed1\u5b9a\u64cd\u4f5c\u5b9e\u9645\u4e0a\u6388\u4e88\u8be5\u670d\u52a1\u8d26\u53f7\u4f7f\u7528\u6240\u6307\u5b9a\u7684 GMSA \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u7684\u8bbf\u95ee\u6743\u9650\u3002 \u4e0b\u9762\u663e\u793a\u7684\u662f\u4e00\u4e2a\u7ed1\u5b9a\u5230\u96c6\u7fa4\u89d2\u8272 `webapp1-role` \u4e0a\u7684 default \u670d\u52a1\u8d26\u53f7\uff0c\u4f7f\u4e4b \u80fd\u591f\u4f7f\u7528\u524d\u9762\u6240\u521b\u5efa\u7684 `gmsa-WebApp1` \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u3002 ```yaml apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: allow-default-svc-account-read-on-gmsa-WebApp1 namespace: default subjects: - kind: ServiceAccount name: default namespace: default roleRef: kind: ClusterRole name: webapp1-role apiGroup: rbac.authorization.k8s.io ``` ## \u5728 Pod \u89c4\u7ea6\u4e2d\u914d\u7f6e GMSA \u51ed\u636e\u89c4\u7ea6\u5f15\u7528 Pod \u89c4\u7ea6\u5b57\u6bb5 `securityContext.windowsOptions.gmsaCredentialSpecName` \u53ef\u7528\u6765 \u8bbe\u7f6e\u5bf9\u6307\u5b9a GMSA \u51ed\u636e\u89c4\u7ea6\u81ea\u5b9a\u4e49\u8d44\u6e90\u7684\u5f15\u7528\u3002 \u8bbe\u7f6e\u6b64\u5f15\u7528\u5c06\u4f1a\u914d\u7f6e Pod \u4e2d\u7684\u6240\u6709\u5bb9\u5668\u4f7f\u7528\u6240\u7ed9\u7684 GMSA\u3002 \u4e0b\u9762\u662f\u4e00\u4e2a Pod \u89c4\u7ea6\u793a\u4f8b\uff0c\u5176\u4e2d\u5305\u542b\u4e86\u5bf9 `gmsa-WebApp1` \u51ed\u636e\u89c4\u7ea6\u7684\u5f15\u7528\uff1a ```yaml apiVersion: apps/v1 kind: Deployment metadata: labels: run: with-creds name: with-creds namespace: default spec: replicas: 1 selector: matchLabels: run: with-creds template: metadata: labels: run: with-creds spec: securityContext: windowsOptions: gmsaCredentialSpecName: gmsa-webapp1 containers: - image: mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019 imagePullPolicy: Always name: iis nodeSelector: kubernetes.io/os: windows ``` Pod \u4e2d\u7684\u5404\u4e2a\u5bb9\u5668\u4e5f\u53ef\u4ee5\u4f7f\u7528\u5bf9\u5e94\u5bb9\u5668\u7684 `securityContext.windowsOptions.gmsaCredentialSpecName` \u5b57\u6bb5\u6765\u8bbe\u7f6e\u671f\u671b\u4f7f\u7528\u7684 GMSA \u51ed\u636e\u89c4\u7ea6\u3002 \u4f8b\u5982\uff1a ```yaml apiVersion: apps/v1 kind: Deployment metadata: labels: run: with-creds name: with-creds namespace: default spec: replicas: 1 selector: matchLabels: run: with-creds template: metadata: labels: run: with-creds spec: containers: - image: mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019 imagePullPolicy: Always name: iis securityContext: windowsOptions: gmsaCredentialSpecName: gmsa-Webapp1 nodeSelector: kubernetes.io/os: windows ``` \u5f53 Pod \u89c4\u7ea6\u4e2d\u586b\u5145\u4e86 GMSA \u76f8\u5173\u5b57\u6bb5\uff08\u5982\u4e0a\u6240\u8ff0\uff09\uff0c\u5728\u96c6\u7fa4\u4e2d\u5e94\u7528 Pod \u89c4\u7ea6\u65f6\u4f1a\u4f9d\u6b21 \u53d1\u751f\u4ee5\u4e0b\u4e8b\u4ef6\uff1a 1. Mutating Webhook \u89e3\u6790\u5bf9 GMSA \u51ed\u636e\u89c4\u7ea6\u8d44\u6e90\u7684\u5f15\u7528\uff0c\u5e76\u5c06\u5176\u5168\u90e8\u5c55\u5f00\uff0c \u5f97\u5230 GMSA \u51ed\u636e\u89c4\u7ea6\u7684\u5b9e\u9645\u5185\u5bb9\u3002 1. Validating Webhook \u786e\u4fdd\u4e0e Pod \u76f8\u5173\u8054\u7684\u670d\u52a1\u8d26\u53f7\u6709\u6743\u5728\u6240\u7ed9\u7684 GMSA \u51ed\u636e\u89c4\u7ea6 \u4e0a\u6267\u884c `use` \u52a8\u4f5c\u3002 1. \u5bb9\u5668\u8fd0\u884c\u65f6\u4e3a\u6bcf\u4e2a Windows \u5bb9\u5668\u914d\u7f6e\u6240\u6307\u5b9a\u7684 GMSA \u51ed\u636e\u89c4\u7ea6\uff0c\u8fd9\u6837\u5bb9\u5668\u5c31\u53ef\u4ee5\u4ee5 \u6d3b\u52a8\u76ee\u5f55\u4e2d\u8be5 GMSA \u6240\u4ee3\u8868\u7684\u8eab\u4efd\u6765\u6267\u884c\u64cd\u4f5c\uff0c\u4f7f\u7528\u8be5\u8eab\u4efd\u6765\u8bbf\u95ee\u57df\u4e2d\u7684\u670d\u52a1\u3002 ## \u6545\u969c\u6392\u67e5 \u5982\u679c\u5728\u4f60\u7684\u73af\u5883\u4e2d\u914d\u7f6e GMSA \u65f6\u9047\u5230\u4e86\u56f0\u96be\uff0c\u4f60\u53ef\u4ee5\u91c7\u53d6\u82e5\u5e72\u6b65\u9aa4\u6765\u6392\u67e5\u53ef\u80fd \u7684\u6545\u969c\u3002 \u9996\u5148\uff0c\u786e\u4fdd\u51ed\u636e\u89c4\u7ea6\u5df2\u7ecf\u88ab\u4f20\u9012\u5230 Pod\u3002\u8981\u5b9e\u73b0\u8fd9\u70b9\uff0c\u4f60\u9700\u8981\u5148\u901a\u8fc7 `exec` \u8fdb\u5165\u5230 \u4f60\u7684 Pod \u4e4b\u4e00\uff0c\u68c0\u67e5 `nltest.exe /parentdomain` \u547d\u4ee4\u7684\u8f93\u51fa\u3002 \u5728\u4e0b\u9762\u7684\u4f8b\u5b50\u4e2d\uff0cPod \u672a\u80fd\u6b63\u786e\u5730\u83b7\u5f97\u51ed\u636e\u89c4\u7ea6\uff1a ```shell kubectl exec -it iis-auth-7776966999-n5nzr powershell.exe Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:> nltest.exe /parentdomain Getting parent domain failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE PS C:> ``` \u5982\u679c Pod \u672a\u80fd\u6b63\u786e\u83b7\u5f97\u51ed\u636e\u89c4\u7ea6\uff0c\u5219\u4e0b\u4e00\u6b65\u5c31\u8981\u68c0\u67e5\u4e0e\u57df\u4e4b\u95f4\u7684\u901a\u4fe1\u3002 \u9996\u5148\uff0c\u4ece Pod \u5185\u90e8\u5feb\u901f\u6267\u884c\u4e00\u4e2a nslookup \u64cd\u4f5c\uff0c\u627e\u5230\u57df\u6839\u3002 \u8fd9\u4e00\u64cd\u4f5c\u4f1a\u544a\u8bc9\u6211\u4eec\u4e09\u4ef6\u4e8b\u60c5\uff1a 1. Pod \u80fd\u5426\u8bbf\u95ee\u57df\u63a7\u5236\u5668\uff08DC\uff09 1. DC \u80fd\u5426\u8bbf\u95ee Pod 1. DNS \u662f\u5426\u6b63\u5e38\u5de5\u4f5c \u5982\u679c DNS \u548c\u901a\u4fe1\u6d4b\u8bd5\u901a\u8fc7\uff0c\u63a5\u4e0b\u6765\u4f60\u9700\u8981\u68c0\u67e5\u662f\u5426 Pod \u5df2\u7ecf\u4e0e\u57df\u4e4b\u95f4\u5efa\u7acb\u4e86 \u5b89\u5168\u901a\u4fe1\u901a\u9053\u3002\u8981\u6267\u884c\u8fd9\u4e00\u68c0\u67e5\uff0c\u4f60\u9700\u8981\u518d\u6b21\u901a\u8fc7 `exec` \u8fdb\u5165\u5230\u4f60\u7684 Pod \u4e2d \u5e76\u6267\u884c `nltest.exe /query` \u547d\u4ee4\u3002 ```shell PS C:> nltest.exe /query I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE ``` \u8fd9\u4e00\u8f93\u51fa\u544a\u8bc9\u6211\u4eec\uff0c\u7531\u4e8e\u67d0\u4e9b\u539f\u56e0\uff0cPod \u65e0\u6cd5\u4f7f\u7528\u51ed\u636e\u89c4\u7ea6\u4e2d\u7684\u8d26\u53f7\u767b\u5f55\u5230\u57df\u3002 \u4f60\u53ef\u4ee5\u901a\u8fc7\u8fd0\u884c `nltest.exe /sc_reset:domain.example` \u547d\u4ee4\u5c1d\u8bd5\u4fee\u590d\u5b89\u5168\u901a\u9053\u3002 ```shell PS C:> nltest /sc_reset:domain.example Flags: 30 HAS_IP HAS_TIMESERV Trusted DC Name dc10.domain.example Trusted DC Connection Status Status = 0 0x0 NERR_Success The command completed successfully PS C:> ``` \u5982\u679c\u4e0a\u8ff0\u547d\u4ee4\u4fee\u590d\u4e86\u9519\u8bef\uff0c\u4f60\u5c31\u53ef\u4ee5\u901a\u8fc7\u5411\u4f60\u7684 Pod \u89c4\u7ea6\u6dfb\u52a0\u751f\u547d\u5468\u671f\u56de\u8c03\u6765\u5c06\u6b64\u64cd\u4f5c \u81ea\u52a8\u5316\u3002\u5982\u679c\u4e0a\u8ff0\u547d\u4ee4\u672a\u80fd\u594f\u6548\uff0c\u4f60\u5c31\u9700\u8981\u518d\u6b21\u68c0\u67e5\u51ed\u636e\u89c4\u7ea6\uff0c\u4ee5\u786e\u4fdd\u5176\u6570\u636e\u65f6\u6b63\u786e\u7684 \u800c\u4e14\u662f\u5b8c\u6574\u7684\u3002 ```yaml image: registry.domain.example/iis-auth:1809v1 lifecycle: postStart: exec: command: [\"powershell.exe\",\"-command\",\"do { Restart-Service -Name netlogon } while ( $($Result = (nltest.exe /query); if ($Result -like '*0x0 NERR_Success*') {return $true} else {return $false}) -eq $false)\"] imagePullPolicy: IfNotPresent ``` \u5982\u679c\u4f60\u5411\u4f60\u7684 Pod \u89c4\u7ea6\u4e2d\u6dfb\u52a0\u5982\u4e0a\u6240\u793a\u7684 `lifecycle` \u8282\uff0c\u5219 Pod \u4f1a\u81ea\u52a8\u6267\u884c\u6240 \u5217\u4e3e\u7684\u547d\u4ee4\u6765\u91cd\u542f `netlogon` \u670d\u52a1\uff0c\u76f4\u5230 `nltest.exe /query` \u547d\u4ee4\u8fd4\u56de\u65f6\u6ca1\u6709\u9519\u8bef\u4fe1\u606f\u3002 ## GMSA \u7684\u5c40\u9650 \u5728\u4f7f\u7528 [Windows \u7248\u672c\u7684 ContainerD \u8fd0\u884c\u65f6](/zh/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#cri-containerd) \u65f6\uff0c\u901a\u8fc7 GMSA \u57df\u8eab\u4efd\u6807\u8bc6\u8bbf\u95ee\u53d7\u9650\u5236\u7684\u7f51\u7edc\u5171\u4eab\u8d44\u6e90\u65f6\u4f1a\u51fa\u9519\u3002 \u5bb9\u5668\u4f1a\u6536\u5230\u8eab\u4efd\u6807\u8bc6\u4e14 `nltest.exe /query` \u8c03\u7528\u4e5f\u80fd\u6b63\u5e38\u5de5\u4f5c\u3002 \u5f53\u9700\u8981\u8bbf\u95ee\u7f51\u7edc\u5171\u4eab\u8d44\u6e90\u65f6\uff0c\u5efa\u8bae\u4f7f\u7528 [Docker EE \u8fd0\u884c\u65f6](/zh/docs/setup/production-environment/windows/intro-windows-in-kubernetes/#docker-ee)\u3002 Windows Server \u56e2\u961f\u6b63\u5728 Windows \u5185\u6838\u4e2d\u89e3\u51b3\u8fd9\u4e00\u95ee\u9898\uff0c\u5e76\u5728\u5c06\u6765\u53d1\u5e03\u89e3\u51b3\u6b64\u95ee\u9898\u7684\u8865\u4e01\u3002 \u4f60\u53ef\u4ee5\u5728 [Microsoft Windows Containers \u95ee\u9898\u8ddf\u8e2a\u5217\u8868](https://github.com/microsoft/Windows-Containers/issues/44) \u4e2d\u67e5\u627e\u8fd9\u7c7b\u66f4\u65b0\u3002 ", "commid": "website_pr_24634"}], "negative_passages": []} {"query_id": "q-en-website-a156808cbb38a820c7cb79522ab318fd7db288080800eb31a33cf787a755b20c", "query": "This is a Bug Report Problem: The following pages under are currently manually maintained. It is expected that each generated page under has at least one link to it from these files, otherwise it becomes orphaned. The following pages are orphaned: Proposed Solution: Add links to these generated pages.\nThanks /sig cluster-lifecycle /triage accepted /kind cleanup /language en /priority backlog\nWe could instead use Docsy's automatic list generation, and add descriptions to each page (eg, to the front matter of ).\nis marked as deprecated in 1.20, so i assume the generation for it will be skipped (the command will be hidden). the command is graduated as . the graduation and missing is covered here: the rest are indeed missing. is there a way to catch this during CI of website PRs? i don't know how Docsy works, but would appreciate ideas around this as manually maintaining the subcommands is not ideal.\nHmm, looking at this a bit more just setting a might not be enough. The current pages are a mix of generated and manually written ones. There are a few different ways to combine these. It sounds like extending the generator could help there - that could be a separate feature request against the generator code, eg to warn if a subcommand isn't documented as expected.\ni think we could do the following: on the main pages that are currently manually maintained for etc, \"include\" the parent generated page () the generated page could have relative hyperlinks to the generated pages of sub-sub-commands (e.g. having links to , and this can reveal the whole tree relation between sub-commands and sub-sub-commands (and deeper). this means that ideally the generated pages should have a title on top too: and a section for the sub-commands. EDIT: and if the kubeadm commands lack sufficient information it should be in the source code of kubeadm. would navigating around /generated pages sound like a good idea? e.g.\nthat sounds like a plan. BTW, if the generator has the smarts to add metadata into generated Markdown (eg: a YAML list of subcommands, in front matter) then we can implement a Hugo layout that automatically processes that metadata into HTML. I can probably help with this approach, if selected. So you have options: more code in the docs generator, or less docs generator code but then more work for the Go templating.\ngiven the subcommand relation is already described by the filenames: can Hugo just process that instead of requiring the metadata to be part of the markdown? i think i'm leaning towards the first option, but that is because i don't know much about Hugo. if the docs team and prefer the second option, we should go for that.\nI'd rather not hard-code in a full path into the layout code, because I think that could be fragile when it doesn't need to be. If we can set some marker eg in the for each page where that applies, I think I could persuade Hugo to work out the rest of the details.\nLet's fix it by following the current practices. We can file a new issue to track the improvement/automation.\nLGTMed the PR, will add notes to thanks", "positive_passages": [{"docid": "doc-en-website-32f98857ace0affa5292646b0169ac5d25825bb52a7637d028694f190cca91e4", "text": "from the community. Please try it out and give us feedback! {{< /caution >}} ## kubeadm alpha certs {#cmd-certs} A collection of operations for operating Kubernetes certificates. {{< tabs name=\"tab-certs\" >}} {{< tab name=\"overview\" include=\"generated/kubeadm_alpha_certs.md\" />}} {{< /tabs >}} ## kubeadm alpha certs renew {#cmd-certs-renew} You can renew all Kubernetes certificates using the `all` subcommand or renew them selectively.", "commid": "website_pr_24557"}], "negative_passages": []} {"query_id": "q-en-website-a156808cbb38a820c7cb79522ab318fd7db288080800eb31a33cf787a755b20c", "query": "This is a Bug Report Problem: The following pages under are currently manually maintained. It is expected that each generated page under has at least one link to it from these files, otherwise it becomes orphaned. The following pages are orphaned: Proposed Solution: Add links to these generated pages.\nThanks /sig cluster-lifecycle /triage accepted /kind cleanup /language en /priority backlog\nWe could instead use Docsy's automatic list generation, and add descriptions to each page (eg, to the front matter of ).\nis marked as deprecated in 1.20, so i assume the generation for it will be skipped (the command will be hidden). the command is graduated as . the graduation and missing is covered here: the rest are indeed missing. is there a way to catch this during CI of website PRs? i don't know how Docsy works, but would appreciate ideas around this as manually maintaining the subcommands is not ideal.\nHmm, looking at this a bit more just setting a might not be enough. The current pages are a mix of generated and manually written ones. There are a few different ways to combine these. It sounds like extending the generator could help there - that could be a separate feature request against the generator code, eg to warn if a subcommand isn't documented as expected.\ni think we could do the following: on the main pages that are currently manually maintained for etc, \"include\" the parent generated page () the generated page could have relative hyperlinks to the generated pages of sub-sub-commands (e.g. having links to , and this can reveal the whole tree relation between sub-commands and sub-sub-commands (and deeper). this means that ideally the generated pages should have a title on top too: and a section for the sub-commands. EDIT: and if the kubeadm commands lack sufficient information it should be in the source code of kubeadm. would navigating around /generated pages sound like a good idea? e.g.\nthat sounds like a plan. BTW, if the generator has the smarts to add metadata into generated Markdown (eg: a YAML list of subcommands, in front matter) then we can implement a Hugo layout that automatically processes that metadata into HTML. I can probably help with this approach, if selected. So you have options: more code in the docs generator, or less docs generator code but then more work for the Go templating.\ngiven the subcommand relation is already described by the filenames: can Hugo just process that instead of requiring the metadata to be part of the markdown? i think i'm leaning towards the first option, but that is because i don't know much about Hugo. if the docs team and prefer the second option, we should go for that.\nI'd rather not hard-code in a full path into the layout code, because I think that could be fragile when it doesn't need to be. If we can set some marker eg in the for each page where that applies, I think I could persuade Hugo to work out the rest of the details.\nLet's fix it by following the current practices. We can file a new issue to track the improvement/automation.\nLGTMed the PR, will add notes to thanks", "positive_passages": [{"docid": "doc-en-website-e80171b7dd4877f030999c2954a1adfe84cb2b592e80747ff657cd418e2bedfb", "text": "{{< tab name=\"certificate-key\" include=\"generated/kubeadm_alpha_certs_certificate-key.md\" />}} {{< /tabs >}} ## kubeadm alpha certs generate-csr {#cmd-certs-generate-csr} This command can be used to generate certificate signing requests (CSRs) which can be submitted to a certificate authority (CA) for signing. {{< tabs name=\"tab-certs-generate-csr\" >}} {{< tab name=\"certificate-generate-csr\" include=\"generated/kubeadm_alpha_certs_generate-csr.md\" />}} {{< /tabs >}} ## kubeadm alpha certs check-expiration {#cmd-certs-check-expiration} This command checks expiration for the certificates in the local PKI managed by kubeadm.", "commid": "website_pr_24557"}], "negative_passages": []} {"query_id": "q-en-website-a156808cbb38a820c7cb79522ab318fd7db288080800eb31a33cf787a755b20c", "query": "This is a Bug Report Problem: The following pages under are currently manually maintained. It is expected that each generated page under has at least one link to it from these files, otherwise it becomes orphaned. The following pages are orphaned: Proposed Solution: Add links to these generated pages.\nThanks /sig cluster-lifecycle /triage accepted /kind cleanup /language en /priority backlog\nWe could instead use Docsy's automatic list generation, and add descriptions to each page (eg, to the front matter of ).\nis marked as deprecated in 1.20, so i assume the generation for it will be skipped (the command will be hidden). the command is graduated as . the graduation and missing is covered here: the rest are indeed missing. is there a way to catch this during CI of website PRs? i don't know how Docsy works, but would appreciate ideas around this as manually maintaining the subcommands is not ideal.\nHmm, looking at this a bit more just setting a might not be enough. The current pages are a mix of generated and manually written ones. There are a few different ways to combine these. It sounds like extending the generator could help there - that could be a separate feature request against the generator code, eg to warn if a subcommand isn't documented as expected.\ni think we could do the following: on the main pages that are currently manually maintained for etc, \"include\" the parent generated page () the generated page could have relative hyperlinks to the generated pages of sub-sub-commands (e.g. having links to , and this can reveal the whole tree relation between sub-commands and sub-sub-commands (and deeper). this means that ideally the generated pages should have a title on top too: and a section for the sub-commands. EDIT: and if the kubeadm commands lack sufficient information it should be in the source code of kubeadm. would navigating around /generated pages sound like a good idea? e.g.\nthat sounds like a plan. BTW, if the generator has the smarts to add metadata into generated Markdown (eg: a YAML list of subcommands, in front matter) then we can implement a Hugo layout that automatically processes that metadata into HTML. I can probably help with this approach, if selected. So you have options: more code in the docs generator, or less docs generator code but then more work for the Go templating.\ngiven the subcommand relation is already described by the filenames: can Hugo just process that instead of requiring the metadata to be part of the markdown? i think i'm leaning towards the first option, but that is because i don't know much about Hugo. if the docs team and prefer the second option, we should go for that.\nI'd rather not hard-code in a full path into the layout code, because I think that could be fragile when it doesn't need to be. If we can set some marker eg in the for each page where that applies, I think I could persuade Hugo to work out the rest of the details.\nLet's fix it by following the current practices. We can file a new issue to track the improvement/automation.\nLGTMed the PR, will add notes to thanks", "positive_passages": [{"docid": "doc-en-website-2ce02b5e125a9f0426e33b42cb3a04fff0c5f588e26bcdb7a7d4c33842816428", "text": "{{< tab name=\"bootstrap-token\" include=\"generated/kubeadm_init_phase_bootstrap-token.md\" />}} {{< /tabs >}} ## kubeadm init phase kubelet-finialize {#cmd-phase-kubelet-finalize-all} Use the following phase to update settings relevant to the kubelet after TLS bootstrap. You can use the `all` subcommand to run all `kubelet-finalize` phases. {{< tabs name=\"tab-kubelet-finalize\" >}} {{< tab name=\"kublet-finalize\" include=\"generated/kubeadm_init_phase_kubelet-finalize.md\" />}} {{< tab name=\"kublet-finalize-all\" include=\"generated/kubeadm_init_phase_kubelet-finalize_all.md\" />}} {{< tab name=\"kublet-finalize-cert-rotation\" include=\"generated/kubeadm_init_phase_kubelet-finalize_experimental-cert-rotation.md\" />}} {{< /tabs >}} ## kubeadm init phase addon {#cmd-phase-addon}", "commid": "website_pr_24557"}], "negative_passages": []} {"query_id": "q-en-website-a156808cbb38a820c7cb79522ab318fd7db288080800eb31a33cf787a755b20c", "query": "This is a Bug Report Problem: The following pages under are currently manually maintained. It is expected that each generated page under has at least one link to it from these files, otherwise it becomes orphaned. The following pages are orphaned: Proposed Solution: Add links to these generated pages.\nThanks /sig cluster-lifecycle /triage accepted /kind cleanup /language en /priority backlog\nWe could instead use Docsy's automatic list generation, and add descriptions to each page (eg, to the front matter of ).\nis marked as deprecated in 1.20, so i assume the generation for it will be skipped (the command will be hidden). the command is graduated as . the graduation and missing is covered here: the rest are indeed missing. is there a way to catch this during CI of website PRs? i don't know how Docsy works, but would appreciate ideas around this as manually maintaining the subcommands is not ideal.\nHmm, looking at this a bit more just setting a might not be enough. The current pages are a mix of generated and manually written ones. There are a few different ways to combine these. It sounds like extending the generator could help there - that could be a separate feature request against the generator code, eg to warn if a subcommand isn't documented as expected.\ni think we could do the following: on the main pages that are currently manually maintained for etc, \"include\" the parent generated page () the generated page could have relative hyperlinks to the generated pages of sub-sub-commands (e.g. having links to , and this can reveal the whole tree relation between sub-commands and sub-sub-commands (and deeper). this means that ideally the generated pages should have a title on top too: and a section for the sub-commands. EDIT: and if the kubeadm commands lack sufficient information it should be in the source code of kubeadm. would navigating around /generated pages sound like a good idea? e.g.\nthat sounds like a plan. BTW, if the generator has the smarts to add metadata into generated Markdown (eg: a YAML list of subcommands, in front matter) then we can implement a Hugo layout that automatically processes that metadata into HTML. I can probably help with this approach, if selected. So you have options: more code in the docs generator, or less docs generator code but then more work for the Go templating.\ngiven the subcommand relation is already described by the filenames: can Hugo just process that instead of requiring the metadata to be part of the markdown? i think i'm leaning towards the first option, but that is because i don't know much about Hugo. if the docs team and prefer the second option, we should go for that.\nI'd rather not hard-code in a full path into the layout code, because I think that could be fragile when it doesn't need to be. If we can set some marker eg in the for each page where that applies, I think I could persuade Hugo to work out the rest of the details.\nLet's fix it by following the current practices. We can file a new issue to track the improvement/automation.\nLGTMed the PR, will add notes to thanks", "positive_passages": [{"docid": "doc-en-website-e73272fc307fa06cd9a5b41ab4d6746d992729921d75341e4d572777f7687c64", "text": "{{< tabs name=\"tab-phase\" >}} {{< tab name=\"phase\" include=\"generated/kubeadm_upgrade_node_phase.md\" />}} {{< tab name=\"preflight\" include=\"generated/kubeadm_upgrade_node_phase_preflight.md\" />}} {{< tab name=\"control-plane\" include=\"generated/kubeadm_upgrade_node_phase_control-plane.md\" />}} {{< tab name=\"kubelet-config\" include=\"generated/kubeadm_upgrade_node_phase_kubelet-config.md\" />}} {{< /tabs >}}", "commid": "website_pr_24557"}], "negative_passages": []} {"query_id": "q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72", "query": "I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help\nThis 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. 3. To see the Deployment rollout status, run `kubectl rollout status deployment.v1.apps/nginx-deployment`. 3. To see the Deployment rollout status, run `kubectl rollout status deployment/nginx-deployment`. The output is similar to: ```", "commid": "website_pr_25491"}], "negative_passages": []} {"query_id": "q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72", "query": "I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help\nThis 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. kubectl rollout status deployment.v1.apps/nginx-deployment kubectl rollout status deployment/nginx-deployment ``` The output is similar to this:", "commid": "website_pr_25491"}], "negative_passages": []} {"query_id": "q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72", "query": "I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help\nThis 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. kubectl rollout status deployment.v1.apps/nginx-deployment kubectl rollout status deployment/nginx-deployment ``` The output is similar to this:", "commid": "website_pr_25491"}], "negative_passages": []} {"query_id": "q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72", "query": "I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help\nThis 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. kubectl rollout status deployment.v1.apps/nginx-deployment kubectl rollout status deployment/nginx-deployment ``` The output is similar to this: ```", "commid": "website_pr_25491"}], "negative_passages": []} {"query_id": "q-en-website-9b1ccf3bbf5a6089dd4a72412dd4a898a7d7e537cd487b7e0356e96c04a6ce72", "query": "I am following the minikube tutorial () and find two different ways to getting the roll-out status of an deployment: vs. I am using locally: What is the difference between these two? Might be a good idea to add a node to step number 3 which explains this.\nI think that an appropriate improvement that's in line with your comment is to change to run instead. That sounds reasonable to do. /language en /kind cleanup /triage accepted /help\nThis 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. kubectl rollout status deployment.v1.apps/nginx-deployment kubectl rollout status deployment/nginx-deployment ``` The output is similar to this: ```", "commid": "website_pr_25491"}], "negative_passages": []} {"query_id": "q-en-website-4fdda25e0c05378b3e540313cc61cdcc39ecb037f571b22f8815a35543d5560e", "query": "translate into Chinese\nThis 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. --- title: \u5bf9\u8c61 id: object date: 2020-10-12 full_link: https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#kubernetes-objects short_description: > Kubernetes \u7cfb\u7edf\u4e2d\u7684\u5b9e\u4f53, \u4ee3\u8868\u4e86\u96c6\u7fa4\u7684\u90e8\u5206\u72b6\u6001\u3002 aka: tags: - fundamental --- Kubernetes \u7cfb\u7edf\u4e2d\u7684\u5b9e\u4f53\u3002Kubernetes API \u7528\u8fd9\u4e9b\u5b9e\u4f53\u8868\u793a\u96c6\u7fa4\u7684\u72b6\u6001\u3002 Kubernetes \u5bf9\u8c61\u901a\u5e38\u662f\u4e00\u4e2a\u201c\u76ee\u6807\u8bb0\u5f55\u201d-\u4e00\u65e6\u4f60\u521b\u5efa\u4e86\u4e00\u4e2a\u5bf9\u8c61\uff0cKubernetes {{< glossary_tooltip text=\"\u63a7\u5236\u5e73\u9762\" term_id=\"control-plane\" >}} \u4e0d\u65ad\u5de5\u4f5c\uff0c\u4ee5\u786e\u4fdd\u5b83\u4ee3\u8868\u7684\u9879\u76ee\u786e\u5b9e\u5b58\u5728\u3002 \u521b\u5efa\u4e00\u4e2a\u5bf9\u8c61\u76f8\u5f53\u4e8e\u544a\u77e5 Kubernetes \u7cfb\u7edf\uff1a\u4f60\u671f\u671b\u8fd9\u90e8\u5206\u96c6\u7fa4\u8d1f\u8f7d\u770b\u8d77\u6765\u50cf\u4ec0\u4e48\uff1b\u8fd9\u4e5f\u5c31\u662f\u4f60\u96c6\u7fa4\u7684\u671f\u671b\u72b6\u6001\u3002 No newline at end of file", "commid": "website_pr_25038"}], "negative_passages": []} {"query_id": "q-en-website-26575fa3dd263ae8230e52acb79ae6cd37dda955d2011325f178019dd3597f70", "query": "This is a Bug Report Garbage collection is a helpful function of kubelet that will clean up unused images and unused containers. Kubelet will perform garbage collection for containers every minute and garbage collection for images every five minutes. Garbage collection is a helpful function of kubelet that will clean up unused [images](/docs/concepts/containers/#container-images) and unused [containers](/docs/concepts/containers/). Kubelet will perform garbage collection for containers every minute and garbage collection for images every five minutes. External garbage collection tools are not recommended as these tools can potentially break the behavior of kubelet by removing containers expected to exist.", "commid": "website_pr_25457"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. }}/staging/https-nginx/). This requires having go and make tools installed. If you don't want to install those, then follow the manual steps later. In short: --> ## Service \u5b89\u5168 ## \u4fdd\u62a4 Service {#securing-the-service} \u5230\u73b0\u5728\u4e3a\u6b62\uff0c\u6211\u4eec\u53ea\u5728\u96c6\u7fa4\u5185\u90e8\u8bbf\u95ee\u4e86 Nginx server\u3002\u5728\u5c06 Service \u66b4\u9732\u5230 Internet \u4e4b\u524d\uff0c\u6211\u4eec\u5e0c\u671b\u786e\u4fdd\u901a\u4fe1\u4fe1\u9053\u662f\u5b89\u5168\u7684\u3002\u5bf9\u4e8e\u8fd9\u53ef\u80fd\u9700\u8981\uff1a \u5230\u73b0\u5728\u4e3a\u6b62\uff0c\u6211\u4eec\u53ea\u5728\u96c6\u7fa4\u5185\u90e8\u8bbf\u95ee\u4e86 Nginx \u670d\u52a1\u5668\u3002\u5728\u5c06 Service \u66b4\u9732\u5230\u56e0\u7279\u7f51\u4e4b\u524d\uff0c\u6211\u4eec\u5e0c\u671b\u786e\u4fdd\u901a\u4fe1\u4fe1\u9053\u662f\u5b89\u5168\u7684\u3002 \u4e3a\u5b9e\u73b0\u8fd9\u4e00\u76ee\u7684\uff0c\u53ef\u80fd\u9700\u8981\uff1a * https \u81ea\u7b7e\u540d\u8bc1\u4e66\uff08\u9664\u975e\u5df2\u7ecf\u6709\u4e86\u4e00\u4e2a\u8bc6\u522b\u8eab\u4efd\u7684\u8bc1\u4e66\uff09 * \u4f7f\u7528\u8bc1\u4e66\u914d\u7f6e\u7684 Nginx server * \u7528\u4e8e HTTPS \u7684\u81ea\u7b7e\u540d\u8bc1\u4e66\uff08\u9664\u975e\u5df2\u7ecf\u6709\u4e86\u4e00\u4e2a\u8bc6\u522b\u8eab\u4efd\u7684\u8bc1\u4e66\uff09 * \u4f7f\u7528\u8bc1\u4e66\u914d\u7f6e\u7684 Nginx \u670d\u52a1\u5668 * \u4f7f\u8bc1\u4e66\u53ef\u4ee5\u8bbf\u95ee Pod \u7684 [Secret](/zh/docs/concepts/configuration/secret/) \u53ef\u4ee5\u4ece [Nginx https \u793a\u4f8b](https://github.com/kubernetes/kubernetes/tree/{{< param \"githubbranch\" >}}/examples/https-nginx/) \u83b7\u53d6\u6240\u6709\u4e0a\u8ff0\u5185\u5bb9\uff0c\u7b80\u660e\u793a\u4f8b\u5982\u4e0b\uff1a \u4f60\u53ef\u4ee5\u4ece [Nginx https \u793a\u4f8b](https://github.com/kubernetes/kubernetes/tree/{{< param \"githubbranch\" >}}/staging/https-nginx/) \u83b7\u53d6\u6240\u6709\u4e0a\u8ff0\u5185\u5bb9\u3002\u4f60\u9700\u8981\u5b89\u88c5 go \u548c make \u5de5\u5177\u3002\u5982\u679c\u4f60\u4e0d\u60f3\u5b89\u88c5\u8fd9\u4e9b\u8f6f\u4ef6\uff0c\u53ef\u4ee5\u6309\u7167 \u540e\u6587\u6240\u8ff0\u7684\u624b\u52a8\u6267\u884c\u6b65\u9aa4\u6267\u884c\u64cd\u4f5c\u3002\u7b80\u8981\u8fc7\u7a0b\u5982\u4e0b\uff1a ```shell make keys KEY=/tmp/nginx.key CERT=/tmp/nginx.crt", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u4ee5\u4e0b\u662f\u60a8\u5728\u8fd0\u884cmake\u65f6\u9047\u5230\u95ee\u9898\u65f6\u8981\u9075\u5faa\u7684\u624b\u52a8\u6b65\u9aa4\uff08\u4f8b\u5982\uff0c\u5728Windows\u4e0a\uff09\uff1a \u4ee5\u4e0b\u662f\u4f60\u5728\u8fd0\u884c make \u65f6\u9047\u5230\u95ee\u9898\u65f6\u8981\u9075\u5faa\u7684\u624b\u52a8\u6b65\u9aa4\uff08\u4f8b\u5982\uff0c\u5728 Windows \u4e0a\uff09\uff1a ```shell # Create a public private key pair", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u4f7f\u7528\u524d\u9762\u547d\u4ee4\u7684\u8f93\u51fa\u6765\u521b\u5efayaml\u6587\u4ef6\uff0c\u5982\u4e0b\u6240\u793a\u3002 base64\u7f16\u7801\u7684\u503c\u5e94\u5168\u90e8\u653e\u5728\u4e00\u884c\u4e0a\u3002 \u4f7f\u7528\u524d\u9762\u547d\u4ee4\u7684\u8f93\u51fa\u6765\u521b\u5efa yaml \u6587\u4ef6\uff0c\u5982\u4e0b\u6240\u793a\u3002 base64 \u7f16\u7801\u7684\u503c\u5e94\u5168\u90e8\u653e\u5728\u4e00\u884c\u4e0a\u3002 ```yaml apiVersion: \"v1\"", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u73b0\u5728\u4f7f\u7528\u6587\u4ef6\u521b\u5efa secrets\uff1a \u73b0\u5728\u4f7f\u7528\u6587\u4ef6\u521b\u5efa Secrets\uff1a ```shell kubectl apply -f nginxsecrets.yaml", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u73b0\u5728\u4fee\u6539 Nginx \u526f\u672c\uff0c\u542f\u52a8\u4e00\u4e2a\u4f7f\u7528\u5728\u79d8\u94a5\u4e2d\u7684\u8bc1\u4e66\u7684 https \u670d\u52a1\u5668\u548c Servcie\uff0c\u90fd\u66b4\u9732\u7aef\u53e3\uff0880 \u548c 443\uff09\uff1a \u73b0\u5728\u4fee\u6539 nginx \u526f\u672c\uff0c\u542f\u52a8\u4e00\u4e2a\u4f7f\u7528\u5728\u79d8\u94a5\u4e2d\u7684\u8bc1\u4e66\u7684 HTTPS \u670d\u52a1\u5668\u548c Servcie\uff0c\u66b4\u9732\u7aef\u53e3\uff0880 \u548c 443\uff09\uff1a {{< codenew file=\"service/networking/nginx-secure-app.yaml\" >}}", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u5173\u4e8e nginx-secure-app \u6e05\u5355\uff0c\u503c\u5f97\u6ce8\u610f\u7684\u51e0\u70b9\u5982\u4e0b\uff1a \u5173\u4e8e nginx-secure-app manifest \u503c\u5f97\u6ce8\u610f\u7684\u70b9\u5982\u4e0b\uff1a - \u5b83\u5728\u76f8\u540c\u7684\u6587\u4ef6\u4e2d\u5305\u542b\u4e86 Deployment \u548c Service \u7684\u89c4\u683c - [Nginx \u670d\u52a1\u5668](https://github.com/kubernetes/kubernetes/tree/{{< param \"githubbranch\" >}}/examples/https-nginx/default.conf) \u5904\u7406 80 \u7aef\u53e3\u4e0a\u7684 http \u6d41\u91cf\uff0c\u4ee5\u53ca 443 \u7aef\u53e3\u4e0a\u7684 https \u6d41\u91cf\uff0cNginx Service \u66b4\u9732\u4e86\u8fd9\u4e24\u4e2a\u7aef\u53e3\u3002 - \u6bcf\u4e2a\u5bb9\u5668\u8bbf\u95ee\u6302\u8f7d\u5728 /etc/nginx/ssl \u5377\u4e0a\u7684\u79d8\u94a5\u3002\u8fd9\u9700\u8981\u5728 Nginx server \u542f\u52a8\u4e4b\u524d\u5b89\u88c5\u597d\u3002 - \u5b83\u5728\u76f8\u540c\u7684\u6587\u4ef6\u4e2d\u5305\u542b\u4e86 Deployment \u548c Service \u7684\u89c4\u7ea6 - [nginx \u670d\u52a1\u5668](https://github.com/kubernetes/kubernetes/tree/{{< param \"githubbranch\" >}}/staging/https-nginx/default.conf) \u5904\u7406 80 \u7aef\u53e3\u4e0a\u7684 HTTP \u6d41\u91cf\uff0c\u4ee5\u53ca 443 \u7aef\u53e3\u4e0a\u7684 HTTPS \u6d41\u91cf\uff0cNginx Service \u66b4\u9732\u4e86\u8fd9\u4e24\u4e2a\u7aef\u53e3\u3002 - \u6bcf\u4e2a\u5bb9\u5668\u8bbf\u95ee\u6302\u8f7d\u5728 /etc/nginx/ssl \u5377\u4e0a\u7684\u79d8\u94a5\u3002\u8fd9\u9700\u8981\u5728 Nginx \u670d\u52a1\u5668\u542f\u52a8\u4e4b\u524d\u5b89\u88c5\u597d\u3002 ```shell kubectl delete deployments,svc my-nginx; kubectl create -f ./nginx-secure-app.yaml", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u8fd9\u65f6\u53ef\u4ee5\u4ece\u4efb\u4f55\u8282\u70b9\u8bbf\u95ee\u5230 Nginx server\u3002 \u8fd9\u65f6\uff0c\u4f60\u53ef\u4ee5\u4ece\u4efb\u4f55\u8282\u70b9\u8bbf\u95ee\u5230 Nginx \u670d\u52a1\u5668\u3002 ```shell kubectl get pods -o yaml | grep -i podip", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u6ce8\u610f\u6700\u540e\u4e00\u6b65\u6211\u4eec\u662f\u5982\u4f55\u63d0\u4f9b `-k` \u53c2\u6570\u6267\u884c curl\u547d\u4ee4\u7684\uff0c\u8fd9\u662f\u56e0\u4e3a\u5728\u8bc1\u4e66\u751f\u6210\u65f6\uff0c \u6211\u4eec\u4e0d\u77e5\u9053\u4efb\u4f55\u5173\u4e8e\u8fd0\u884c Nginx \u7684 Pod \u7684\u4fe1\u606f\uff0c\u6240\u4ee5\u4e0d\u5f97\u4e0d\u5728\u6267\u884c curl \u547d\u4ee4\u65f6\u5ffd\u7565 CName \u4e0d\u5339\u914d\u7684\u60c5\u51b5\u3002 \u901a\u8fc7\u521b\u5efa Service\uff0c\u6211\u4eec\u8fde\u63a5\u4e86\u5728\u8bc1\u4e66\u4e2d\u7684 CName \u4e0e\u5728 Service \u67e5\u8be2\u65f6\u88ab Pod\u4f7f\u7528\u7684\u5b9e\u9645 DNS \u540d\u5b57\u3002 \u6ce8\u610f\u6700\u540e\u4e00\u6b65\u6211\u4eec\u662f\u5982\u4f55\u63d0\u4f9b `-k` \u53c2\u6570\u6267\u884c curl \u547d\u4ee4\u7684\uff0c\u8fd9\u662f\u56e0\u4e3a\u5728\u8bc1\u4e66\u751f\u6210\u65f6\uff0c \u6211\u4eec\u4e0d\u77e5\u9053\u4efb\u4f55\u5173\u4e8e\u8fd0\u884c nginx \u7684 Pod \u7684\u4fe1\u606f\uff0c\u6240\u4ee5\u4e0d\u5f97\u4e0d\u5728\u6267\u884c curl \u547d\u4ee4\u65f6\u5ffd\u7565 CName \u4e0d\u5339\u914d\u7684\u60c5\u51b5\u3002 \u901a\u8fc7\u521b\u5efa Service\uff0c\u6211\u4eec\u8fde\u63a5\u4e86\u5728\u8bc1\u4e66\u4e2d\u7684 CName \u4e0e\u5728 Service \u67e5\u8be2\u65f6\u88ab Pod \u4f7f\u7528\u7684\u5b9e\u9645 DNS \u540d\u5b57\u3002 \u8ba9\u6211\u4eec\u4ece\u4e00\u4e2a Pod \u6765\u6d4b\u8bd5\uff08\u4e3a\u4e86\u7b80\u5316\u4f7f\u7528\u540c\u4e00\u4e2a\u79d8\u94a5\uff0cPod \u4ec5\u9700\u8981\u4f7f\u7528 nginx.crt \u53bb\u8bbf\u95ee Service\uff09\uff1a {{< codenew file=\"service/networking/curlpod.yaml\" >}}", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-d2caa5d0ccdabc7aa59dc064f41cb2c4156b7c988cce1e2414d822d59f48f890", "query": "Nginx https 404\nThis 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. \u8ba9\u6211\u4eec\u91cd\u65b0\u521b\u5efa\u4e00\u4e2a Service\uff0c\u4f7f\u7528\u4e00\u4e2a\u4e91\u8d1f\u8f7d\u5747\u8861\u5668\uff0c\u53ea\u9700\u8981\u5c06 `my-nginx` Service \u7684 `Type` \u7531 `NodePort` \u6539\u6210 `LoadBalancer`\u3002 \u8ba9\u6211\u4eec\u91cd\u65b0\u521b\u5efa\u4e00\u4e2a Service\uff0c\u4f7f\u7528\u4e00\u4e2a\u4e91\u8d1f\u8f7d\u5747\u8861\u5668\uff0c\u53ea\u9700\u8981\u5c06 `my-nginx` Service \u7684 `Type` \u7531 `NodePort` \u6539\u6210 `LoadBalancer`\u3002 ```shell kubectl edit svc my-nginx", "commid": "website_pr_25931"}], "negative_passages": []} {"query_id": "q-en-website-7e7e2dd21679b1368c732867d816c4506e8e407dcadec6fed3c1629e01cb2c9f", "query": "This is a Bug Report {{ end }} {{ partial \"hooks/body-end.html\" . }} ", "commid": "website_pr_26324"}], "negative_passages": []} {"query_id": "q-en-website-a2b8642adc8f2889b5df544f5c34c4dd888e048b89c47eafad6f1454d44ef5b3", "query": "It\u2018s Content have no change from following link:\nThis 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. /* Copyright (C) Federico Zivolo 2018 Distributed under the MIT License (license terms are at http://opensource.org/licenses/MIT). */(function(e,t){'object'==typeof exports&&'undefined'!=typeof module?module.exports=t():'function'==typeof define&&define.amd?define(t):e.Popper=t()})(this,function(){'use strict';function e(e){return e&&'[object Function]'==={}.toString.call(e)}function t(e,t){if(1!==e.nodeType)return[];var o=getComputedStyle(e,null);return t?o[t]:o}function o(e){return'HTML'===e.nodeName?e:e.parentNode||e.host}function n(e){if(!e)return document.body;switch(e.nodeName){case'HTML':case'BODY':return e.ownerDocument.body;case'#document':return e.body;}var i=t(e),r=i.overflow,p=i.overflowX,s=i.overflowY;return /(auto|scroll|overlay)/.test(r+s+p)?e:n(o(e))}function r(e){return 11===e?re:10===e?pe:re||pe}function p(e){if(!e)return document.documentElement;for(var o=r(10)?document.body:null,n=e.offsetParent;n===o&&e.nextElementSibling;)n=(e=e.nextElementSibling).offsetParent;var i=n&&n.nodeName;return i&&'BODY'!==i&&'HTML'!==i?-1!==['TD','TABLE'].indexOf(n.nodeName)&&'static'===t(n,'position')?p(n):n:e?e.ownerDocument.documentElement:document.documentElement}function s(e){var t=e.nodeName;return'BODY'!==t&&('HTML'===t||p(e.firstElementChild)===e)}function d(e){return null===e.parentNode?e:d(e.parentNode)}function a(e,t){if(!e||!e.nodeType||!t||!t.nodeType)return document.documentElement;var o=e.compareDocumentPosition(t)&Node.DOCUMENT_POSITION_FOLLOWING,n=o?e:t,i=o?t:e,r=document.createRange();r.setStart(n,0),r.setEnd(i,0);var l=r.commonAncestorContainer;if(e!==l&&t!==l||n.contains(i))return s(l)?l:p(l);var f=d(e);return f.host?a(f.host,t):a(e,d(t).host)}function l(e){var t=1=o.clientWidth&&n>=o.clientHeight}),l=0a[e]&&!t.escapeWithReference&&(n=J(f[o],a[e]-('right'===e?f.width:f.height))),ae({},o,n)}};return l.forEach(function(e){var t=-1===['left','top'].indexOf(e)?'secondary':'primary';f=le({},f,m[t](e))}),e.offsets.popper=f,e},priority:['left','right','top','bottom'],padding:5,boundariesElement:'scrollParent'},keepTogether:{order:400,enabled:!0,fn:function(e){var t=e.offsets,o=t.popper,n=t.reference,i=e.placement.split('-')[0],r=Z,p=-1!==['top','bottom'].indexOf(i),s=p?'right':'bottom',d=p?'left':'top',a=p?'width':'height';return o[s]r(n[s])&&(e.offsets.popper[d]=r(n[s])),e}},arrow:{order:500,enabled:!0,fn:function(e,o){var n;if(!q(e.instance.modifiers,'arrow','keepTogether'))return e;var i=o.element;if('string'==typeof i){if(i=e.instance.popper.querySelector(i),!i)return e;}else if(!e.instance.popper.contains(i))return console.warn('WARNING: `arrow.element` must be child of its popper element!'),e;var r=e.placement.split('-')[0],p=e.offsets,s=p.popper,d=p.reference,a=-1!==['left','right'].indexOf(r),l=a?'height':'width',f=a?'Top':'Left',m=f.toLowerCase(),h=a?'left':'top',c=a?'bottom':'right',u=S(i)[l];d[c]-us[c]&&(e.offsets.popper[m]+=d[m]+u-s[c]),e.offsets.popper=g(e.offsets.popper);var b=d[m]+d[l]/2-u/2,y=t(e.instance.popper),w=parseFloat(y['margin'+f],10),E=parseFloat(y['border'+f+'Width'],10),v=b-e.offsets.popper[m]-w-E;return v=$(J(s[l]-u,v),0),e.arrowElement=i,e.offsets.arrow=(n={},ae(n,m,Q(v)),ae(n,h,''),n),e},element:'[x-arrow]'},flip:{order:600,enabled:!0,fn:function(e,t){if(W(e.instance.modifiers,'inner'))return e;if(e.flipped&&e.placement===e.originalPlacement)return e;var o=v(e.instance.popper,e.instance.reference,t.padding,t.boundariesElement,e.positionFixed),n=e.placement.split('-')[0],i=T(n),r=e.placement.split('-')[1]||'',p=[];switch(t.behavior){case he.FLIP:p=[n,i];break;case he.CLOCKWISE:p=z(n);break;case he.COUNTERCLOCKWISE:p=z(n,!0);break;default:p=t.behavior;}return p.forEach(function(s,d){if(n!==s||p.length===d+1)return e;n=e.placement.split('-')[0],i=T(n);var a=e.offsets.popper,l=e.offsets.reference,f=Z,m='left'===n&&f(a.right)>f(l.left)||'right'===n&&f(a.left)f(l.top)||'bottom'===n&&f(a.top)f(o.right),g=f(a.top)f(o.bottom),b='left'===n&&h||'right'===n&&c||'top'===n&&g||'bottom'===n&&u,y=-1!==['top','bottom'].indexOf(n),w=!!t.flipVariations&&(y&&'start'===r&&h||y&&'end'===r&&c||!y&&'start'===r&&g||!y&&'end'===r&&u);(m||b||w)&&(e.flipped=!0,(m||b)&&(n=p[d+1]),w&&(r=G(r)),e.placement=n+(r?'-'+r:''),e.offsets.popper=le({},e.offsets.popper,C(e.instance.popper,e.offsets.reference,e.placement)),e=P(e.instance.modifiers,e,'flip'))}),e},behavior:'flip',padding:5,boundariesElement:'viewport'},inner:{order:700,enabled:!1,fn:function(e){var t=e.placement,o=t.split('-')[0],n=e.offsets,i=n.popper,r=n.reference,p=-1!==['left','right'].indexOf(o),s=-1===['top','left'].indexOf(o);return i[p?'left':'top']=r[o]-(s?i[p?'width':'height']:0),e.placement=T(t),e.offsets.popper=g(i),e}},hide:{order:800,enabled:!0,fn:function(e){if(!q(e.instance.modifiers,'hide','preventOverflow'))return e;var t=e.offsets.reference,o=D(e.instance.modifiers,function(e){return'preventOverflow'===e.name}).boundaries;if(t.bottomo.right||t.top>o.bottom||t.right", "commid": "website_pr_26324"}], "negative_passages": []} {"query_id": "q-en-website-7c88f86de42344238abc46551b48f3b8481150cc50799f122aca757899b3184c", "query": "command: wget \"-O\" \"/work-\" : command: wget \"-O\" \"/work-\"\nThis 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. - http://kubernetes.io - http://info.cern.ch volumeMounts: - name: workdir mountPath: \"/work-dir\"", "commid": "website_pr_26331"}], "negative_passages": []} {"query_id": "q-en-website-bff413ca3ae681003cef26f5589e114934acce773adcc4c1158b6b9c5f5ad6a3", "query": "This is a Bug Report SIG Docs\u306f\u3001Kubernetes\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u5185\u306e [special interest groups](https://github.com/kubernetes/community/blob/master/sig-list.md)\u306e1\u3064\u3067\u3042\u308a\u3001 Kubernetes\u5168\u4f53\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306e\u4f5c\u6210\u3001\u66f4\u65b0\u3001\u304a\u3088\u3073\u4fdd\u5b88\u306b\u91cd\u70b9\u3092\u7f6e\u3044\u3066\u3044\u307e\u3059\u3002 SIG\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001[SIG Docs\u306eGithub\u30ea\u30dd\u30b8\u30c8\u30ea](https://github.com/kubernetes/community/blob/master/sig-list.md)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 SIG Docs\u306f\u3001\u3059\u3079\u3066\u306e\u5bc4\u7a3f\u8005\u304b\u3089\u306e\u30b3\u30f3\u30c6\u30f3\u30c4\u3068\u30ec\u30d3\u30e5\u30fc\u3092\u6b53\u8fce\u3057\u307e\u3059\u3002 \u8ab0\u3067\u3082Pull Request(PR)\u3092\u958b\u304f\u3053\u3068\u304c\u3067\u304d\u3001\u30b3\u30f3\u30c6\u30f3\u30c4\u306b\u95a2\u3059\u308bissue\u3092\u63d0\u51fa\u3057\u305f\u308a\u3001\u9032\u884c\u4e2d\u306ePull Request\u306b\u30b3\u30e1\u30f3\u30c8\u3057\u305f\u308a\u3067\u304d\u307e\u3059\u3002 \u3042\u306a\u305f\u306f\u3001[member](/docs/contribute/participate/roles-and-responsibilities/#members)\u3084\u3001 [reviewer](/docs/contribute/participate/roles-and-responsibilities/#reviewers)\u3001 [approver](/docs/contribute/participate/roles-and-responsibilities/#approvers)\u306b\u306a\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002 \u3053\u308c\u3089\u306e\u5f79\u5272\u306b\u306f\u3088\u308a\u591a\u304f\u306e\u30a2\u30af\u30bb\u30b9\u304c\u5fc5\u8981\u3067\u3042\u308a\u3001\u5909\u66f4\u3092\u627f\u8a8d\u304a\u3088\u3073\u30b3\u30df\u30c3\u30c8\u3059\u308b\u305f\u3081\u306e\u7279\u5b9a\u306e\u8cac\u4efb\u304c\u4f34\u3044\u307e\u3059\u3002 Kubernetes\u30b3\u30df\u30e5\u30cb\u30c6\u30a3\u5185\u3067\u30e1\u30f3\u30d0\u30fc\u30b7\u30c3\u30d7\u304c\u3069\u306e\u3088\u3046\u306b\u6a5f\u80fd\u3059\u308b\u304b\u306b\u3064\u3044\u3066\u306e\u8a73\u7d30\u306f\u3001 [community-membership](https://github.com/kubernetes/community/blob/master/community-membership.md) \u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002 \u3053\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306e\u6b8b\u308a\u306e\u90e8\u5206\u3067\u306f\u3001kubernetes\u306e\u4e2d\u3067\u6700\u3082\u5e83\u304f\u516c\u958b\u3055\u308c\u3066\u3044\u308b Kubernetes\u306e\u30a6\u30a7\u30d6\u30b5\u30a4\u30c8\u3068\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u306e\u7ba1\u7406\u3092\u62c5\u5f53\u3057\u3066\u3044\u308bSIG Docs\u306e\u4e2d\u3067\u3001\u3053\u308c\u3089\u306e\u5f79\u5272\u304c\u3069\u306e\u3088\u3046\u306b\u6a5f\u80fd\u3059\u308b\u306e\u304b\u3092\u6982\u8aac\u3057\u307e\u3059\u3002 ## SIG Docs chairperson SIG Docs\u3092\u542b\u3080\u5404SIG\u306f\u3001\u8b70\u9577\u3068\u3057\u3066\u6a5f\u80fd\u3059\u308b1\u4eba\u4ee5\u4e0a\u306eSIG\u30e1\u30f3\u30d0\u30fc\u3092\u9078\u629e\u3057\u307e\u3059\u3002 \u3053\u308c\u3089\u306f\u3001SIGDocs\u3068Kubernetes organization\u306e\u4ed6\u306e\u90e8\u5206\u3068\u306e\u9023\u7d61\u5148\u3067\u3059\u3002 \u305d\u308c\u3089\u306b\u306f\u3001Kubernetes\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u5168\u4f53\u306e\u69cb\u9020\u3068\u3001SIG Docs\u304c\u305d\u306e\u4e2d\u3067\u3069\u306e\u3088\u3046\u306b\u6a5f\u80fd\u3059\u308b\u304b\u306b\u3064\u3044\u3066\u306e\u5e83\u7bc4\u306a\u77e5\u8b58\u304c\u5fc5\u8981\u3067\u3059\u3002 \u73fe\u5728\u306echairperson\u306e\u30ea\u30b9\u30c8\u306b\u3064\u3044\u3066\u306f\u3001 [Leadership](https://github.com/kubernetes/community/tree/master/sig-docs#leadership) \u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ## SIG Docs teams\u3068\u81ea\u52d5\u5316 SIG Docs\u306e\u81ea\u52d5\u5316\u306f\u3001GitHub teams\u3068OWNERS\u30d5\u30a1\u30a4\u30eb\u306e2\u3064\u306e\u7570\u306a\u308b\u30e1\u30ab\u30cb\u30ba\u30e0\u306b\u4f9d\u5b58\u3057\u3066\u3044\u307e\u3059\u3002 ### GitHub teams GitHub\u306b\u306f\u3001\u4e8c\u3064\u306eSIG Docs [teams](https://github.com/orgs/kubernetes/teams?query=sig-docs) \u30ab\u30c6\u30b4\u30ea\u304c\u3042\u308a\u307e\u3059: - `@sig-docs-{language}-owners`\u306f\u627f\u8a8d\u8005\u304b\u3064\u30ea\u30fc\u30c9\u3067\u3059\u3002 - `@sig-docs-{language}-reviewers` \u306f\u30ec\u30d3\u30e5\u30a2\u30fc\u3067\u3059\u3002 \u305d\u308c\u305e\u308c\u3092GitHub\u30b3\u30e1\u30f3\u30c8\u306e`@name`\u3067\u53c2\u7167\u3057\u3066\u3001\u305d\u306e\u30b0\u30eb\u30fc\u30d7\u306e\u5168\u54e1\u3068\u30b3\u30df\u30e5\u30cb\u30b1\u30fc\u30b7\u30e7\u30f3\u3067\u304d\u307e\u3059\u3002 Prow\u30c1\u30fc\u30e0\u3068GitHub teams\u304c\u5b8c\u5168\u306b\u4e00\u81f4\u305b\u305a\u306b\u91cd\u8907\u3059\u308b\u5834\u5408\u304c\u3042\u308a\u307e\u3059\u3002 \u554f\u984c\u306e\u5272\u308a\u5f53\u3066\u3001Pull Request\u3001\u304a\u3088\u3073PR\u627f\u8a8d\u306e\u30b5\u30dd\u30fc\u30c8\u306e\u305f\u3081\u306b\u3001\u81ea\u52d5\u5316\u3067\u306fOWNERS\u30d5\u30a1\u30a4\u30eb\u304b\u3089\u306e\u60c5\u5831\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002 ### OWNERS\u30d5\u30a1\u30a4\u30eb\u3068front-matter Kubernetes\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u306f\u3001GitHub\u306eissue\u3068Pull Request\u306b\u95a2\u9023\u3059\u308b\u81ea\u52d5\u5316\u306e\u305f\u3081\u306bprow\u3068\u547c\u3070\u308c\u308b\u81ea\u52d5\u5316\u30c4\u30fc\u30eb\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002 [Kubernetes Web\u30b5\u30a4\u30c8\u30ea\u30dd\u30b8\u30c8\u30ea](https://github.com/kubernetes/website) \u306f\u30012\u3064\u306e[prow\u30d7\u30e9\u30b0\u30a4\u30f3](https://github.com/kubernetes/test-infra/tree/master/prow/plugins)\u3092\u4f7f\u7528\u3057\u307e\u3059\uff1a - blunderbuss - approve \u3053\u308c\u3089\u306e2\u3064\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u306f`kubernetes.website`\u306eGithub\u30ea\u30dd\u30b8\u30c8\u30ea\u306e\u30c8\u30c3\u30d7\u30ec\u30d9\u30eb\u306b\u3042\u308b [OWNERS](https://github.com/kubernetes/website/blob/master/OWNERS)\u30d5\u30a1\u30a4\u30eb\u3068\u3001 [OWNERS_ALIASES](https://github.com/kubernetes/website/blob/master/OWNERS_ALIASES)\u30d5\u30a1\u30a4\u30eb\u3092\u4f7f\u7528\u3057\u3066\u3001 \u30ea\u30dd\u30b8\u30c8\u30ea\u5185\u3067\u306eprow\u306e\u52d5\u4f5c\u3092\u5236\u5fa1\u3057\u307e\u3059\u3002 OWNERS\u30d5\u30a1\u30a4\u30eb\u306b\u306f\u3001SIG Docs\u306e\u30ec\u30d3\u30e5\u30fc\u62c5\u5f53\u8005\u304a\u3088\u3073\u627f\u8a8d\u8005\u3067\u3042\u308b\u30e6\u30fc\u30b6\u30fc\u306e\u30ea\u30b9\u30c8\u304c\u542b\u307e\u308c\u3066\u3044\u307e\u3059\u3002 OWNERS\u30d5\u30a1\u30a4\u30eb\u306f\u30b5\u30d6\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u306b\u5b58\u5728\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u3001\u305d\u306e\u30b5\u30d6\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u3068\u305d\u306e\u5b50\u5b6b\u306e\u30d5\u30a1\u30a4\u30eb\u306e\u30ec\u30d3\u30e5\u30fc\u62c5\u5f53\u8005\u307e\u305f\u306f\u627f\u8a8d\u8005\u3068\u3057\u3066\u6a5f\u80fd\u3067\u304d\u308b\u30e6\u30fc\u30b6\u30fc\u3092\u4e0a\u66f8\u304d\u3067\u304d\u307e\u3059\u3002 \u4e00\u822c\u7684\u306aOWNERS\u30d5\u30a1\u30a4\u30eb\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001 [OWNERS](https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 \u3055\u3089\u306b\u3001\u500b\u3005\u306eMarkdown\u30d5\u30a1\u30a4\u30eb\u306f\u3001\u500b\u3005\u306eGitHub\u30e6\u30fc\u30b6\u30fc\u540d\u307e\u305f\u306fGitHub\u30b0\u30eb\u30fc\u30d7\u3092\u4e00\u89a7\u8868\u793a\u3059\u308b\u3053\u3068\u306b\u3088\u308a\u3001\u305d\u306efront-matter\u3067\u30ec\u30d3\u30e5\u30fc\u62c5\u5f53\u8005\u3068\u627f\u8a8d\u8005\u3092\u4e00\u89a7\u8868\u793a\u3067\u304d\u307e\u3059\u3002 OWNERS\u30d5\u30a1\u30a4\u30eb\u3068Markdown\u30d5\u30a1\u30a4\u30eb\u306efront-matter\u306e\u7d44\u307f\u5408\u308f\u305b\u306b\u3088\u308a\u3001PR\u306e\u6280\u8853\u7684\u304a\u3088\u3073\u7de8\u96c6\u4e0a\u306e\u30ec\u30d3\u30e5\u30fc\u3092\u8ab0\u306b\u4f9d\u983c\u3059\u308b\u304b\u306b\u3064\u3044\u3066PR\u306e\u6240\u6709\u8005\u304c\u81ea\u52d5\u5316\u30b7\u30b9\u30c6\u30e0\u304b\u3089\u5f97\u308b\u30a2\u30c9\u30d0\u30a4\u30b9\u304c\u6c7a\u307e\u308a\u307e\u3059\u3002 ## \u30de\u30fc\u30b8\u306e\u4ed5\u7d44\u307f Pull Request\u304c\u30b3\u30f3\u30c6\u30f3\u30c4\u306e\u516c\u958b\u306b\u4f7f\u7528\u3055\u308c\u308b\u30d6\u30e9\u30f3\u30c1\u306b\u30de\u30fc\u30b8\u3055\u308c\u308b\u3068\u3001\u305d\u306e\u30b3\u30f3\u30c6\u30f3\u30c4\u306f http://kubernetes.io \u306b\u516c\u958b\u3055\u308c\u307e\u3059\u3002 \u516c\u958b\u3055\u308c\u305f\u30b3\u30f3\u30c6\u30f3\u30c4\u306e\u54c1\u8cea\u3092\u9ad8\u304f\u3059\u308b\u305f\u3081\u306b\u3001Pull Request\u306e\u30de\u30fc\u30b8\u306fSIG Docs\u306e\u627f\u8a8d\u8005\u306b\u9650\u5b9a\u3057\u3066\u3044\u307e\u3059\u3002\u4ed5\u7d44\u307f\u306f\u6b21\u306e\u3068\u304a\u308a\u3067\u3059\u3002 - Pull Request\u306b`lgtm`\u30e9\u30d9\u30eb\u3068`approve`\u30e9\u30d9\u30eb\u306e\u4e21\u65b9\u304c\u3042\u308a\u3001`hold`\u30e9\u30d9\u30eb\u304c\u306a\u304f\u3001\u3059\u3079\u3066\u306e\u30c6\u30b9\u30c8\u306b\u5408\u683c\u3059\u308b\u3068\u3001Pull Request\u306f\u81ea\u52d5\u7684\u306b\u30de\u30fc\u30b8\u3055\u308c\u307e\u3059\u3002 - Kubernetes organization\u306e\u30e1\u30f3\u30d0\u30fc\u3068SIG Docs\u306e\u627f\u8a8d\u8005\u306f\u30b3\u30e1\u30f3\u30c8\u3092\u8ffd\u52a0\u3057\u3066\u3001\u7279\u5b9a\u306ePull Request\u304c\u81ea\u52d5\u7684\u306b\u30de\u30fc\u30b8\u3055\u308c\u306a\u3044\u3088\u3046\u306b\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059(`/hold`\u30b3\u30e1\u30f3\u30c8\u3092\u8ffd\u52a0\u3059\u308b\u304b\u3001`/lgtm`\u30b3\u30e1\u30f3\u30c8\u3092\u4fdd\u7559\u3057\u307e\u3059)\u3002 - Kubernetes\u30e1\u30f3\u30d0\u30fc\u306f\u8ab0\u3067\u3082\u3001`/lgtm`\u30b3\u30e1\u30f3\u30c8\u3092\u8ffd\u52a0\u3059\u308b\u3053\u3068\u3067`lgtm`\u30e9\u30d9\u30eb\u3092\u8ffd\u52a0\u3067\u304d\u307e\u3059\u3002 - `/approve`\u30b3\u30e1\u30f3\u30c8\u3092\u8ffd\u52a0\u3057\u3066Pull Request\u3092\u30de\u30fc\u30b8\u3067\u304d\u308b\u306e\u306f\u3001SIG Docs\u306e\u627f\u8a8d\u8005\u3060\u3051\u3067\u3059\u3002\u4e00\u90e8\u306e\u627f\u8a8d\u8005\u306f\u3001[PR Wrangler](/docs/contribute/participate/pr-wranglers/)\u3084[SIG Docs\u306echairperson](#sig-docs-chairperson)\u306a\u3069\u3001\u8ffd\u52a0\u306e\u7279\u5b9a\u306e\u5f79\u5272\u3082\u5b9f\u884c\u3057\u307e\u3059\u3002 ## {{% heading \"whatsnext\" %}} Kubernetes\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3078\u306e\u8ca2\u732e\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001\u4ee5\u4e0b\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\uff1a - [Contributing new content](/docs/contribute/new-content/overview/) - [Reviewing content](/docs/contribute/review/reviewing-prs) - [\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u30b9\u30bf\u30a4\u30eb\u306e\u6982\u8981](/ja/docs/contribute/style/) ", "commid": "website_pr_26604"}], "negative_passages": []} {"query_id": "q-en-website-5a512241392474648e1b72fdb21fe7506594ed4b93f6f47589a6604a498224ca", "query": "This is a Bug Report Problem: The dockershim alias () now directs to the Chinese localized version () because the same alias exists in multiple files. Proposed Solution: Removal of the alias in the Chinese version of the blog post or updated to be A policy or linter might be worth putting in place for aliases as well to prevent future issues. Page to Update:\n/triage accepted /kind bug /language zh\nA similar problem occurred some time ago with aliases in security. I just checked a few other files. Aliases field is set: content/zh/docs/reference/issues- content/zh/docs/reference/issues- Aliases field not set (set in version): content/zh/docs/reference/access-authn- Should add a note to the localization or documentation about how to update the field.\n/assign", "positive_passages": [{"docid": "doc-en-website-dfbd174530c5d6e68fc5df9b5429e3875fed61de8fde171d4f2fb35ce9958064", "text": "title: \"\u5f03\u7528 Dockershim \u7684\u5e38\u89c1\u95ee\u9898\" date: 2020-12-02 slug: dockershim-faq aliases: [ '/dockershim' ] --- ## \u5bb9\u5668", "commid": "website_pr_27217"}], "negative_passages": []} {"query_id": "q-en-website-c85df5a0fe24baaae76f1bb451f33522fddbd55e607b7b12f3aac07bd641dd4e", "query": "! Chinese page link can not open\nThis 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. \u4f7f\u7528\u5e26\u6709\u8f83\u5f3a\u9694\u79bb\u80fd\u529b\u7684\u5bb9\u5668\u8fd0\u884c\u65f6 | \u9009\u62e9\u63d0\u4f9b\u8f83\u5f3a\u9694\u79bb\u80fd\u529b\u7684[\u5bb9\u5668\u8fd0\u884c\u65f6\u7c7b](/zh/docs/concepts/containers/runtime-class/)\u3002 \u5b66\u4e60\u4e86\u89e3\u76f8\u5173\u7684 Kubernetes \u5b89\u5168\u4e3b\u9898\uff1a", "commid": "website_pr_27217"}], "negative_passages": []} {"query_id": "q-en-website-c85df5a0fe24baaae76f1bb451f33522fddbd55e607b7b12f3aac07bd641dd4e", "query": "! Chinese page link can not open\nThis 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. * [\u8fd0\u884c\u65f6\u7c7b](/zh/docs/concepts/containers/runtime-class) ", "commid": "website_pr_27217"}], "negative_passages": []} {"query_id": "q-en-website-98a66d2d724672a8819406347a82a8cd743af3be7c91974086a6a2cbc0026c80", "query": "This is a Bug Report This page explains how to upgrade a Kubernetes cluster created with kubeadm from version {{< skew latestVersionAddMinor -1 >}}.x to version {{< skew latestVersion >}}.x, and from version {{< skew latestVersion >}}.x to {{< skew latestVersion >}}.y (where `y > x`). Skipping MINOR versions {{< skew currentVersionAddMinor -1 >}}.x to version {{< skew currentVersion >}}.x, and from version {{< skew currentVersion >}}.x to {{< skew currentVersion >}}.y (where `y > x`). Skipping MINOR versions when upgrading is unsupported. To see information about upgrading clusters created using older versions of kubeadm, please refer to following pages instead: - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -2 >}} to {{< skew latestVersionAddMinor -1 >}}](https://v{{< skew latestVersionAddMinor -1 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -3 >}} to {{< skew latestVersionAddMinor -2 >}}](https://v{{< skew latestVersionAddMinor -2 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -4 >}} to {{< skew latestVersionAddMinor -3 >}}](https://v{{< skew latestVersionAddMinor -3 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew latestVersionAddMinor -5 >}} to {{< skew latestVersionAddMinor -4 >}}](https://v{{< skew latestVersionAddMinor -4 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -2 >}} to {{< skew currentVersionAddMinor -1 >}}](https://v{{< skew currentVersionAddMinor -1 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -3 >}} to {{< skew currentVersionAddMinor -2 >}}](https://v{{< skew currentVersionAddMinor -2 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -4 >}} to {{< skew currentVersionAddMinor -3 >}}](https://v{{< skew currentVersionAddMinor -3 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) - [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -5 >}} to {{< skew currentVersionAddMinor -4 >}}](https://v{{< skew currentVersionAddMinor -4 \"-\" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) The upgrade workflow at high level is the following:", "commid": "website_pr_29746"}], "negative_passages": []} {"query_id": "q-en-website-98a66d2d724672a8819406347a82a8cd743af3be7c91974086a6a2cbc0026c80", "query": "This is a Bug Report {{- if eq $version \"currentVersion\" -}} {{- $currentVersion -}} {{- end -}} {{- if eq $version \"currentVersionAddMinor\" -}} {{- $seperator := .Get 2 -}} {{- if eq $seperator \"\" -}} {{- $seperator = \".\" -}} {{- end -}} {{- $currentVersionAddMinor := int (.Get 1) -}} {{- $currentVersionAddMinor = add $currentMinorVersion $currentVersionAddMinor -}} {{- $currentVersionAddMinor = printf \"%s%s%d\" (index $versionArray 0) $seperator $currentVersionAddMinor -}} {{- $currentVersionAddMinor -}} {{- end -}} No newline at end of file", "commid": "website_pr_29746"}], "negative_passages": []} {"query_id": "q-en-website-b307b0abb8b5d4cf1bf1a69869d3b98b1a3e16953279e3b03d8df71a2919c666", "query": "This is a Bug Report ", "commid": "website_pr_27554"}], "negative_passages": []} {"query_id": "q-en-website-6ff6e751e652c98c4d3a37f23271dd8f8c25fd972041a1c701d83de3f5b4e54b", "query": "This is a Bug Report {{% thirdparty-content %}} \u30a2\u30c9\u30aa\u30f3\u306fKubernetes\u306e\u6a5f\u80fd\u3092\u62e1\u5f35\u3059\u308b\u3082\u306e\u3067\u3059\u3002 \u3053\u306e\u30da\u30fc\u30b8\u3067\u306f\u3001\u5229\u7528\u53ef\u80fd\u306a\u30a2\u30c9\u30aa\u30f3\u306e\u4e00\u90e8\u306e\u4e00\u89a7\u3068\u3001\u305d\u308c\u305e\u308c\u306e\u30a2\u30c9\u30aa\u30f3\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u65b9\u6cd5\u3078\u306e\u30ea\u30f3\u30af\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 ## \u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc * [ACI](https://www.github.com/noironetworks/aci-containers)\u306f\u3001\u7d71\u5408\u3055\u308c\u305f\u30b3\u30f3\u30c6\u30ca\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u3092Cisco ACI\u3092\u4f7f\u7528\u3057\u3066\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [Antrea](https://antrea.io/)\u306f\u3001L3\u307e\u305f\u306fL4\u3067\u52d5\u4f5c\u3057\u3066\u3001Open vSwitch\u3092\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30c7\u30fc\u30bf\u30d7\u30ec\u30fc\u30f3\u3068\u3057\u3066\u6d3b\u7528\u3059\u308b\u3001Kubernetes\u5411\u3051\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30b5\u30fc\u30d3\u30b9\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [Calico](https://docs.projectcalico.org/latest/introduction/)\u306f\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30ea\u30b7\u30fc\u306e\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3067\u3059\u3002Calico\u306f\u3001BGP\u3092\u4f7f\u7528\u307e\u305f\u306f\u672a\u4f7f\u7528\u306e\u975e\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u304a\u3088\u3073\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u542b\u3080\u3001\u30d5\u30ec\u30ad\u30b7\u30d6\u30eb\u306a\u3055\u307e\u3056\u307e\u306a\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30aa\u30d7\u30b7\u30e7\u30f3\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u307e\u3059\u3002Calico\u306f\u30db\u30b9\u30c8\u3001Pod\u3001\u305d\u3057\u3066(Istio\u3068Envoy\u3092\u4f7f\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u306b\u306f)\u30b5\u30fc\u30d3\u30b9\u30e1\u30c3\u30b7\u30e5\u4e0a\u306e\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306b\u5bfe\u3057\u3066\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u5f37\u5236\u3059\u308b\u305f\u3081\u306b\u3001\u540c\u4e00\u306e\u30a8\u30f3\u30b8\u30f3\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002 * [Canal](https://github.com/tigera/canal/tree/master/k8s-install)\u306fFlannel\u3068Calico\u3092\u3042\u308f\u305b\u305f\u3082\u306e\u3067\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [Cilium](https://github.com/cilium/cilium)\u306f\u3001L3\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u3001HTTP/API/L7\u306e\u30dd\u30ea\u30b7\u30fc\u3092\u900f\u904e\u7684\u306b\u5f37\u5236\u3067\u304d\u307e\u3059\u3002\u30eb\u30fc\u30c6\u30a3\u30f3\u30b0\u3068overlay/encapsulation\u30e2\u30fc\u30c9\u306e\u4e21\u65b9\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u304a\u308a\u3001\u4ed6\u306eCNI\u30d7\u30e9\u30b0\u30a4\u30f3\u4e0a\u3067\u6a5f\u80fd\u3067\u304d\u307e\u3059\u3002 * [CNI-Genie](https://github.com/Huawei-PaaS/CNI-Genie)\u306f\u3001Kubernetes\u3092Calico\u3001Canal\u3001Flannel\u3001Romana\u3001Weave\u306a\u3069\u9078\u629e\u3057\u305fCNI\u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u30b7\u30fc\u30e0\u30ec\u30b9\u306b\u63a5\u7d9a\u3067\u304d\u308b\u3088\u3046\u306b\u3059\u308b\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u3059\u3002 * [Contiv](https://contiv.github.io)\u306f\u3001\u3055\u307e\u3056\u307e\u306a\u30e6\u30fc\u30b9\u30b1\u30fc\u30b9\u3068\u8c4a\u5bcc\u306a\u30dd\u30ea\u30b7\u30fc\u30d5\u30ec\u30fc\u30e0\u30ef\u30fc\u30af\u5411\u3051\u306b\u8a2d\u5b9a\u53ef\u80fd\u306a\u30cd\u30c3\u30c8\u30ef\u30fc\u30af(BGP\u3092\u4f7f\u7528\u3057\u305f\u30cd\u30a4\u30c6\u30a3\u30d6\u306eL3\u3001vxlan\u3092\u4f7f\u7528\u3057\u305f\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u3001\u53e4\u5178\u7684\u306aL2\u3001Cisco-SDN/ACI)\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002Contiv\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u306f\u5b8c\u5168\u306b[\u30aa\u30fc\u30d7\u30f3\u30bd\u30fc\u30b9](https://github.com/contiv)\u3067\u3059\u3002[\u30a4\u30f3\u30b9\u30c8\u30fc\u30e9](https://github.com/contiv/install)\u306fkubeadm\u3068kubeadm\u4ee5\u5916\u306e\u4e21\u65b9\u3092\u30d9\u30fc\u30b9\u3068\u3057\u305f\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u30aa\u30d7\u30b7\u30e7\u30f3\u304c\u3042\u308a\u307e\u3059\u3002 * [Contrail](https://www.juniper.net/us/en/products-services/sdn/contrail/contrail-networking/)\u306f\u3001[Tungsten Fabric](https://tungsten.io)\u3092\u30d9\u30fc\u30b9\u306b\u3057\u3066\u3044\u308b\u3001\u30aa\u30fc\u30d7\u30f3\u30bd\u30fc\u30b9\u3067\u30de\u30eb\u30c1\u30af\u30e9\u30a6\u30c9\u306b\u5bfe\u5fdc\u3057\u305f\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u4eee\u60f3\u5316\u304a\u3088\u3073\u30dd\u30ea\u30b7\u30fc\u7ba1\u7406\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3067\u3059\u3002Contrail\u304a\u3088\u3073Tungsten Fabric\u306f\u3001Kubernetes\u3001OpenShift\u3001OpenStack\u3001Mesos\u306a\u3069\u306e\u30aa\u30fc\u30b1\u30b9\u30c8\u30ec\u30fc\u30b7\u30e7\u30f3\u30b7\u30b9\u30c6\u30e0\u3068\u7d71\u5408\u3055\u308c\u3066\u304a\u308a\u3001\u4eee\u60f3\u30de\u30b7\u30f3\u3001\u30b3\u30f3\u30c6\u30ca/Pod\u3001\u30d9\u30a2\u30e1\u30bf\u30eb\u306e\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306b\u9694\u96e2\u30e2\u30fc\u30c9\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [Flannel](https://github.com/coreos/flannel/blob/master/Documentation/kubernetes.md)\u306f\u3001Kubernetes\u3067\u4f7f\u7528\u3067\u304d\u308b\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u3067\u3059\u3002 * [Knitter](https://github.com/ZTE/Knitter/)\u306f\u30011\u3064\u306eKubernetes Pod\u3067\u8907\u6570\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30a4\u30b9\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u305f\u3081\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u3059\u3002 * [Multus](https://github.com/Intel-Corp/multus-cni)\u306f\u3001\u3059\u3079\u3066\u306eCNI\u30d7\u30e9\u30b0\u30a4\u30f3(\u305f\u3068\u3048\u3070\u3001Calico\u3001Cilium\u3001Contiv\u3001Flannel)\u306b\u52a0\u3048\u3066\u3001SRIOV\u3001DPDK\u3001OVS-DPDK\u3001VPP\u3092\u30d9\u30fc\u30b9\u3068\u3059\u308bKubernetes\u4e0a\u306e\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3092\u30b5\u30dd\u30fc\u30c8\u3059\u308b\u3001\u8907\u6570\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30b5\u30dd\u30fc\u30c8\u306e\u305f\u3081\u306e\u30de\u30eb\u30c1\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u3059\u3002 * [OVN-Kubernetes](https://github.com/ovn-org/ovn-kubernetes/)\u306f\u3001Open vSwitch(OVS)\u30d7\u30ed\u30b8\u30a7\u30af\u30c8\u304b\u3089\u751f\u307e\u308c\u305f\u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u5b9f\u88c5\u3067\u3042\u308b[OVN(Open Virtual Network)](https://github.com/ovn-org/ovn/)\u3092\u30d9\u30fc\u30b9\u3068\u3059\u308b\u3001Kubernetes\u306e\u305f\u3081\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d7\u30ed\u30d0\u30a4\u30c0\u3067\u3059\u3002OVN-Kubernetes\u306f\u3001OVS\u30d9\u30fc\u30b9\u306e\u30ed\u30fc\u30c9\u30d0\u30e9\u30f3\u30b5\u30fc\u304a\u3088\u3073\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u306e\u5b9f\u88c5\u3092\u542b\u3080\u3001Kubernetes\u5411\u3051\u306e\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30d9\u30fc\u30b9\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u5b9f\u88c5\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [OVN4NFV-K8S-Plugin](https://github.com/opnfv/ovn4nfv-k8s-plugin)\u306f\u3001\u30af\u30e9\u30a6\u30c9\u30cd\u30a4\u30c6\u30a3\u30d6\u30d9\u30fc\u30b9\u306eService function chaining(SFC)\u3001Multiple OVN\u30aa\u30fc\u30d0\u30fc\u30ec\u30a4\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3001\u52d5\u7684\u306a\u30b5\u30d6\u30cd\u30c3\u30c8\u306e\u4f5c\u6210\u3001\u52d5\u7684\u306a\u4eee\u60f3\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u306e\u4f5c\u6210\u3001VLAN\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3001Direct\u30d7\u30ed\u30d0\u30a4\u30c0\u30fc\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u63d0\u4f9b\u3057\u3001\u4ed6\u306eMulti-network\u30d7\u30e9\u30b0\u30a4\u30f3\u3068\u4ed8\u3051\u66ff\u3048\u53ef\u80fd\u306aOVN\u30d9\u30fc\u30b9\u306eCNI\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u30d7\u30e9\u30b0\u30a4\u30f3\u3067\u3059\u3002 * [NSX-T](https://docs.vmware.com/en/VMware-NSX-T/2.0/nsxt_20_ncp_kubernetes.pdf) Container Plug-in(NCP)\u306f\u3001VMware NSX-T\u3068Kubernetes\u306a\u3069\u306e\u30b3\u30f3\u30c6\u30ca\u30aa\u30fc\u30b1\u30b9\u30c8\u30ec\u30fc\u30bf\u30fc\u9593\u306e\u30a4\u30f3\u30c6\u30b0\u30ec\u30fc\u30b7\u30e7\u30f3\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002\u307e\u305f\u3001NSX-T\u3068\u3001Pivotal Container Service(PKS)\u3068OpenShift\u306a\u3069\u306e\u30b3\u30f3\u30c6\u30ca\u30d9\u30fc\u30b9\u306eCaaS/PaaS\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3068\u306e\u30a4\u30f3\u30c6\u30b0\u30ec\u30fc\u30b7\u30e7\u30f3\u3082\u63d0\u4f9b\u3057\u307e\u3059\u3002 * [Nuage](https://github.com/nuagenetworks/nuage-kubernetes/blob/v5.1.1-1/docs/kubernetes-1-installation.rst)\u306f\u3001Kubernetes Pod\u3068\u975eKubernetes\u74b0\u5883\u9593\u3067\u53ef\u8996\u5316\u3068\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30e2\u30cb\u30bf\u30ea\u30f3\u30b0\u3092\u4f7f\u7528\u3057\u3066\u30dd\u30ea\u30b7\u30fc\u30d9\u30fc\u30b9\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3092\u63d0\u4f9b\u3059\u308bSDN\u30d7\u30e9\u30c3\u30c8\u30d5\u30a9\u30fc\u30e0\u3067\u3059\u3002 * [Romana](https://romana.io)\u306f\u3001[NetworkPolicy API](/docs/concepts/services-networking/network-policies/)\u3082\u30b5\u30dd\u30fc\u30c8\u3059\u308bPod\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u5411\u3051\u306eL3\u306e\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30bd\u30ea\u30e5\u30fc\u30b7\u30e7\u30f3\u3067\u3059\u3002Kubeadm\u30a2\u30c9\u30aa\u30f3\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u306e\u8a73\u7d30\u306f[\u3053\u3061\u3089](https://github.com/romana/romana/tree/master/containerize)\u3067\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 * [Weave Net](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/)\u306f\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30d1\u30fc\u30c6\u30a3\u30b7\u30e7\u30f3\u306e\u4e21\u9762\u3067\u6a5f\u80fd\u3057\u3001\u5916\u90e8\u30c7\u30fc\u30bf\u30d9\u30fc\u30b9\u3092\u5fc5\u8981\u3068\u305b\u305a\u306b\u3001\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u3068\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30dd\u30ea\u30b7\u30fc\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002 ## \u30b5\u30fc\u30d3\u30b9\u30c7\u30a3\u30b9\u30ab\u30d0\u30ea * [CoreDNS](https://coredns.io)\u306f\u3001\u30d5\u30ec\u30ad\u30b7\u30d6\u30eb\u3067\u62e1\u5f35\u53ef\u80fd\u306aDNS\u30b5\u30fc\u30d0\u30fc\u3067\u3059\u3002Pod\u5411\u3051\u306e\u30af\u30e9\u30b9\u30bf\u30fc\u5185DNS\u3068\u3057\u3066[\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb](https://github.com/coredns/deployment/tree/master/kubernetes)\u3067\u304d\u307e\u3059\u3002 ## \u53ef\u8996\u5316\u3068\u5236\u5fa1 * [Dashboard](https://github.com/kubernetes/dashboard#kubernetes-dashboard)\u306fKubernetes\u5411\u3051\u306e\u30c0\u30c3\u30b7\u30e5\u30dc\u30fc\u30c9\u3092\u63d0\u4f9b\u3059\u308b\u30a6\u30a7\u30d6\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30a4\u30b9\u3067\u3059\u3002 * [Weave Scope](https://www.weave.works/documentation/scope-latest-installing/#k8s)\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u3001Pod\u3001Service\u306a\u3069\u3092\u30b0\u30e9\u30d5\u30a3\u30ab\u30eb\u306b\u53ef\u8996\u5316\u3059\u308b\u30c4\u30fc\u30eb\u3067\u3059\u3002[Weave Cloud account](https://cloud.weave.works/)\u3068\u7d44\u307f\u5408\u308f\u305b\u3066\u4f7f\u3046\u304b\u3001UI\u3092\u81ea\u5206\u3067\u30db\u30b9\u30c8\u3057\u3066\u4f7f\u3044\u307e\u3059\u3002 ## \u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3 * [KubeVirt](https://kubevirt.io/user-guide/#/installation/installation)\u306f\u4eee\u60f3\u30de\u30b7\u30f3\u3092Kubernetes\u4e0a\u3067\u5b9f\u884c\u3059\u308b\u305f\u3081\u306e\u30a2\u30c9\u30aa\u30f3\u3067\u3059\u3002\u901a\u5e38\u3001\u30d9\u30a2\u30e1\u30bf\u30eb\u306e\u30af\u30e9\u30b9\u30bf\u3067\u5b9f\u884c\u3057\u307e\u3059\u3002 ## \u30ec\u30ac\u30b7\u30fc\u306a\u30a2\u30c9\u30aa\u30f3 \u3044\u304f\u3064\u304b\u306e\u30a2\u30c9\u30aa\u30f3\u306f\u3001\u5ec3\u6b62\u3055\u308c\u305f[cluster/addons](https://git.k8s.io/kubernetes/cluster/addons)\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u306b\u63b2\u8f09\u3055\u308c\u3066\u3044\u307e\u3059\u3002 \u3088\u304f\u30e1\u30f3\u30c6\u30ca\u30f3\u30b9\u3055\u308c\u305f\u30a2\u30c9\u30aa\u30f3\u306f\u3053\u3053\u306b\u30ea\u30f3\u30af\u3057\u3066\u304f\u3060\u3055\u3044\u3002PR\u3092\u6b53\u8fce\u3057\u3066\u3044\u307e\u3059\u3002 ", "commid": "website_pr_27837"}], "negative_passages": []} {"query_id": "q-en-website-c9270b65e4e4ea37cea789ac98a60a55cac6c6e677afe2b9382036a5e7b8a6a2", "query": "This is a Bug Report concepts page for spanish links doesn't take to spanish pages {{< feature-state for_k8s_version=\"v1.21\" state=\"alpha\" >}} _\u62d3\u6251\u611f\u77e5\u63d0\u793a_ \u542f\u7528\u5177\u6709\u62d3\u6251\u611f\u77e5\u80fd\u529b\u7684\u8def\u7531\uff0c\u5176\u4e2d\u62d3\u6251\u611f\u77e5\u4fe1\u606f\u5305\u542b\u5728 {{< glossary_tooltip text=\"EndpointSlices\" term_id=\"endpoint-slice\" >}} \u4e2d\u3002 \u6b64\u529f\u80fd\u5c3d\u91cf\u5c06\u6d41\u91cf\u9650\u5236\u5728\u5b83\u7684\u53d1\u8d77\u533a\u57df\u9644\u8fd1\uff1b \u53ef\u4ee5\u964d\u4f4e\u6210\u672c\uff0c\u6216\u8005\u63d0\u9ad8\u7f51\u7edc\u6027\u80fd\u3002 ## {{% heading \"prerequisites\" %}} {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} \u4e3a\u4e86\u542f\u7528\u62d3\u6251\u611f\u77e5\u63d0\u793a\uff0c\u5148\u8981\u6ee1\u8db3\u4ee5\u4e0b\u5148\u51b3\u6761\u4ef6\uff1a * \u914d\u7f6e {{< glossary_tooltip text=\"kube-proxy\" term_id=\"kube-proxy\" >}} \u4ee5 iptables \u6216 IPVS \u6a21\u5f0f\u8fd0\u884c * \u786e\u4fdd\u672a\u7981\u7528 EndpointSlices ## \u542f\u52a8\u62d3\u6251\u611f\u77e5\u63d0\u793a {#enable-topology-aware-hints} \u8981\u542f\u7528\u670d\u52a1\u62d3\u6251\u611f\u77e5\uff0c\u8bf7\u542f\u7528 kube-apiserver\u3001kube-controller-manager\u3001\u548c kube-proxy \u7684 [\u7279\u6027\u95e8\u63a7](/zh/docs/reference/command-line-tools-reference/feature-gates/) `TopologyAwareHints`\u3002 ``` --feature-gates=\"TopologyAwareHints=true\" ``` ## {{% heading \"whatsnext\" %}} * \u53c2\u9605\u9762\u5411\u670d\u52a1\u7684[\u62d3\u6251\u611f\u77e5\u63d0\u793a](/zh/docs/concepts/services-networking/topology-aware-hints) * \u53c2\u9605[\u7528\u670d\u52a1\u8fde\u901a\u5e94\u7528](/zh/docs/concepts/services-networking/connect-applications-service/) ", "commid": "website_pr_28155"}], "negative_passages": []} {"query_id": "q-en-website-526c7ae8a5989f0b4441532f28ef37c4493153e2b2e8ad6d6d8b8f3cfeb16f1c", "query": "A on is broken and returning 404 page.\nThis 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. /docs/tasks/administer-cluster/out-of-resource/ /docs/concepts/scheduling-eviction/pod-eviction/ 301 /docs/tasks/administer-cluster/out-of-resource/ /docs/concepts/scheduling-eviction/node-pressure-eviction/ 301 /docs/tasks/administer-cluster/romana-network-policy/ /docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/ 301 /docs/tasks/administer-cluster/running-cloud-controller.md /docs/tasks/administer-cluster/running-cloud-controller/ 301 /docs/tasks/administer-cluster/share-configuration/ /docs/tasks/access-application-cluster/configure-access-multiple-clusters/ 301", "commid": "website_pr_28080"}], "negative_passages": []} {"query_id": "q-en-website-be366a0e7e3d1c9e6d77b30acb963348724f104cbaeab0a8da44d0628e8e6f07", "query": "This is a Bug Report Adding entries to a Pod's `/etc/hosts` file provides Pod-level override of hostname resolution when DNS and other options are not applicable. You can add these custom entries with the HostAliases field in PodSpec. Modification not using HostAliases is not suggested because the file is managed by the kubelet and can be overwritten on during Pod creation/restart. ## Default hosts file content Start an Nginx Pod which is assigned a Pod IP: ```shell kubectl run nginx --image nginx ``` ``` pod/nginx created ``` Examine a Pod IP: ```shell kubectl get pods --output=wide ``` ``` NAME READY STATUS RESTARTS AGE IP NODE nginx 1/1 Running 0 13s 10.200.0.4 worker0 ``` The hosts file content would look like this: ```shell kubectl exec nginx -- cat /etc/hosts ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.4\tnginx ``` By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like `localhost` and its own hostname. ## Adding additional entries with hostAliases In addition to the default boilerplate, you can add additional entries to the `hosts` file. For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under `.spec.hostAliases`: {{< codenew file=\"service/networking/hostaliases-pod.yaml\" >}} You can start a Pod with that configuration by running: ```shell kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml ``` ``` pod/hostaliases-pod created ``` Examine a Pod's details to see its IPv4 address and its status: ```shell kubectl get pod --output=wide ``` ``` NAME READY STATUS RESTARTS AGE IP NODE hostaliases-pod 0/1 Completed 0 6s 10.200.0.5 worker0 ``` The `hosts` file content looks like this: ```shell kubectl logs hostaliases-pod ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.5\thostaliases-pod # Entries added by HostAliases. 127.0.0.1\tfoo.local\tbar.local 10.1.2.3\tfoo.remote\tbar.remote ``` with the additional entries specified at the bottom. ## Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file} The kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the `hosts` file for each container of the Pod to prevent Docker from [modifying](https://github.com/moby/moby/issues/17190) the file after the containers have already been started. {{< caution >}} Avoid making manual changes to the hosts file inside a container. If you make manual changes to the hosts file, those changes are lost when the container exits. {{< /caution >}} ", "commid": "website_pr_28631"}], "negative_passages": []} {"query_id": "q-en-website-a1db360be651aafe95f4fd8fe6d7c0ee9fc36337cda5ed4c617c91368c09585a", "query": "Affected page: Move this page from Concepts to Tasks (potentially under Tasks Networking). Update to redirect the old URL to the new location (use a 301 code, similar to other entries in this file). /sig docs /language en\n/triage accepted /help\n/remove-help\nI'd like to work on this one to learn something new in website page organizing. Thanks. /assign", "positive_passages": [{"docid": "doc-en-website-ab66c7c4d876d7e8410ebf8471cba0f88dd9b3d17627eb9183608b001825978a", "text": " --- reviewers: - rickypai - thockin title: Adding entries to Pod /etc/hosts with HostAliases content_type: task weight: 60 min-kubernetes-server-version: 1.7 --- Adding entries to a Pod's `/etc/hosts` file provides Pod-level override of hostname resolution when DNS and other options are not applicable. You can add these custom entries with the HostAliases field in PodSpec. Modification not using HostAliases is not suggested because the file is managed by the kubelet and can be overwritten on during Pod creation/restart. ## Default hosts file content Start an Nginx Pod which is assigned a Pod IP: ```shell kubectl run nginx --image nginx ``` ``` pod/nginx created ``` Examine a Pod IP: ```shell kubectl get pods --output=wide ``` ``` NAME READY STATUS RESTARTS AGE IP NODE nginx 1/1 Running 0 13s 10.200.0.4 worker0 ``` The hosts file content would look like this: ```shell kubectl exec nginx -- cat /etc/hosts ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.4\tnginx ``` By default, the `hosts` file only includes IPv4 and IPv6 boilerplates like `localhost` and its own hostname. ## Adding additional entries with hostAliases In addition to the default boilerplate, you can add additional entries to the `hosts` file. For example: to resolve `foo.local`, `bar.local` to `127.0.0.1` and `foo.remote`, `bar.remote` to `10.1.2.3`, you can configure HostAliases for a Pod under `.spec.hostAliases`: {{< codenew file=\"service/networking/hostaliases-pod.yaml\" >}} You can start a Pod with that configuration by running: ```shell kubectl apply -f https://k8s.io/examples/service/networking/hostaliases-pod.yaml ``` ``` pod/hostaliases-pod created ``` Examine a Pod's details to see its IPv4 address and its status: ```shell kubectl get pod --output=wide ``` ``` NAME READY STATUS RESTARTS AGE IP NODE hostaliases-pod 0/1 Completed 0 6s 10.200.0.5 worker0 ``` The `hosts` file content looks like this: ```shell kubectl logs hostaliases-pod ``` ``` # Kubernetes-managed hosts file. 127.0.0.1\tlocalhost ::1\tlocalhost ip6-localhost ip6-loopback fe00::0\tip6-localnet fe00::0\tip6-mcastprefix fe00::1\tip6-allnodes fe00::2\tip6-allrouters 10.200.0.5\thostaliases-pod # Entries added by HostAliases. 127.0.0.1\tfoo.local\tbar.local 10.1.2.3\tfoo.remote\tbar.remote ``` with the additional entries specified at the bottom. ## Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file} The kubelet [manages](https://github.com/kubernetes/kubernetes/issues/14633) the `hosts` file for each container of the Pod to prevent Docker from [modifying](https://github.com/moby/moby/issues/17190) the file after the containers have already been started. {{< caution >}} Avoid making manual changes to the hosts file inside a container. If you make manual changes to the hosts file, those changes are lost when the container exits. {{< /caution >}} ", "commid": "website_pr_28631"}], "negative_passages": []} {"query_id": "q-en-website-a1db360be651aafe95f4fd8fe6d7c0ee9fc36337cda5ed4c617c91368c09585a", "query": "Affected page: Move this page from Concepts to Tasks (potentially under Tasks Networking). Update to redirect the old URL to the new location (use a 301 code, similar to other entries in this file). /sig docs /language en\n/triage accepted /help\n/remove-help\nI'd like to work on this one to learn something new in website page organizing. Thanks. /assign", "positive_passages": [{"docid": "doc-en-website-05c82aeb721fc079c480dc4a89ae94bb5b1777f4b5b39dc14ab4c3f0cfad16fb", "text": "/docs/concepts/scheduling-eviction/eviction-policy/ /docs/concepts/scheduling-eviction/node-pressure-eviction/ 301 /docs/concepts/service-catalog/ /docs/concepts/extend-kubernetes/service-catalog/ 301 /docs/concepts/services-networking/networkpolicies/ /docs/concepts/services-networking/network-policies/ 301 /docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/ /docs/tasks/network/customize-hosts-file-for-pods/ 301 /docs/concepts/storage/etcd-store-api-object/ /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301 /docs/concepts/storage/volumes/emptyDirapiVersion/ /docs/concepts/storage/volumes/#emptydir/ 301 /docs/concepts/tools/kubectl/object-management-overview/ /docs/concepts/overview/object-management-kubectl/overview/ 301", "commid": "website_pr_28631"}], "negative_passages": []} {"query_id": "q-en-website-15474e2a544d42f35d55b4a54b4595a167afd2c5b246e6f569319bcc7702b3d5", "query": "What would you like to be In Seccomp should link to instead of Why For a better understanding of how Seccomp works in k8s. As Seccomp is stable fetaure in k8s.\nThis 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. * [Seccomp](https://en.wikipedia.org/wiki/Seccomp): Filter a process's system calls. * [Seccomp](/docs/tutorials/clusters/seccomp/): Filter a process's system calls. * AllowPrivilegeEscalation: Controls whether a process can gain more privileges than its parent process. This bool directly controls whether the [`no_new_privs`](https://www.kernel.org/doc/Documentation/prctl/no_new_privs.txt) flag gets set on the container process. AllowPrivilegeEscalation is true always when the container is: 1) run as Privileged OR 2) has `CAP_SYS_ADMIN`.", "commid": "website_pr_28678"}], "negative_passages": []} {"query_id": "q-en-website-e34093bba3db13b222938482d29cd031aedd7b97c833318fb7130475d92462f8", "query": "Document's section: Currenty it says: Kubernetes creates one PersistentVolume for each VolumeClaimTemplate That is not wrong, but not exact. What about replacing it by something like this: Per each StatefulSet triggered pod Kubernetes creates a PersistentVolumeClaim object for each VolumeClaimTemplates entry defined in the StatefulSet object /language en\nThis 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. Kubernetes creates one [PersistentVolume](/docs/concepts/storage/persistent-volumes/) for each VolumeClaimTemplate. In the nginx example above, each Pod will receive a single PersistentVolume with a StorageClass of `my-storage-class` and 1 Gib of provisioned storage. If no StorageClass For each VolumeClaimTemplate entry defined in a StatefulSet, each Pod receives one PersistentVolumeClaim. In the nginx example above, each Podreceives a single PersistentVolume with a StorageClass of `my-storage-class` and 1 Gib of provisioned storage. If no StorageClass is specified, then the default StorageClass will be used. When a Pod is (re)scheduled onto a node, its `volumeMounts` mount the PersistentVolumes associated with its PersistentVolume Claims. Note that, the PersistentVolumes associated with the", "commid": "website_pr_29012"}], "negative_passages": []} {"query_id": "q-en-website-c93fb4d7eff6cc5d3f448751af75a21ba6b1b18e7ea2a4c241ecdffce8b82148", "query": "This is a Bug Report {{ $ulNr := 0 }} {{ $ulShow := cond (isset .Site.Params.ui \"ul_show\") .Site.Params.ui.ul_show 1 }} {{ $sidebarMenuTruncate := cond (isset .Site.Params.ui \"sidebar_menu_truncate\") .Site.Params.ui.sidebar_menu_truncate 50 }} {{ $currentLang := .Site.Language }} {{ $ulNr := 0 -}} {{ $ulShow := cond (isset .Site.Params.ui \"ul_show\") .Site.Params.ui.ul_show 1 -}} {{ $sidebarMenuTruncate := cond (isset .Site.Params.ui \"sidebar_menu_truncate\") .Site.Params.ui.sidebar_menu_truncate 50 -}} {{ $currentLang := .Site.Language -}}
    {{ template \"section-tree-nav-section\" (dict \"page\" . \"section\" .FirstSection \"shouldDelayActive\" $shouldDelayActive \"sidebarMenuTruncate\" $sidebarMenuTruncate \"ulNr\" $ulNr \"ulShow\" (add $ulShow 1) \"currentLang\" $currentLang) }}
{{ define \"section-tree-nav-section\" }} {{ $s := .section }} {{ $p := .page }} {{ $shouldDelayActive := .shouldDelayActive }} {{ $sidebarMenuTruncate := .sidebarMenuTruncate }} {{ $treeRoot := cond (eq .ulNr 0) true false }} {{ $ulNr := .ulNr }} {{ $ulShow := .ulShow }} {{ $active := and (not $shouldDelayActive) (eq $s $p) }} {{ $activePath := and (not $shouldDelayActive) ($p.IsDescendant $s) }} {{ $show := cond (or (lt $ulNr $ulShow) $activePath (and (not $shouldDelayActive) (eq $s.Parent $p.Parent)) (and (not $shouldDelayActive) (eq $s.Parent $p)) (and (not $shouldDelayActive) ($p.IsDescendant $s.Parent))) true false }} {{ $mid := printf \"m-%s\" ($s.RelPermalink | anchorize) }} {{ $pages_tmp := where (union $s.Pages $s.Sections).ByWeight \".Params.toc_hide\" \"!=\" true }} {{ $pages := $pages_tmp | first $sidebarMenuTruncate }} {{ $withChild := gt (len $pages) 0 }} {{ $manualLink := cond (isset $s.Params \"manuallink\") $s.Params.manualLink ( cond (isset $s.Params \"manuallinkrelref\") (relref $s $s.Params.manualLinkRelref) $s.RelPermalink) }} {{ $manualLinkTitle := cond (isset $s.Params \"manuallinktitle\") $s.Params.manualLinkTitle $s.Title }} {{ define \"section-tree-nav-section\" -}} {{ $s := .section -}} {{ $p := .page -}} {{ $shouldDelayActive := .shouldDelayActive -}} {{ $sidebarMenuTruncate := .sidebarMenuTruncate -}} {{ $treeRoot := cond (eq .ulNr 0) true false -}} {{ $ulNr := .ulNr -}} {{ $ulShow := .ulShow -}} {{ $active := and (not $shouldDelayActive) (eq $s $p) -}} {{ $activePath := and (not $shouldDelayActive) ($p.IsDescendant $s) -}} {{ $show := cond (or (lt $ulNr $ulShow) $activePath (and (not $shouldDelayActive) (eq $s.Parent $p.Parent)) (and (not $shouldDelayActive) (eq $s.Parent $p)) (and (not $shouldDelayActive) ($p.IsDescendant $s.Parent))) true false -}} {{ $mid := printf \"m-%s\" ($s.RelPermalink | anchorize) -}} {{ $pages_tmp := where (union $s.Pages $s.Sections).ByWeight \".Params.toc_hide\" \"!=\" true -}} {{ $pages := $pages_tmp | first $sidebarMenuTruncate -}} {{ $withChild := gt (len $pages) 0 -}} {{ $manualLink := cond (isset $s.Params \"manuallink\") $s.Params.manualLink ( cond (isset $s.Params \"manuallinkrelref\") (relref $s $s.Params.manualLinkRelref) $s.RelPermalink) -}} {{ $manualLinkTitle := cond (isset $s.Params \"manuallinktitle\") $s.Params.manualLinkTitle $s.Title -}}
  • {{ if (and $p.Site.Params.ui.sidebar_menu_foldable (ge $ulNr 1)) }} {{ if (and $p.Site.Params.ui.sidebar_menu_foldable (ge $ulNr 1)) -}} {{ else }} {{ else -}} {{ if not $treeRoot }} {{ with $s.Params.Icon}}{{ end }}{{ $s.LinkTitle }} {{ end }} {{ end }} {{if $withChild }} {{ $ulNr := add $ulNr 1 }} {{ end -}} {{ end -}} {{ if $withChild -}} {{ $ulNr := add $ulNr 1 -}}
      {{ $pages := where (union $s.Pages $s.Sections).ByWeight \".Params.toc_hide\" \"!=\" true }} {{ with site.Params.language_alternatives }} {{ $pages := where (union $s.Pages $s.Sections).ByWeight \".Params.toc_hide\" \"!=\" true -}} {{ with site.Params.language_alternatives -}} {{ range . }} {{ with (where $.section.Translations \".Lang\" . ) }} {{ $p := index . 0 }} {{ $pages = $pages | lang.Merge (union $p.Pages $p.Sections) }} {{ end }} {{ end }} {{ end }} {{ $pages := $pages | first 50 }} {{ range $pages }} {{ if (not (and (eq $s $p.Site.Home) (eq .Params.toc_root true)) ) }} {{ $mid := printf \"m-%s\" (.RelPermalink | anchorize) }} {{ $active := eq . $p }} {{ $isForeignLanguage := (ne (string .Lang) (string $.currentLang)) }} {{ if (and $isForeignLanguage ($p.IsDescendant $s)) }} {{ with (where $.section.Translations \".Lang\" . ) -}} {{ $p := index . 0 -}} {{ $pages = $pages | lang.Merge (union $p.Pages $p.Sections) -}} {{ end -}} {{ end -}} {{ end -}} {{ $pages := $pages | first 50 -}} {{ range $pages -}} {{ if (not (and (eq $s $p.Site.Home) (eq .Params.toc_root true)) ) -}} {{ $mid := printf \"m-%s\" (.RelPermalink | anchorize) -}} {{ $active := eq . $p -}} {{ $isForeignLanguage := (ne (string .Lang) (string $.currentLang)) -}} {{ if (and $isForeignLanguage ($p.IsDescendant $s)) -}} {{ .LinkTitle }}{{ if $isForeignLanguage }} ({{ .Lang | upper }}){{ end }} {{ .LinkTitle }}{{ if $isForeignLanguage }} ({{ .Lang | upper }}){{ end -}} {{ else }} {{ else -}} {{ template \"section-tree-nav-section\" (dict \"page\" $p \"section\" . \"currentLang\" $.currentLang \"shouldDelayActive\" $shouldDelayActive \"sidebarMenuTruncate\" $sidebarMenuTruncate \"ulNr\" $ulNr \"ulShow\" $ulShow) }} {{ end }} {{ end }} {{ end }} {{- end }} {{- end }} {{- end }}
    {{ end }} {{- end }}
    • {{ end }} {{- end }} ", "commid": "website_pr_29006"}], "negative_passages": []} {"query_id": "q-en-website-7903097305e6ea169afd0e65fec18385d832ae780e6312ba8b2abd7f67f7c5c5", "query": "This is a Bug Report This page shows how to install the `kubeadm` toolbox. For information how to create a cluster with kubeadm once you have performed this installation process, see the [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) page. For information on how to create a cluster with kubeadm once you have performed this installation process, see the [Using kubeadm to Create a Cluster](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/) page. ", "commid": "website_pr_29011"}], "negative_passages": []} {"query_id": "q-en-website-3ddabc97b64beb2129ce4114521bc76a75636e727501009178e1bdb79848e4e9", "query": "According to the : this feature has been graduated to GA in 1.22 The doc still indicates:\n/retitle Incorrect feature state for Server-side Apply /kind bug /language en Which page is wrong, ? Can you provide the URL for it?\n/wg api-expression\nI think the page is /triage accepted\n/assign", "positive_passages": [{"docid": "doc-en-website-521fb601a736f17ee6ed72259e353d568f5fd81c35d4df6d31ba3f21d4abc48a", "text": " {{< feature-state for_k8s_version=\"v1.16\" state=\"beta\" >}} {{< feature-state for_k8s_version=\"v1.22\" state=\"stable\" >}} ## Introduction", "commid": "website_pr_29271"}], "negative_passages": []} {"query_id": "q-en-website-121d19e2df240b809749eaf933eb4d7c45ba6e09ca2ab7d917fc01d779d797e6", "query": "This is a Bug Report Problem: The konnectivity docs: Include the following instruction: Setting to doesn't seem right: This will break authentication for all tokens that use the default audience value (taken from the value), which is most tokens. This will allow tokens with in them to authenticate directly to kube-apiserver. I don't think we want that. Instead, we should just depend on konnectivity-server specifying the right audience in . Also: is unlikely to be a valid value for . In practice is typically an URL. Proposed Solution: Instead of including incorrect flag values inline, just link out to the correct documentation at Page to Update:\n/triage accepted\n/assign cheftako\nGitHub didn't allow me to assign the following users: jkh. Note that only , repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the `ServiceAccountTokenVolumeProjection` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled. You can enable [service account token volume protection](/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) by providing the following flags to the kube-apiserver: ``` --service-account-issuer=api --service-account-signing-key-file=/etc/kubernetes/pki/sa.key --api-audiences=system:konnectivity-server ``` [Service Account Token Volume Projection](/docs/tasks/configure-pod-container/configure-service-account/#service-account-token-volume-projection) feature enabled in your cluster. It is enabled by default since Kubernetes v1.20. 1. Create an egress configuration file such as `admin/konnectivity/egress-selector-configuration.yaml`. 1. Set the `--egress-selector-config-file` flag of the API Server to the path of your API Server egress configuration file.", "commid": "website_pr_30385"}], "negative_passages": []} {"query_id": "q-en-website-806f20bac8ba9503d1da4047a34313a5f72f6f9a6fc9333b8837f0f000b31904", "query": "This is a Bug Report Kubernetes\u6587\u6863\u4e2d[\u4f7f\u7528\u624b\u518c](/zh/docs/user-guide/)\u90e8\u5206\u4e2d\u7684\u4e3b\u9898\u88ab\u79fb\u52a8\u5230 Kubernetes\u6587\u6863\u4e2d[\u7528\u6237\u6307\u5357](/zh/docs/user-guide/)\u90e8\u5206\u4e2d\u7684\u4e3b\u9898\u88ab\u79fb\u52a8\u5230 [\u4efb\u52a1](/zh/docs/tasks/)\u3001[\u6559\u7a0b](/zh/docs/tutorials/)\u548c[\u6982\u5ff5](/zh/docs/concepts)\u8282\u3002 \u672c\u4e3b\u9898\u5185\u5bb9\u5df2\u79fb\u81f3:", "commid": "website_pr_31495"}], "negative_passages": []} {"query_id": "q-en-website-4fb6c389b3996451aa91b1848bf78b86f645e05170661d74c10348717f83264e", "query": "This is a Feature Request {{< feature-state for_k8s_version=\"v1.18\" state=\"beta\" >}} Pod\u3092Node\u4e0a\u3067\u5b9f\u884c\u3059\u308b\u6642\u306b\u3001Pod\u81ea\u8eab\u306f\u5927\u91cf\u306e\u30b7\u30b9\u30c6\u30e0\u30ea\u30bd\u30fc\u30b9\u3092\u6d88\u8cbb\u3057\u307e\u3059\u3002\u3053\u308c\u3089\u306e\u30ea\u30bd\u30fc\u30b9\u306f\u3001Pod\u5185\u306e\u30b3\u30f3\u30c6\u30ca(\u7fa4)\u3092\u5b9f\u884c\u3059\u308b\u305f\u3081\u306b\u5fc5\u8981\u306a\u30ea\u30bd\u30fc\u30b9\u3068\u3057\u3066\u8ffd\u52a0\u3055\u308c\u307e\u3059\u3002Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u306e\u8981\u6c42\u3068\u5236\u9650\u306b\u52a0\u3048\u3066\u3001Pod\u306e\u30a4\u30f3\u30d5\u30e9\u30b9\u30c8\u30e9\u30af\u30c1\u30e3\u3067\u6d88\u8cbb\u3055\u308c\u308b\u30ea\u30bd\u30fc\u30b9\u3092\u8a08\u7b97\u3059\u308b\u305f\u3081\u306e\u6a5f\u80fd\u3067\u3059\u3002 Kubernetes\u3067\u306f\u3001Pod\u306e[RuntimeClass](/docs/concepts/containers/runtime-class/)\u306b\u95a2\u9023\u3059\u308b\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u306b\u5fdc\u3058\u3066\u3001[\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3](/ja/docs/reference/access-authn-authz/extensible-admission-controllers/#what-are-admission-webhooks)\u6642\u306bPod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u304c\u8a2d\u5b9a\u3055\u308c\u307e\u3059\u3002 Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u3092\u6709\u52b9\u306b\u3057\u305f\u5834\u5408\u3001Pod\u306e\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u6642\u306b\u30b3\u30f3\u30c6\u30ca\u306e\u30ea\u30bd\u30fc\u30b9\u8981\u6c42\u306e\u5408\u8a08\u306b\u52a0\u3048\u3066\u3001\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u3082\u8003\u616e\u3055\u308c\u307e\u3059\u3002\u540c\u69d8\u306b\u3001Kubelet\u306f\u3001Pod\u306ecgroup\u306e\u30b5\u30a4\u30ba\u6c7a\u5b9a\u6642\u304a\u3088\u3073Pod\u306e\u9000\u5f79\u306e\u9806\u4f4d\u4ed8\u3051\u6642\u306b\u3001Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u3092\u542b\u3081\u307e\u3059\u3002 ## Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u306e\u6709\u52b9\u5316\u3000{#set-up} \u30af\u30e9\u30b9\u30bf\u30fc\u5168\u4f53\u3067`PodOverhead`\u306e[\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8](/ja/docs/reference/command-line-tools-reference/feature-gates/)\u304c\u6709\u52b9\u306b\u306a\u3063\u3066\u3044\u308b\u3053\u3068\uff081.18\u6642\u70b9\u3067\u306f\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u30aa\u30f3\u306b\u306a\u3063\u3066\u3044\u307e\u3059\uff09\u3068\u3001`overhead`\u30d5\u30a3\u30fc\u30eb\u30c9\u3092\u5b9a\u7fa9\u3059\u308b`RuntimeClass`\u304c\u5229\u7528\u3055\u308c\u3066\u3044\u308b\u3053\u3068\u3092\u78ba\u8a8d\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 ## \u4f7f\u7528\u4f8b Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u6a5f\u80fd\u3092\u4f7f\u7528\u3059\u308b\u305f\u3081\u306b\u306f\u3001`overhead`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u5b9a\u7fa9\u3055\u308c\u305fRuntimeClass\u304c\u5fc5\u8981\u3067\u3059\u3002\u4f8b\u3068\u3057\u3066\u3001\u4eee\u60f3\u30de\u30b7\u30f3\u3068\u30b2\u30b9\u30c8OS\u306bPod\u3042\u305f\u308a\u7d04120MiB\u3092\u4f7f\u7528\u3059\u308b\u4eee\u60f3\u5316\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u3067\u3001\u6b21\u306e\u3088\u3046\u306aRuntimeClass\u3092\u5b9a\u7fa9\u3067\u304d\u307e\u3059\u3002 ```yaml --- kind: RuntimeClass apiVersion: node.k8s.io/v1 metadata: name: kata-fc handler: kata-fc overhead: podFixed: memory: \"120Mi\" cpu: \"250m\" ``` `kata-fc`RuntimeClass\u30cf\u30f3\u30c9\u30e9\u30fc\u3092\u6307\u5b9a\u3057\u3066\u4f5c\u6210\u3055\u308c\u305f\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306f\u3001\u30ea\u30bd\u30fc\u30b9\u30af\u30a9\u30fc\u30bf\u306e\u8a08\u7b97\u3084\u3001Node\u306e\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u3001\u304a\u3088\u3073Pod\u306ecgroup\u306e\u30b5\u30a4\u30ba\u6c7a\u5b9a\u306b\u30e1\u30e2\u30ea\u30fc\u3068CPU\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u304c\u8003\u616e\u3055\u308c\u307e\u3059\u3002 \u6b21\u306etest-pod\u306e\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306e\u4f8b\u3092\u5b9f\u884c\u3059\u308b\u3068\u3057\u307e\u3059\u3002 ```yaml apiVersion: v1 kind: Pod metadata: name: test-pod spec: runtimeClassName: kata-fc containers: - name: busybox-ctr image: busybox stdin: true tty: true resources: limits: cpu: 500m memory: 100Mi - name: nginx-ctr image: nginx resources: limits: cpu: 1500m memory: 100Mi ``` \u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u6642\u3001RuntimeClass[\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc](/docs/reference/access-authn-authz/admission-controllers/)\u306f\u3001RuntimeClass\u5185\u306b\u8a18\u8ff0\u3055\u308c\u305f`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u3092\u542b\u3080\u3088\u3046\u306b\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306ePodSpec\u3092\u66f4\u65b0\u3057\u307e\u3059\u3002\u3082\u3057\u65e2\u306bPodSpec\u5185\u306b\u3053\u306e\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u5b9a\u7fa9\u6e08\u307f\u306e\u5834\u5408\u3001\u305d\u306ePod\u306f\u62d2\u5426\u3055\u308c\u307e\u3059\u3002\u3053\u306e\u4f8b\u3067\u306f\u3001RuntimeClass\u306e\u540d\u524d\u3057\u304b\u6307\u5b9a\u3055\u308c\u3066\u3044\u306a\u3044\u305f\u3081\u3001\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u3092\u542b\u3080\u3088\u3046\u306bPod\u3092\u5909\u66f4\u3057\u307e\u3059\u3002 RuntimeClass\u306e\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306e\u5f8c\u3001\u66f4\u65b0\u3055\u308c\u305fPodSpec\u3092\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 ```bash kubectl get pod test-pod -o jsonpath='{.spec.overhead}' ``` \u51fa\u529b\u306f\u6b21\u306e\u901a\u308a\u3067\u3059: ``` map[cpu:250m memory:120Mi] ``` ResourceQuota\u304c\u5b9a\u7fa9\u3055\u308c\u3066\u3044\u308b\u5834\u5408\u3001\u30b3\u30f3\u30c6\u30ca\u8981\u6c42\u306e\u5408\u8a08\u3068`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u30ab\u30a6\u30f3\u30c8\u3055\u308c\u307e\u3059\u3002 kube-scheduler\u304c\u65b0\u3057\u3044Pod\u3092\u5b9f\u884c\u3059\u3079\u304dNode\u3092\u6c7a\u5b9a\u3059\u308b\u969b\u3001\u30b9\u30b1\u30b8\u30e5\u30fc\u30e9\u30fc\u306f\u305d\u306ePod\u306e`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u3068\u3001\u305d\u306ePod\u306b\u5bfe\u3059\u308b\u30b3\u30f3\u30c6\u30ca\u8981\u6c42\u306e\u5408\u8a08\u3092\u8003\u616e\u3057\u307e\u3059\u3002\u3053\u306e\u4f8b\u3060\u3068\u3001\u30b9\u30b1\u30b8\u30e5\u30fc\u30e9\u30fc\u306f\u3001\u8981\u6c42\u3068\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u3092\u8ffd\u52a0\u3057\u30012.25CPU\u3068320MiB\u306e\u30e1\u30e2\u30ea\u3092\u6301\u3064Node\u3092\u63a2\u3057\u307e\u3059\u3002 Pod\u304cNode\u306b\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3055\u308c\u308b\u3068\u3001\u305d\u306eNode\u306ekubelet\u306fPod\u306e\u305f\u3081\u306b\u65b0\u3057\u3044{{< glossary_tooltip text=\"cgroup\" term_id=\"cgroup\" >}}\u3092\u751f\u6210\u3057\u307e\u3059\u3002\u57fa\u76e4\u3068\u306a\u308b\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u304c\u30b3\u30f3\u30c6\u30ca\u3092\u4f5c\u6210\u3059\u308b\u306e\u306f\u3001\u3053\u306ePod\u5185\u3067\u3059\u3002 \u30ea\u30bd\u30fc\u30b9\u306b\u30b3\u30f3\u30c6\u30ca\u3054\u3068\u306e\u5236\u9650\u304c\u5b9a\u7fa9\u3055\u308c\u3066\u3044\u308b\u5834\u5408(\u5236\u9650\u304c\u5b9a\u7fa9\u3055\u308c\u3066\u3044\u308bGuaranteed QoS\u307e\u305f\u306fBustrable QoS)\u3001kubelet\u306f\u305d\u306e\u30ea\u30bd\u30fc\u30b9(CPU\u306fcpu.cfs_quota_us\u3001\u30e1\u30e2\u30ea\u306fmemory.limit_in_bytes)\u306b\u95a2\u9023\u3059\u308bPod\u306ecgroup\u306e\u4e0a\u9650\u3092\u8a2d\u5b9a\u3057\u307e\u3059\u3002\u3053\u306e\u4e0a\u9650\u306f\u3001\u30b3\u30f3\u30c6\u30ca\u306e\u5236\u9650\u3068PodSpec\u3067\u5b9a\u7fa9\u3055\u308c\u305f`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u306e\u5408\u8a08\u306b\u57fa\u3065\u304d\u307e\u3059\u3002 CPU\u306b\u3064\u3044\u3066\u306f\u3001Pod\u304cGuaranteed\u307e\u305f\u306fBurstable QoS\u306e\u5834\u5408\u3001kubelet\u306f\u30b3\u30f3\u30c6\u30ca\u306e\u8981\u6c42\u306e\u5408\u8a08\u3068PodSpec\u306b\u5b9a\u7fa9\u3055\u308c\u305f`\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9`\u306b\u57fa\u3065\u3044\u3066`cpu.share`\u3092\u8a2d\u5b9a\u3057\u307e\u3059\u3002 \u6b21\u306e\u4f8b\u3088\u308a\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306b\u5bfe\u3059\u308b\u30b3\u30f3\u30c6\u30ca\u306e\u8981\u6c42\u3092\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 ```bash kubectl get pod test-pod -o jsonpath='{.spec.containers[*].resources.limits}' ``` \u30b3\u30f3\u30c6\u30ca\u306e\u8981\u6c42\u306e\u5408\u8a08\u306f\u3001CPU\u306f2000m\u3001\u30e1\u30e2\u30ea\u30fc\u306f200MiB\u3067\u3059\u3002 ``` map[cpu: 500m memory:100Mi] map[cpu:1500m memory:100Mi] ``` Node\u3067\u89b3\u6e2c\u3055\u308c\u308b\u5024\u3068\u6bd4\u8f03\u3057\u3066\u307f\u307e\u3057\u3087\u3046\u3002 ```bash kubectl describe node | grep test-pod -B2 ``` \u51fa\u529b\u3067\u306f\u30012250m\u306eCPU\u3068320MiB\u306e\u30e1\u30e2\u30ea\u30fc\u304c\u8981\u6c42\u3055\u308c\u3066\u304a\u308a\u3001Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u304c\u542b\u307e\u308c\u3066\u3044\u308b\u3053\u3068\u304c\u5206\u304b\u308a\u307e\u3059\u3002 ``` Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE --------- ---- ------------ ---------- --------------- ------------- --- default test-pod 2250m (56%) 2250m (56%) 320Mi (1%) 320Mi (1%) 36m ``` ## Pod\u306ecgroup\u306e\u5236\u9650\u3092\u78ba\u8a8d \u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u3067\u5b9f\u884c\u4e2d\u306eNode\u4e0a\u306b\u3042\u308b\u3001Pod\u306e\u30e1\u30e2\u30ea\u30fc\u306ecgroup\u3092\u78ba\u8a8d\u3057\u307e\u3059\u3002\u6b21\u306b\u793a\u3059\u4f8b\u3067\u306f\u3001CRI\u4e92\u63db\u306e\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u306eCLI\u3092\u63d0\u4f9b\u3059\u308bNode\u3067[`crictl`](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md)\u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059\u3002\u3053\u308c\u306fPod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u306e\u52d5\u4f5c\u3092\u793a\u3059\u305f\u3081\u306e\u9ad8\u5ea6\u306a\u4f8b\u3067\u3042\u308a\u3001\u30e6\u30fc\u30b6\u30fc\u304cNode\u4e0a\u3067\u76f4\u63a5cgroups\u3092\u78ba\u8a8d\u3059\u308b\u5fc5\u8981\u306f\u3042\u308a\u307e\u305b\u3093\u3002 \u307e\u305a\u3001\u7279\u5b9a\u306eNode\u3067\u3001Pod\u306e\u8b58\u5225\u5b50\u3092\u6c7a\u5b9a\u3057\u307e\u3059\u3002 ```bash # Pod\u304c\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3055\u308c\u3066\u3044\u308bNode\u3067\u5b9f\u884c POD_ID=\"$(sudo crictl pods --name test-pod -q)\" ``` \u3053\u3053\u304b\u3089\u3001Pod\u306ecgroup\u306e\u30d1\u30b9\u304c\u6c7a\u5b9a\u3057\u307e\u3059\u3002 ```bash # Pod\u304c\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3055\u308c\u3066\u3044\u308bNode\u3067\u5b9f\u884c sudo crictl inspectp -o=json $POD_ID | grep cgroupsPath ``` \u7d50\u679c\u306ecgroup\u30d1\u30b9\u306b\u306fPod\u306e`\u30dd\u30fc\u30ba\u4e2d`\u30b3\u30f3\u30c6\u30ca\u3082\u542b\u307e\u308c\u307e\u3059\u3002Pod\u30ec\u30d9\u30eb\u306ecgroup\u306f\uff11\u3064\u4e0a\u306e\u30c7\u30a3\u30ec\u30af\u30c8\u30ea\u3067\u3059\u3002 ``` \"cgroupsPath\": \"/kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2/7ccf55aee35dd16aca4189c952d83487297f3cd760f1bbf09620e206e7d0c27a\" ``` \u4eca\u56de\u306e\u30b1\u30fc\u30b9\u3067\u306f\u3001Pod\u306ecgroup\u30d1\u30b9\u306f\u3001`kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2`\u3068\u306a\u308a\u307e\u3059\u3002\u30e1\u30e2\u30ea\u30fc\u306ePod\u30ec\u30d9\u30eb\u306ecgroup\u306e\u8a2d\u5b9a\u3092\u78ba\u8a8d\u3057\u307e\u3057\u3087\u3046\u3002 ```bash # Pod\u304c\u30b9\u30b1\u30b8\u30e5\u30fc\u30eb\u3055\u308c\u3066\u3044\u308bNode\u3067\u5b9f\u884c # \u307e\u305f\u3001Pod\u306b\u5272\u308a\u5f53\u3066\u3089\u308c\u305fcgroup\u3068\u540c\u3058\u540d\u524d\u306b\u5909\u66f4 cat /sys/fs/cgroup/memory/kubepods/podd7f4b509-cf94-4951-9417-d1087c92a5b2/memory.limit_in_bytes ``` \u4e88\u60f3\u901a\u308a320MiB\u3067\u3059\u3002 ``` 335544320 ``` ### Observability Pod\u306e\u30aa\u30fc\u30d0\u30d8\u30c3\u30c9\u304c\u5229\u7528\u3055\u308c\u3066\u3044\u308b\u30bf\u30a4\u30df\u30f3\u30b0\u3092\u7279\u5b9a\u3057\u3001\u5b9a\u7fa9\u3055\u308c\u305f\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u3067\u5b9f\u884c\u3055\u308c\u3066\u3044\u308b\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306e\u5b89\u5b9a\u6027\u3092\u89b3\u5bdf\u3059\u308b\u305f\u3081\u3001[kube-state-metrics](https://github.com/kubernetes/kube-state-metrics)\u306b\u306f`kube_pod_overhead`\u3068\u3044\u3046\u30e1\u30c8\u30ea\u30af\u30b9\u304c\u7528\u610f\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u3053\u306e\u6a5f\u80fd\u306fv1.9\u306ekube-state-metrics\u3067\u306f\u5229\u7528\u3067\u304d\u307e\u305b\u3093\u304c\u3001\u6b21\u306e\u30ea\u30ea\u30fc\u30b9\u3067\u671f\u5f85\u3055\u308c\u3066\u3044\u307e\u3059\u3002\u305d\u308c\u307e\u3067\u306f\u3001kube-state-metrics\u3092\u30bd\u30fc\u30b9\u304b\u3089\u30d3\u30eb\u30c9\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 ## {{% heading \"whatsnext\" %}} * [RuntimeClass](/ja/docs/concepts/containers/runtime-class/) * [Pod\u306e\u30aa\u30fc\u30d0\u30fc\u30d8\u30c3\u30c9\u306e\u8a2d\u8a08](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/688-pod-overhead) ", "commid": "website_pr_31928"}], "negative_passages": []} {"query_id": "q-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29", "query": "There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\nThis 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. `docker`, and `journald`) is consuming more resources than were reserved via and `journald`) is consuming more resources than were reserved via `system-reserved` or `kube-reserved` allocations, and the node only has `Guaranteed` or `Burstable` pods using less resources than requests left on it, then the kubelet must choose to evict one of these pods to preserve node stability", "commid": "website_pr_31983"}], "negative_passages": []} {"query_id": "q-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29", "query": "There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\nThis 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. \u4ec5\u5f53 `Guaranteed` Pod \u4e2d\u6240\u6709\u5bb9\u5668\u90fd\u88ab\u6307\u5b9a\u4e86\u8bf7\u6c42\u548c\u9650\u5236\u5e76\u4e14\u4e8c\u8005\u76f8\u7b49\u65f6\uff0c\u624d\u4fdd\u8bc1 Pod \u4e0d\u88ab\u9a71\u9010\u3002 \u8fd9\u4e9b Pod \u6c38\u8fdc\u4e0d\u4f1a\u56e0\u4e3a\u53e6\u4e00\u4e2a Pod \u7684\u8d44\u6e90\u6d88\u8017\u800c\u88ab\u9a71\u9010\u3002 \u5982\u679c\u7cfb\u7edf\u5b88\u62a4\u8fdb\u7a0b\uff08\u4f8b\u5982 `kubelet`\u3001`docker` \u548c `journald`\uff09 \u5982\u679c\u7cfb\u7edf\u5b88\u62a4\u8fdb\u7a0b\uff08\u4f8b\u5982 `kubelet` \u548c `journald`\uff09 \u6d88\u8017\u7684\u8d44\u6e90\u6bd4\u901a\u8fc7 `system-reserved` \u6216 `kube-reserved` \u5206\u914d\u4fdd\u7559\u7684\u8d44\u6e90\u591a\uff0c \u5e76\u4e14\u8be5\u8282\u70b9\u53ea\u6709 `Guaranteed` \u6216 `Burstable` Pod \u4f7f\u7528\u7684\u8d44\u6e90\u5c11\u4e8e\u5176\u4e0a\u5269\u4f59\u7684\u8bf7\u6c42\uff0c \u90a3\u4e48 kubelet \u5fc5\u987b\u9009\u62e9\u9a71\u9010\u8fd9\u4e9b Pod \u4e2d\u7684\u4e00\u4e2a\u4ee5\u4fdd\u6301\u8282\u70b9\u7a33\u5b9a\u6027\u5e76\u51cf\u5c11\u8d44\u6e90\u532e\u4e4f\u5bf9\u5176\u4ed6 Pod \u7684\u5f71\u54cd\u3002", "commid": "website_pr_31983"}], "negative_passages": []} {"query_id": "q-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29", "query": "There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\nThis 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. full_link: /zh/docs/concepts/configuration/pod-priority-preemption/#pod-priority full_link: /zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority short_description: > Pod \u4f18\u5148\u7ea7\u8868\u793a\u4e00\u4e2a Pod \u76f8\u5bf9\u4e8e\u5176\u4ed6 Pod \u7684\u91cd\u8981\u6027\u3002", "commid": "website_pr_31983"}], "negative_passages": []} {"query_id": "q-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29", "query": "There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\nThis 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. full_link: /docs/concepts/configuration/pod-priority-preemption/#pod-priority full_link: /docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority short_description: > Pod Priority indicates the importance of a Pod relative to other Pods.", "commid": "website_pr_31983"}], "negative_passages": []} {"query_id": "q-en-website-15c090ca8ee9175d97ce7175924fdbc22f4726a6e61db2144af742d7756cfc29", "query": "There is a bug: ,%E8%AE%BE%E4%B8%BA%20%2D997%E3%80%82 \"\"'s hyperlink status is 404, it should be changed to \"\"\nThis 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. [Pod \u4f18\u5148\u7ea7](/zh/docs/concepts/configuration/pod-priority-preemption/#pod-priority) [Pod \u4f18\u5148\u7ea7](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/#pod-priority) \u5141\u8bb8\u7528\u6237\u4e3a Pod \u8bbe\u7f6e\u9ad8\u4e8e\u6216\u4f4e\u4e8e\u5176\u4ed6 Pod \u7684\u4f18\u5148\u7ea7 -- \u8fd9\u5bf9\u4e8e\u751f\u4ea7\u96c6\u7fa4 \u5de5\u4f5c\u8d1f\u8f7d\u800c\u8a00\u662f\u4e00\u4e2a\u91cd\u8981\u7684\u7279\u6027\u3002", "commid": "website_pr_31983"}], "negative_passages": []} {"query_id": "q-en-website-c440581b2df3ea77f2d772b74751bc635d26f72c9a0993ca90840200713f92fd", "query": "This is a Feature Request Our workflow has been a great way to meet our commitment in keeping PR numbers at a manageable amount. We've recently introduced a way for new contributors to understand the PR Wrangling process, as a way to onboard possible new reviewers, approvers, and wranglers. What would you like to be The above-mentioned shadowing process was brought up and discussed in a late 2021 SIG Docs meeting, however, has no documentation to explain the process or the expectations of the PR Wrangler and their shadow. We should put together information, to our existing PR Wranglers , that lists details about this program, how to become a shadow, and what participants can expect to learn. Why is this needed To ensure our shadow process is successful, a clearly documented guide is needed so we can better recruit for this program and evangelize it. Given we'll be reporting on this addition to our training in the 2021 Kubernetes Annual Report, we should prioritize the creation of these docs. cc:\n/language en /sig docs /triage accepted\nHi, I would like to work on this issue. Thanks. /assign", "positive_passages": [{"docid": "doc-en-website-4b6f83f358d5469a4b731bad6da46fff5cd5d3c4520016cb5f0d7f1df2023b61", "text": "The [`fejta-bot`](https://github.com/fejta-bot) bot marks issues as stale after 90 days of inactivity. After 30 more days it marks issues as rotten and closes them. PR wranglers should close issues after 14-30 days of inactivity. {{< /note >}} ## PR Wrangler shadow program In late 2021, SIG Docs introduced the PR Wrangler Shadow Program. The program was introduced to help new contributors understand the PR wrangling process. ### Become a shadow - If you are interested in shadowing as a PR wrangler, please visit the [PR Wranglers Wiki page](https://github.com/kubernetes/website/wiki/PR-Wranglers) to see the PR wrangling schedule for this year and sign up. - Kubernetes org members can edit the [PR Wranglers Wiki page](https://github.com/kubernetes/website/wiki/PR-Wranglers) and sign up to shadow an existing PR Wrangler for a week. - Others can reach out on the [#sig-docs Slack channel](https://kubernetes.slack.com/messages/sig-docs) for requesting to shadow an assigned PR Wrangler for a specific week. Feel free to reach out to Brad Topol (`@bradtopol`) or one of the [SIG Docs co-chairs/leads](https://github.com/kubernetes/community/tree/master/sig-docs#leadership). - Once you've signed up to shadow a PR Wrangler, introduce yourself to the PR Wrangler on the [Kubernetes Slack](slack.k8s.io). No newline at end of file", "commid": "website_pr_32098"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. }} Only use kubeconfig files from trusted sources. Using a specially-crafted kubeconfig file could result in malicious code execution or file exposure. Only use kubeconfig files from trusted sources. Using a specially-crafted kubeconfig file could result in malicious code execution or file exposure. If you must use an untrusted kubeconfig file, inspect it carefully first, much as you would a shell script. {{< /warning>}}", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. ```shell ```yaml apiVersion: v1 kind: Config preferences: {}", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. export KUBECONFIG_SAVED=$KUBECONFIG export KUBECONFIG_SAVED=\"$KUBECONFIG\" ``` ### Windows PowerShell", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. export KUBECONFIG=$KUBECONFIG:config-demo:config-demo-2 export KUBECONFIG=\"${KUBECONFIG}:config-demo:config-demo-2\" ``` ### Windows PowerShell", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. export KUBECONFIG=$KUBECONFIG:$HOME/.kube/config export KUBECONFIG=\"${KUBECONFIG}:${HOME}/.kube/config\" ``` ### Windows Powershell", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-bc8ba2cd4173f9ec85b3e178fabd7b44c5af080ecd8f8cc33fbae6fcec39e684", "query": "Setting KUBECONFIG variable doesn't work very well on macOS (Monterey 12.2.1). In the line: The first colon (:) will make the following character (c) dissappear: What I get is the mangled text: What works for me better is explicitly using full paths:\nThis 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. export KUBECONFIG=$KUBECONFIG_SAVED export KUBECONFIG=\"$KUBECONFIG_SAVED\" ``` ### Windows PowerShell", "commid": "website_pr_34127"}], "negative_passages": []} {"query_id": "q-en-website-b15e60c66f0fd739f2fb31060f88342323f57121d5be223510513a453901f522", "query": "This is a Feature Request \u30d0\u30fc\u30b8\u30e7\u30f3v1.23\u3088\u308a\u524d\u306eKubernetes\u3067\u306f\u3001\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u30dd\u30ea\u30b7\u30fc\u3092\u4f7f\u7528\u3057\u3066\u3001*predicates*\u3068*priorities*\u306e\u51e6\u7406\u3092\u6307\u5b9a\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3057\u305f\u3002\u4f8b\u3048\u3070\u3001`kube-scheduler --policy-config-file `\u307e\u305f\u306f`kube-scheduler --policy-configmap `\u3092\u5b9f\u884c\u3059\u308b\u3068\u3001\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u30dd\u30ea\u30b7\u30fc\u3092\u8a2d\u5b9a\u3059\u308b\u3053\u3068\u304c\u53ef\u80fd\u3067\u3059\u3002 \u3053\u306e\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0\u30dd\u30ea\u30b7\u30fc\u306f\u3001\u30d0\u30fc\u30b8\u30e7\u30f3v1.23\u4ee5\u964d\u306eKubernetes\u3067\u306f\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002\u95a2\u9023\u3059\u308b\u30d5\u30e9\u30b0\u3067\u3042\u308b\u3001`policy-config-file`\u3001`policy-configmap`\u3001`policy-configmap-namespace`\u3001`use-legacy-policy-config`\u3082\u540c\u69d8\u306b\u30b5\u30dd\u30fc\u30c8\u3055\u308c\u3066\u3044\u307e\u305b\u3093\u3002 \u4ee3\u308f\u308a\u306b\u3001[\u30b9\u30b1\u30b8\u30e5\u30fc\u30e9\u30fc\u8a2d\u5b9a](/ja/docs/reference/scheduling/config/)\u3092\u4f7f\u7528\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ## {{% heading \"whatsnext\" %}} * [\u30b9\u30b1\u30b8\u30e5\u30fc\u30ea\u30f3\u30b0](/ja/docs/concepts/scheduling-eviction/kube-scheduler/)\u306b\u3064\u3044\u3066\u5b66\u3076 * [kube-scheduler\u8a2d\u5b9a](/ja/docs/reference/scheduling/config/)\u306b\u3064\u3044\u3066\u5b66\u3076 * [kube-scheduler\u8a2d\u5b9a\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9(v1beta3)](/docs/reference/config-api/kube-scheduler-config.v1beta3/)\u306b\u3064\u3044\u3066\u8aad\u3080 ", "commid": "website_pr_32084"}], "negative_passages": []} {"query_id": "q-en-website-41e086576cfe5c619ac935e47802c2f978dcc4955edb7353615e1c119f7bbbcd", "query": "In the v1beta1 admission config example, I had to use rather than See\nThis 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. runtimeClassNames: [] runtimeClasses: [] # Array of namespaces to exempt. namespaces: [] ```", "commid": "website_pr_32268"}], "negative_passages": []} {"query_id": "q-en-website-fff038ba39281fa9f68f4f7cf1c791e9a9867e0cc8c10d6ff8d148e851ce8d68", "query": "This is a Bug Report {{< feature-state for_k8s_version=\"v1.23\" state=\"beta\" >}} Kubernetes\u306e[Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96](/ja/docs/concepts/security/pod-security-standards/)\u306fPod\u306b\u5bfe\u3057\u3066\u7570\u306a\u308b\u5206\u96e2\u30ec\u30d9\u30eb\u3092\u5b9a\u7fa9\u3057\u307e\u3059\u3002 \u3053\u308c\u3089\u306e\u6a19\u6e96\u306b\u3088\u3063\u3066\u3001Pod\u306e\u52d5\u4f5c\u3092\u3069\u306e\u3088\u3046\u306b\u5236\u9650\u3057\u305f\u3044\u304b\u3092\u3001\u660e\u78ba\u304b\u3064\u4e00\u8cab\u3057\u305f\u65b9\u6cd5\u3067\u5b9a\u7fa9\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u30d9\u30fc\u30bf\u7248\u6a5f\u80fd\u3068\u3057\u3066\u3001Kubernetes\u306f[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/)\u306e\u5f8c\u7d99\u3067\u3042\u308b\u7d44\u307f\u8fbc\u307f\u306e _Pod Security_ {{< glossary_tooltip text=\"\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\" term_id=\"admission-controller\" >}}\u3092\u63d0\u4f9b\u3057\u3066\u3044\u307e\u3059\u3002 Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u5236\u9650\u306f\u3001Pod\u4f5c\u6210\u6642\u306b{{< glossary_tooltip text=\"\u540d\u524d\u7a7a\u9593\" term_id=\"namespace\" >}}\u30ec\u30d9\u30eb\u3067\u9069\u7528\u3055\u308c\u307e\u3059\u3002 {{< note >}} PodSecurityPolicy API\u306f\u975e\u63a8\u5968\u3067\u3042\u308a\u3001v1.25\u3067Kubernetes\u304b\u3089[\u524a\u9664](/docs/reference/using-api/deprecation-guide/#v1-25)\u3055\u308c\u308b\u4e88\u5b9a\u3067\u3059\u3002 {{< /note >}} ## `PodSecurity`\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30d7\u30e9\u30b0\u30a4\u30f3\u306e\u6709\u52b9\u5316 {#enabling-the-podsecurity-admission-plugin} v1.23\u306b\u304a\u3044\u3066\u3001`PodSecurity`\u306e[\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8](/ja/docs/reference/command-line-tools-reference/feature-gates/)\u306f\u30d9\u30fc\u30bf\u7248\u306e\u6a5f\u80fd\u3067\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u6709\u52b9\u5316\u3055\u308c\u3066\u3044\u307e\u3059\u3002 v1.22\u306b\u304a\u3044\u3066\u3001`PodSecurity`\u306e[\u30d5\u30a3\u30fc\u30c1\u30e3\u30fc\u30b2\u30fc\u30c8](/ja/docs/reference/command-line-tools-reference/feature-gates/)\u306f\u30a2\u30eb\u30d5\u30a1\u7248\u306e\u6a5f\u80fd\u3067\u3001\u7d44\u307f\u8fbc\u307f\u306e\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u4f7f\u7528\u3059\u308b\u306b\u306f\u3001`kube-apiserver`\u3067\u6709\u52b9\u306b\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 ```shell --feature-gates=\"...,PodSecurity=true\" ``` ## \u4ee3\u66ff\u6848:`PodSecurity`\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3webhook\u306e\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb {#webhook} \u30af\u30e9\u30b9\u30bf\u30fc\u304cv1.22\u3088\u308a\u53e4\u3044\u3001\u3042\u308b\u3044\u306f`PodSecurity`\u6a5f\u80fd\u3092\u6709\u52b9\u306b\u3067\u304d\u306a\u3044\u306a\u3069\u306e\u7406\u7531\u3067\u3001\u30d3\u30eb\u30c8\u30a4\u30f3\u306e`PodSecurity`\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30d7\u30e9\u30b0\u30a4\u30f3\u304c\u4f7f\u3048\u306a\u3044\u74b0\u5883\u3067\u306f\u3001`PodSecurity`\u306f\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30ed\u30b8\u30c3\u30af\u306f\u30d9\u30fc\u30bf\u7248\u306e[validating admission webhook](https://git.k8s.io/pod-security-admission/webhook)\u3068\u3057\u3066\u3082\u63d0\u4f9b\u3055\u308c\u3066\u3044\u307e\u3059\u3002 \u30d3\u30eb\u30c9\u524d\u306e\u30b3\u30f3\u30c6\u30ca\u30a4\u30e1\u30fc\u30b8\u3001\u8a3c\u660e\u66f8\u751f\u6210\u30b9\u30af\u30ea\u30d7\u30c8\u3001\u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u306e\u4f8b\u306f\u3001[https://git.k8s.io/pod-security-admission/webhook](https://git.k8s.io/pod-security-admission/webhook)\u3067\u5165\u624b\u53ef\u80fd\u3067\u3059\u3002 \u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u65b9\u6cd5: ```shell git clone git@github.com:kubernetes/pod-security-admission.git cd pod-security-admission/webhook make certs kubectl apply -k . ``` {{< note >}} \u751f\u6210\u3055\u308c\u305f\u8a3c\u660e\u66f8\u306e\u6709\u52b9\u671f\u9650\u306f2\u5e74\u9593\u3067\u3059\u3002\u6709\u52b9\u671f\u9650\u304c\u5207\u308c\u308b\u524d\u306b\u3001\u8a3c\u660e\u66f8\u3092\u518d\u751f\u6210\u3059\u308b\u304b\u3001\u5185\u8535\u306e\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30d7\u30e9\u30b0\u30a4\u30f3\u3092\u4f7f\u7528\u3057\u3066Webhook\u3092\u524a\u9664\u3057\u3066\u304f\u3060\u3055\u3044\u3002 {{< /note >}} ## Pod\u306e\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30ec\u30d9\u30eb {#pod-security-levels} Pod\u306e\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u306f\u3001Pod\u306e[Security Context](/docs/tasks/configure-pod-container/security-context/)\u3068\u305d\u306e\u4ed6\u306e\u95a2\u9023\u30d5\u30a3\u30fc\u30eb\u30c9\u306b\u3001[Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96](/ja/docs/concepts/security/pod-security-standards)\u3067\u5b9a\u7fa9\u3055\u308c\u305f3\u3064\u306e\u30ec\u30d9\u30eb\u3001`privileged`\u3001`baseline`\u3001`restricted`\u306b\u5f93\u3063\u3066\u8981\u4ef6\u3092\u8a2d\u5b9a\u3059\u308b\u3082\u306e\u3067\u3059\u3002 \u3053\u308c\u3089\u306e\u8981\u4ef6\u306e\u8a73\u7d30\u306b\u3064\u3044\u3066\u306f\u3001[Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96](/ja/docs/concepts/security/pod-security-standards)\u306e\u30da\u30fc\u30b8\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ## Pod\u306e\u540d\u524d\u7a7a\u9593\u306b\u5bfe\u3059\u308b\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30e9\u30d9\u30eb {#pod-security-admission-labels-for-namespaces} \u3053\u306e\u6a5f\u80fd\u3092\u6709\u52b9\u306b\u3059\u308b\u304b\u3001Webhook\u3092\u30a4\u30f3\u30b9\u30c8\u30fc\u30eb\u3059\u308b\u3068\u3001\u540d\u524d\u7a7a\u9593\u3092\u8a2d\u5b9a\u3057\u3066\u3001\u5404\u540d\u524d\u7a7a\u9593\u3067Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306b\u4f7f\u7528\u3057\u305f\u3044admission control\u30e2\u30fc\u30c9\u3092\u5b9a\u7fa9\u3067\u304d\u307e\u3059\u3002 Kubernetes\u306f\u3001\u540d\u524d\u7a7a\u9593\u306b\u4f7f\u7528\u3057\u305f\u3044\u5b9a\u7fa9\u6e08\u307f\u306ePod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96\u30ec\u30d9\u30eb\u306e\u3044\u305a\u308c\u304b\u3092\u9069\u7528\u3059\u308b\u305f\u3081\u306b\u8a2d\u5b9a\u3067\u304d\u308b{{< glossary_tooltip term_id=\"label\" text=\"\u30e9\u30d9\u30eb\" >}}\u306e\u30bb\u30c3\u30c8\u3092\u7528\u610f\u3057\u3066\u3044\u307e\u3059\u3002 \u9078\u629e\u3057\u305f\u30e9\u30d9\u30eb\u306f\u3001\u4ee5\u4e0b\u306e\u3088\u3046\u306b\u9055\u53cd\u306e\u53ef\u80fd\u6027\u304c\u691c\u51fa\u3055\u308c\u305f\u5834\u5408\u306b{{< glossary_tooltip text=\"\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\" term_id=\"control-plane\" >}}\u304c\u53d6\u308b\u30a2\u30af\u30b7\u30e7\u30f3\u3092\u5b9a\u7fa9\u3057\u307e\u3059\u3002 {{< table caption=\"Pod\u306e\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u306e\u30e2\u30fc\u30c9\" >}} \u30e2\u30fc\u30c9 | \u8aac\u660e :---------|:------------ **enforce** | \u30dd\u30ea\u30b7\u30fc\u306b\u9055\u53cd\u3057\u305f\u5834\u5408\u3001Pod\u306f\u62d2\u5426\u3055\u308c\u307e\u3059\u3002 **audit** | \u30dd\u30ea\u30b7\u30fc\u9055\u53cd\u306f\u3001[\u76e3\u67fb\u30ed\u30b0](/ja/docs/tasks/debug-application-cluster/audit/)\u306b\u8a18\u9332\u3055\u308c\u308b\u30a4\u30d9\u30f3\u30c8\u306b\u76e3\u67fb\u30a2\u30ce\u30c6\u30fc\u30b7\u30e7\u30f3\u3092\u8ffd\u52a0\u3059\u308b\u30c8\u30ea\u30ac\u30fc\u3068\u306a\u308a\u307e\u3059\u304c\u3001\u305d\u308c\u4ee5\u5916\u306f\u8a31\u53ef\u3055\u308c\u307e\u3059\u3002 **warn** | \u30dd\u30ea\u30b7\u30fc\u306b\u9055\u53cd\u3057\u305f\u5834\u5408\u306f\u3001\u30e6\u30fc\u30b6\u30fc\u3078\u306e\u8b66\u544a\u304c\u30c8\u30ea\u30ac\u30fc\u3055\u308c\u307e\u3059\u304c\u3001\u305d\u308c\u4ee5\u5916\u306f\u8a31\u53ef\u3055\u308c\u307e\u3059\u3002 {{< /table >}} \u540d\u524d\u7a7a\u9593\u306f\u3001\u4efb\u610f\u306e\u307e\u305f\u306f\u3059\u3079\u3066\u306e\u30e2\u30fc\u30c9\u3092\u8a2d\u5b9a\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u3001\u7570\u306a\u308b\u30e2\u30fc\u30c9\u306b\u5bfe\u3057\u3066\u7570\u306a\u308b\u30ec\u30d9\u30eb\u3092\u8a2d\u5b9a\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002 \u5404\u30e2\u30fc\u30c9\u306b\u306f\u3001\u4f7f\u7528\u3059\u308b\u30dd\u30ea\u30b7\u30fc\u3092\u6c7a\u5b9a\u3059\u308b2\u3064\u306e\u30e9\u30d9\u30eb\u304c\u3042\u308a\u307e\u3059\u3002 ```yaml # \u30e2\u30fc\u30c9\u3054\u3068\u306e\u30ec\u30d9\u30eb\u30e9\u30d9\u30eb\u306f\u3001\u305d\u306e\u30e2\u30fc\u30c9\u306b\u9069\u7528\u3059\u308b\u30dd\u30ea\u30b7\u30fc\u30ec\u30d9\u30eb\u3092\u793a\u3059\u3002 # # MODE\u306f`enforce`\u3001`audit`\u3001`warn`\u306e\u3044\u305a\u308c\u304b\u3067\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u3002 # LEVEL\u306f`privileged`\u3001`baseline`\u3001`restricted`\u306e\u3044\u305a\u308c\u304b\u3067\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u3002 pod-security.kubernetes.io/: # \u30aa\u30d7\u30b7\u30e7\u30f3: \u30e2\u30fc\u30c9\u3054\u3068\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u30e9\u30d9\u30eb\u306f\u3001Kubernetes\u306e\u30de\u30a4\u30ca\u30fc\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u540c\u68b1\u3055\u308c\u308b # \u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u30dd\u30ea\u30b7\u30fc\u3092\u56fa\u5b9a\u3059\u308b\u305f\u3081\u306b\u4f7f\u7528\u3067\u304d\u308b\uff08\u4f8b\u3048\u3070v{{< skew latestVersion >}}\u306a\u3069\uff09\u3002 # # MODE\u306f`enforce`\u3001`audit`\u3001`warn`\u306e\u3044\u305a\u308c\u304b\u3067\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u3002 # VERSION\u306f\u6709\u52b9\u306aKubernetes\u306e\u30de\u30a4\u30ca\u30fc\u30d0\u30fc\u30b8\u30e7\u30f3\u304b`latest`\u3067\u306a\u3051\u308c\u3070\u306a\u3089\u306a\u3044\u3002 pod-security.kubernetes.io/-version: ``` [\u540d\u524d\u7a7a\u9593\u30e9\u30d9\u30eb\u3067\u306ePod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96\u306e\u9069\u7528](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels)\u3067\u4f7f\u7528\u4f8b\u3092\u78ba\u8a8d\u3067\u304d\u307e\u3059\u3002 ## Workload\u306e\u30ea\u30bd\u30fc\u30b9\u3068Pod\u30c6\u30f3\u30d7\u30ec\u30fc\u30c8 {#workload-resources-and-pod-templates} Pod\u306f\u3001{{< glossary_tooltip term_id=\"deployment\" >}}\u3084{{< glossary_tooltip term_id=\"job\">}}\u306e\u3088\u3046\u306a[\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30aa\u30d6\u30b8\u30a7\u30af\u30c8](/ja/docs/concepts/workloads/controllers/)\u3092\u4f5c\u6210\u3059\u308b\u3053\u3068\u306b\u3088\u3063\u3066\u3001\u3057\u3070\u3057\u3070\u9593\u63a5\u7684\u306b\u751f\u6210\u3055\u308c\u307e\u3059\u3002 \u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306f_Pod template_\u3092\u5b9a\u7fa9\u3057\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9\u306e{{< glossary_tooltip term_id=\"controller\" text=\"\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\" >}}\u306f\u305d\u306e\u30c6\u30f3\u30d7\u30ec\u30fc\u30c8\u306b\u57fa\u3065\u304dPod\u3092\u4f5c\u6210\u3057\u307e\u3059\u3002 \u9055\u53cd\u306e\u65e9\u671f\u767a\u898b\u3092\u652f\u63f4\u3059\u308b\u305f\u3081\u306b\u3001audit\u30e2\u30fc\u30c9\u3068warning\u30e2\u30fc\u30c9\u306f\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9\u306b\u9069\u7528\u3055\u308c\u307e\u3059\u3002 \u305f\u3060\u3057\u3001enforce\u30e2\u30fc\u30c9\u306f\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9\u306b\u306f**\u9069\u7528\u3055\u308c\u305a**\u3001\u7d50\u679c\u3068\u3057\u3066\u306ePod\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306b\u306e\u307f\u9069\u7528\u3055\u308c\u307e\u3059\u3002 ## \u9069\u7528\u9664\u5916(Exemption) {#exemptions} Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u65bd\u884c\u304b\u3089 _exemptions_ \u3092\u5b9a\u7fa9\u3059\u308b\u3053\u3068\u3067\u3001\u7279\u5b9a\u306e\u540d\u524d\u7a7a\u9593\u306b\u95a2\u9023\u3059\u308b\u30dd\u30ea\u30b7\u30fc\u306e\u305f\u3081\u306b\u7981\u6b62\u3055\u308c\u3066\u3044\u305fPod\u306e\u4f5c\u6210\u3092\u8a31\u53ef\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 Exemption\u306f[\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306e\u8a2d\u5b9a](/docs/tasks/configure-pod-container/enforce-standards-admission-controller/#configure-the-admission-controller)\u3067\u9759\u7684\u306b\u8a2d\u5b9a\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 Exemption\u306f\u660e\u793a\u7684\u306b\u5217\u6319\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 Exemption\u3092\u6e80\u305f\u3057\u305f\u30ea\u30af\u30a8\u30b9\u30c8\u306f\u3001\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306b\u3088\u3063\u3066 _\u7121\u8996_ \u3055\u308c\u307e\u3059(`enforce`\u3001`audit`\u3001`warn`\u306e\u3059\u3079\u3066\u306e\u52d5\u4f5c\u304c\u30b9\u30ad\u30c3\u30d7\u3055\u308c\u307e\u3059)\u3002Exemption\u306e\u6b21\u5143\u306f\u4ee5\u4e0b\u306e\u901a\u308a\u3067\u3059\u3002 - **Usernames:** \u8a8d\u8a3c\u3055\u308c\u3066\u3044\u306a\u3044(\u3042\u308b\u3044\u306f\u507d\u88c5\u3055\u308c\u305f)\u30e6\u30fc\u30b6\u30fc\u540d\u3092\u6301\u3064\u30e6\u30fc\u30b6\u30fc\u304b\u3089\u306e\u8981\u6c42\u306f\u7121\u8996\u3055\u308c\u307e\u3059\u3002 - **RuntimeClassNames:** Pod\u3068[\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9](#workload-resources-and-pod-templates)\u3067\u6307\u5b9a\u3055\u308c\u305f\u9664\u5916\u30e9\u30f3\u30bf\u30a4\u30e0\u30af\u30e9\u30b9\u540d\u306f\u3001\u7121\u8996\u3055\u308c\u307e\u3059\u3002 - **Namespaces:** \u9664\u5916\u3055\u308c\u305f\u540d\u524d\u7a7a\u9593\u306ePod\u3068[\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9](#workload-resources-and-pod-templates)\u306f\u3001\u7121\u8996\u3055\u308c\u307e\u3059\u3002 {{< caution >}} \u307b\u3068\u3093\u3069\u306ePod\u306f\u3001[\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9](#workload-resources-and-pod-templates)\u306b\u5bfe\u5fdc\u3057\u3066\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u304c\u4f5c\u6210\u3057\u307e\u3059\u3002\u3064\u307e\u308a\u3001\u30a8\u30f3\u30c9\u30e6\u30fc\u30b6\u30fc\u3092\u9069\u7528\u9664\u5916\u306b\u3059\u308b\u306e\u306fPod\u3092\u76f4\u63a5\u4f5c\u6210\u3059\u308b\u5834\u5408\u306e\u307f\u3067\u3001\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9\u3092\u4f5c\u6210\u3059\u308b\u5834\u5408\u306f\u9069\u7528\u9664\u5916\u306b\u306a\u308a\u307e\u305b\u3093\u3002 \u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u30b5\u30fc\u30d3\u30b9\u30a2\u30ab\u30a6\u30f3\u30c8(`system:serviceaccount:kube-system:replicaset-controller`\u306a\u3069)\u306f\u901a\u5e38\u3001\u9664\u5916\u3057\u3066\u306f\u3044\u3051\u307e\u305b\u3093\u3002\u305d\u3046\u3057\u305f\u5834\u5408\u3001\u5bfe\u5fdc\u3059\u308b\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u30ea\u30bd\u30fc\u30b9\u3092\u4f5c\u6210\u3067\u304d\u308b\u3059\u3079\u3066\u306e\u30e6\u30fc\u30b6\u30fc\u3092\u6697\u9ed9\u7684\u306b\u9664\u5916\u3057\u3066\u3057\u307e\u3046\u305f\u3081\u3067\u3059\u3002 {{< /caution >}} \u4ee5\u4e0b\u306ePod\u30d5\u30a3\u30fc\u30eb\u30c9\u306b\u5bfe\u3059\u308b\u66f4\u65b0\u306f\u3001\u30dd\u30ea\u30b7\u30fc\u30c1\u30a7\u30c3\u30af\u306e\u5bfe\u8c61\u5916\u3068\u306a\u308a\u307e\u3059\u3002\u3064\u307e\u308a\u3001Pod\u306e\u66f4\u65b0\u8981\u6c42\u304c\u3053\u308c\u3089\u306e\u30d5\u30a3\u30fc\u30eb\u30c9\u3092\u5909\u66f4\u3059\u308b\u3060\u3051\u3067\u3042\u308c\u3070\u3001Pod\u304c\u73fe\u5728\u306e\u30dd\u30ea\u30b7\u30fc\u30ec\u30d9\u30eb\u306b\u9055\u53cd\u3057\u3066\u3044\u3066\u3082\u62d2\u5426\u3055\u308c\u308b\u3053\u3068\u306f\u3042\u308a\u307e\u305b\u3093\u3002 - \u3059\u3079\u3066\u306e\u30e1\u30bf\u30c7\u30fc\u30bf\u306e\u66f4\u65b0(seccomp\u307e\u305f\u306fAppArmor\u30a2\u30ce\u30c6\u30fc\u30b7\u30e7\u30f3\u3078\u306e\u5909\u66f4\u3092**\u9664\u304f**) - `seccomp.security.alpha.kubernetes.io/pod`(\u975e\u63a8\u5968) - `container.seccomp.security.alpha.kubernetes.io/*`(\u975e\u63a8\u5968) - `container.apparmor.security.beta.kubernetes.io/*` - `.spec.activeDeadlineSeconds`\u306b\u5bfe\u3059\u308b\u6709\u52b9\u306a\u66f4\u65b0 - `.spec.tolerations`\u306b\u5bfe\u3059\u308b\u6709\u52b9\u306a\u66f4\u65b0 ## {{% heading \"whatsnext\" %}} - [Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96](/ja/docs/concepts/security/pod-security-standards) - [Pod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96\u306e\u9069\u7528](/docs/setup/best-practices/enforcing-pod-security-standards) - [\u30d3\u30eb\u30c8\u30a4\u30f3\u306e\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306e\u8a2d\u5b9a\u306b\u3088\u308bPod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96\u306e\u9069\u7528](/docs/tasks/configure-pod-container/enforce-standards-admission-controller) - [\u540d\u524d\u7a7a\u9593\u30e9\u30d9\u30eb\u3067\u306ePod\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u306e\u6a19\u6e96\u306e\u9069\u7528](/docs/tasks/configure-pod-container/enforce-standards-namespace-labels) - [PodSecurityPolicy\u304b\u3089\u30d3\u30eb\u30c8\u30a4\u30f3\u306ePodSecurity\u30a2\u30c9\u30df\u30c3\u30b7\u30e7\u30f3\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u3078\u306e\u79fb\u884c](/docs/tasks/configure-pod-container/migrate-from-psp) ", "commid": "website_pr_32581"}], "negative_passages": []} {"query_id": "q-en-website-48fb8579b5eeb3d432876b518e800e05e460a8f095c1bbaad7728e78677802ec", "query": "Update , job-tracking-with-finalizers section, as k/k PR is disabling by default due to an unresolved bug.\nSpecifically the note () says that \"it is enabled by default.\"\nthis feature is currently enabled by default in v1.23 and will be disabled in v1.24, right?\n/sig apps /language en\nI also proposed to disable it by default in 1.23 , but the release managers haven't approved it yet.\n/triage accepted /sig apps\n/assign\nThanks", "positive_passages": [{"docid": "doc-en-website-ed435159e984e239b1090da350b118463cbb986d53cbc69f0c3e4e5a8b7cccf4", "text": "[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) on the [API server](/docs/reference/command-line-tools-reference/kube-apiserver/) and the [controller manager](/docs/reference/command-line-tools-reference/kube-controller-manager/). It is enabled by default. When enabled, the control plane tracks new Jobs using the behavior described below. Jobs created before the feature was enabled are unaffected. As a user,", "commid": "website_pr_34397"}], "negative_passages": []} {"query_id": "q-en-website-a7fe5888cd3e3303489db159dbc5df31a25401fab65a27b34caca25634b4f8f1", "query": "This is a Bug Report **\u4f5c\u8005\uff1a** Ricardo Katz (VMware), James Strong (Chainguard) [Ingress](/zh-cn/docs/concepts/services-networking/ingress/) \u53ef\u80fd\u662f Kubernetes \u6700\u5bb9\u6613\u53d7\u653b\u51fb\u7684\u7ec4\u4ef6\u4e4b\u4e00\u3002 Ingress \u901a\u5e38\u5b9a\u4e49\u4e00\u4e2a HTTP \u53cd\u5411\u4ee3\u7406\uff0c\u66b4\u9732\u5728\u4e92\u8054\u7f51\u4e0a\uff0c\u5305\u542b\u591a\u4e2a\u7f51\u7ad9\uff0c\u5e76\u5177\u6709\u5bf9 Kubernetes API \u7684\u4e00\u4e9b\u7279\u6743\u8bbf\u95ee\uff08\u4f8b\u5982\u8bfb\u53d6\u4e0e TLS \u8bc1\u4e66\u53ca\u5176\u79c1\u94a5\u76f8\u5173\u7684 Secret\uff09\u3002 \u867d\u7136\u5b83\u662f\u67b6\u6784\u4e2d\u7684\u4e00\u4e2a\u98ce\u9669\u7ec4\u4ef6\uff0c\u4f46\u5b83\u4ecd\u7136\u662f\u6b63\u5e38\u516c\u5f00\u670d\u52a1\u7684\u6700\u6d41\u884c\u65b9\u5f0f\u3002 Ingress-NGINX \u4e00\u76f4\u662f\u5b89\u5168\u8bc4\u4f30\u7684\u91cd\u5934\u620f\uff0c\u8fd9\u7c7b\u8bc4\u4f30\u4f1a\u53d1\u73b0\u6211\u4eec\u6709\u7740\u5f88\u5927\u7684\u95ee\u9898\uff1a \u5728\u5c06\u914d\u7f6e\u8f6c\u6362\u4e3a `nginx.conf` \u6587\u4ef6\u4e4b\u524d\uff0c\u6211\u4eec\u6ca1\u6709\u8fdb\u884c\u6240\u6709\u9002\u5f53\u7684\u6e05\u7406\uff0c\u8fd9\u53ef\u80fd\u4f1a\u5bfc\u81f4\u4fe1\u606f\u6cc4\u9732\u98ce\u9669\u3002 \u867d\u7136\u6211\u4eec\u4e86\u89e3\u6b64\u98ce\u9669\u4ee5\u53ca\u89e3\u51b3\u6b64\u95ee\u9898\u7684\u771f\u6b63\u9700\u6c42\uff0c\u4f46\u8fd9\u5e76\u4e0d\u662f\u4e00\u4e2a\u5bb9\u6613\u7684\u8fc7\u7a0b\uff0c \u56e0\u6b64\u6211\u4eec\u5728\u5f53\u524d(v1.2.0)\u7248\u672c\u4e2d\u91c7\u53d6\u4e86\u53e6\u4e00\u79cd\u65b9\u6cd5\u6765\u51cf\u5c11\uff08\u4f46\u4e0d\u662f\u6d88\u9664\uff01\uff09\u8fd9\u79cd\u98ce\u9669\u3002 ## \u4e86\u89e3 Ingress NGINX v1.2.0 \u548c chrooted NGINX \u8fdb\u7a0b \u4e3b\u8981\u6311\u6218\u4e4b\u4e00\u662f Ingress-NGINX \u8fd0\u884c\u7740 Web \u4ee3\u7406\u670d\u52a1\u5668\uff08NGINX\uff09\uff0c\u5e76\u4e0e Ingress \u63a7\u5236\u5668\u4e00\u8d77\u8fd0\u884c \uff08\u540e\u8005\u662f\u4e00\u4e2a\u53ef\u4ee5\u8bbf\u95ee Kubernetes API \u5e76\u521b\u5efa `nginx.conf` \u7684\u7ec4\u4ef6\uff09\u3002 \u56e0\u6b64\uff0cNGINX \u5bf9\u63a7\u5236\u5668\u7684\u6587\u4ef6\u7cfb\u7edf\uff08\u548c Kubernetes \u670d\u52a1\u5e10\u6237\u4ee4\u724c\uff0c\u4ee5\u53ca\u5bb9\u5668\u4e2d\u7684\u5176\u4ed6\u914d\u7f6e\uff09\u5177\u6709\u76f8\u540c\u7684\u8bbf\u95ee\u6743\u9650\u3002 \u867d\u7136\u62c6\u5206\u8fd9\u4e9b\u7ec4\u4ef6\u662f\u6211\u4eec\u7684\u6700\u7ec8\u76ee\u6807\uff0c\u4f46\u8be5\u9879\u76ee\u9700\u8981\u5feb\u901f\u54cd\u5e94\uff1b\u8fd9\u8ba9\u6211\u4eec\u60f3\u5230\u4e86\u4f7f\u7528 `chroot()`\u3002 \u8ba9\u6211\u4eec\u770b\u4e00\u4e0b Ingress-NGINX \u5bb9\u5668\u5728\u6b64\u66f4\u6539\u4e4b\u524d\u7684\u6837\u5b50\uff1a ![Ingress NGINX pre chroot](ingress-pre-chroot.png) \u6b63\u5982\u6211\u4eec\u6240\u89c1\uff0c\u7528\u6765\u63d0\u4f9b HTTP Proxy \u7684\u5bb9\u5668\uff08\u4e0d\u662f Pod\uff0c\u662f\u5bb9\u5668\uff01\uff09\u4e5f\u662f\u662f\u76d1\u89c6 Ingress \u5bf9\u8c61\u5e76\u5c06\u6570\u636e\u5199\u5165\u5bb9\u5668\u5377\u7684\u5bb9\u5668\u3002 \u73b0\u5728\uff0c\u89c1\u8bc6\u4e00\u4e0b\u65b0\u67b6\u6784\uff1a ![Ingress NGINX post chroot](ingress-post-chroot.png) \u8fd9\u4e00\u5207\u610f\u5473\u7740\u4ec0\u4e48\uff1f\u4e00\u4e2a\u57fa\u672c\u7684\u603b\u7ed3\u662f\uff1a\u6211\u4eec\u5c06 NGINX \u670d\u52a1\u9694\u79bb\u4e3a\u63a7\u5236\u5668\u5bb9\u5668\u5185\u7684\u5bb9\u5668\u3002 \u867d\u7136\u8fd9\u5e76\u4e0d\u5b8c\u5168\u6b63\u786e\uff0c\u4f46\u8981\u4e86\u89e3\u8fd9\u91cc\u6240\u505a\u7684\u4e8b\u60c5\uff0c\u6700\u597d\u4e86\u89e3 Linux \u5bb9\u5668\uff08\u4ee5\u53ca\u5185\u6838\u547d\u540d\u7a7a\u95f4\u7b49\u5e95\u5c42\u673a\u5236\uff09\u662f\u5982\u4f55\u5de5\u4f5c\u7684\u3002 \u4f60\u53ef\u4ee5\u5728 Kubernetes \u8bcd\u6c47\u8868\u4e2d\u9605\u8bfb\u6709\u5173 cgroup \u7684\u4fe1\u606f\uff1a[`cgroup`](/zh-cn/docs/reference/glossary/?fundamental=true#term-cgroup)\uff0c \u5e76\u5728 NGINX \u9879\u76ee\u6587\u7ae0[\u4ec0\u4e48\u662f\u547d\u540d\u7a7a\u95f4\u548c cgroup\uff0c\u4ee5\u53ca\u5b83\u4eec\u5982\u4f55\u5de5\u4f5c\uff1f](https://www.nginx.com/blog/what-are-namespaces-cgroups-how-do-they-work/) \u4e2d\u4e86\u89e3\u6709\u5173 cgroup \u4e0e\u547d\u540d\u7a7a\u95f4\u4ea4\u4e92\u7684\u66f4\u591a\u4fe1\u606f\u3002\uff08\u5f53\u4f60\u9605\u8bfb\u65f6\uff0c\u8bf7\u8bb0\u4f4f Linux \u5185\u6838\u547d\u540d\u7a7a\u95f4\u4e0e [Kubernetes \u547d\u540d\u7a7a\u95f4](/zh-cn/docs/concepts/overview/working-with-objects/namespaces/)\u4e0d\u540c\uff09\u3002 ## \u8df3\u8fc7\u8c08\u8bdd\uff0c\u6211\u9700\u8981\u4ec0\u4e48\u624d\u80fd\u4f7f\u7528\u8fd9\u79cd\u65b0\u65b9\u6cd5\uff1f \u867d\u7136\u8fd9\u589e\u52a0\u4e86\u5b89\u5168\u6027\uff0c\u4f46\u6211\u4eec\u5728\u8fd9\u4e2a\u7248\u672c\u4e2d\u628a\u8fd9\u4e2a\u529f\u80fd\u4f5c\u4e3a\u4e00\u4e2a\u9009\u9879\uff0c\u8fd9\u6837\u4f60\u5c31\u53ef\u4ee5\u6709\u65f6\u95f4\u5728\u4f60\u7684\u73af\u5883\u4e2d\u505a\u51fa\u6b63\u786e\u7684\u8c03\u6574\u3002 \u6b64\u65b0\u529f\u80fd\u4ec5\u5728 Ingress-NGINX \u63a7\u5236\u5668\u7684 v1.2.0 \u7248\u672c\u4e2d\u53ef\u7528\u3002 \u8981\u4f7f\u7528\u8fd9\u4e2a\u529f\u80fd\uff0c\u5728\u4f60\u7684\u90e8\u7f72\u4e2d\u6709\u4e24\u4e2a\u5fc5\u8981\u7684\u6539\u53d8\uff1a * \u5c06\u540e\u7f00 \"-chroot\" \u6dfb\u52a0\u5230\u5bb9\u5668\u955c\u50cf\u540d\u79f0\u4e2d\u3002\u4f8b\u5982\uff1a`gcr.io/k8s-staging-ingress-nginx/controller-chroot:v1.2.0` * \u5728\u4f60\u7684 Ingress \u63a7\u5236\u5668\u7684 Pod \u6a21\u677f\u4e2d\uff0c\u627e\u5230\u6dfb\u52a0 `NET_BIND_SERVICE` \u6743\u80fd\u7684\u4f4d\u7f6e\u5e76\u6dfb\u52a0 `SYS_CHROOT` \u6743\u80fd\u3002 \u7f16\u8f91\u6e05\u5355\u540e\uff0c\u4f60\u5c06\u770b\u5230\u5982\u4e0b\u4ee3\u7801\u6bb5\uff1a ```yaml capabilities: drop: - ALL add: - NET_BIND_SERVICE - SYS_CHROOT ``` \u5982\u679c\u4f60\u4f7f\u7528\u5b98\u65b9 Helm Chart \u90e8\u7f72\u63a7\u5236\u5668\uff0c\u5219\u5728 `values.yaml` \u4e2d\u66f4\u6539\u4ee5\u4e0b\u8bbe\u7f6e\uff1a ```yaml controller: image: chroot: true ``` Ingress \u63a7\u5236\u5668\u901a\u5e38\u90e8\u7f72\u5728\u96c6\u7fa4\u4f5c\u7528\u57df\uff08IngressClass API \u662f\u96c6\u7fa4\u4f5c\u7528\u57df\u7684\uff09\u3002 \u5982\u679c\u4f60\u7ba1\u7406 Ingress-NGINX \u63a7\u5236\u5668\u4f46\u4f60\u4e0d\u662f\u6574\u4e2a\u96c6\u7fa4\u7684\u64cd\u4f5c\u5458\uff0c \u8bf7\u5728\u90e8\u7f72\u4e2d\u542f\u7528\u5b83**\u4e4b\u524d**\u4e0e\u96c6\u7fa4\u7ba1\u7406\u5458\u786e\u8ba4\u4f60\u662f\u5426\u53ef\u4ee5\u4f7f\u7528 `SYS_CHROOT` \u529f\u80fd\u3002 ## \u597d\u5427\uff0c\u4f46\u8fd9\u5982\u4f55\u80fd\u63d0\u9ad8\u6211\u7684 Ingress \u63a7\u5236\u5668\u7684\u5b89\u5168\u6027\u5462\uff1f \u4ee5\u4e0b\u9762\u7684\u914d\u7f6e\u7247\u6bb5\u4e3a\u4f8b\uff0c\u60f3\u8c61\u4e00\u4e0b\uff0c\u7531\u4e8e\u67d0\u79cd\u539f\u56e0\uff0c\u5b83\u88ab\u6dfb\u52a0\u5230\u4f60\u7684 `nginx.conf` \u4e2d\uff1a ``` location /randomthing/ { alias /; autoindex on; } ``` \u5982\u679c\u4f60\u90e8\u7f72\u4e86\u8fd9\u79cd\u914d\u7f6e\uff0c\u6709\u4eba\u53ef\u4ee5\u8c03\u7528 `http://website.example/randomthing` \u5e76\u83b7\u53d6\u5bf9 Ingress \u63a7\u5236\u5668\u7684\u6574\u4e2a\u6587\u4ef6\u7cfb\u7edf\u7684\u4e00\u4e9b\u5217\u8868\uff08\u548c\u8bbf\u95ee\u6743\u9650\uff09\u3002 \u73b0\u5728\uff0c\u4f60\u80fd\u5728\u4e0b\u9762\u7684\u5217\u8868\u4e2d\u53d1\u73b0 chroot \u5904\u7406\u8fc7\u548c\u672a\u7ecf chroot \u5904\u7406\u8fc7\u7684 Nginx \u4e4b\u95f4\u7684\u533a\u522b\u5417\uff1f | \u4e0d\u989d\u5916\u8c03\u7528 `chroot()` | \u989d\u5916\u8c03\u7528 `chroot()` | |----------------------------|--------| | `bin` | `bin` | | `dev` | `dev` | | `etc` | `etc` | | `home` | | | `lib` | `lib` | | `media` | | | `mnt` | | | `opt` | `opt` | | `proc` | `proc` | | `root` | | | `run` | `run` | | `sbin` | | | `srv` | | | `sys` | | | `tmp` | `tmp` | | `usr` | `usr` | | `var` | `var` | | `dbg` | | | `nginx-ingress-controller` | | | `wait-shutdown` | | \u5de6\u4fa7\u7684\u90a3\u4e2a\u6ca1\u6709 chroot \u5904\u7406\u3002\u6240\u4ee5 NGINX \u53ef\u4ee5\u5b8c\u5168\u8bbf\u95ee\u6587\u4ef6\u7cfb\u7edf\u3002\u53f3\u4fa7\u7684\u90a3\u4e2a\u7ecf\u8fc7 chroot \u5904\u7406\uff0c \u56e0\u6b64\u521b\u5efa\u4e86\u4e00\u4e2a\u65b0\u6587\u4ef6\u7cfb\u7edf\uff0c\u5176\u4e2d\u53ea\u6709\u4f7f NGINX \u5de5\u4f5c\u6240\u9700\u7684\u6587\u4ef6\u3002 ## \u6b64\u7248\u672c\u4e2d\u7684\u5176\u4ed6\u5b89\u5168\u6539\u8fdb\u5982\u4f55\uff1f \u6211\u4eec\u77e5\u9053\u65b0\u7684 `chroot()` \u673a\u5236\u6709\u52a9\u4e8e\u89e3\u51b3\u90e8\u5206\u98ce\u9669\uff0c\u4f46\u4ecd\u7136\u6709\u4eba\u53ef\u4ee5\u5c1d\u8bd5\u6ce8\u5165\u547d\u4ee4\u6765\u8bfb\u53d6\uff0c\u4f8b\u5982 `nginx.conf` \u6587\u4ef6\u5e76\u63d0\u53d6\u654f\u611f\u4fe1\u606f\u3002 \u6240\u4ee5\uff0c\u8fd9\u4e2a\u7248\u672c\u7684\u53e6\u4e00\u4e2a\u53d8\u5316\uff08\u53ef\u9009\u62e9\u53d6\u6d88\uff09\u662f **\u6df1\u5ea6\u63a2\u6d4b\uff08Deep Inspector\uff09**\u3002 \u6211\u4eec\u77e5\u9053\u67d0\u4e9b\u6307\u4ee4\u6216\u6b63\u5219\u8868\u8fbe\u5f0f\u53ef\u80fd\u5bf9 NGINX \u9020\u6210\u5371\u9669\uff0c\u56e0\u6b64\u6df1\u5ea6\u63a2\u6d4b\u5668\u4f1a\u68c0\u67e5 Ingress \u5bf9\u8c61\u4e2d\u7684\u6240\u6709\u5b57\u6bb5 \uff08\u5728\u5176\u534f\u8c03\u671f\u95f4\uff0c\u5e76\u4e14\u8fd8\u4f7f\u7528[\u9a8c\u8bc1\u51c6\u5165 webhook](/zh-cn/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook)) \u9a8c\u8bc1\u662f\u5426\u6709\u4efb\u4f55\u5b57\u6bb5\u5305\u542b\u8fd9\u4e9b\u5371\u9669\u6307\u4ee4\u3002 Ingress \u63a7\u5236\u5668\u5df2\u7ecf\u901a\u8fc7\u6ce8\u89e3\u505a\u4e86\u8fd9\u4e2a\u5de5\u4f5c\uff0c\u6211\u4eec\u7684\u76ee\u6807\u662f\u628a\u73b0\u6709\u7684\u9a8c\u8bc1\u8f6c\u79fb\u5230\u6df1\u5ea6\u63a2\u6d4b\u4e2d\uff0c\u4f5c\u4e3a\u672a\u6765\u7248\u672c\u7684\u4e00\u90e8\u5206\u3002 \u4f60\u53ef\u4ee5\u5728 [https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go](https://github.com/kubernetes/ingress-nginx/blob/main/internal/ingress/inspector/rules.go) \u4e2d\u67e5\u770b\u73b0\u6709\u89c4\u5219\u3002 \u7531\u4e8e\u68c0\u67e5\u548c\u5339\u914d\u76f8\u5173 Ingress \u5bf9\u8c61\u4e2d\u7684\u6240\u6709\u5b57\u7b26\u4e32\u7684\u6027\u8d28\uff0c\u6b64\u65b0\u529f\u80fd\u53ef\u80fd\u4f1a\u6d88\u8017\u66f4\u591a CPU\u3002 \u4f60\u53ef\u4ee5\u901a\u8fc7\u4f7f\u7528\u547d\u4ee4\u884c\u53c2\u6570 `--deep-inspect=false` \u8fd0\u884c Ingress \u63a7\u5236\u5668\u6765\u7981\u7528\u5b83\u3002 ## \u4e0b\u4e00\u6b65\u662f\u4ec0\u4e48? \u8fd9\u4e0d\u662f\u6211\u4eec\u7684\u6700\u7ec8\u76ee\u6807\u3002\u6211\u4eec\u7684\u6700\u7ec8\u76ee\u6807\u662f\u62c6\u5206\u63a7\u5236\u5e73\u9762\u548c\u6570\u636e\u5e73\u9762\u8fdb\u7a0b\u3002 \u4e8b\u5b9e\u4e0a\uff0c\u8fd9\u6837\u505a\u4e5f\u5c06\u5e2e\u52a9\u6211\u4eec\u5b9e\u73b0 [Gateway](https://gateway-api.sigs.k8s.io/) API \u5b9e\u73b0\uff0c \u56e0\u4e3a\u4e00\u65e6\u5b83\u201c\u77e5\u9053\u201d\u8981\u63d0\u4f9b\u4ec0\u4e48\uff0c\u6211\u4eec\u53ef\u80fd\u4f1a\u6709\u4e0d\u540c\u7684\u63a7\u5236\u5668 \u6570\u636e\u5e73\u9762\uff08\u6211\u4eec\u9700\u8981\u4e00\u4e9b\u5e2e\u52a9\uff01\uff01\uff09 Kubernetes \u4e2d\u7684\u5176\u4ed6\u4e00\u4e9b\u9879\u76ee\u5df2\u7ecf\u91c7\u7528\u4e86\u8fd9\u79cd\u65b9\u6cd5\uff08\u5982 [KPNG](https://github.com/kubernetes-sigs/kpng)\uff0c \u5efa\u8bae\u66ff\u6362 `kube-proxy`\uff09\uff0c\u6211\u4eec\u8ba1\u5212\u4e0e\u4ed6\u4eec\u4fdd\u6301\u4e00\u81f4\uff0c\u5e76\u4e3a Ingress-NGINX \u83b7\u5f97\u76f8\u540c\u7684\u4f53\u9a8c\u3002 ## \u5ef6\u4f38\u9605\u8bfb \u5982\u679c\u4f60\u60f3\u4e86\u89e3\u5982\u4f55\u5728 Ingress NGINX \u4e2d\u5b8c\u6210 chrooting\uff0c\u8bf7\u67e5\u770b [https://github.com/kubernetes/ingress-nginx/pull/8337](https://github.com/kubernetes/ingress-nginx/pull/8337)\u3002 \u5305\u542b\u6240\u6709\u66f4\u6539\u7684\u7248\u672c v1.2.0 \u53ef\u4ee5\u5728\u4ee5\u4e0b\u4f4d\u7f6e\u627e\u5230 [https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0](https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.2.0) ", "commid": "website_pr_35526"}], "negative_passages": []} {"query_id": "q-en-website-89ec09a0ee7274de005227b6ef5aebfa2cab9d889b99eecbb002548242d2b6f6", "query": "This is a Feature Request \u64cd\u4f5c | \u8bed\u6cd5 | \u63cf\u8ff0 -------------------- | -------------------- | -------------------- `alpha` | `kubectl alpha SUBCOMMAND [flags]` | \u5217\u51fa\u4e0e alpha \u7279\u6027\u5bf9\u5e94\u7684\u53ef\u7528\u547d\u4ee4\uff0c\u8fd9\u4e9b\u7279\u6027\u5728 Kubernetes \u96c6\u7fa4\u4e2d\u9ed8\u8ba4\u60c5\u51b5\u4e0b\u662f\u4e0d\u542f\u7528\u7684\u3002 `annotate` | kubectl annotate (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags] | \u6dfb\u52a0\u6216\u66f4\u65b0\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u6ce8\u89e3\u3002 `api-resources` | `kubectl api-resources [flags]` | \u5217\u51fa\u53ef\u7528\u7684 API \u8d44\u6e90\u3002 `api-versions` | `kubectl api-versions [flags]` | \u5217\u51fa\u53ef\u7528\u7684 API \u7248\u672c\u3002 `apply` | `kubectl apply -f FILENAME [flags]`| \u4ece\u6587\u4ef6\u6216 stdin \u5bf9\u8d44\u6e90\u5e94\u7528\u914d\u7f6e\u66f4\u6539\u3002 `attach` | `kubectl attach POD -c CONTAINER [-i] [-t] [flags]` | \u6302\u63a5\u5230\u6b63\u5728\u8fd0\u884c\u7684\u5bb9\u5668\uff0c\u67e5\u770b\u8f93\u51fa\u6d41\u6216\u4e0e\u5bb9\u5668\uff08stdin\uff09\u4ea4\u4e92\u3002 `auth` | `kubectl auth [flags] [options]` | \u68c0\u67e5\u6388\u6743\u3002 `autoscale` | kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] [flags] | \u81ea\u52a8\u6269\u7f29\u7531\u526f\u672c\u63a7\u5236\u5668\u7ba1\u7406\u7684\u4e00\u7ec4 pod\u3002 `certificate` | `kubectl certificate SUBCOMMAND [options]` | \u4fee\u6539\u8bc1\u4e66\u8d44\u6e90\u3002 `cluster-info` | `kubectl cluster-info [flags]` | \u663e\u793a\u6709\u5173\u96c6\u7fa4\u4e2d\u4e3b\u670d\u52a1\u5668\u548c\u670d\u52a1\u7684\u7aef\u53e3\u4fe1\u606f\u3002 `completion` | `kubectl completion SHELL [options]` | \u4e3a\u6307\u5b9a\u7684 Shell\uff08Bash \u6216 Zsh\uff09\u8f93\u51fa Shell \u8865\u9f50\u4ee3\u7801\u3002 `config` | `kubectl config SUBCOMMAND [flags]` | \u4fee\u6539 kubeconfig \u6587\u4ef6\u3002\u6709\u5173\u8be6\u7ec6\u4fe1\u606f\uff0c\u8bf7\u53c2\u9605\u5404\u4e2a\u5b50\u547d\u4ee4\u3002 `convert` | `kubectl convert -f FILENAME [options]` | \u5728\u4e0d\u540c\u7684 API \u7248\u672c\u4e4b\u95f4\u8f6c\u6362\u914d\u7f6e\u6587\u4ef6\u3002\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u662f YAML \u6216 JSON \u683c\u5f0f\u3002\u6ce8\u610f - \u9700\u8981\u5b89\u88c5 `kubectl-convert` \u63d2\u4ef6\u3002 `cordon` | `kubectl cordon NODE [options]` | \u5c06\u8282\u70b9\u6807\u8bb0\u4e3a\u4e0d\u53ef\u8c03\u5ea6\u3002 `cp` | `kubectl cp [options]` | \u4ece\u5bb9\u5668\u590d\u5236\u6587\u4ef6\u3001\u76ee\u5f55\u6216\u5c06\u6587\u4ef6\u3001\u76ee\u5f55\u590d\u5236\u5230\u5bb9\u5668\u3002 `create` | `kubectl create -f FILENAME [flags]` | \u4ece\u6587\u4ef6\u6216 stdin \u521b\u5efa\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u3002 `delete` | kubectl delete (-f FILENAME | TYPE [NAME | /NAME | -l label | --all]) [flags] | \u57fa\u4e8e\u6587\u4ef6\u3001\u6807\u51c6\u8f93\u5165\u6216\u901a\u8fc7\u6307\u5b9a\u6807\u7b7e\u9009\u62e9\u5668\u3001\u540d\u79f0\u3001\u8d44\u6e90\u9009\u62e9\u5668\u6216\u8d44\u6e90\u672c\u8eab\uff0c\u5220\u9664\u8d44\u6e90\u3002 `describe` | kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | /NAME | -l label]) [flags] | \u663e\u793a\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u8be6\u7ec6\u72b6\u6001\u3002 `diff` | `kubectl diff -f FILENAME [flags]`| \u5728\u5f53\u524d\u8d77\u4f5c\u7528\u7684\u914d\u7f6e\u548c\u6587\u4ef6\u6216\u6807\u51c6\u8f93\u4e4b\u95f4\u4f5c\u5bf9\u6bd4 (**BETA**) `drain` | `kubectl drain NODE [options]` | \u817e\u7a7a\u8282\u70b9\u4ee5\u51c6\u5907\u7ef4\u62a4\u3002 `edit` | kubectl edit (-f FILENAME | TYPE NAME | TYPE/NAME) [flags] | \u4f7f\u7528\u9ed8\u8ba4\u7f16\u8f91\u5668\u7f16\u8f91\u548c\u66f4\u65b0\u670d\u52a1\u5668\u4e0a\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u5b9a\u4e49\u3002 `exec` | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | \u5bf9 Pod \u4e2d\u7684\u5bb9\u5668\u6267\u884c\u547d\u4ee4\u3002 `explain` | `kubectl explain [--recursive=false] [flags]` | \u83b7\u53d6\u591a\u79cd\u8d44\u6e90\u7684\u6587\u6863\u3002\u4f8b\u5982 Pod\u3001Node\u3001Service \u7b49\u3002 `expose` | kubectl expose (-f FILENAME | TYPE NAME | TYPE/NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags] | \u5c06\u526f\u672c\u63a7\u5236\u5668\u3001\u670d\u52a1\u6216 Pod \u4f5c\u4e3a\u65b0\u7684 Kubernetes \u670d\u52a1\u66b4\u9732\u3002 `get` | kubectl get (-f FILENAME | TYPE [NAME | /NAME | -l label]) [--watch] [--sort-by=FIELD] [[-o | --output]=OUTPUT_FORMAT] [flags] | \u5217\u51fa\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u3002 `kustomize` | kubectl kustomize [flags] [options]` | \u5217\u51fa\u4ece kustomization.yaml \u6587\u4ef6\u4e2d\u7684\u6307\u4ee4\u751f\u6210\u7684\u4e00\u7ec4 API \u8d44\u6e90\u3002\u53c2\u6570\u5fc5\u987b\u662f\u5305\u542b\u6587\u4ef6\u7684\u76ee\u5f55\u7684\u8def\u5f84\uff0c\u6216\u8005\u662f git \u5b58\u50a8\u5e93 URL\uff0c\u5176\u8def\u5f84\u540e\u7f00\u76f8\u5bf9\u4e8e\u5b58\u50a8\u5e93\u6839\u76ee\u5f55\u6307\u5b9a\u4e86\u76f8\u540c\u7684\u8def\u5f84\u3002 \u64cd\u4f5c | \u8bed\u6cd5 | \u63cf\u8ff0 -------------------- | -------------------- | -------------------- `alpha` | `kubectl alpha SUBCOMMAND [flags]` | \u5217\u51fa\u4e0e alpha \u7279\u6027\u5bf9\u5e94\u7684\u53ef\u7528\u547d\u4ee4\uff0c\u8fd9\u4e9b\u7279\u6027\u5728 Kubernetes \u96c6\u7fa4\u4e2d\u9ed8\u8ba4\u60c5\u51b5\u4e0b\u662f\u4e0d\u542f\u7528\u7684\u3002 `annotate` | kubectl annotate (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags] | \u6dfb\u52a0\u6216\u66f4\u65b0\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u6ce8\u89e3\u3002 `api-resources` | `kubectl api-resources [flags]` | \u5217\u51fa\u53ef\u7528\u7684 API \u8d44\u6e90\u3002 `api-versions` | `kubectl api-versions [flags]` | \u5217\u51fa\u53ef\u7528\u7684 API \u7248\u672c\u3002 `apply` | `kubectl apply -f FILENAME [flags]`| \u4ece\u6587\u4ef6\u6216 stdin \u5bf9\u8d44\u6e90\u5e94\u7528\u914d\u7f6e\u66f4\u6539\u3002 `attach` | `kubectl attach POD -c CONTAINER [-i] [-t] [flags]` | \u6302\u63a5\u5230\u6b63\u5728\u8fd0\u884c\u7684\u5bb9\u5668\uff0c\u67e5\u770b\u8f93\u51fa\u6d41\u6216\u4e0e\u5bb9\u5668\uff08stdin\uff09\u4ea4\u4e92\u3002 `auth` | `kubectl auth [flags] [options]` | \u68c0\u67e5\u6388\u6743\u3002 `autoscale` | kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU] [flags] | \u81ea\u52a8\u6269\u7f29\u7531\u526f\u672c\u63a7\u5236\u5668\u7ba1\u7406\u7684\u4e00\u7ec4 pod\u3002 `certificate` | `kubectl certificate SUBCOMMAND [options]` | \u4fee\u6539\u8bc1\u4e66\u8d44\u6e90\u3002 `cluster-info` | `kubectl cluster-info [flags]` | \u663e\u793a\u6709\u5173\u96c6\u7fa4\u4e2d\u4e3b\u670d\u52a1\u5668\u548c\u670d\u52a1\u7684\u7aef\u53e3\u4fe1\u606f\u3002 `completion` | `kubectl completion SHELL [options]` | \u4e3a\u6307\u5b9a\u7684 Shell\uff08Bash \u6216 Zsh\uff09\u8f93\u51fa Shell \u8865\u9f50\u4ee3\u7801\u3002 `config` | `kubectl config SUBCOMMAND [flags]` | \u4fee\u6539 kubeconfig \u6587\u4ef6\u3002\u6709\u5173\u8be6\u7ec6\u4fe1\u606f\uff0c\u8bf7\u53c2\u9605\u5404\u4e2a\u5b50\u547d\u4ee4\u3002 `convert` | `kubectl convert -f FILENAME [options]` | \u5728\u4e0d\u540c\u7684 API \u7248\u672c\u4e4b\u95f4\u8f6c\u6362\u914d\u7f6e\u6587\u4ef6\u3002\u914d\u7f6e\u6587\u4ef6\u53ef\u4ee5\u662f YAML \u6216 JSON \u683c\u5f0f\u3002\u6ce8\u610f - \u9700\u8981\u5b89\u88c5 `kubectl-convert` \u63d2\u4ef6\u3002 `cordon` | `kubectl cordon NODE [options]` | \u5c06\u8282\u70b9\u6807\u8bb0\u4e3a\u4e0d\u53ef\u8c03\u5ea6\u3002 `cp` | `kubectl cp [options]` | \u4ece\u5bb9\u5668\u590d\u5236\u6587\u4ef6\u3001\u76ee\u5f55\u6216\u5c06\u6587\u4ef6\u3001\u76ee\u5f55\u590d\u5236\u5230\u5bb9\u5668\u3002 `create` | `kubectl create -f FILENAME [flags]` | \u4ece\u6587\u4ef6\u6216 stdin \u521b\u5efa\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u3002 `delete` | kubectl delete (-f FILENAME | TYPE [NAME | /NAME | -l label | --all]) [flags] | \u57fa\u4e8e\u6587\u4ef6\u3001\u6807\u51c6\u8f93\u5165\u6216\u901a\u8fc7\u6307\u5b9a\u6807\u7b7e\u9009\u62e9\u5668\u3001\u540d\u79f0\u3001\u8d44\u6e90\u9009\u62e9\u5668\u6216\u8d44\u6e90\u672c\u8eab\uff0c\u5220\u9664\u8d44\u6e90\u3002 `describe` | kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | /NAME | -l label]) [flags] | \u663e\u793a\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u8be6\u7ec6\u72b6\u6001\u3002 `diff` | `kubectl diff -f FILENAME [flags]`| \u5728\u5f53\u524d\u8d77\u4f5c\u7528\u7684\u914d\u7f6e\u548c\u6587\u4ef6\u6216\u6807\u51c6\u8f93\u4e4b\u95f4\u4f5c\u5bf9\u6bd4 (**BETA**) `drain` | `kubectl drain NODE [options]` | \u817e\u7a7a\u8282\u70b9\u4ee5\u51c6\u5907\u7ef4\u62a4\u3002 `edit` | kubectl edit (-f FILENAME | TYPE NAME | TYPE/NAME) [flags] | \u4f7f\u7528\u9ed8\u8ba4\u7f16\u8f91\u5668\u7f16\u8f91\u548c\u66f4\u65b0\u670d\u52a1\u5668\u4e0a\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u5b9a\u4e49\u3002 `exec` | `kubectl exec POD [-c CONTAINER] [-i] [-t] [flags] [-- COMMAND [args...]]` | \u5bf9 Pod \u4e2d\u7684\u5bb9\u5668\u6267\u884c\u547d\u4ee4\u3002 `explain` | `kubectl explain [--recursive=false] [flags]` | \u83b7\u53d6\u591a\u79cd\u8d44\u6e90\u7684\u6587\u6863\u3002\u4f8b\u5982 Pod\u3001Node\u3001Service \u7b49\u3002 `expose` | kubectl expose (-f FILENAME | TYPE NAME | TYPE/NAME) [--port=port] [--protocol=TCP|UDP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type] [flags] | \u5c06\u526f\u672c\u63a7\u5236\u5668\u3001\u670d\u52a1\u6216 Pod \u4f5c\u4e3a\u65b0\u7684 Kubernetes \u670d\u52a1\u66b4\u9732\u3002 `get` | kubectl get (-f FILENAME | TYPE [NAME | /NAME | -l label]) [--watch] [--sort-by=FIELD] [[-o | --output]=OUTPUT_FORMAT] [flags] | \u5217\u51fa\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u3002 `kustomize` | kubectl kustomize [flags] [options]` | \u5217\u51fa\u4ece kustomization.yaml \u6587\u4ef6\u4e2d\u7684\u6307\u4ee4\u751f\u6210\u7684\u4e00\u7ec4 API \u8d44\u6e90\u3002\u53c2\u6570\u5fc5\u987b\u662f\u5305\u542b\u6587\u4ef6\u7684\u76ee\u5f55\u7684\u8def\u5f84\uff0c\u6216\u8005\u662f git \u5b58\u50a8\u5e93 URL\uff0c\u5176\u8def\u5f84\u540e\u7f00\u76f8\u5bf9\u4e8e\u5b58\u50a8\u5e93\u6839\u76ee\u5f55\u6307\u5b9a\u4e86\u76f8\u540c\u7684\u8def\u5f84\u3002 `label` | kubectl label (-f FILENAME | TYPE NAME | TYPE/NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--overwrite] [--all] [--resource-version=version] [flags] | \u6dfb\u52a0\u6216\u66f4\u65b0\u4e00\u4e2a\u6216\u591a\u4e2a\u8d44\u6e90\u7684\u6807\u7b7e\u3002 `logs` | `kubectl logs POD [-c CONTAINER] [--follow] [flags]` | \u6253\u5370 Pod \u4e2d\u5bb9\u5668\u7684\u65e5\u5fd7\u3002 `options` | `kubectl options` | \u5168\u5c40\u547d\u4ee4\u884c\u9009\u9879\u5217\u8868\uff0c\u8fd9\u4e9b\u9009\u9879\u9002\u7528\u4e8e\u6240\u6709\u547d\u4ee4\u3002", "commid": "website_pr_35728"}], "negative_passages": []} {"query_id": "q-en-website-47741c81ffa1b144414db9041a2621bf5c0692295fcc5902a783a1c3a2c89f9d", "query": "web\n/retitle [zh-cn] Fix table formatting errors on the kubectl page\n/triage accepted", "positive_passages": [{"docid": "doc-en-website-3d2a780dce1ecb1dfb97b7f31702eed120cb739ef4929708b5925f1855055b6d", "text": "`replace` | `kubectl replace -f FILENAME` | \u57fa\u4e8e\u6587\u4ef6\u6216\u6807\u51c6\u8f93\u5165\u66ff\u6362\u8d44\u6e90\u3002 `rollout` | `kubectl rollout SUBCOMMAND [options]` | \u7ba1\u7406\u8d44\u6e90\u7684\u4e0a\u7ebf\u3002\u6709\u6548\u7684\u8d44\u6e90\u7c7b\u578b\u5305\u62ec\uff1aDeployment\u3001 DaemonSet \u548c StatefulSet\u3002 `run` | kubectl run NAME --image=image [--env=\"key=value\"] [--port=port] [--dry-run=server | client | none] [--overrides=inline-json] [flags] | \u5728\u96c6\u7fa4\u4e0a\u8fd0\u884c\u6307\u5b9a\u7684\u955c\u50cf\u3002 `scale` | kubectl scale (-f FILENAME | TYPE NAME | TYPE/NAME) --replicas=COUNT [--resource-version=version] [--current-replicas=count] [flags] | \u66f4\u65b0\u6307\u5b9a\u526f\u672c\u63a7\u5236\u5668\u7684\u5927\u5c0f\u3002 `set` | `kubectl set SUBCOMMAND [options]` | \u914d\u7f6e\u5e94\u7528\u8d44\u6e90\u3002 `taint` | `kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N [options]` | \u66f4\u65b0\u4e00\u4e2a\u6216\u591a\u4e2a\u8282\u70b9\u4e0a\u7684\u6c61\u70b9\u3002", "commid": "website_pr_35728"}], "negative_passages": []} {"query_id": "q-en-website-aa94bbae7c17b3209db89fa80124d07bf7ae2c7befec859a57eb802e00c3789b", "query": "This is a Bug Report \u0935\u0930\u094d\u0915\u0932\u094b\u0921 \u0911\u092c\u094d\u091c\u0947\u0915\u094d\u091f\u094d\u0938, \u091c\u0948\u0938\u0947 {{< glossary_tooltip text=\"\u0921\u093f\u092a\u094d\u0932\u0949\u092f\u092e\u0947\u0902\u091f\" term_id=\"deployment\" >}}, \u0930\u0947\u092a\u094d\u0932\u093f\u0915\u093e\u0938\u0947\u091f\u094d\u0938 \u0915\u0947 \u0935\u093f\u0928\u093f\u0930\u094d\u0926\u0947\u0936 \u0915\u0947 \u0906\u0927\u093e\u0930 \u092a\u0930 \u0906\u092a\u0915\u0947 \u0915\u094d\u0932\u0938\u094d\u091f\u0930 \u092a\u0930 \u0915\u0949\u0928\u094d\u092b\u093c\u093f\u0917\u0930 \u0915\u0940 \u0917\u0908 \u0938\u0902\u0916\u094d\u092f\u093e \u092e\u0947\u0902 {{< glossary_tooltip term_id=\"pod\" text=\"\u092a\u0949\u0921\u094d\u0938\" >}} \u091a\u0932 \u0930\u0939\u0947 \u0939\u0948 \u092f\u0947 \u0938\u0941\u0928\u093f\u0936\u094d\u091a\u093f\u0924 \u0915\u0930\u0924\u0947 \u0939\u0948\u0902\u0964 ", "commid": "website_pr_37543"}], "negative_passages": []} {"query_id": "q-en-website-e25372679a1ae4e8a519f69ed80315fe9d788a6496495ce883b82d6c681e7e7f", "query": "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 text FlexVolume to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume) plugins, Kubernetes also includes support for [FlexVolume](/docs/concepts/storage/volumes/#flexvolume-deprecated) plugins, which are deprecated since Kubernetes v1.23 (in favour of CSI). FlexVolume plugins allow users to mount volume types that aren't natively supported by Kubernetes. When", "commid": "website_pr_37608"}], "negative_passages": []} {"query_id": "q-en-website-e25372679a1ae4e8a519f69ed80315fe9d788a6496495ce883b82d6c681e7e7f", "query": "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 text FlexVolume to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. ### flexVolume (deprecated) ### flexVolume (deprecated) {#flexvolume} {{< feature-state for_k8s_version=\"v1.23\" state=\"deprecated\" >}}", "commid": "website_pr_37637"}], "negative_passages": []} {"query_id": "q-en-website-e25372679a1ae4e8a519f69ed80315fe9d788a6496495ce883b82d6c681e7e7f", "query": "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 text FlexVolume to and not to this . /kind document /assign /language en\nThe label(s) cannot be applied, because the repository doesn't have them. * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume-deprecated) * [`FlexVolume plugins`](/docs/concepts/storage/volumes/#flexvolume) * Please note that FlexVolumes have been deprecated as of 1.23 * [`CSI Plugins`](/docs/concepts/storage/volumes/#csi)", "commid": "website_pr_37637"}], "negative_passages": []} {"query_id": "q-en-website-b1ea532711c3074cf1ae265c435c0b6a95ebcd3f2607b5c7873412e1dda826c4", "query": "This is a Bug Report ## Metrics (auto-generated 2022 Nov 01) This page details the metrics that different Kubernetes components export. You can query the metrics endpoint for these components using an HTTP scrape, and fetch the current metrics data in Prometheus format.", "commid": "website_pr_37953"}], "negative_passages": []} {"query_id": "q-en-website-b1ea532711c3074cf1ae265c435c0b6a95ebcd3f2607b5c7873412e1dda826c4", "query": "This is a Bug Report ## Control Plane Components", "commid": "website_pr_46260"}], "negative_passages": []} {"query_id": "q-en-website-d4e088e49775a905a0ad78fd2230ef28029f40b6a5023f2d34c7a9719f5efe08", "query": "This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:\n/area web-development /kind feature\n/area web-development Something similar to https://medium- ?\n/retitle Enable click-to-zoom for some diagrams and other images\n/triage accepted /priority backlog /lifecycle frozen\nThanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.\nFor now I'll investigate more and try to find out what can work so assigning it to myself /assign\nA couple of hints:\nThere is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code\none is a good reference for same functionality with example. I'll try both and raise a PR after that.\nWe using vector images.\nThis issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted\nMy apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.\nThis could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen\nLet me see if I can assist with this. Edit: I request review and feedback on pull request", "positive_passages": [{"docid": "doc-en-website-4abf4dc7f91dda4bb6ea5ff6fea5778115878d7d9bbda250239286798702599d", "text": " {{- end -}} {{- if .HasShortcode \"figure\" -}} {{- end -}} {{- if eq (lower .Params.cid) \"community\" -}} {{- if eq .Params.community_styles_migrated true -}} ", "commid": "website_pr_46260"}], "negative_passages": []} {"query_id": "q-en-website-d4e088e49775a905a0ad78fd2230ef28029f40b6a5023f2d34c7a9719f5efe08", "query": "This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:\n/area web-development /kind feature\n/area web-development Something similar to https://medium- ?\n/retitle Enable click-to-zoom for some diagrams and other images\n/triage accepted /priority backlog /lifecycle frozen\nThanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.\nFor now I'll investigate more and try to find out what can work so assigning it to myself /assign\nA couple of hints:\nThere is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code\none is a good reference for same functionality with example. I'll try both and raise a PR after that.\nWe using vector images.\nThis issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted\nMy apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.\nThis could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen\nLet me see if I can assist with this. Edit: I request review and feedback on pull request", "positive_passages": [{"docid": "doc-en-website-5825865e8d621d67190e82ccbcfe9179f095195bae66faeceb09402459c7ff40", "text": " {{ $src := (.Page.Resources.GetMatch (printf \"**%s*\" (.Get \"src\"))) }} {{ $clickToZoom := .Get \"clicktozoom\" }} {{- if .Get \"link\" -}} {{- end }} \"{{ {{- if .Get \"link\" }}{{ end -}} {{- if or (or (.Get \"title\") (.Get \"caption\")) (.Get \"attr\") -}}
    {{ with (.Get \"title\") -}}

    {{ . }}

    {{- end -}} {{- if or (.Get \"caption\") (.Get \"attr\") -}}

    {{- .Get \"caption\" | markdownify -}} {{- with .Get \"attrlink\" }} {{- end -}} {{- .Get \"attr\" | markdownify -}} {{- if .Get \"attrlink\" }}{{ end }}

    {{- end }}
    {{- end }}     No newline at end of file", "commid": "website_pr_46260"}], "negative_passages": []} {"query_id": "q-en-website-d4e088e49775a905a0ad78fd2230ef28029f40b6a5023f2d34c7a9719f5efe08", "query": "This is a Feature Request Some images in concepts sections are quite detailed but in normal scope the texts inside of them look small and unreadable. Can we add feature for the images to pop up on clicking? It will add to the user experience as well as ease the pain of zooming out the page in whole. What would you like to be Feature to Pop up images on click Why is this needed The texts and details seem too small to read. Comments Reference of some of the pages where the issue arises: Example to the pop-up view for image:\n/area web-development /kind feature\n/area web-development Something similar to https://medium- ?\n/retitle Enable click-to-zoom for some diagrams and other images\n/triage accepted /priority backlog /lifecycle frozen\nThanks , I investigated on hugo's documents regarding any shortcode or feature that provide this functionality. but till now haven't found any.\nFor now I'll investigate more and try to find out what can work so assigning it to myself /assign\nA couple of hints:\nThere is one more way like the above reference link mentioned, If we put full-resolution images in other paths and do this : It is in case we want minimal change in the code. I'm going to add ways here as I find so the community can vote or suggest which will be better for a clean code\none is a good reference for same functionality with example. I'll try both and raise a PR after that.\nWe using vector images.\nThis issue has not been updated in over 1 year, and should be re-triaged. You can: Confirm that this issue is still relevant with (org members only) Close this issue with For more details on the triage process, see /remove-triage accepted\nMy apologies,Due to bandwidth issue couldn't work on this, It's open for other people to self-assign.\nThis could be a positive and beneficial addition to the website. Worth doing (re-triaging as accepted). /triage accepted /lifecycle frozen\nLet me see if I can assist with this. Edit: I request review and feedback on pull request", "positive_passages": [{"docid": "doc-en-website-6265e5e494308cf9e4d8c4753118133706435a3cacfd878b985fc668519584e0", "text": " // The page and script is loaded successfully $(document).ready(function() { // Function to handle hover over
    elements function handleFigureHover() { // Only change cursor to zoom-in if figure has 'clickable-zoom' class if ($(this).hasClass('clickable-zoom') && !$(this).hasClass('figure-fullscreen-content')) { $(this).css('cursor', 'zoom-in'); } } // Attach hover event to
    elements with 'clickable-zoom' class $('figure.clickable-zoom').hover(handleFigureHover, function() { // Mouse out - revert cursor back to default $(this).css('cursor', 'default'); }); // Attach click event to
    elements with 'clickable-zoom' class $('figure.clickable-zoom').click(function() { var $figure = $(this); // Check if the figure has 'clickable-zoom' class if ($figure.hasClass('clickable-zoom')) { var $img = $figure.find('img'); // Get the element within the clicked
    // Toggle 'figure-zoomed' class to scale the image $img.toggleClass('figure-zoomed'); // Create a full-screen overlay var $fullscreenOverlay = $('
    '); // Clone the element to display in full-screen var $fullscreenImg = $img.clone(); $fullscreenImg.addClass('figure-fullscreen-img'); // Append the full-screen image to the overlay $fullscreenOverlay.append($fullscreenImg); // Create a close button for the full-screen overlay var $closeButton = $('×'); $closeButton.click(function() { // Remove the full-screen overlay when close button is clicked $fullscreenOverlay.remove(); $('body').css('overflow', 'auto'); // Restore scrolling to the underlying page // Remove 'figure-zoomed' class to reset image scale $img.removeClass('figure-zoomed'); }); $fullscreenOverlay.append($closeButton); // Append the overlay to the body $('body').append($fullscreenOverlay); // Disable scrolling on the underlying page $('body').css('overflow', 'hidden'); // Close full-screen figure when clicking outside of it (on the overlay) $fullscreenOverlay.click(function(event) { if (event.target === this) { // Clicked on the overlay area (outside the full-screen image) $fullscreenOverlay.remove(); $('body').css('overflow', 'auto'); // Restore scrolling to the underlying page // Remove 'figure-zoomed' class to reset image scale $img.removeClass('figure-zoomed'); } }); } }); }); ", "commid": "website_pr_46260"}], "negative_passages": []} {"query_id": "q-en-website-b0cd9125ba23cb615c65468d551574cb465d19bac54d3f7f37d7e987286f5b2b", "query": "This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :\n/sig docs / language en /assign\nIf triage is accepted, i would be happy to contribute on it. PTAL.\n/language en Fixed here .\n/triage accepted", "positive_passages": [{"docid": "doc-en-website-d721a717cbc30c664d98795040573fc95946bfc93be03ec2603def08307bf3f1", "text": " Kubernetes runs your workload by placing containers into Pods to run on _Nodes_. Kubernetes runs your {{< glossary_tooltip text=\"workload\" term_id=\"workload\" >}} by placing containers into Pods to run on _Nodes_. A node may be a virtual or physical machine, depending on the cluster. Each node is managed by the {{< glossary_tooltip text=\"control plane\" term_id=\"control-plane\" >}}", "commid": "website_pr_38213"}], "negative_passages": []} {"query_id": "q-en-website-b0cd9125ba23cb615c65468d551574cb465d19bac54d3f7f37d7e987286f5b2b", "query": "This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :\n/sig docs / language en /assign\nIf triage is accepted, i would be happy to contribute on it. PTAL.\n/language en Fixed here .\n/triage accepted", "positive_passages": [{"docid": "doc-en-website-4b4b2da2cdc0869fb3504472cd7a08f503f0dcff735e96658ddfd558ca2fa791", "text": "section [Graceful Node Shutdown](#graceful-node-shutdown) for more details. When a node is shutdown but not detected by kubelet's Node Shutdown Manager, the pods that are part of a StatefulSet will be stuck in terminating status on that are part of a {{< glossary_tooltip text=\"StatefulSet\" term_id=\"statefulset\" >}} will be stuck in terminating status on the shutdown node and cannot move to a new running node. This is because kubelet on the shutdown node is not available to delete the pods so the StatefulSet cannot create a new pod with the same name. If there are volumes used by the pods, the", "commid": "website_pr_38213"}], "negative_passages": []} {"query_id": "q-en-website-b0cd9125ba23cb615c65468d551574cb465d19bac54d3f7f37d7e987286f5b2b", "query": "This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :\n/sig docs / language en /assign\nIf triage is accepted, i would be happy to contribute on it. PTAL.\n/language en Fixed here .\n/triage accepted", "positive_passages": [{"docid": "doc-en-website-704d30e735ba0f6816a9e81fe4cff493a71a13e0c2f2f6d6592b7b7156ec6201", "text": "To mitigate the above situation, a user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to a Node marking it out-of-service. If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint, the is enabled on {{< glossary_tooltip text=\"kube-controller-manager\" term_id=\"kube-controller-manager\" >}}, and a Node is marked out-of-service with this taint, the pods on the node will be forcefully deleted if there are no matching tolerations on it and volume detach operations for the pods terminating on the node will happen immediately. This allows the Pods on the out-of-service node to recover quickly on a different node.", "commid": "website_pr_38213"}], "negative_passages": []} {"query_id": "q-en-website-b0cd9125ba23cb615c65468d551574cb465d19bac54d3f7f37d7e987286f5b2b", "query": "This is a Feature Request What would you like to be Below are terms that can use the addition of a glossary tooltip to show the meaning of the said term.Below points can be to section of Nodes page which will help users for quick follow-ups. Why is this needed These references can help user understanding the concept while staying on same page or finding more about the concept with right link. it will enhance user experience and bring more clarity and less confusion. Comments :\n/sig docs / language en /assign\nIf triage is accepted, i would be happy to contribute on it. PTAL.\n/language en Fixed here .\n/triage accepted", "positive_passages": [{"docid": "doc-en-website-669395a645ff20eb3e2402ed3d52c4b95daf3c54bade9a0baab8cf342e3398d8", "text": "## {{% heading \"whatsnext\" %}} * Learn about the [components](/docs/concepts/overview/components/#node-components) that make up a node. * Read the [API definition for Node](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#node-v1-core). * Read the [Node](https://git.k8s.io/design-proposals-archive/architecture/architecture.md#the-kubernetes-node) section of the architecture design document. * Read about [taints and tolerations](/docs/concepts/scheduling-eviction/taint-and-toleration/). Learn more about the following: * [Components](/docs/concepts/overview/components/#node-components) that make up a node. * [API definition for Node](/docs/reference/generated/kubernetes-api/{{< param \"version\" >}}/#node-v1-core). * [Node](https://git.k8s.io/design-proposals-archive/architecture/architecture.md#the-kubernetes-node) section of the architecture design document. * [Taints and Tolerations](/docs/concepts/scheduling-eviction/taint-and-toleration/). * [Node Resource Managers](/docs/concepts/policy/node-resource-managers/). * [Resource Management for Windows nodes](/docs/concepts/configuration/windows-resource-management/). ", "commid": "website_pr_38213"}], "negative_passages": []} {"query_id": "q-en-website-d24958dbd3ea1898ccfc04bdfeac1e967ca3a83581035e7db7119351a204bf4d", "query": "Observed this issue while reading . I have gone through the the whole file need to do these changes. \u094d\u0930\u0940\u0917\u0947\u0936\u0928 \u0932\u0947\u092f\u0930 \u0906\u092a\u0915\u094b \u0905\u092a\u0928\u0947 \u0915\u094d\u0932\u0938\u094d\u091f\u0930 \u092e\u0947\u0902 \u0905\u0924\u093f\u0930\u093f\u0915\u094d\u0924 \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938-\u0936\u0948\u0932\u0940 API \u0938\u094d\u0925\u093e\u092a\u093f\u0924 \u0915\u0930\u0928\u0947 \u0926\u0947\u0924\u093e \u0939\u0948\u0964 Need to remove this \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938 need to change this to -API \u0947\u0902 URL -URL \u092a\u093e\u0925 /assign\nThis 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. \u090f\u0917\u094d\u0930\u0940\u0917\u0947\u0936\u0928 \u0932\u0947\u092f\u0930 \u0906\u092a\u0915\u094b \u0905\u092a\u0928\u0947 \u0915\u094d\u0932\u0938\u094d\u091f\u0930 \u092e\u0947\u0902 \u0905\u0924\u093f\u0930\u093f\u0915\u094d\u0924 \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938-\u0936\u0948\u0932\u0940 API \u0938\u094d\u0925\u093e\u092a\u093f\u0924 \u0915\u0930\u0928\u0947 \u0926\u0947\u0924\u093e \u0939\u0948\u0964``` \u090f\u0917\u094d\u0930\u0940\u0917\u0947\u0936\u0928 \u0932\u0947\u092f\u0930 \u0906\u092a\u0915\u094b \u0905\u092a\u0928\u0947 \u0915\u094d\u0932\u0938\u094d\u091f\u0930 \u092e\u0947\u0902 \u0905\u0924\u093f\u0930\u093f\u0915\u094d\u0924 \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938-\u0936\u0948\u0932\u0940 API \u0938\u094d\u0925\u093e\u092a\u093f\u0924 \u0915\u0930\u0928\u0947 \u0926\u0947\u0924\u093e \u0939\u0948\u0964 \u091c\u092c \u0906\u092a\u0928\u0947 {{< glossary_tooltip text=\"\u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938 API \u0938\u0930\u094d\u0935\u0930\" term_id=\"kube-apiserver\" >}} \u0915\u094b [\u0905\u0924\u093f\u0930\u093f\u0915\u094d\u0924 API \u0915\u093e \u0938\u092e\u0930\u094d\u0925\u0928](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) \u0915\u0930\u0928\u0947 \u0915\u0947 \u0932\u093f\u090f \u0915\u0949\u0928\u094d\u092b\u093c\u093f\u0917\u0930 \u0915\u093f\u092f\u093e \u0939\u094b, \u0906\u092a \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938 \u090f\u092a\u0940\u0906\u0908 \u092e\u0947\u0902 URL \u092a\u0925 \u0915\u093e \"\u0926\u093e\u0935\u093e\" \u0915\u0930\u0928\u0947 \u0915\u0947 \u0932\u093f\u090f `APIService` \u0911\u092c\u094d\u091c\u0947\u0915\u094d\u091f \u091c\u094b\u0921\u093c \u0938\u0915\u0924\u0947 \u0939\u0948\u0902\u0964 \u091c\u092c \u0906\u092a\u0928\u0947 {{< glossary_tooltip text=\"\u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938 API \u0938\u0930\u094d\u0935\u0930\" term_id=\"kube-apiserver\" >}} \u0915\u094b [\u0905\u0924\u093f\u0930\u093f\u0915\u094d\u0924 API \u0915\u093e \u0938\u092e\u0930\u094d\u0925\u0928](/docs/tasks/extend-kubernetes/configure-aggregation-layer/) \u0915\u0930\u0928\u0947 \u0915\u0947 \u0932\u093f\u090f \u0915\u0949\u0928\u094d\u092b\u093c\u093f\u0917\u0930 \u0915\u093f\u092f\u093e \u0939\u094b, \u0906\u092a \u0915\u0941\u092c\u0947\u0930\u0928\u0947\u091f\u094d\u0938 API \u092e\u0947\u0902 URL \u092a\u093e\u0925 \u0915\u093e \"\u0926\u093e\u0935\u093e\" \u0915\u0930\u0928\u0947 \u0915\u0947 \u0932\u093f\u090f `APIService` \u0911\u092c\u094d\u091c\u0947\u0915\u094d\u091f \u091c\u094b\u0921\u093c \u0938\u0915\u0924\u0947 \u0939\u0948\u0902\u0964 ", "commid": "website_pr_38155"}], "negative_passages": []} {"query_id": "q-en-website-3d560b207efb75cde6445cd8a6069c5934c4aa02d3b15e368303ec24ab127b2f", "query": "This is a Feature Request add and translate Chinese document: content/en/docs/concepts/scheduling-eviction/dynamic-resource- URL {{< feature-state for_k8s_version=\"v1.26\" state=\"alpha\" >}} \u52a8\u6001\u8d44\u6e90\u5206\u914d\u662f\u4e00\u4e2a\u7528\u4e8e\u5728 Pod \u4e4b\u95f4\u548c Pod \u5185\u90e8\u5bb9\u5668\u4e4b\u95f4\u8bf7\u6c42\u548c\u5171\u4eab\u8d44\u6e90\u7684\u65b0 API\u3002 \u5b83\u662f\u5bf9\u4e3a\u901a\u7528\u8d44\u6e90\u6240\u63d0\u4f9b\u7684\u6301\u4e45\u5377 API \u7684\u6cdb\u5316\u3002\u7b2c\u4e09\u65b9\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u8d1f\u8d23\u8ddf\u8e2a\u548c\u5206\u914d\u8d44\u6e90\u3002 \u4e0d\u540c\u7c7b\u578b\u7684\u8d44\u6e90\u652f\u6301\u7528\u4efb\u610f\u53c2\u6570\u8fdb\u884c\u5b9a\u4e49\u548c\u521d\u59cb\u5316\u3002 ## {{% heading \"prerequisites\" %}} Kubernetes v{{< skew currentVersion >}} \u5305\u542b\u7528\u4e8e\u52a8\u6001\u8d44\u6e90\u5206\u914d\u7684\u96c6\u7fa4\u7ea7 API \u652f\u6301\uff0c \u4f46\u5b83\u9700\u8981\u88ab[\u663e\u5f0f\u542f\u7528](#enabling-dynamic-resource-allocation)\u3002 \u4f60\u8fd8\u5fc5\u987b\u4e3a\u6b64 API \u8981\u7ba1\u7406\u7684\u7279\u5b9a\u8d44\u6e90\u5b89\u88c5\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u3002 \u5982\u679c\u4f60\u672a\u8fd0\u884c Kubernetes v{{< skew currentVersion>}}\uff0c \u8bf7\u67e5\u770b\u5bf9\u5e94\u7248\u672c\u7684 Kubernetes \u6587\u6863\u3002 ## API {#api} \u65b0\u7684 `resource.k8s.io/v1alpha1` {{< glossary_tooltip text=\"API \u7ec4\" term_id=\"api-group\" >}}\u63d0\u4f9b\u56db\u79cd\u65b0\u7c7b\u578b\uff1a ResourceClass : \u5b9a\u4e49\u7531\u54ea\u4e2a\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u5904\u7406\u67d0\u79cd\u8d44\u6e90\uff0c\u5e76\u4e3a\u5176\u63d0\u4f9b\u901a\u7528\u53c2\u6570\u3002 \u96c6\u7fa4\u7ba1\u7406\u5458\u5728\u5b89\u88c5\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u65f6\u521b\u5efa ResourceClass\u3002 ResourceClaim : \u5b9a\u4e49\u5de5\u4f5c\u8d1f\u8f7d\u6240\u9700\u7684\u7279\u5b9a\u8d44\u6e90\u5b9e\u4f8b\u3002 \u7531\u7528\u6237\u521b\u5efa\uff08\u624b\u52a8\u7ba1\u7406\u751f\u547d\u5468\u671f\uff0c\u53ef\u4ee5\u5728\u4e0d\u540c\u7684 Pod \u4e4b\u95f4\u5171\u4eab\uff09\uff0c \u6216\u8005\u7531\u63a7\u5236\u5e73\u9762\u57fa\u4e8e ResourceClaimTemplate \u4e3a\u7279\u5b9a Pod \u521b\u5efa \uff08\u81ea\u52a8\u7ba1\u7406\u751f\u547d\u5468\u671f\uff0c\u901a\u5e38\u4ec5\u7531\u4e00\u4e2a Pod \u4f7f\u7528\uff09\u3002 ResourceClaimTemplate : \u5b9a\u4e49\u7528\u4e8e\u521b\u5efa ResourceClaim \u7684 spec \u548c\u4e00\u4e9b\u5143\u6570\u636e\u3002 \u90e8\u7f72\u5de5\u4f5c\u8d1f\u8f7d\u65f6\u7531\u7528\u6237\u521b\u5efa\u3002 PodScheduling : \u4f9b\u63a7\u5236\u5e73\u9762\u548c\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u5185\u90e8\u4f7f\u7528\uff0c \u5728\u9700\u8981\u4e3a Pod \u5206\u914d ResourceClaim \u65f6\u534f\u8c03 Pod \u8c03\u5ea6\u3002 ResourceClass \u548c ResourceClaim \u7684\u53c2\u6570\u5b58\u50a8\u5728\u5355\u72ec\u7684\u5bf9\u8c61\u4e2d\uff0c \u901a\u5e38\u4f7f\u7528\u5b89\u88c5\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u65f6\u521b\u5efa\u7684 {{< glossary_tooltip term_id=\"CustomResourceDefinition\" text=\"CRD\" >}} \u6240\u5b9a\u4e49\u7684\u7c7b\u578b\u3002 `core/v1` \u7684 `PodSpec` \u5728\u65b0\u7684 `resourceClaims` \u5b57\u6bb5\u4e2d\u5b9a\u4e49 Pod \u6240\u9700\u7684 ResourceClaim\u3002 \u8be5\u5217\u8868\u4e2d\u7684\u6761\u76ee\u5f15\u7528 ResourceClaim \u6216 ResourceClaimTemplate\u3002 \u5f53\u5f15\u7528 ResourceClaim \u65f6\uff0c\u4f7f\u7528\u6b64 PodSpec \u7684\u6240\u6709 Pod \uff08\u4f8b\u5982 Deployment \u6216 StatefulSet \u4e2d\u7684 Pod\uff09\u5171\u4eab\u76f8\u540c\u7684 ResourceClaim \u5b9e\u4f8b\u3002 \u5f15\u7528 ResourceClaimTemplate \u65f6\uff0c\u6bcf\u4e2a Pod \u90fd\u6709\u81ea\u5df1\u7684\u5b9e\u4f8b\u3002 \u5bb9\u5668\u8d44\u6e90\u7684 `resources.claims` \u5217\u8868\u5b9a\u4e49\u5bb9\u5668\u53ef\u4ee5\u8bbf\u95ee\u7684\u8d44\u6e90\u5b9e\u4f8b\uff0c \u4ece\u800c\u53ef\u4ee5\u5b9e\u73b0\u5728\u4e00\u4e2a\u6216\u591a\u4e2a\u5bb9\u5668\u4e4b\u95f4\u5171\u4eab\u8d44\u6e90\u3002 \u4e0b\u9762\u662f\u4e00\u4e2a\u865a\u6784\u7684\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u7684\u793a\u4f8b\u3002 \u8be5\u793a\u4f8b\u5c06\u4e3a\u6b64 Pod \u521b\u5efa\u4e24\u4e2a ResourceClaim \u5bf9\u8c61\uff0c\u6bcf\u4e2a\u5bb9\u5668\u90fd\u53ef\u4ee5\u8bbf\u95ee\u5176\u4e2d\u4e00\u4e2a\u3002 ```yaml apiVersion: resource.k8s.io/v1alpha1 kind: ResourceClass name: resource.example.com driverName: resource-driver.example.com --- apiVersion: cats.resource.example.com/v1 kind: ClaimParameters name: large-black-cat-claim-parameters spec: color: black size: large --- apiVersion: resource.k8s.io/v1alpha1 kind: ResourceClaimTemplate metadata: name: large-black-cat-claim-template spec: spec: resourceClassName: resource.example.com parametersRef: apiGroup: cats.resource.example.com kind: ClaimParameters name: large-black-cat-claim-parameters \u2013-- apiVersion: v1 kind: Pod metadata: name: pod-with-cats spec: containers: - name: container0 image: ubuntu:20.04 command: [\"sleep\", \"9999\"] resources: claims: - name: cat-0 - name: container1 image: ubuntu:20.04 command: [\"sleep\", \"9999\"] resources: claims: - name: cat-1 resourceClaims: - name: cat-0 source: resourceClaimTemplateName: large-black-cat-claim-template - name: cat-1 source: resourceClaimTemplateName: large-black-cat-claim-template ``` ## \u8c03\u5ea6 {#scheduling} \u4e0e\u539f\u751f\u8d44\u6e90\uff08CPU\u3001RAM\uff09\u548c\u6269\u5c55\u8d44\u6e90\uff08\u7531\u8bbe\u5907\u63d2\u4ef6\u7ba1\u7406\uff0c\u5e76\u7531 kubelet \u516c\u5e03\uff09\u4e0d\u540c\uff0c \u8c03\u5ea6\u5668\u4e0d\u77e5\u9053\u96c6\u7fa4\u4e2d\u6709\u54ea\u4e9b\u52a8\u6001\u8d44\u6e90\uff0c \u4e5f\u4e0d\u77e5\u9053\u5982\u4f55\u5c06\u5b83\u4eec\u62c6\u5206\u4ee5\u6ee1\u8db3\u7279\u5b9a ResourceClaim \u7684\u8981\u6c42\u3002 \u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u8d1f\u8d23\u8fd9\u4e9b\u4efb\u52a1\u3002 \u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u5728\u4e3a ResourceClaim \u4fdd\u7559\u8d44\u6e90\u540e\u5c06\u5176\u6807\u8bb0\u4e3a\u201c\u5df2\u5206\u914d\uff08Allocated\uff09\u201d\u3002 \u7136\u540e\u544a\u8bc9\u8c03\u5ea6\u5668\u96c6\u7fa4\u4e2d\u53ef\u7528\u7684 ResourceClaim \u7684\u4f4d\u7f6e\u3002 ResourceClaim \u53ef\u4ee5\u5728\u521b\u5efa\u65f6\u5c31\u8fdb\u884c\u5206\u914d\uff08\u201c\u7acb\u5373\u5206\u914d\u201d\uff09\uff0c\u4e0d\u7528\u8003\u8651\u54ea\u4e9b Pod \u5c06\u4f7f\u7528\u5b83\u3002 \u9ed8\u8ba4\u60c5\u51b5\u4e0b\u91c7\u7528\u5ef6\u8fdf\u5206\u914d\uff0c\u76f4\u5230\u9700\u8981 ResourceClaim \u7684 Pod \u88ab\u8c03\u5ea6\u65f6 \uff08\u5373\u201c\u7b49\u5f85\u7b2c\u4e00\u4e2a\u6d88\u8d39\u8005\u201d\uff09\u518d\u8fdb\u884c\u5206\u914d\u3002 \u5728\u8fd9\u79cd\u6a21\u5f0f\u4e0b\uff0c\u8c03\u5ea6\u5668\u68c0\u67e5 Pod \u6240\u9700\u7684\u6240\u6709 ResourceClaim\uff0c\u5e76\u521b\u5efa\u4e00\u4e2a PodScheduling \u5bf9\u8c61\uff0c \u901a\u77e5\u8d1f\u8d23\u8fd9\u4e9b ResourceClaim \u7684\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\uff0c\u544a\u77e5\u5b83\u4eec\u8c03\u5ea6\u5668\u8ba4\u4e3a\u9002\u5408\u8be5 Pod \u7684\u8282\u70b9\u3002 \u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u901a\u8fc7\u6392\u9664\u6ca1\u6709\u8db3\u591f\u5269\u4f59\u8d44\u6e90\u7684\u8282\u70b9\u6765\u54cd\u5e94\u8c03\u5ea6\u5668\u3002 \u4e00\u65e6\u8c03\u5ea6\u5668\u6709\u4e86\u8fd9\u4e9b\u4fe1\u606f\uff0c\u5b83\u5c31\u4f1a\u9009\u62e9\u4e00\u4e2a\u8282\u70b9\uff0c\u5e76\u5c06\u8be5\u9009\u62e9\u5b58\u50a8\u5728 PodScheduling \u5bf9\u8c61\u4e2d\u3002 \u7136\u540e\uff0c\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u4e3a\u5206\u914d\u5176 ResourceClaim\uff0c\u4ee5\u4fbf\u8d44\u6e90\u53ef\u7528\u4e8e\u8be5\u8282\u70b9\u3002 \u5b8c\u6210\u540e\uff0cPod \u5c31\u4f1a\u88ab\u8c03\u5ea6\u3002 \u4f5c\u4e3a\u6b64\u8fc7\u7a0b\u7684\u4e00\u90e8\u5206\uff0cResourceClaim \u4f1a\u4e3a Pod \u4fdd\u7559\u3002 \u76ee\u524d\uff0cResourceClaim \u53ef\u4ee5\u7531\u5355\u4e2a Pod \u72ec\u5360\u4f7f\u7528\u6216\u4e0d\u9650\u6570\u91cf\u7684\u591a\u4e2a Pod \u4f7f\u7528\u3002 \u9664\u975e Pod \u7684\u6240\u6709\u8d44\u6e90\u90fd\u5df2\u5206\u914d\u548c\u4fdd\u7559\uff0c\u5426\u5219 Pod \u4e0d\u4f1a\u88ab\u8c03\u5ea6\u5230\u8282\u70b9\uff0c\u8fd9\u662f\u4e00\u4e2a\u91cd\u8981\u7279\u6027\u3002 \u8fd9\u907f\u514d\u4e86 Pod \u88ab\u8c03\u5ea6\u5230\u4e00\u4e2a\u8282\u70b9\u4f46\u65e0\u6cd5\u5728\u90a3\u91cc\u8fd0\u884c\u7684\u60c5\u51b5\uff0c \u8fd9\u79cd\u60c5\u51b5\u5f88\u7cdf\u7cd5\uff0c\u56e0\u4e3a\u88ab\u6302\u8d77 Pod \u4e5f\u4f1a\u963b\u585e\u4e3a\u5176\u4fdd\u7559\u7684\u5176\u4ed6\u8d44\u6e90\uff0c\u5982 RAM \u6216 CPU\u3002 ## \u9650\u5236 {#limitations} \u8c03\u5ea6\u5668\u63d2\u4ef6\u5fc5\u987b\u53c2\u4e0e\u8c03\u5ea6\u90a3\u4e9b\u4f7f\u7528 ResourceClaim \u7684 Pod\u3002 \u901a\u8fc7\u8bbe\u7f6e `nodeName` \u5b57\u6bb5\u7ed5\u8fc7\u8c03\u5ea6\u5668\u4f1a\u5bfc\u81f4 kubelet \u62d2\u7edd\u542f\u52a8 Pod\uff0c \u56e0\u4e3a ResourceClaim \u6ca1\u6709\u88ab\u4fdd\u7559\u6216\u751a\u81f3\u6839\u672c\u6ca1\u6709\u88ab\u5206\u914d\u3002 \u672a\u6765\u53ef\u80fd[\u53bb\u9664\u8be5\u9650\u5236](https://github.com/kubernetes/kubernetes/issues/114005)\u3002 ## \u542f\u7528\u52a8\u6001\u8d44\u6e90\u5206\u914d {#enabling-dynamic-resource-allocation} \u52a8\u6001\u8d44\u6e90\u5206\u914d\u662f\u4e00\u4e2a **alpha \u7279\u6027**\uff0c\u53ea\u6709\u5728\u542f\u7528 `DynamicResourceAllocation` [\u7279\u6027\u95e8\u63a7](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/) \u548c `resource.k8s.io/v1alpha1` {{< glossary_tooltip text=\"API \u7ec4\" term_id=\"api-group\" >}} \u65f6\u624d\u542f\u7528\u3002 \u6709\u5173\u8be6\u7ec6\u4fe1\u606f\uff0c\u53c2\u9605 `--feature-gates` \u548c `--runtime-config` [kube-apiserver \u53c2\u6570](/zh-cn/docs/reference/command-line-tools-reference/kube-apiserver/)\u3002 kube-scheduler\u3001kube-controller-manager \u548c kubelet \u4e5f\u9700\u8981\u8bbe\u7f6e\u8be5\u7279\u6027\u95e8\u63a7\u3002 \u5feb\u901f\u68c0\u67e5 Kubernetes \u96c6\u7fa4\u662f\u5426\u652f\u6301\u8be5\u529f\u80fd\u7684\u65b9\u6cd5\u662f\u5217\u51fa ResourceClass \u5bf9\u8c61\uff1a ```shell kubectl get resourceclasses ``` \u5982\u679c\u4f60\u7684\u96c6\u7fa4\u652f\u6301\u52a8\u6001\u8d44\u6e90\u5206\u914d\uff0c\u5219\u54cd\u5e94\u662f ResourceClass \u5bf9\u8c61\u5217\u8868\u6216\uff1a ``` No resources found ``` \u5982\u679c\u4e0d\u652f\u6301\uff0c\u5219\u4f1a\u8f93\u51fa\u5982\u4e0b\u9519\u8bef\uff1a ``` error: the server doesn't have a resource type \"resourceclasses\" ``` kube-scheduler \u7684\u9ed8\u8ba4\u914d\u7f6e\u4ec5\u5728\u542f\u7528\u7279\u6027\u95e8\u63a7\u65f6\u624d\u542f\u7528 \"DynamicResources\" \u63d2\u4ef6\u3002 \u81ea\u5b9a\u4e49\u914d\u7f6e\u53ef\u80fd\u9700\u8981\u88ab\u4fee\u6539\u624d\u80fd\u542f\u7528\u5b83\u3002 \u9664\u4e86\u5728\u96c6\u7fa4\u4e2d\u542f\u7528\u8be5\u529f\u80fd\u5916\uff0c\u8fd8\u5fc5\u987b\u5b89\u88c5\u8d44\u6e90\u9a71\u52a8\u7a0b\u5e8f\u3002 \u6b32\u4e86\u89e3\u8be6\u7ec6\u4fe1\u606f\uff0c\u8bf7\u53c2\u9605\u9a71\u52a8\u7a0b\u5e8f\u7684\u6587\u6863\u3002 ## {{% heading \"whatsnext\" %}} - \u4e86\u89e3\u66f4\u591a\u8be5\u8bbe\u8ba1\u7684\u4fe1\u606f\uff0c \u53c2\u9605[\u52a8\u6001\u8d44\u6e90\u5206\u914d KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3063-dynamic-resource-allocation/README.md)\u3002 No newline at end of file", "commid": "website_pr_38679"}], "negative_passages": []} {"query_id": "q-en-website-543dce49c6cc8577a079b662afca34ab8deb7b8443227c66d6a4c8ffc4bbe640", "query": "This is a Feature Request {{}} \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u5229\u7528\u3059\u308b\u3068\u3001\u5bfe\u8c61\u306e\u30ea\u30bd\u30fc\u30b9\u3092\u524a\u9664\u3059\u308b\u524d\u306b\u7279\u5b9a\u306e\u30af\u30ea\u30fc\u30f3\u30a2\u30c3\u30d7\u3092\u884c\u3046\u3088\u3046\u306b{{}}\u306b\u8b66\u544a\u3059\u308b\u3053\u3068\u3067\u3001{{}}\u3092\u7ba1\u7406\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u5927\u62b5\u306e\u5834\u5408\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306f\u5b9f\u884c\u3055\u308c\u308b\u30b3\u30fc\u30c9\u3092\u6307\u5b9a\u3059\u308b\u3053\u3068\u306f\u3042\u308a\u307e\u305b\u3093\u3002 \u305d\u306e\u4ee3\u308f\u308a\u3001\u4e00\u822c\u7684\u306b\u306f\u30a2\u30ce\u30c6\u30fc\u30b7\u30e7\u30f3\u306e\u3088\u3046\u306b\u7279\u5b9a\u306e\u30ea\u30bd\u30fc\u30b9\u306b\u95a2\u3059\u308b\u30ad\u30fc\u306e\u30ea\u30b9\u30c8\u306b\u306a\u308a\u307e\u3059\u3002 Kubernetes\u306f\u3044\u304f\u3064\u304b\u306e\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u81ea\u52d5\u7684\u306b\u8ffd\u52a0\u3057\u307e\u3059\u304c\u3001\u81ea\u5206\u3067\u8ffd\u52a0\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002 ## \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306f\u3069\u306e\u3088\u3046\u306b\u52d5\u4f5c\u3059\u308b\u304b \u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u30d5\u30a1\u30a4\u30eb\u3092\u4f7f\u3063\u3066\u30ea\u30bd\u30fc\u30b9\u3092\u4f5c\u308b\u3068\u304d\u3001`metadata.finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u306e\u4e2d\u3067\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u6307\u5b9a\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u30ea\u30bd\u30fc\u30b9\u3092\u524a\u9664\u3057\u3088\u3046\u3068\u3059\u308b\u3068\u304d\u3001\u524a\u9664\u30ea\u30af\u30a8\u30b9\u30c8\u3092\u6271\u3046API\u30b5\u30fc\u30d0\u30fc\u306f`finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u306e\u5024\u3092\u78ba\u8a8d\u3057\u3001\u4ee5\u4e0b\u306e\u3088\u3046\u306b\u6271\u3044\u307e\u3059\u3002 * \u524a\u9664\u3092\u958b\u59cb\u3057\u305f\u6642\u9593\u3092\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e`metadata.deletionTimestamp`\u30d5\u30a3\u30fc\u30eb\u30c9\u306b\u8a2d\u5b9a\u3057\u307e\u3059\u3002 * `metadata.finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u7a7a\u306b\u306a\u308b\u307e\u3067\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u304c\u524a\u9664\u3055\u308c\u308b\u306e\u3092\u963b\u6b62\u3057\u307e\u3059\u3002 * \u30b9\u30c6\u30fc\u30bf\u30b9\u30b3\u30fc\u30c9`202`(HTTP \"Accepted\")\u3092\u8fd4\u3057\u307e\u3059\u3002 \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u7ba1\u7406\u3057\u3066\u3044\u308b\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u3001\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u524a\u9664\u304c\u30ea\u30af\u30a8\u30b9\u30c8\u3055\u308c\u305f\u3053\u3068\u3092\u793a\u3059`metadata.deletionTimestamp`\u304c\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306b\u8a2d\u5b9a\u3055\u308c\u305f\u3053\u3068\u3092\u691c\u77e5\u3057\u307e\u3059\u3002 \u3059\u308b\u3068\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u30ea\u30bd\u30fc\u30b9\u306b\u6307\u5b9a\u3055\u308c\u305f\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306e\u8981\u6c42\u3092\u6e80\u305f\u305d\u3046\u3068\u3057\u307e\u3059\u3002 \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306e\u6761\u4ef6\u304c\u6e80\u305f\u3055\u308c\u308b\u305f\u3073\u306b\u3001\u305d\u306e\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u30ea\u30bd\u30fc\u30b9\u306e`finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u306e\u5bfe\u8c61\u306e\u30ad\u30fc\u3092\u524a\u9664\u3057\u307e\u3059\u3002 `finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u7a7a\u306b\u306a\u3063\u305f\u3068\u304d\u3001`deletionTimestamp`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u8a2d\u5b9a\u3055\u308c\u305f\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306f\u81ea\u52d5\u7684\u306b\u524a\u9664\u3055\u308c\u307e\u3059\u3002\u7ba1\u7406\u5916\u306e\u30ea\u30bd\u30fc\u30b9\u524a\u9664\u3092\u9632\u3050\u305f\u3081\u306b\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u5229\u7528\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002 \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306e\u4e00\u822c\u7684\u306a\u4f8b\u306f`kubernetes.io/pv-protection`\u3067\u3001\u3053\u308c\u306f `PersistentVolume`\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u304c\u8aa4\u3063\u3066\u524a\u9664\u3055\u308c\u308b\u306e\u3092\u9632\u3050\u305f\u3081\u306e\u3082\u306e\u3067\u3059\u3002 `PersistentVolume`\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092Pod\u304c\u5229\u7528\u4e2d\u306e\u5834\u5408\u3001Kubernetes\u306f`pv-protection`\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u8ffd\u52a0\u3057\u307e\u3059\u3002 `PersistentVolume`\u3092\u524a\u9664\u3057\u3088\u3046\u3068\u3059\u308b\u3068`Terminating`\u30b9\u30c6\u30fc\u30bf\u30b9\u306b\u306a\u308a\u307e\u3059\u304c\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u304c\u5b58\u5728\u3057\u3066\u3044\u308b\u305f\u3081\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u30dc\u30ea\u30e5\u30fc\u30e0\u3092\u524a\u9664\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u305b\u3093\u3002 Pod\u304c`PersistentVolume`\u306e\u5229\u7528\u3092\u505c\u6b62\u3059\u308b\u3068Kubernetes\u306f`pv-protection`\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u524a\u9664\u3057\u3001\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u304c\u30dc\u30ea\u30e5\u30fc\u30e0\u3092\u524a\u9664\u3057\u307e\u3059\u3002 ## \u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u3001\u30e9\u30d9\u30eb\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc {#owners-labels-finalizers} {{}}\u306e\u3088\u3046\u306b\u3001 [\u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9](/docs/concepts/overview/working-with-objects/owners-dependents/)\u306fKubernetes\u306e\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u9593\u306e\u95a2\u4fc2\u6027\u3092\u8aac\u660e\u3057\u307e\u3059\u304c\u3001\u5229\u7528\u3055\u308c\u308b\u76ee\u7684\u304c\u7570\u306a\u308a\u307e\u3059\u3002 {{}} \u304cPod\u306e\u3088\u3046\u306a\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092\u7ba1\u7406\u3059\u308b\u3068\u304d\u3001\u95a2\u9023\u3059\u308b\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u30b0\u30eb\u30fc\u30d7\u306e\u5909\u66f4\u3092\u8ffd\u8de1\u3059\u308b\u305f\u3081\u306b\u30e9\u30d9\u30eb\u3092\u5229\u7528\u3057\u307e\u3059\u3002 \u4f8b\u3048\u3070\u3001{{}}\u304c\u3044\u304f\u3064\u304b\u306ePod\u3092\u4f5c\u6210\u3059\u308b\u3068\u304d\u3001Job\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u305d\u308c\u3089\u306ePod\u306b\u30e9\u30d9\u30eb\u3092\u4ed8\u3051\u3001\u30af\u30e9\u30b9\u30bf\u30fc\u5185\u306e\u540c\u3058\u30e9\u30d9\u30eb\u3092\u6301\u3064Pod\u306e\u5909\u66f4\u3092\u8ffd\u8de1\u3057\u307e\u3059\u3002 Job\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u3001Pod\u3092\u4f5c\u6210\u3057\u305fJob\u3092\u6307\u3059*\u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9*\u3082\u305d\u308c\u3089\u306ePod\u306b\u8ffd\u52a0\u3057\u307e\u3059\u3002 Pod\u304c\u5b9f\u884c\u3055\u308c\u3066\u3044\u308b\u3068\u304d\u306bJob\u3092\u524a\u9664\u3059\u308b\u3068\u3001Kubernetes\u306f\u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9(\u30e9\u30d9\u30eb\u3067\u306f\u306a\u3044)\u3092\u4f7f\u3063\u3066\u3001\u30af\u30ea\u30fc\u30f3\u30a2\u30c3\u30d7\u3059\u308b\u5fc5\u8981\u306e\u3042\u308bPod\u3092\u30af\u30e9\u30b9\u30bf\u30fc\u5185\u304b\u3089\u63a2\u3057\u51fa\u3057\u307e\u3059\u3002 \u307e\u305f\u3001Kubernetes\u306f\u524a\u9664\u5bfe\u8c61\u306e\u30ea\u30bd\u30fc\u30b9\u306e\u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u3092\u8a8d\u8b58\u3057\u3066\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u51e6\u7406\u3057\u307e\u3059\u3002 \u72b6\u6cc1\u306b\u3088\u3063\u3066\u306f\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u304c\u4f9d\u5b58\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u524a\u9664\u3092\u30d6\u30ed\u30c3\u30af\u3057\u3066\u3057\u307e\u3044\u3001\u5bfe\u8c61\u306e\u30aa\u30fc\u30ca\u30fc\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u304c\u5b8c\u5168\u306b\u524a\u9664\u3055\u308c\u305a\u4e88\u60f3\u4ee5\u4e0a\u306b\u9577\u6642\u9593\u6b8b\u3063\u3066\u3057\u307e\u3046\u3053\u3068\u304c\u3042\u308a\u307e\u3059\u3002 \u3053\u306e\u3088\u3046\u306a\u72b6\u6cc1\u3067\u306f\u3001\u5bfe\u8c61\u306e\u30aa\u30fc\u30ca\u30fc\u3068\u4f9d\u5b58\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306e\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3068\u30aa\u30fc\u30ca\u30fc\u30ea\u30d5\u30a1\u30ec\u30f3\u30b9\u3092\u78ba\u8a8d\u3057\u3066\u554f\u984c\u3092\u89e3\u6c7a\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 {{}} \u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u304c\u524a\u9664\u4e2d\u306e\u72b6\u614b\u3067\u8a70\u307e\u3063\u3066\u3057\u307e\u3063\u305f\u5834\u5408\u3001\u524a\u9664\u3092\u7d9a\u884c\u3059\u308b\u305f\u3081\u306b\u624b\u52d5\u3067\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u524a\u9664\u3059\u308b\u3053\u3068\u306f\u907f\u3051\u3066\u304f\u3060\u3055\u3044\u3002 \u901a\u5e38\u3001\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306f\u7406\u7531\u304c\u3042\u3063\u3066\u30ea\u30bd\u30fc\u30b9\u306b\u8ffd\u52a0\u3055\u308c\u3066\u3044\u308b\u3082\u306e\u3067\u3042\u308b\u305f\u3081\u3001\u5f37\u5236\u7684\u306b\u524a\u9664\u3057\u3066\u3057\u307e\u3046\u3068\u30af\u30e9\u30b9\u30bf\u30fc\u3067\u4f55\u3089\u304b\u306e\u554f\u984c\u3092\u5f15\u304d\u8d77\u3053\u3059\u3053\u3068\u304c\u3042\u308a\u307e\u3059\u3002 \u305d\u306e\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306e\u76ee\u7684\u3092\u7406\u89e3\u3057\u3066\u3044\u308b\u304b\u3064\u3001\u5225\u306e\u65b9\u6cd5\u3067\u9054\u6210\u3067\u304d\u308b\u5834\u5408\u306b\u306e\u307f\u884c\u3046\u3079\u304d\u3067\u3059(\u4f8b\u3048\u3070\u3001\u4f9d\u5b58\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092\u624b\u52d5\u3067\u524a\u9664\u3059\u308b\u306a\u3069)\u3002 {{}} ## {{% heading \"whatsnext\" %}} * Kubernetes\u30d6\u30ed\u30b0\u306e[\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u5229\u7528\u3057\u305f\u524a\u9664\u306e\u5236\u5fa1](/blog/2021/05/14/using-finalizers-to-control-deletion/)\u3092\u304a\u8aad\u307f\u304f\u3060\u3055\u3044\u3002 ", "commid": "website_pr_38768"}], "negative_passages": []} {"query_id": "q-en-website-543dce49c6cc8577a079b662afca34ab8deb7b8443227c66d6a4c8ffc4bbe640", "query": "This is a Feature Request Kubernetes\u306b\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u304c\u6307\u5b9a\u3055\u308c\u305f\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092\u524a\u9664\u3059\u308b\u3088\u3046\u306b\u6307\u793a\u3059\u308b\u3068\u3001Kubernetes API\u306f\u305d\u306e\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306b`.metadata.deletionTimestamp`\u3092\u8ffd\u52a0\u3057\u524a\u9664\u5bfe\u8c61\u3068\u3057\u3066\u30de\u30fc\u30af\u3057\u3066\u3001\u30b9\u30c6\u30fc\u30bf\u30b9\u30b3\u30fc\u30c9`202`(HTTP \"Accepted\")\u3092\u8fd4\u3057\u307e\u3059\u3002 \u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30d7\u30ec\u30fc\u30f3\u3084\u305d\u306e\u4ed6\u306e\u30b3\u30f3\u30dd\u30fc\u30cd\u30f3\u30c8\u304c\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306b\u3088\u3063\u3066\u5b9a\u7fa9\u3055\u308c\u305f\u30a2\u30af\u30b7\u30e7\u30f3\u3092\u5b9f\u884c\u3057\u3066\u3044\u308b\u9593\u3001\u5bfe\u8c61\u306e\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u306f\u7d42\u4e86\u4e2d\u306e\u72b6\u614b\u306e\u307e\u307e\u6b8b\u3063\u3066\u3044\u307e\u3059\u3002 \u305d\u308c\u3089\u306e\u30a2\u30af\u30b7\u30e7\u30f3\u304c\u5b8c\u4e86\u3057\u305f\u3089\u3001\u305d\u306e\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u306f\u95a2\u4fc2\u3057\u3066\u3044\u308b\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u5bfe\u8c61\u306e\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u304b\u3089\u524a\u9664\u3057\u307e\u3059\u3002 `metadata.finalizers`\u30d5\u30a3\u30fc\u30eb\u30c9\u304c\u7a7a\u306b\u306a\u3063\u305f\u3089\u3001Kubernetes\u306f\u524a\u9664\u304c\u5b8c\u4e86\u3057\u305f\u3068\u5224\u65ad\u3057\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3092\u524a\u9664\u3057\u307e\u3059\u3002 \u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u306f\u30ea\u30bd\u30fc\u30b9\u306e{{}}\u3092\u7ba1\u7406\u3059\u308b\u305f\u3081\u306b\u4f7f\u3046\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 \u4f8b\u3048\u3070\u3001\u30b3\u30f3\u30c8\u30ed\u30fc\u30e9\u30fc\u304c\u5bfe\u8c61\u306e\u30ea\u30bd\u30fc\u30b9\u3092\u524a\u9664\u3059\u308b\u524d\u306b\u95a2\u9023\u3059\u308b\u30ea\u30bd\u30fc\u30b9\u3084\u30a4\u30f3\u30d5\u30e9\u3092\u30af\u30ea\u30fc\u30f3\u30a2\u30c3\u30d7\u3059\u308b\u305f\u3081\u306b\u30d5\u30a1\u30a4\u30ca\u30e9\u30a4\u30b6\u30fc\u3092\u5b9a\u7fa9\u3059\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002 ", "commid": "website_pr_38768"}], "negative_passages": []} {"query_id": "q-en-website-1d9812d26b20b3685071055b84181ca22bc147b1e059c26cb6fae2e00354437f", "query": "reference:\n/assign\n/assign\nhello, can you please leave this this will be my first contributions towards open source. hope you don't mind.\nSure\n/unassign\n/triage accepted\n/kind documentation", "positive_passages": [{"docid": "doc-en-website-567e1378a89a28e6ec5c5c35e63be530f2584559b12c50298e0cbb3be746a52d", "text": "## Start a Kubelet process configured via the config file {{< note >}} If you use kubeadm to initialize your cluster, use the kubelet-config while creating your cluster with `kubeadmin init`. If you use kubeadm to initialize your cluster, use the kubelet-config while creating your cluster with `kubeadm init`. See [configuring kubelet using kubeadm](/docs/setup/production-environment/tools/kubeadm/kubelet-integration/) for details. {{< /note >}}", "commid": "website_pr_38656"}], "negative_passages": []} {"query_id": "q-en-website-543dce49c6cc8577a079b662afca34ab8deb7b8443227c66d6a4c8ffc4bbe640", "query": "This is a Feature Request Linux\u3067\u306f\u3001{{< glossary_tooltip text=\"\u30b3\u30f3\u30c8\u30ed\u30fc\u30eb\u30b0\u30eb\u30fc\u30d7\" term_id=\"cgroup\" >}}\u304c\u30d7\u30ed\u30bb\u30b9\u306b\u5272\u308a\u5f53\u3066\u3089\u308c\u308b\u30ea\u30bd\u30fc\u30b9\u3092\u5236\u9650\u3057\u3066\u3044\u307e\u3059\u3002 \u30b3\u30f3\u30c6\u30ca\u5316\u3055\u308c\u305f\u30ef\u30fc\u30af\u30ed\u30fc\u30c9\u306e\u3001CPU/\u30e1\u30e2\u30ea\u30fc\u306e\u8981\u6c42\u3068\u5236\u9650\u3092\u542b\u3080[Pod\u3068\u30b3\u30f3\u30c6\u30ca\u306e\u30ea\u30bd\u30fc\u30b9\u7ba1\u7406](/docs/concepts/configuration/manage-resources-containers/)\u3092\u5f37\u5236\u3059\u308b\u305f\u3081\u306b\u3001 {{< glossary_tooltip text=\"kubelet\" term_id=\"kubelet\" >}}\u3068\u57fa\u76e4\u3068\u306a\u308b\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u306fcgroup\u3092\u30a4\u30f3\u30bf\u30fc\u30d5\u30a7\u30fc\u30b9\u3068\u3057\u3066\u63a5\u7d9a\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002 Linux\u3067\u306fcgroup v1\u3068cgroup v2\u306e2\u3064\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u306ecgroup\u304c\u3042\u308a\u307e\u3059\u3002 cgroup v2\u306f\u65b0\u4e16\u4ee3\u306e`cgroup` API\u3067\u3059\u3002 ## cgroup v2\u3068\u306f\u4f55\u304b\uff1f {#cgroup-v2} {{< feature-state for_k8s_version=\"v1.25\" state=\"stable\" >}} cgroup v2\u306fLinux\u306e`cgroup` API\u306e\u6b21\u306e\u30d0\u30fc\u30b8\u30e7\u30f3\u3067\u3059\u3002 cgroup v2\u306f\u30ea\u30bd\u30fc\u30b9\u7ba1\u7406\u6a5f\u80fd\u3092\u5f37\u5316\u3057\u305f\u7d71\u5408\u5236\u5fa1\u30b7\u30b9\u30c6\u30e0\u3092\u63d0\u4f9b\u3057\u3066\u3044\u307e\u3059\u3002 \u4ee5\u4e0b\u306e\u3088\u3046\u306b\u3001cgroup v2\u306fcgroup v1\u304b\u3089\u3044\u304f\u3064\u304b\u306e\u70b9\u3092\u6539\u5584\u3057\u3066\u3044\u307e\u3059\u3002 - \u7d71\u5408\u3055\u308c\u305f\u5358\u4e00\u968e\u5c64\u8a2d\u8a08\u306eAPI - \u3088\u308a\u5b89\u5168\u306a\u30b3\u30f3\u30c6\u30ca\u3078\u306e\u30b5\u30d6\u30c4\u30ea\u30fc\u306e\u79fb\u8b72 - [Pressure Stall Information](https://www.kernel.org/doc/html/latest/accounting/psi.html)\u306a\u3069\u306e\u65b0\u6a5f\u80fd - \u5f37\u5316\u3055\u308c\u305f\u30ea\u30bd\u30fc\u30b9\u5272\u308a\u5f53\u3066\u7ba1\u7406\u3068\u8907\u6570\u30ea\u30bd\u30fc\u30b9\u9593\u306e\u9694\u96e2 - \u7570\u306a\u308b\u30bf\u30a4\u30d7\u306e\u30e1\u30e2\u30ea\u30fc\u5272\u308a\u5f53\u3066\u306e\u7d71\u4e00(\u30cd\u30c3\u30c8\u30ef\u30fc\u30af\u30e1\u30e2\u30ea\u30fc\u3001\u30ab\u30fc\u30cd\u30eb\u30e1\u30e2\u30ea\u30fc\u306a\u3069) - \u30da\u30fc\u30b8\u30ad\u30e3\u30c3\u30b7\u30e5\u306e\u66f8\u304d\u623b\u3057\u3068\u3044\u3063\u305f\u3001\u975e\u5373\u6642\u306e\u30ea\u30bd\u30fc\u30b9\u5909\u66f4 Kubernetes\u306e\u3044\u304f\u3064\u304b\u306e\u6a5f\u80fd\u3067\u306f\u3001\u5f37\u5316\u3055\u308c\u305f\u30ea\u30bd\u30fc\u30b9\u7ba1\u7406\u3068\u9694\u96e2\u306e\u305f\u3081\u306bcgroup v2\u306e\u307f\u3092\u4f7f\u7528\u3057\u3066\u3044\u307e\u3059\u3002 \u4f8b\u3048\u3070\u3001[MemoryQoS](/blog/2021/11/26/qos-memory-resources/)\u6a5f\u80fd\u306f\u30e1\u30e2\u30ea\u30fcQoS\u3092\u6539\u5584\u3057\u3001cgroup v2\u306e\u57fa\u672c\u7684\u306a\u6a5f\u80fd\u306b\u4f9d\u5b58\u3057\u3066\u3044\u307e\u3059\u3002 ## cgroup v2\u3092\u4f7f\u3046 {#using-cgroupv2} cgroup v2\u3092\u4f7f\u3046\u304a\u3059\u3059\u3081\u306e\u65b9\u6cd5\u306f\u3001\u30c7\u30d5\u30a9\u30eb\u30c8\u3067cgroup v2\u304c\u6709\u52b9\u3067\u4f7f\u3046\u3053\u3068\u304c\u3067\u304d\u308bLinux\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u3092\u4f7f\u3046\u3053\u3068\u3067\u3059\u3002 \u3042\u306a\u305f\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u304ccgroup v2\u3092\u4f7f\u3063\u3066\u3044\u308b\u304b\u3069\u3046\u304b\u3092\u78ba\u8a8d\u3059\u308b\u305f\u3081\u306b\u306f\u3001[Linux Node\u306ecgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u7279\u5b9a\u3059\u308b](#check-cgroup-version)\u3092\u53c2\u7167\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ### \u5fc5\u8981\u8981\u4ef6 {#requirements} cgroup v2\u3092\u4f7f\u3046\u306b\u306f\u4ee5\u4e0b\u306e\u3088\u3046\u306a\u5fc5\u8981\u8981\u4ef6\u304c\u3042\u308a\u307e\u3059\u3002 * OS\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u3067cgroup v2\u304c\u6709\u52b9\u3067\u3042\u308b\u3053\u3068 * Linux\u30ab\u30fc\u30cd\u30eb\u30d0\u30fc\u30b8\u30e7\u30f3\u304c5.8\u4ee5\u4e0a\u3067\u3042\u308b\u3053\u3068 * \u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u304ccgroup v2\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u308b\u3053\u3068\u3002\u4f8b\u3048\u3070\u3001 * [containerd](https://containerd.io/) v1.4\u4ee5\u964d * [cri-o](https://cri-o.io/) v1.20\u4ee5\u964d * kubelet\u3068\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0\u304c[systemd cgroup\u30c9\u30e9\u30a4\u30d0\u30fc](/docs/setup/production-environment/container-runtimes#systemd-cgroup-driver)\u3092\u4f7f\u3046\u3088\u3046\u306b\u8a2d\u5b9a\u3055\u308c\u3066\u3044\u308b\u3053\u3068 ### Linux\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u306ecgroup v2\u30b5\u30dd\u30fc\u30c8 cgroup v2\u3092\u4f7f\u3063\u3066\u3044\u308bLinux\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u306e\u4e00\u89a7\u306f[cgroup v2\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8](https://github.com/opencontainers/runc/blob/main/docs/cgroup-v2.md)\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002 * Container-Optimized OS (M97\u4ee5\u964d) * Ubuntu (21.10\u4ee5\u964d, 22.04\u4ee5\u964d\u63a8\u5968) * Debian GNU/Linux (Debian 11 bullseye\u4ee5\u964d) * Fedora (31\u4ee5\u964d) * Arch Linux (April 2021\u4ee5\u964d) * RHEL and RHEL-like distributions (9\u4ee5\u964d) \u3042\u306a\u305f\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u304ccgroup v2\u3092\u4f7f\u3063\u3066\u3044\u308b\u304b\u3069\u3046\u304b\u3092\u78ba\u8a8d\u3059\u308b\u305f\u3081\u306b\u306f\u3001\u3042\u306a\u305f\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u306e\u30c9\u30ad\u30e5\u30e1\u30f3\u30c8\u3092\u53c2\u7167\u3059\u308b\u304b\u3001[Linux Node\u306ecgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u7279\u5b9a\u3059\u308b](#check-cgroup-version)\u306e\u8aac\u660e\u306b\u5f93\u3063\u3066\u304f\u3060\u3055\u3044\u3002 \u30ab\u30fc\u30cd\u30eb\u306ecmdline\u306e\u8d77\u52d5\u6642\u5f15\u6570\u3092\u4fee\u6b63\u3059\u308b\u3053\u3068\u3067\u3001\u624b\u52d5\u3067\u3042\u306a\u305f\u306eLinux\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u306ecgroup v2\u3092\u6709\u52b9\u306b\u3059\u308b\u3053\u3068\u3082\u3067\u304d\u307e\u3059\u3002 \u3042\u306a\u305f\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u304cGRUB\u3092\u4f7f\u3063\u3066\u3044\u308b\u5834\u5408\u306f\u3001 `/etc/default/grub`\u306e\u4e2d\u306e`GRUB_CMDLINE_LINUX`\u306b`systemd.unified_cgroup_hierarchy=1`\u3092\u8ffd\u52a0\u3057\u3001`sudo update-grub`\u3092\u5b9f\u884c\u3057\u3066\u304f\u3060\u3055\u3044\u3002 \u305f\u3060\u3057\u3001\u304a\u3059\u3059\u3081\u306e\u65b9\u6cd5\u306f\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u3059\u3067\u306bcgroup v2\u304c\u6709\u52b9\u306b\u306a\u3063\u3066\u3044\u308b\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u3092\u4f7f\u3046\u3053\u3068\u3067\u3059\u3002 ### cgroup v2\u3078\u306e\u79fb\u884c {#migrating-cgroupv2} cgroup v2\u306b\u79fb\u884c\u3059\u308b\u306b\u306f\u3001[\u5fc5\u8981\u8981\u4ef6](#requirements)\u3092\u6e80\u305f\u3059\u3053\u3068\u3092\u78ba\u8a8d\u3057\u3001 cgroup v2\u304c\u30c7\u30d5\u30a9\u30eb\u30c8\u3067\u6709\u52b9\u3067\u3042\u308b\u30ab\u30fc\u30cd\u30eb\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u30a2\u30c3\u30d7\u30b0\u30ec\u30fc\u30c9\u3057\u307e\u3059\u3002 kubelet\u306fOS\u304ccgroup v2\u3067\u52d5\u4f5c\u3057\u3066\u3044\u308b\u3053\u3068\u3092\u81ea\u52d5\u7684\u306b\u691c\u51fa\u3057\u3001\u305d\u308c\u306b\u5fdc\u3058\u3066\u51e6\u7406\u3092\u884c\u3046\u305f\u3081\u3001\u8ffd\u52a0\u8a2d\u5b9a\u306f\u5fc5\u8981\u3042\u308a\u307e\u305b\u3093\u3002 \u30ce\u30fc\u30c9\u4e0a\u3084\u30b3\u30f3\u30c6\u30ca\u5185\u304b\u3089\u30e6\u30fc\u30b6\u30fc\u304c\u76f4\u63a5cgroup\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306b\u30a2\u30af\u30bb\u30b9\u3057\u306a\u3044\u9650\u308a\u3001cgroup v2\u306b\u5207\u308a\u66ff\u3048\u305f\u3068\u304d\u306e\u30e6\u30fc\u30b6\u30fc\u4f53\u9a13\u306b\u76ee\u7acb\u3063\u305f\u9055\u3044\u306f\u306a\u3044\u306f\u305a\u3067\u3059\u3002 cgroup v2\u306fcgroup v1\u3068\u306f\u9055\u3046API\u3092\u5229\u7528\u3057\u3066\u3044\u308b\u305f\u3081\u3001cgroup\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306b\u76f4\u63a5\u30a2\u30af\u30bb\u30b9\u3057\u3066\u3044\u308b\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3\u306fcgroup v2\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u308b\u65b0\u3057\u3044\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u66f4\u65b0\u3059\u308b\u5fc5\u8981\u304c\u3042\u308a\u307e\u3059\u3002\u4f8b\u3048\u3070\u3001 * \u30b5\u30fc\u30c9\u30d1\u30fc\u30c6\u30a3\u30fc\u306e\u76e3\u8996\u307e\u305f\u306f\u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u30a8\u30fc\u30b8\u30a7\u30f3\u30c8\u306fcgroup\u30d5\u30a1\u30a4\u30eb\u30b7\u30b9\u30c6\u30e0\u306b\u4f9d\u5b58\u3057\u3066\u3044\u308b\u3053\u3068\u304c\u3042\u308a\u307e\u3059\u3002 \u30a8\u30fc\u30b8\u30a7\u30f3\u30c8\u3092cgroup v2\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u308b\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u66f4\u65b0\u3057\u3066\u304f\u3060\u3055\u3044\u3002 * Pod\u3084\u30b3\u30f3\u30c6\u30ca\u3092\u76e3\u8996\u3059\u308b\u305f\u3081\u306b[cAdvisor](https://github.com/google/cadvisor)\u3092\u30b9\u30bf\u30f3\u30c9\u30a2\u30ed\u30fc\u30f3\u306eDaemonSet\u3068\u3057\u3066\u8d77\u52d5\u3057\u3066\u3044\u308b\u5834\u5408\u3001v0.43.0\u4ee5\u4e0a\u306b\u66f4\u65b0\u3057\u3066\u304f\u3060\u3055\u3044\u3002 * JDK\u3092\u5229\u7528\u3057\u3066\u3044\u308b\u5834\u5408\u3001[cgroup v2\u3092\u5b8c\u5168\u306b\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u308b](https://bugs.openjdk.org/browse/JDK-8230305)JDK 11.0.16\u4ee5\u964d\u3001\u307e\u305f\u306fJDK15\u4ee5\u964d\u3092\u5229\u7528\u3059\u308b\u3053\u3068\u304c\u671b\u307e\u3057\u3044\u3067\u3059\u3002 ## Linux Node\u306ecgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u7279\u5b9a\u3059\u308b {#check-cgroup-version} cgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u306f\u5229\u7528\u3055\u308c\u3066\u3044\u308bLinux\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u3068\u3001OS\u3067\u8a2d\u5b9a\u3055\u308c\u3066\u3044\u308b\u30c7\u30d5\u30a9\u30eb\u30c8\u306ecgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u306b\u4f9d\u5b58\u3057\u307e\u3059\u3002 \u3042\u306a\u305f\u306e\u30c7\u30a3\u30b9\u30c8\u30ea\u30d3\u30e5\u30fc\u30b7\u30e7\u30f3\u304c\u3069\u3061\u3089\u306ecgroup\u30d0\u30fc\u30b8\u30e7\u30f3\u3092\u5229\u7528\u3057\u3066\u3044\u308b\u306e\u304b\u3092\u78ba\u8a8d\u3059\u308b\u306b\u306f\u3001`stat -fc %T /sys/fs/cgroup/`\u30b3\u30de\u30f3\u30c9\u3092\u30ce\u30fc\u30c9\u4e0a\u3067\u5b9f\u884c\u3057\u3066\u304f\u3060\u3055\u3044\u3002 ```shell stat -fc %T /sys/fs/cgroup/ ``` cgroup v2\u3067\u306f\u3001`cgroup2fs`\u3068\u51fa\u529b\u3055\u308c\u307e\u3059\u3002 cgroup v1\u3067\u306f\u3001`tmpfs`\u3068\u51fa\u529b\u3055\u308c\u307e\u3059\u3002 ## {{% heading \"whatsnext\" %}} - [cgroups](https://man7.org/linux/man-pages/man7/cgroups.7.html)\u306b\u3064\u3044\u3066\u3082\u3063\u3068\u5b66\u7fd2\u3057\u307e\u3057\u3087\u3046\u3002 - [\u30b3\u30f3\u30c6\u30ca\u30e9\u30f3\u30bf\u30a4\u30e0](/ja/docs/concepts/architecture/cri)\u306b\u3064\u3044\u3066\u3082\u3063\u3068\u5b66\u7fd2\u3057\u307e\u3057\u3087\u3046\u3002 - [cgroup\u30c9\u30e9\u30a4\u30d0\u30fc](/docs/setup/production-environment/container-runtimes#cgroup-drivers)\u306b\u3064\u3044\u3066\u3082\u3063\u3068\u5b66\u7fd2\u3057\u307e\u3057\u3087\u3046\u3002 ", "commid": "website_pr_39085"}], "negative_passages": []} {"query_id": "q-en-website-48802673bcb1a5b7c6624b4fd0c4dc8f115a6aa4205dccae2bf428082bfd6daa", "query": "This is a Bug Report ", "commid": "website_pr_39168"}], "negative_passages": []} {"query_id": "q-en-website-48802673bcb1a5b7c6624b4fd0c4dc8f115a6aa4205dccae2bf428082bfd6daa", "query": "This is a Bug Report ", "commid": "website_pr_39168"}], "negative_passages": []} {"query_id": "q-en-website-8832f3c1d52762d5e12a743c053b754543b94e4473bd2230f8298c8f8f467cea", "query": "This is a Feature Request What would you like to be Add the commands which are under the Clean up section of the and tutorials into the shell code block snippet. Currently, it is under the triple backticks () as shown in the following screenshot: ! ! Which is not look more prominent. Why is this needed It provides a better structure to the section. and then it will be highlighted on the page. Comments None\nThis 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. Run `kind delete cluster --name psa-with-cluster-pss` and `kind delete cluster --name psa-wo-cluster-pss` to delete the clusters you created. Now delete the clusters which you created above by running the following command: ```shell kind delete cluster --name psa-with-cluster-pss ``` ```shell kind delete cluster --name psa-wo-cluster-pss ``` ## {{% heading \"whatsnext\" %}}", "commid": "website_pr_39065"}], "negative_passages": []} {"query_id": "q-en-website-8832f3c1d52762d5e12a743c053b754543b94e4473bd2230f8298c8f8f467cea", "query": "This is a Feature Request What would you like to be Add the commands which are under the Clean up section of the and tutorials into the shell code block snippet. Currently, it is under the triple backticks () as shown in the following screenshot: ! ! Which is not look more prominent. Why is this needed It provides a better structure to the section. and then it will be highlighted on the page. Comments None\nThis 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. Run `kind delete cluster --name psa-ns-level` to delete the cluster created. Now delete the cluster which you created above by running the following command: ```shell kind delete cluster --name psa-ns-level ``` ## {{% heading \"whatsnext\" %}}", "commid": "website_pr_39065"}], "negative_passages": []} {"query_id": "q-en-website-c427590bfe5872ba7ea2727992246cf4bc01ade4da5462dab563c71ae3046bdc", "query": "This is a Feature Request CEL expressions were originally documented for . When ValidationAdmissionPolicy was , the to the new API. We now multiple other enhancements (e.g. ) where the documentation would need to be duplicated. What would you like to be Instead of continuing to duplicate this documentation, resulting in documentation that will invariably drift and become inaccurate, let's instead introduce website documentation and link to it for all the documentation that is the same for all usages of CEL in Kubernetes. Website documentation will contain: escaping rules Kubernetes specific type information (e.g. equality) Libraries available What data is accessible to CEL expressions (e.g. ) API documentation of fields that contain CEL: What root variables are available in the specific context (e.g. \"object\" or \"self\") and what the variables provide access to What level of type safety is provided (full type checking, informational type checking, runtime only type checks?) Why is this needed Avoid API documentation inaccuracies and drift. Comments\nNeed to also document\n/sig api-machinery /sig docs /language en /triage accepted\nHow about a Reference page titled \u201cCEL in Kubernetes\u201d?\nIf we'd like a short docs URL, eg , that can be a thing (using a Netlify redirect with a temporarily moved status)\n/retitle Move CEL expression documentation from API documentation to website\nThe reference page idea is great. Once we get past enhancement freeze I'll open a PR.\nSIG API Machinery folks: what's your preferred priority for these docs?\nI intend to complete this for 1.27.\nStarting work on this now.", "positive_passages": [{"docid": "doc-en-website-4d4806e8ed7a60ee86ebb12caf39f55a3d278d32a13b4688e8e35f6c3dc341fc", "text": " --- title: Common Expression Language in Kubernetes reviewers: - jpbetz - cici37 content_type: concept weight: 35 min-kubernetes-server-version: 1.25 --- The [Common Expression Language (CEL)](https://github.com/google/cel-go) is used in the Kubernetes API to declare validation rules, policy rules, and other constraints or conditions. CEL expressions are evaluated directly in the {{< glossary_tooltip text=\"API server\" term_id=\"kube-apiserver\" >}}, making CEL a convenient alternative to out-of-process mechanisms, such as webhooks, for many extensibility use cases. Your CEL expressions continue to execute so long as the control plane's API server component remains available. ## Language overview The [CEL language](https://github.com/google/cel-spec/blob/master/doc/langdef.md) has a straightforward syntax that is similar to the expressions in C, C++, Java, JavaScript and Go. CEL was designed to be embedded into applications. Each CEL \"program\" is a single expression that evaluates to a single value. CEL expressions are typically short \"one-liners\" that inline well into the string fields of Kubernetes API resources. Inputs to a CEL program are \"variables\". Each Kubernetes API field that contains CEL declares in the API documentation which variables are available to use for that field. For example, in the `x-kubernetes-validations[i].rules` field of CustomResourceDefinitions, the `self` and `oldSelf` variables are available and refer to the previous and current state of the custom resource data to be validated by the CEL expression. Other Kubernetes API fields may declare different variables. See the API documentation of the API fields to learn which variables are available for that field. Example CEL expressions: {{< table caption=\"Examples of CEL expressions and the purpose of each\" >}} | Rule | Purpose | |------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| | `self.minReplicas <= self.replicas && self.replicas <= self.maxReplicas` | Validate that the three fields defining replicas are ordered appropriately | | `'Available' in self.stateCounts` | Validate that an entry with the 'Available' key exists in a map | | `(self.list1.size() == 0) != (self.list2.size() == 0)` | Validate that one of two lists is non-empty, but not both | | `self.envars.filter(e, e.name = 'MY_ENV').all(e, e.value.matches('^[a-zA-Z]*$')` | Validate the 'value' field of a listMap entry where key field 'name' is 'MY_ENV' | | `has(self.expired) && self.created + self.ttl < self.expired` | Validate that 'expired' date is after a 'create' date plus a 'ttl' duration | | `self.health.startsWith('ok')` | Validate a 'health' string field has the prefix 'ok' | | `self.widgets.exists(w, w.key == 'x' && w.foo < 10)` | Validate that the 'foo' property of a listMap item with a key 'x' is less than 10 | | `type(self) == string ? self == '99%' : self == 42` | Validate an int-or-string field for both the the int and string cases | | `self.metadata.name == 'singleton'` | Validate that an object's name matches a specific value (making it a singleton) | | `self.set1.all(e, !(e in self.set2))` | Validate that two listSets are disjoint | | `self.names.size() == self.details.size() && self.names.all(n, n in self.details)` | Validate the 'details' map is keyed by the items in the 'names' listSet | ## CEL community libraries Kubernetes CEL expressions have access to the following CEL community libraries: - CEL standard functions, defined in the [list of standard definitions](https://github.com/google/cel-spec/blob/master/doc/langdef.md#list-of-standard-definitions) - CEL standard [macros](https://github.com/google/cel-spec/blob/v0.7.0/doc/langdef.md#macros) - CEL [extended string function library](https://pkg.go.dev/github.com/google/cel-go/ext#Strings) ## Kubernetes CEL libraries In additional to the CEL community libraries, Kubernetes includes CEL libraries that are available everywhere CEL is used in Kubernetes. ### Kubernetes list library The list library includes `indexOf` and `lastIndexOf`, which work similar to the strings functions of the same names. These functions either the first or last positional index of the provided element in the list. The list library also includes `min`, `max` and `sum`. Sum is supported on all number types as well as the duration type. Min and max are supported on all comparable types. `isSorted` is also provided as a convenience function and is supported on all comparable types. Examples: {{< table caption=\"Examples of CEL expressions using list library functions\" >}} | CEL Expression | Purpose | |------------------------------------------------------------------------------------|-----------------------------------------------------------| | `names.isSorted()` | Verify that a list of names is kept in alphabetical order | | `items.map(x, x.weight).sum() == 1.0` | Verify that the \"weights\" of a list of objects sum to 1.0 | | `lowPriorities.map(x, x.priority).max() < highPriorities.map(x, x.priority).min()` | Verify that two sets of priorities do not overlap | | `names.indexOf('should-be-first') == 1` | Require that the first name in a list if a specific value | See the [Kubernetes List Library](https://pkg.go.dev/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/library#Lists) godoc for more information. ### Kubernetes regex library In addition to the `matches` function provided by the CEL standard library, the regex library provides `find` and `findAll`, enabling a much wider range of regex operations. Examples: {{< table caption=\"Examples of CEL expressions using regex library functions\" >}} | CEL Expression | Purpose | |-------------------------------------------------------------|----------------------------------------------------------| | `\"abc 123\".find('[0-9]*')` | Find the first number in a string | | `\"1, 2, 3, 4\".findAll('[0-9]*').map(x, int(x)).sum() < 100` | Verify that the numbers in a string sum to less than 100 | See the [Kubernetes regex library](https://pkg.go.dev/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/library#Regex) godoc for more information. ### Kubernetes URL library To make it easier and safer to process URLs, the following functions have been added: - `isURL(string)` checks if a string is a valid URL according to the [Go's net/url](https://pkg.go.dev/net/url#URL) package. The string must be an absolute URL. - `url(string) URL` converts a string to a URL or results in an error if the string is not a valid URL. Once parsed via the `url` function, the resulting URL object has `getScheme`, `getHost`, `getHostname`, `getPort`, `getEscapedPath` and `getQuery` accessors. Examples: {{< table caption=\"Examples of CEL expressions using URL library functions\" >}} | CEL Expression | Purpose | |-----------------------------------------------------------------|------------------------------------------------| | `url('https://example.com:80/').getHost()` | Get the 'example.com:80' host part of the URL. | | `url('https://example.com/path with spaces/').getEscapedPath()` | Returns '/path%20with%20spaces/' | See the [Kubernetes URL library](https://pkg.go.dev/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/library#URLs) godoc for more information. ## Type checking CEL is a [gradually typed language](https://github.com/google/cel-spec/blob/master/doc/langdef.md#gradual-type-checking). Some Kubernetes API fields contain fully type checked CEL expressions. For example, [CustomResourceDefinitions Validation Rules](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation-rules) are fully type checked. Some Kubernetes API fields contain partially type checked CEL expressions. A partially type checked expression is an experessions where some of the variables are statically typed but others are dynamically typed. For example, in the CEL expressions of [ValidatingAdmissionPolicies](/docs/reference/access-authn-authz/validating-admission-policy/) the `request` variable is typed, but the `object` variable is dynamically typed. As a result, an expression containing `request.namex` would fail type checking because the `namex` field is not defined. However, `object.namex` would pass type checking even when the `namex` field is not defined for the resource kinds that `object` refers to, because `object` is dynamically typed. The `has()` macro in CEL may be used in CEL expressions to check if a field of a dynamically typed variable is accessable before attempting to access the field's value. For example: ```cel has(object.namex) ? object.namex == 'special' : request.name == 'special' ``` ## Type system integration {{< table caption=\"Table showing the relationship between OpenAPIv3 types and CEL types\" >}} | OpenAPIv3 type | CEL type | |----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | 'object' with Properties | object / \"message type\" (`type()` evaluates to `selfType.path.to.object.from.self` | | 'object' with AdditionalProperties | map | | 'object' with x-kubernetes-embedded-type | object / \"message type\", 'apiVersion', 'kind', 'metadata.name' and 'metadata.generateName' are implicitly included in schema | | 'object' with x-kubernetes-preserve-unknown-fields | object / \"message type\", unknown fields are NOT accessible in CEL expression | | x-kubernetes-int-or-string | union of int or string, `self.intOrString < 100 || self.intOrString == '50%'` evaluates to true for both `50` and `\"50%\"` | | 'array | list | | 'array' with x-kubernetes-list-type=map | list with map based Equality & unique key guarantees | | 'array' with x-kubernetes-list-type=set | list with set based Equality & unique entry guarantees | | 'boolean' | boolean | | 'number' (all formats) | double | | 'integer' (all formats) | int (64) | | _no equivalent_ | uint (64) | | 'null' | null_type | | 'string' | string | | 'string' with format=byte (base64 encoded) | bytes | | 'string' with format=date | timestamp (google.protobuf.Timestamp) | | 'string' with format=datetime | timestamp (google.protobuf.Timestamp) | | 'string' with format=duration | duration (google.protobuf.Duration) | Also see: [CEL types](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#values), [OpenAPI types](https://swagger.io/specification/#data-types), [Kubernetes Structural Schemas](/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#specifying-a-structural-schema). Equality comparison for arrays with `x-kubernetes-list-type` of `set` or `map` ignores element order. For example `[1, 2] == [2, 1]` if the arrays represent Kubernetes `set` values. Concatenation on arrays with `x-kubernetes-list-type` use the semantics of the list type: - `set`: `X + Y` performs a union where the array positions of all elements in `X` are preserved and non-intersecting elements in `Y` are appended, retaining their partial order. - `map`: `X + Y` performs a merge where the array positions of all keys in `X` are preserved but the values are overwritten by values in `Y` when the key sets of `X` and `Y` intersect. Elements in `Y` with non-intersecting keys are appended, retaining their partial order. ## Escaping Only Kubernetes resource property names of the form `[a-zA-Z_.-/][a-zA-Z0-9_.-/]*` are accessible from CEL. Accessible property names are escaped according to the following rules when accessed in the expression: {{< table caption=\"Table of CEL identifier escaping rules\" >}} | escape sequence | property name equivalent | |-------------------|----------------------------------------------------------------------------------------------| | `__underscores__` | `__` | | `__dot__` | `.` | | `__dash__` | `-` | | `__slash__` | `/` | | `__{keyword}__` | [CEL **RESERVED** keyword](https://github.com/google/cel-spec/blob/v0.6.0/doc/langdef.md#syntax) | When you escape any of CEL's **RESERVED** keywords you need to match the exact property name use the underscore escaping (for example, `int` in the word `sprint` would not be escaped and nor would it need to be). Examples on escaping: {{< table caption=\"Examples escaped CEL identifiers\" >}} | property name | rule with escaped property name | |---------------|-----------------------------------| | `namespace` | `self.__namespace__ > 0` | | `x-prop` | `self.x__dash__prop > 0` | | `redact__d` | `self.redact__underscores__d > 0` | | `string` | `self.startsWith('kube')` | ## Resource constraints CEL is non-Turing complete and offers a variety of production safety controls to limit execution time. CEL's _resource constraint_ features provide feedback to developers about expression complexity and help protect the API server from excessive resource consumption during evaluation. CEL's resource constraint features are used to prevent CEL evaluation from consuming excessive API server resources. A key element of the resource constraint features is a _cost unit_ that CEL defines as a way of tracking CPU utilization. Cost units are independant of system load and hardware. Cost units are also deterministic; for any given CEL expression and input data, evaluation of the expression by the CEL interpreter will always result in the same cost. Many of CEL's core operations have fixed costs. The simplest operations, such as comparisons (e.g. `<`) have a cost of 1. Some have a higher fixed cost, for example list literal declarations have a fixed base cost of 40 cost units. Calls to functions implemented in native code approximate cost based on the time complexity of the operation. For example: operations that use regular expressions, such as `match` and `find`, are estimated using an approximated cost of `length(regexString)*length(inputString)`. The approximated cost reflects the worst case time complexity of Go's RE2 implementation. ### Runtime cost budget All CEL expressions evaluated by Kubernetes are constrained by a runtime cost budget. The runtime cost budget is an estimate of actual CPU utilization computed by incrementing a cost unit counter while interpreting a CEL expression. If the CEL interpreter executes too many instructions, the runtime cost budget will be exceeded, execution of the expressions will be halted, and an error will result. Some Kubernetes resources define an additional runtime cost budget that bounds the execution of multiple expressions. If the sum total of the cost of expressions exceed the budget, execution of the expressions will be halted, and an error will result. For example the validation of a custom resource has a _per-validation_ runtime cost budget for all [Validation Rules](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#validation-rules) evaluated to validate the custom resource. ### Estimated cost limits For some Kubernetes resources, the API server may also check if worst case estimated running time of CEL expressions would be prohibitively expensive to execute. If so, the API server prevent the CEL expression from being written to API resources by rejecting create or update operations containing the CEL expression to the API resources. This feature offers a stronger assurance that CEL expressions written to the API resource will be evaluate at runtime without exceeding the runtime cost budget. No newline at end of file", "commid": "website_pr_39642"}], "negative_passages": []} {"query_id": "q-en-website-b477db53a8daa4eade7e0cbdc389229cf993f88deb1955a6a7dd14e485f64f62", "query": "The docs on currently make no mention of field validation. Now that of unknown and duplicate fields is graduating to GA, we should mention it briefly here.\n/cc\n/triage accepted\n/wg api-expression /language en /priority important-longterm /sig api-machinery\n/assign", "positive_passages": [{"docid": "doc-en-website-13af63160d93b3b05205466903a5d24ac73b646bbaef7b5d78f35bac8f400493", "text": "Different kinds of object can also have different `.status`; again, the API reference pages detail the structure of that `.status` field, and its content for each different type of object. ## Server side field validation Starting with Kubernetes v1.25, the API server offers server side [field validation](/docs/reference/using-api/api-concepts/#field-validation) that detects unrecognized or duplicate fields in an object. It provides all the functionality of `kubectl --validate` on the server side. The `kubectl` tool uses the `--validate` flag to set the level of field validation. It accepts the values `ignore`, `warn`, and `strict` while also accepting the values `true` (equivalent to `strict`) and `false` (equivalent to `ignore`). The default validation setting for `kubectl` is `--validate=true`. `Strict` : Strict field validation, errors on validation failure `Warn` : Field validation is performed, but errors are exposed as warnings rather than failing the request `Ignore` : No server side field validation is performed When `kubectl` cannot connect to an API server that supports field validation it will fall back to using client-side validation. Kubernetes 1.27 and later versions always offer field validation; older Kubernetes releases might not. If your cluster is older than v1.27, check the documentation for your version of Kubernetes. ## {{% heading \"whatsnext\" %}} If you're new to Kubernetes, read more about the following:", "commid": "website_pr_41094"}], "negative_passages": []} {"query_id": "q-en-website-b50f3e957d5d1e5cb22c3eda4f6f5f5e506a70d1592f4359d69452258236334a", "query": "This is a Bug Report Make network services available by using an extensible, role-oriented, protocol-aware configuration mechanism. [Gateway API](https://gateway-api.sigs.k8s.io/) is an {{}} containing API [kinds](https://gateway-api.sigs.k8s.io/references/spec/) that provide dynamic infrastructure provisioning and advanced traffic routing. ## Design principles The following principles shaped the design and architecture of Gateway API: * __Role-oriented:__ Gateway API kinds are modeled after organizational roles that are responsible for managing Kubernetes service networking: * __Infrastructure Provider:__ Manages infrastructure that allows multiple isolated clusters to serve multiple tenants, e.g. a cloud provider. * __Cluster Operator:__ Manages clusters and is typically concerned with policies, network access, application permissions, etc. * __Application Developer:__ Manages an application running in a cluster and is typically concerned with application-level configuration and [Service](/docs/concepts/services-networking/service/) composition. * __Portable:__ Gateway API specifications are defined as [custom resources](docs/concepts/extend-kubernetes/api-extension/custom-resources) and are supported by many [implementations](https://gateway-api.sigs.k8s.io/implementations/). * __Expressive:__ Gateway API kinds support functionality for common traffic routing use cases such as header-based matching, traffic weighting, and others that were only possible in [Ingress](/docs/concepts/services-networking/ingress/) by using custom annotations. * __Extensible:__ Gateway allows for custom resources to be linked at various layers of the API. This makes granular customization possible at the appropriate places within the API structure. ## Resource model Gateway API has three stable API kinds: * __GatewayClass:__ Defines a set of gateways with common configuration and managed by a controller that implements the class. * __Gateway:__ Defines an instance of traffic handling infrastructure, such as cloud load balancer. * __HTTPRoute:__ Defines HTTP-specific rules for mapping traffic from a Gateway listener to a representation of backend network endpoints. These endpoints are often represented as a {{}}. Gateway API is organized into different API kinds that have interdependent relationships to support the role-oriented nature of organizations. A Gateway object is associated with exactly one GatewayClass; the GatewayClass describes the gateway controller responsible for managing Gateways of this class. One or more route kinds such as HTTPRoute, are then associated to Gateways. A Gateway can filter the routes that may be attached to its `listeners`, forming a bidirectional trust model with routes. The following figure illustrates the relationships of the three stable Gateway API kinds: {{< figure src=\"/docs/images/gateway-kind-relationships.svg\" alt=\"A figure illustrating the relationships of the three stable Gateway API kinds\" class=\"diagram-medium\" >}} ### GatewayClass {#api-kind-gateway-class} Gateways can be implemented by different controllers, often with different configurations. A Gateway must reference a GatewayClass that contains the name of the controller that implements the class. A minimal GatewayClass example: ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: GatewayClass metadata: name: example-class spec: controllerName: example.com/gateway-controller ``` In this example, a controller that has implemented Gateway API is configured to manage GatewayClasses with the controller name `example.com/gateway-controller`. Gateways of this class will be managed by the implementation's controller. See the [GatewayClass](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.GatewayClass) reference for a full definition of this API kind. ### Gateway {#api-kind-gateway} A Gateway describes an instance of traffic handling infrastructure. It defines a network endpoint that can be used for processing traffic, i.e. filtering, balancing, splitting, etc. for backends such as a Service. For example, a Gateway may represent a cloud load balancer or an in-cluster proxy server that is configured to accept HTTP traffic. A minimal Gateway resource example: ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: example-gateway spec: gatewayClassName: example-class listeners: - name: http protocol: HTTP port: 80 ``` In this example, an instance of traffic handling infrastructure is programmed to listen for HTTP traffic on port 80. Since the `addresses` field is unspecified, an address or hostname is assigned to the Gateway by the implementation's controller. This address is used as a network endpoint for processing traffic of backend network endpoints defined in routes. See the [Gateway](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.Gateway) reference for a full definition of this API kind. ### HTTPRoute {#api-kind-httproute} The HTTPRoute kind specifies routing behavior of HTTP requests from a Gateway listener to backend network endpoints. For a Service backend, an implementation may represent the backend network endpoint as a Service IP or the backing Endpoints of the Service. An HTTPRoute represents configuration that is applied to the underlying Gateway implementation. For example, defining a new HTTPRoute may result in configuring additional traffic routes in a cloud load balancer or in-cluster proxy server. A minimal HTTPRoute example: ```yaml apiVersion: gateway.networking.k8s.io/v1 kind: HTTPRoute metadata: name: example-httproute spec: parentRefs: - name: example-gateway hostnames: - \"www.example.com\" rules: - matches: - path: type: PathPrefix value: /login backendRefs: - name: example-svc port: 8080 ``` In this example, HTTP traffic from Gateway `example-gateway` with the Host: header set to `www.example.com` and the request path specified as `/login` will be routed to Service `example-svc` on port `8080`. See the [HTTPRoute](https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1.HTTPRoute) reference for a full definition of this API kind. ## Request flow Here is a simple example of HTTP traffic being routed to a Service by using a Gateway and an HTTPRoute: {{< figure src=\"/docs/images/gateway-request-flow.svg\" alt=\"A diagram that provides an example of HTTP traffic being routed to a Service by using a Gateway and an HTTPRoute\" class=\"diagram-medium\" >}} In this example, the request flow for a Gateway implemented as a reverse proxy is: 1. The client starts to prepare an HTTP request for the URL `http://www.example.com` 2. The client's DNS resolver queries for the destination name and learns a mapping to one or more IP addresses associated with the Gateway. 3. The client sends a request to the Gateway IP address; the reverse proxy receives the HTTP request and uses the Host: header to match a configuration that was derived from the Gateway and attached HTTPRoute. 4. Optionally, the reverse proxy can perform request header and/or path matching based on match rules of the HTTPRoute. 5. Optionally, the reverse proxy can modify the request; for example, to add or emove headers, based on filter rules of the HTTPRoute. 6. Lastly, the reverse proxy forwards the request to one or more backends. ## Conformance Gateway API covers a broad set of features and is widely implemented. This combination requires clear conformance definitions and tests to ensure that the API provides a consistent experience wherever it is used. See the [conformance](https://gateway-api.sigs.k8s.io/concepts/conformance/) documentation to understand details such as release channels, support levels, and running conformance tests. ## Migrating from Ingress Gateway API is the successor to the [Ingress](/docs/concepts/services-networking/ingress/) API. However, it does not include the Ingress kind. As a result, a one-time conversion from your existing Ingress resources to Gateway API resources is necessary. Refer to the [ingress migration](https://gateway-api.sigs.k8s.io/guides/migrating-from-ingress/#migrating-from-ingress) guide for details on migrating Ingress resources to Gateway API resources. ## {{% heading \"whatsnext\" %}} Instead of Gateway API resources being natively implemented by Kubernetes, the specifications are defined as [Custom Resources](docs/concepts/extend-kubernetes/api-extension/custom-resources) supported by a wide range of [implementations](https://gateway-api.sigs.k8s.io/implementations/). [Install](https://gateway-api.sigs.k8s.io/guides/#installing-gateway-api) the Gateway API CRDs or follow the installation instructions of your selected implementation. After installing an implementation, use the [Getting Started](https://gateway-api.sigs.k8s.io/guides/) guide to help you quickly start working with Gateway API. {{< note >}} Make sure to review the documentation of your selected implementation to understand any caveats. {{< /note >}} Refer to the [API specification](https://gateway-api.sigs.k8s.io/reference/spec/) for additional details of all Gateway API kinds. ", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1", "query": "This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see", "positive_passages": [{"docid": "doc-en-website-a3a55de52e73a7c2c8e2ab90634394374f61f7b708e2ae999d711b8b5b94cc72", "text": "{{< feature-state for_k8s_version=\"v1.19\" state=\"stable\" >}} {{< glossary_definition term_id=\"ingress\" length=\"all\" >}} {{< note >}} Ingress is frozen. New features are being added to the [Gateway API](/docs/concepts/services-networking/gateway/). {{< /note >}} ## Terminology", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1", "query": "This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see", "positive_passages": [{"docid": "doc-en-website-a94fe4231fd770e7e8f3e8c513178271090cb6dc75717af2b80d4838fbf3f482", "text": "* Read about [Ingress](/docs/concepts/services-networking/ingress/), which exposes HTTP and HTTPS routes from outside the cluster to Services within your cluster. * Read about [Gateway](https://gateway-api.sigs.k8s.io/), an extension to * Read about [Gateway](/docs/concepts/services-networking/gateway/), an extension to Kubernetes that provides more flexibility than Ingress. For more context, read the following:", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1", "query": "This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see", "positive_passages": [{"docid": "doc-en-website-8bdf1321df8a453fb7ea987114531581630f4874cfbdc8daeef2787af164a770", "text": "
    cluster
    GatewayClass
    Gateway
    HTTPRoute
         No newline at end of file", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1", "query": "This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see", "positive_passages": [{"docid": "doc-en-website-9dffc8197ebd66b2870fd87f610ab62847e37e642a4ea17f5556f7583a7b0a42", "text": " No newline at end of file", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-b93a7193ccb4472f8870115052311cf4aa4ea4fbd861ca216edb32e2c4b35fb1", "query": "This is a Feature Request What would you like to be High level documentation for Gateway API with links out to https://gateway- This should include the following: new \"Gateway API\" page between Service and Ingress in This should provide a high level overview of Gateway API, with a focus on content that is unlikely to become stale. This can likely take some content from both https://gateway- and https://gateway- and would help increase the discoverability of Gateway API. the \"Ingress\" page to note that the API is effectively frozen and all new features are being to Gateway API (with a corresponding link to the page by 1). the section on the \"Service\" page that references Ingress and Gateway API to give more prominence to Gateway API. Why is this needed With the upcoming graduation of Gateway API to GA (x-ref ), it's past time to cover it in Kubernetes docs. Comments I'd previously talked with about this at a high level, but definitely let me know if you've got any suggestions for how we can scope/adjust this differently. /sig network /assign\ncheckout the gateway API in the section and look out for the bugs\n/triage accepted /priority important-longterm\nHow about adding a short link eg that redirects (302) to https://gateway- ?\nI'd put Service, Ingress, then Gateway - and leave it in that order until most new clusters include Gateway as an add-on.\nAlso see", "positive_passages": [{"docid": "doc-en-website-25a0f1c6b2ebaffe218c8e172ced51a3ae37b810f351c4f02a08d8fec8389856", "text": " --- title: Gateway API id: gateway-api date: 2023-10-19 full_link: /docs/concepts/services-networking/gateway/ short_description: > An API for modeling service networking in Kubernetes. aka: tags: - networking - architecture - extension --- A family of API kinds for modeling service networking in Kubernetes. Gateway API provides a family of extensible, role-oriented, protocol-aware API kinds for modeling service networking in Kubernetes. ", "commid": "website_pr_43621"}], "negative_passages": []} {"query_id": "q-en-website-78a0c1802b897b0651a8e86e46745f88bc205a8705c6211e9b59a67defd1ab60", "query": "This is a Feature Request In Kubernetes, you can _scale_ a workload depending on the current demand of resources. This allows your cluster to react to changes in resource demand more elastically and efficiently. When you scale a workload, you can either increase or decrease the number of replicas managed by the workload, or adjust the resources available to the replicas in-place. The first approach is referred to as _horizontal scaling_, while the second is referred to as _vertical scaling_. There are manual and automatic ways to scale your workloads, depending on your use case. ## Scaling workloads manually Kubernetes supports _manual scaling_ of workloads. Horizontal scaling can be done using the `kubectl` CLI. For vertical scaling, you need to _patch_ the resource definition of your workload. See below for examples of both strategies. - **Horizontal scaling**: [Running multiple instances of your app](/docs/tutorials/kubernetes-basics/scale/scale-intro/) - **Vertical scaling**: [Resizing CPU and memory resources assigned to containers](/docs/tasks/configure-pod-container/resize-container-resources) ## Scaling workloads automatically Kubernetes also supports _automatic scaling_ of workloads, which is the focus of this page. The concept of _Autoscaling_ in Kubernetes refers to the ability to automatically update an object that manages a set of Pods (for example a {{< glossary_tooltip text=\"Deployment\" term_id=\"deployment\" >}}. ### Scaling workloads horizontally In Kubernetes, you can automatically scale a workload horizontally using a _HorizontalPodAutoscaler_ (HPA). It is implemented as a Kubernetes API resource and a {{< glossary_tooltip text=\"controller\" term_id=\"controller\" >}} and periodically adjusts the number of {{< glossary_tooltip text=\"replicas\" term_id=\"replica\" >}} in a workload to match observed resource utilization such as CPU or memory usage. There is a [walkthrough tutorial](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough) of configuring a HorizontalPodAutoscaler for a Deployment. ### Scaling workloads vertically {{< feature-state for_k8s_version=\"v1.25\" state=\"stable\" >}} You can automatically scale a workload vertically using a _VerticalPodAutoscaler_ (VPA). Different to the HPA, the VPA doesn't come with Kubernetes by default, but is a separate project that can be found [on GitHub](https://github.com/kubernetes/autoscaler/tree/9f87b78df0f1d6e142234bb32e8acbd71295585a/vertical-pod-autoscaler). Once installed, it allows you to create {{< glossary_tooltip text=\"CustomResourceDefinitions\" term_id=\"customresourcedefinition\" >}} (CRDs) for your workloads which define _how_ and _when_ to scale the resources of the managed replicas. {{< note >}} You will need to have the [Metrics Server](https://github.com/kubernetes-sigs/metrics-server) installed to your cluster for the HPA to work. {{< /note >}} At the moment, the VPA can operate in four different modes: {{< table caption=\"Different modes of the VPA\" >}} Mode | Description :----|:----------- `Auto` | Currently `Recreate`, might change to in-place updates in the future `Recreate` | The VPA assigns resource requests on pod creation as well as updates them on existing pods by evicting them when the requested resources differ significantly from the new recommendation `Initial` | The VPA only assigns resource requests on pod creation and never changes them later. `Off` | The VPA does not automatically change the resource requirements of the pods. The recommendations are calculated and can be inspected in the VPA object. {{< /table >}} #### Requirements for in-place resizing {{< feature-state for_k8s_version=\"v1.27\" state=\"alpha\" >}} Resizing a workload in-place **without** restarting the {{< glossary_tooltip text=\"Pods\" term_id=\"pod\" >}} or its {{< glossary_tooltip text=\"Containers\" term_id=\"container\" >}} requires Kubernetes version 1.27 or later.
    Additionally, the `InPlaceVerticalScaling` feature gate needs to be enabled. {{< feature-gate-description name=\"InPlacePodVerticalScaling\" >}} ### Autoscaling based on cluster size For workloads that need to be scaled based on the size of the cluster (for example `cluster-dns` or other system components), you can use the _Cluster Proportional Autoscaler_.
    Just like the VPA, it is not part of the Kubernetes core, but hosted in its own repository [on GitHub](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler). The Cluster Proportional Autoscaler watches the number of schedulable {{< glossary_tooltip text=\"nodes\" term_id=\"node\" >}} and cores and scales the number of replicas of the target workload accordingly. ### Event driven Autoscaling It is also possible to scale workloads based on events, for example using the [_Kubernetes Event Driven Autoscaler_ (**KEDA**)](https://keda.sh/). KEDA is a CNCF graduated enabling you to scale your workloads based on the number of events to be processed, for example the amount of messages in a queue. There exists a wide range of adapters for different event sources to choose from. ### Autoscaling based on schedules Another strategy for scaling your workloads is to **schedule** the scaling operations, for example in order to reduce resource consumption during off-peak hours. Similar to event driven autoscaling, such behavior can be achieved using KEDA in conjunction with its [`Cron` scaler](https://keda.sh/docs/2.13/scalers/cron/). The `Cron` scaler allows you to define schedules (and time zones) for scaling your workloads in or out. ## Scaling cluster infrastructure If scaling workloads isn't enough to meet your needs, you can also scale your cluster infrastructure itself. Scaling the cluster infrastructure normally means adding or removing {{< glossary_tooltip text=\"nodes\" term_id=\"node\" >}}. This can be done using one of two available autoscalers: - [**Cluster Autoscaler**](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler) - [**Karpenter**](https://github.com/kubernetes-sigs/karpenter?tab=readme-ov-file) Both scalers work by watching for pods marked as _unschedulable_ or _underutilized_ nodes and then adding or removing nodes as needed. ## {{% heading \"whatsnext\" %}} - Learn more about scaling horizontally - [Scale a StatefulSet](/docs/tasks/run-application/scale-stateful-set/) - [HorizontalPodAutoscaler Walkthrough](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/) - [Resize Container Resources In-Place](/docs/tasks/configure-pod-container/resize-container-resources/) - [Autoscale the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/) ", "commid": "website_pr_44959"}], "negative_passages": []} {"query_id": "q-en-website-294bf34ec688d7f154f12ae076aa7df8a9009536b82d434f04217f7fda23237b", "query": "This is a Bug Report Problem: The link for in is incorrect. It is redirecting to but it should redirect to Proposed Solution: should redirect to instead of\n/sig docs /kind bug\nPage related to the issue:\n/language en\nI would to like to solve this issue if triage gets accepted.\n/triage accepted\n/assign\nThe issue is fixed here:", "positive_passages": [{"docid": "doc-en-website-baf563b1a37db6ba47190962ddbaff1d127f1391e99287fcb315db48456402e5", "text": "You can use {{< glossary_tooltip term_id=\"containerd\" text=\"ContainerD\" >}} 1.4.0+ as the container runtime for Kubernetes nodes that run Windows. Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#install-containerd). Learn how to [install ContainerD on a Windows node](/docs/setup/production-environment/container-runtimes/#containerd). {{< note >}} There is a [known limitation](/docs/tasks/configure-pod-container/configure-gmsa/#gmsa-limitations) when using GMSA with containerd to access Windows network shares, which requires a", "commid": "website_pr_44150"}], "negative_passages": []} {"query_id": "q-en-website-365e9687894267021dc2445e25427204970c928fe4b20e1383fe4bcf2eb81912", "query": "This is a Bug Report This page explains how to add Linux worker nodes to a kubeadm cluster. ## {{% heading \"prerequisites\" %}} * Each joining worker node has installed the required components from [Installing kubeadm](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/), such as, kubeadm, the kubelet and a {{< glossary_tooltip term_id=\"container-runtime\" text=\"container runtime\" >}}. * A running kubeadm cluster created by `kubeadm init` and following the steps in the document [Creating a cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/). * You need superuser access to the node. ## Adding Linux worker nodes To add new Linux worker nodes to your cluster do the following for each machine: 1. Connect to the machine by using SSH or another method. 1. Run the command that was output by `kubeadm init`. For example: ```bash sudo kubeadm join --token : --discovery-token-ca-cert-hash sha256: ``` ### Additional information for kubeadm join {{< note >}} To specify an IPv6 tuple for `:`, IPv6 address must be enclosed in square brackets, for example: `[2001:db8::101]:2073`. {{< /note >}} If you do not have the token, you can get it by running the following command on the control plane node: ```bash sudo kubeadm token list ``` The output is similar to this: ```console TOKEN TTL EXPIRES USAGES DESCRIPTION EXTRA GROUPS 8ewj1p.9r9hcjoqgajrj4gi 23h 2018-06-12T02:51:28Z authentication, The default bootstrap system: signing token generated by bootstrappers: 'kubeadm init'. kubeadm: default-node-token ``` By default, node join tokens expire after 24 hours. If you are joining a node to the cluster after the current token has expired, you can create a new token by running the following command on the control plane node: ```bash sudo kubeadm token create ``` The output is similar to this: ```console 5didvk.d09sbcov8ph2amjw ``` If you don't have the value of `--discovery-token-ca-cert-hash`, you can get it by running the following commands on the control plane node: ```bash sudo cat /etc/kubernetes/pki/ca.crt | openssl x509 -pubkey | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //' ``` The output is similar to: ```console 8cb2de97839780a412b93877f8507ad6c94f73add17d5d7058e91741c9d5ec78 ``` The output of the `kubeadm join` command should look something like: ``` [preflight] Running pre-flight checks ... (log output of join workflow) ... Node join complete: * Certificate signing request sent to control-plane and response received. * Kubelet informed of new secure connection details. Run 'kubectl get nodes' on control-plane to see this machine join. ``` A few seconds later, you should notice this node in the output from `kubectl get nodes`. (for example, run `kubectl` on a control plane node). {{< note >}} As the cluster nodes are usually initialized sequentially, the CoreDNS Pods are likely to all run on the first control plane node. To provide higher availability, please rebalance the CoreDNS Pods with `kubectl -n kube-system rollout restart deployment coredns` after at least one new node is joined. {{< /note >}} ## {{% heading \"whatsnext\" %}} * See how to [add Windows worker nodes](/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes/). ", "commid": "website_pr_47888"}], "negative_passages": []} {"query_id": "q-en-website-9b20aa1d7b434b6ac5dc76003bcd629434c04ffb8329fb9aad9a9c3dc9870747", "query": "Please note: This issue is not suitable for new contributors since you need some familiarity with how Kubernetes works. The Kubernetes website currently lacks a guide on creating Windows/Linux nodes. See for more details. SIG Windows opted to remove the guide that did exist for creating Windows nodes, in PR Write a new task page about creating nodes for all operating systems. This could, potentially, be in a tabbed format as mentions in the issue referenced above. We would also need the entry reflected on the creates the Linux task page by moving / refactoring the existing \"join node\" contents from the \"create a cluster\" page: creates the Windows task page by taking the content from at the end of the Windows page we add note/disclaimer whatever that says that CNI on Windows needs special handling and we link to the various CNI choices at: adds tabs in the to choose between OS for joining nodes. /priority backlog /help\nThis request has been marked as needing help from a contributor. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. --- title: Adding Windows worker nodes content_type: task weight: 50 --- This page explains how to add Windows worker nodes to a kubeadm cluster. ## {{% heading \"prerequisites\" %}} * A running [Windows Server 2022](https://www.microsoft.com/cloud-platform/windows-server-pricing) (or higher) instance with administrative access. * A running kubeadm cluster created by `kubeadm init` and following the steps in the document [Creating a cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/). ## Adding Windows worker nodes {{< note >}} To facilitate the addition of Windows worker nodes to a cluster, PowerShell scripts from the repository https://sigs.k8s.io/sig-windows-tools are used. {{< /note >}} Do the following for each machine: 1. Open a PowerShell session on the machine. 1. Make sure you are Administrator or a privileged user. Then proceed with the steps outlined below. ### Install containerd {{% thirdparty-content %}} To install containerd, first run the following command: ```PowerShell curl.exe -LO https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/hostprocess/Install-Containerd.ps1 `````` Then run the following command, but first replace `CONTAINERD_VERSION` with a recent release from the [containerd repository](https://github.com/containerd/containerd/releases). The version must not have a `v` prefix. For example, use `1.7.22` instead of `v1.7.22`: ```PowerShell .Install-Containerd.ps1 -ContainerDVersion CONTAINERD_VERSION ``` * Adjust any other parameters for `Install-Containerd.ps1` such as `netAdapterName` as you need them. * Set `skipHypervisorSupportCheck` if your machine does not support Hyper-V and cannot host Hyper-V isolated containers. * If you change the `Install-Containerd.ps1` optional parameters `CNIBinPath` and/or `CNIConfigPath` you will need to configure the installed Windows CNI plugin with matching values. ### Install kubeadm and kubelet Run the following commands to install kubeadm and the kubelet: ```PowerShell curl.exe -LO https://raw.githubusercontent.com/kubernetes-sigs/sig-windows-tools/master/hostprocess/PrepareNode.ps1 .PrepareNode.ps1 -KubernetesVersion v{{< skew currentVersion >}} ``` * Adjust the parameter `KubernetesVersion` of `PrepareNode.ps1` if needed. ### Run `kubeadm join` Run the command that was output by `kubeadm init`. For example: ```bash kubeadm join --token : --discovery-token-ca-cert-hash sha256: ``` #### Additional information about kubeadm join {{< note >}} To specify an IPv6 tuple for `:`, IPv6 address must be enclosed in square brackets, for example: `[2001:db8::101]:2073`. {{< /note >}} If you do not have the token, you can get it by running the following command on the control plane node: ```bash kubeadm token list ``` The output is similar to this: ```console TOKEN TTL EXPIRES USAGES DESCRIPTION EXTRA GROUPS 8ewj1p.9r9hcjoqgajrj4gi 23h 2018-06-12T02:51:28Z authentication, The default bootstrap system: signing token generated by bootstrappers: 'kubeadm init'. kubeadm: default-node-token ``` By default, node join tokens expire after 24 hours. If you are joining a node to the cluster after the current token has expired, you can create a new token by running the following command on the control plane node: ```bash kubeadm token create ``` The output is similar to this: ```console 5didvk.d09sbcov8ph2amjw ``` If you don't have the value of `--discovery-token-ca-cert-hash`, you can get it by running the following commands on the control plane node: ```bash sudo cat /etc/kubernetes/pki/ca.crt | openssl x509 -pubkey | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex | sed 's/^.* //' ``` The output is similar to: ```console 8cb2de97839780a412b93877f8507ad6c94f73add17d5d7058e91741c9d5ec78 ``` The output of the `kubeadm join` command should look something like: ``` [preflight] Running pre-flight checks ... (log output of join workflow) ... Node join complete: * Certificate signing request sent to control-plane and response received. * Kubelet informed of new secure connection details. Run 'kubectl get nodes' on control-plane to see this machine join. ``` A few seconds later, you should notice this node in the output from `kubectl get nodes`. (for example, run `kubectl` on a control plane node). ### Network configuration CNI setup on clusters mixed with Linux and Windows nodes requires more steps than just running `kubectl apply` on a manifest file. Additionally, the CNI plugin running on control plane nodes must be prepared to support the CNI plugin running on Windows worker nodes. {{% thirdparty-content %}} Only a few CNI plugins currently support Windows. Below you can find individual setup instructions for them: * [Flannel](https://sigs.k8s.io/sig-windows-tools/guides/flannel.md) * [Calico](https://docs.tigera.io/calico/latest/getting-started/kubernetes/windows-calico/) ### Install kubectl for Windows (optional) {#install-kubectl} See [Install and Set Up kubectl on Windows](/docs/tasks/tools/install-kubectl-windows/). ## {{% heading \"whatsnext\" %}} * See how to [add Linux worker nodes](/docs/tasks/administer-cluster/kubeadm/adding-linux-nodes/). ", "commid": "website_pr_47888"}], "negative_passages": []} {"query_id": "q-en-website-bd4dfde8efbc01170c61323b19f9c0c7288762ae5ba3c7478ff92fe13cf027aa", "query": "This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:\n/sig docs /language en\n/assign\nBeta APIs are off by default with\nis not a beta API though /triage accepted", "positive_passages": [{"docid": "doc-en-website-95bf5b6581ccd8f08b4406d99eed5a42f3125b186b23dd922b250fc3114bea5b", "text": "## Enabling sidecar containers Starting with Kubernetes 1.28, a Enabled by default with Kubernetes 1.29, a [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers` allows you to specify a `restartPolicy` for containers listed in a Pod's `initContainers` field. These restartable _sidecar_ containers are independent with", "commid": "website_pr_44335"}], "negative_passages": []} {"query_id": "q-en-website-bd4dfde8efbc01170c61323b19f9c0c7288762ae5ba3c7478ff92fe13cf027aa", "query": "This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:\n/sig docs /language en\n/assign\nBeta APIs are off by default with\nis not a beta API though /triage accepted", "positive_passages": [{"docid": "doc-en-website-cac84d356604925c87564e7e3738fc0c3711382c5500db54eea9e1aed222ac9e", "text": "Here's an example of a Job with two containers, one of which is a sidecar: {{% code_sample language=\"yaml\" file=\"application/job/job-sidecar.yaml\" %}} By default, this feature is not available in Kubernetes. To avail this feature, you need to enable the [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) named `SidecarContainers`. ## Differences from regular containers", "commid": "website_pr_44335"}], "negative_passages": []} {"query_id": "q-en-website-bd4dfde8efbc01170c61323b19f9c0c7288762ae5ba3c7478ff92fe13cf027aa", "query": "This is a Bug Report Problem: text is no longer needed as sidecar containers are now entered into beta state and they are enable by default. reference link of sidecar containers present in page is wrongly redirecting to page. Proposed Solution: the text below from sidecar containers documentation. reference link present in page from page to page. Page to Update:\n/sig docs /language en\n/assign\nBeta APIs are off by default with\nis not a beta API though /triage accepted", "positive_passages": [{"docid": "doc-en-website-43f5e1657155ab3f2498daf97599635965fb04dab30c939d23efa1d2f94043ca", "text": "--- Allow setting the `restartPolicy` of an init container to `Always` so that the container becomes a sidecar container (restartable init containers). See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/init-containers/#sidecar-containers-and-restartpolicy) See [Sidecar containers and restartPolicy](/docs/concepts/workloads/pods/sidecar-containers/) for more details. ", "commid": "website_pr_44335"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. Annotations: kubectl.kubernetes.io/last-applied-configuration: {\"apiVersion\":\"apps/v1\",\"kind\":\"ReplicaSet\",\"metadata\":{\"annotations\":{},\"labels\":{\"app\":\"guestbook\",\"tier\":\"frontend\"},\"name\":\"frontend\",... Annotations: Replicas: 3 current / 3 desired Pods Status: 3 Running / 0 Waiting / 0 Succeeded / 0 Failed Pod Template: Labels: tier=frontend Containers: php-redis: Image: gcr.io/google_samples/gb-frontend:v3 Image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5 Port: Host Port: Environment: ", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. Normal SuccessfulCreate 117s replicaset-controller Created pod: frontend-wtsmm Normal SuccessfulCreate 116s replicaset-controller Created pod: frontend-b2zdv Normal SuccessfulCreate 116s replicaset-controller Created pod: frontend-vcmts Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-gbgfx Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-rwz57 Normal SuccessfulCreate 13s replicaset-controller Created pod: frontend-wkl7w ``` And lastly you can check for the Pods brought up:", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. frontend-b2zdv 1/1 Running 0 6m36s frontend-vcmts 1/1 Running 0 6m36s frontend-wtsmm 1/1 Running 0 6m36s frontend-gbgfx 1/1 Running 0 10m frontend-rwz57 1/1 Running 0 10m frontend-wkl7w 1/1 Running 0 10m ``` You can also verify that the owner reference of these pods is set to the frontend ReplicaSet. To do this, get the yaml of one of the Pods running: ```shell kubectl get pods frontend-b2zdv -o yaml kubectl get pods frontend-gbgfx -o yaml ``` The output will look similar to this, with the frontend ReplicaSet's info set in the metadata's ownerReferences field:", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. creationTimestamp: \"2020-02-12T07:06:16Z\" creationTimestamp: \"2024-02-28T22:30:44Z\" generateName: frontend- labels: tier: frontend name: frontend-b2zdv name: frontend-gbgfx namespace: default ownerReferences: - apiVersion: apps/v1", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. uid: f391f6db-bb9b-4c09-ae74-6a1f77f3d5cf uid: e129deca-f864-481b-bb16-b27abfd92292 ... ```", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-7c83566c4f62b106c1d66bbfd0937bb9991123663fc7001ef51aa274977125dd", "query": "Hi Currently we obsrved that following image is not availble\nThis 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. image: gcr.io/google_samples/gb-frontend:v3 image: us-docker.pkg.dev/google-samples/containers/gke/gb-frontend:v5 ", "commid": "website_pr_45385"}], "negative_passages": []} {"query_id": "q-en-website-0b11797e8859523eb0e1cc3a2d92c0c438b909b0fffef922670c863b5b817a9c", "query": "Missing important step new people SSH into the node\n/language en\nHi could you please explain the issue in detail. /triage needs-information\nPage mentioned in the issue (based on the title): /language en\n/retitle Users not instructed to SSH into the node before executing commands in \"Upgrading Linux nodes\" page\n/sig cluster-lifecycle\nI'm not sure this is valid, though there isn't much detail to the issue to explain what the concern is. The commands on that page need to be run on the node being upgraded, but I think how the administrator connects to that node is out of scope. It may be SSH, it may be by accessing the cloud providers console. It may be by rolling up a crash cart and plugging in a monitor and keyboard. That all depends on the individuals environment.\n/remove-triage needs-information\n/remove-kind support /priority awaiting-more-evidence /kind feature /sig cluster-lifecycle\nThose labels are not set on the issue: {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} {{< include \"task-tutorial-prereqs-node-upgrade.md\" >}} {{< version-check >}} * Familiarize yourself with [the process for upgrading the rest of your kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to upgrade the control plane nodes before upgrading your Linux Worker nodes.", "commid": "website_pr_45778"}], "negative_passages": []} {"query_id": "q-en-website-0b11797e8859523eb0e1cc3a2d92c0c438b909b0fffef922670c863b5b817a9c", "query": "Missing important step new people SSH into the node\n/language en\nHi could you please explain the issue in detail. /triage needs-information\nPage mentioned in the issue (based on the title): /language en\n/retitle Users not instructed to SSH into the node before executing commands in \"Upgrading Linux nodes\" page\n/sig cluster-lifecycle\nI'm not sure this is valid, though there isn't much detail to the issue to explain what the concern is. The commands on that page need to be run on the node being upgraded, but I think how the administrator connects to that node is out of scope. It may be SSH, it may be by accessing the cloud providers console. It may be by rolling up a crash cart and plugging in a monitor and keyboard. That all depends on the individuals environment.\n/remove-triage needs-information\n/remove-kind support /priority awaiting-more-evidence /kind feature /sig cluster-lifecycle\nThose labels are not set on the issue: {{< include \"task-tutorial-prereqs.md\" >}} {{< version-check >}} {{< include \"task-tutorial-prereqs-node-upgrade.md\" >}} {{< version-check >}} * Familiarize yourself with [the process for upgrading the rest of your kubeadm cluster](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade). You will want to upgrade the control plane nodes before upgrading your Windows nodes.", "commid": "website_pr_45778"}], "negative_passages": []} {"query_id": "q-en-website-0b11797e8859523eb0e1cc3a2d92c0c438b909b0fffef922670c863b5b817a9c", "query": "Missing important step new people SSH into the node\n/language en\nHi could you please explain the issue in detail. /triage needs-information\nPage mentioned in the issue (based on the title): /language en\n/retitle Users not instructed to SSH into the node before executing commands in \"Upgrading Linux nodes\" page\n/sig cluster-lifecycle\nI'm not sure this is valid, though there isn't much detail to the issue to explain what the concern is. The commands on that page need to be run on the node being upgraded, but I think how the administrator connects to that node is out of scope. It may be SSH, it may be by accessing the cloud providers console. It may be by rolling up a crash cart and plugging in a monitor and keyboard. That all depends on the individuals environment.\n/remove-triage needs-information\n/remove-kind support /priority awaiting-more-evidence /kind feature /sig cluster-lifecycle\nThose labels are not set on the issue: You need to have shell access to all the nodes, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. ", "commid": "website_pr_45778"}], "negative_passages": []} {"query_id": "q-en-website-fe29d03168fdbebd9f13a3305c2c5336921beff85629d6d4956dceafee405fd1", "query": "found typo \"ontrolPlaneEndpoint\" in the below \"typostring
    StringAPI Object
    \"pods\"Pod
    \"servicesService
    \"services\"Service
    \"replicationcontrollers\"ReplicationController
    \"resourcequotas\"ResourceQuota
    \"secrets\"Secret

    ontrolPlaneEndpoint sets a stable IP address or DNS name for the control plane;

    controlPlaneEndpoint sets a stable IP address or DNS name for the control plane; It can be a valid IP address or a RFC-1123 DNS subdomain, both with optional TCP port. In case the controlPlaneEndpoint is not specified, the advertiseAddress + bindPort are used; in case the controlPlaneEndpoint is specified but without a TCP port,", "commid": "website_pr_45709"}], "negative_passages": []} {"query_id": "q-en-website-fe29d03168fdbebd9f13a3305c2c5336921beff85629d6d4956dceafee405fd1", "query": "found typo \"ontrolPlaneEndpoint\" in the below \"typo

    localAPIEndpoint represents the endpoint of the API server instance that's deployed on this control plane node. In HA setups, this differs from ClusterConfiguration.controlPlaneEndpoint in the sense that ontrolPlaneEndpoint is the global endpoint for the cluster, which then in the sense that controlPlaneEndpoint is the global endpoint for the cluster, which then loadbalances the requests to each individual API server. This configuration object lets you customize what IP/DNS name and port the local API server advertises it's accessible on. By default, kubeadm tries to auto-detect the IP of the default", "commid": "website_pr_45709"}], "negative_passages": []} {"query_id": "q-en-website-cb1fa64fcf6f6439541b56d0a24e4be5a354e115075f31166889a1e331dad530", "query": "chapter refers to the Memory QoS feature but pointing ; link should be updated to point to feature description in k8s official documentation.\nThis 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. [MemoryQoS](/blog/2021/11/26/qos-memory-resources/) feature improves memory QoS [MemoryQoS](/docs/concepts/workloads/pods/pod-qos/#memory-qos-with-cgroup-v2) feature improves memory QoS and relies on cgroup v2 primitives.", "commid": "website_pr_45935"}], "negative_passages": []} {"query_id": "q-en-website-5382a1d88442546b93aeeba0afa5f02f8cc1d944d80a4ba96824212378eabd91", "query": "in\nThis 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. For example, if there are 1,253 pods on the cluster and you wants to receive chunks For example, if there are 1,253 pods on the cluster and you want to receive chunks of 500 pods at a time, request those chunks as follows: 1. List all of the pods on a cluster, retrieving up to 500 pods each time.", "commid": "website_pr_45942"}], "negative_passages": []} {"query_id": "q-en-website-8c70215724b3414e64fc43b22542bd6d8b5fd3bf42e2a4b374c3bd09585d0f28", "query": "This is a Bug Report In Kubernetes Training page in hindi the link is not valid which do not show the several Kubernetes Training Partners.