From 7fc60ca00a1e93c8e522a2e99c468896c677179e Mon Sep 17 00:00:00 2001 From: Jim Angel Date: Mon, 17 Jun 2019 13:28:57 -0500 Subject: [PATCH] Revert "Removing merge conflicts for branch dev1.15 (#14940)" This reverts commit 3c42770bc4c939cd371caa0f3b9bc229533d3d8f. --- .../bug-report.md => ISSUE_TEMPLATE.md} | 16 +- .github/ISSUE_TEMPLATE/feature-request.md | 18 - .github/ISSUE_TEMPLATE/support.md | 19 - .github/PULL_REQUEST_TEMPLATE.md | 12 +- .gitignore | 1 + Dockerfile | 2 +- Makefile | 19 +- OWNERS_ALIASES | 44 +- README-de.md | 18 +- README-es.md | 76 - README-hi.md | 84 - README-id.md | 72 - README-ko.md | 4 +- README-pt.md | 82 - README.md | 40 +- config.toml | 43 - content/de/_index.html | 2 +- content/de/blog/_index.md | 10 - content/de/community/_index.html | 61 - content/de/docs/concepts/_index.md | 75 - .../de/docs/concepts/architecture/_index.md | 4 - .../architecture/master-node-communication.md | 72 - .../de/docs/concepts/architecture/nodes.md | 247 - .../concepts/cluster-administration/_index.md | 5 - .../de/docs/concepts/configuration/_index.md | 5 - content/de/docs/concepts/containers/_index.md | 5 - .../docs/concepts/example-concept-template.md | 38 - .../docs/concepts/extend-kubernetes/_index.md | 4 - content/de/docs/concepts/overview/_index.md | 5 - .../de/docs/concepts/overview/components.md | 112 - content/de/docs/concepts/policy/_index.md | 5 - .../concepts/services-networking/_index.md | 5 - content/de/docs/concepts/storage/_index.md | 5 - content/de/docs/concepts/workloads/_index.md | 5 - content/de/docs/contribute/_index.md | 62 - content/de/docs/home/_index.md | 56 - .../de/docs/home/supported-doc-versions.md | 30 - content/de/docs/reference/_index.md | 61 - .../reference/access-authn-authz/_index.md | 5 - .../command-line-tools-reference/_index.md | 5 - .../de/docs/reference/federation/_index.html | 4 - content/de/docs/reference/glossary/etcd.md | 19 - content/de/docs/reference/glossary/index.md | 12 - .../docs/reference/glossary/kube-apiserver.md | 19 - .../glossary/kube-controller-manager.md | 19 - .../docs/reference/glossary/kube-scheduler.md | 19 - content/de/docs/reference/glossary/kubelet.md | 18 - .../docs/reference/issues-security/_index.md | 5 - content/de/docs/reference/kubectl/_index.md | 5 - .../de/docs/reference/kubectl/cheatsheet.md | 351 - .../docs/reference/kubernetes-api/_index.md | 4 - .../de/docs/reference/setup-tools/_index.md | 5 - content/de/docs/reference/tools.md | 52 - content/de/docs/reference/using-api/_index.md | 5 - content/de/docs/search.md | 5 - content/de/docs/setup/_index.md | 82 - content/de/docs/setup/custom-cloud/_index.md | 4 - content/de/docs/setup/independent/_index.md | 5 - content/de/docs/setup/minikube.md | 442 - .../de/docs/setup/on-permises-vm/_index.md | 4 - content/de/docs/setup/release/_index.md | 5 - .../setup/release/building-from-source.md | 32 - content/de/docs/setup/turnkey/_index.md | 4 - content/de/docs/sitemap.md | 114 - content/de/docs/tasks/_index.md | 85 - .../access-application-cluster/_index.md | 5 - .../tasks/access-kubernetes-api/_index.md | 5 - .../docs/tasks/administer-cluster/_index.md | 5 - .../tasks/configure-pod-container/_index.md | 5 - .../tasks/debug-application-cluster/_index.md | 5 - content/de/docs/tasks/federation/_index.md | 5 - .../tasks/inject-data-application/_index.md | 5 - content/de/docs/tasks/job/_index.md | 5 - content/de/docs/tasks/manage-daemon/_index.md | 5 - .../de/docs/tasks/run-application/_index.md | 5 - .../horizontal-pod-autoscale.md | 171 - .../de/docs/tasks/service-catalog/_index.md | 5 - content/de/docs/tasks/tls/_index.md | 5 - content/de/docs/tasks/tools/_index.md | 5 - .../de/docs/tasks/tools/install-kubectl.md | 429 - .../de/docs/tasks/tools/install-minikube.md | 132 - .../de/docs/templates/feature-state-beta.txt | 8 - content/de/docs/templates/index.md | 13 - content/de/docs/tutorials/_index.md | 75 - content/de/docs/tutorials/hello-minikube.md | 271 - .../tutorials/kubernetes-basics/_index.html | 119 - .../create-cluster/_index.md | 2 +- .../create-cluster/cluster-interactive.html | 2 +- .../kubernetes-basics/deploy-app/_index.md | 4 - .../deploy-app/deploy-interactive.html | 41 - .../deploy-app/deploy-intro.html | 118 - .../kubernetes-basics/explore/_index.md | 4 - .../explore/explore-interactive.html | 41 - .../explore/explore-intro.html | 141 - .../kubernetes-basics/expose/_index.md | 4 - .../expose/expose-interactive.html | 38 - .../expose/expose-intro.html | 114 - .../kubernetes-basics/scale/_index.md | 4 - .../scale/scale-interactive.html | 40 - .../kubernetes-basics/scale/scale-intro.html | 121 - .../kubernetes-basics/update/_index.md | 4 - .../update/update-interactive.html | 37 - .../update/update-intro.html | 137 - content/de/examples/minikube/Dockerfile | 4 - content/de/examples/minikube/server.js | 9 - .../includes/default-storage-class-prereqs.md | 1 - .../federated-task-tutorial-prereqs.md | 5 - .../federation-deprecation-warning-note.md | 3 - content/de/includes/index.md | 3 - .../includes/user-guide-migration-notice.md | 12 - content/{es/includes => de}/index.md | 0 content/de/partners/_index.html | 91 - content/en/_index.html | 4 +- content/en/blog/OWNERS | 21 +- .../2015-05-00-Kubernetes-Release-0170.md | 4 +- ...-How-Did-Quake-Demo-From-Dockercon-Work.md | 2 +- ...0-Creating-Raspberry-Pi-Cluster-Running.md | 2 +- ...rnetes-community-meeting-notes-20160211.md | 4 +- .../2016-07-00-Oh-The-Places-You-Will-Go.md | 2 +- ...l-applications-in-containers-kubernetes.md | 2 +- .../_posts/2017-11-00-Kubernetes-Easy-Way.md | 2 +- ...7-12-00-Introducing-Kubeflow-Composable.md | 4 +- .../2018-05-04-Announcing-Kubeflow-0-1.md | 4 +- .../blog/_posts/2018-06-06-4-years-of-k8s.md | 2 +- .../en/blog/_posts/2018-07-10-coredns-ga.md | 4 +- .../2018-07-18-11-ways-not-to-get-hacked.md | 2 +- .../2018-08-10-introducing-kubebuilder.md | 2 +- ...ng-ci-automating-contributor-experience.md | 2 +- .../2018-10-04-non-code-contributors-guide.md | 4 +- ...0-11-topology-aware-volume-provisioning.md | 3 +- .../en/blog/_posts/2019-03-28-PID-Limiting.md | 32 - ...bernetes-locally-on-linux-with-minikube.md | 174 - ...gging-an-intermittent-connection-resets.md | 193 - ...upport-for-nodes-and-windows-containers.md | 81 - .../2019-04-04-local-persistent-volumes-ga.md | 336 - ...d-priority-and-preemption-in-kubernetes.md | 35 - ...ernetes-Device-Plugins-and-RuntimeClass.md | 174 - .../2019-04-26-latest-on-localization.md | 55 - ...-05-02-kubecon-diversity-lunch-and-hack.md | 39 - ...05-13-kubernetes-1-14-release-interview.md | 235 - ...-14-expanding-our-contributor-workshops.md | 77 - ...xtend-and-build-on-kubernetes-with-ease.md | 126 - .../2019-06-12-contributor-summit-shanghai.md | 48 - ...rking-Visibility-in-Kubernetes-Clusters.md | 48 - ...Cloud-Native-and-the-Future-of-Software.md | 54 - ...ernetes-setup-using-Ansible-and-Vagrant.md | 17 - .../blog/_posts/future-of-cloud-providers.md | 36 - .../ant-financial_featured_logo.png | Bin 10263 -> 0 bytes .../en/case-studies/ant-financial/index.html | 96 - content/en/case-studies/appdirect/index.html | 8 +- .../case-studies/bose/bose_featured_logo.png | Bin 3564 -> 0 bytes content/en/case-studies/bose/index.html | 103 - .../chinaunicom/chinaunicom_featured_logo.png | Bin 11459 -> 0 bytes .../en/case-studies/chinaunicom/index.html | 99 - .../city-of-montreal_featured_logo.png | Bin 9647 -> 0 bytes .../case-studies/city-of-montreal/index.html | 99 - content/en/case-studies/ibm/index.html | 7 +- content/en/case-studies/jd-com/index.html | 97 - .../jd-com/jd-com_featured_logo.png | Bin 6581 -> 0 bytes content/en/case-studies/naic/index.html | 15 +- content/en/case-studies/nav/index.html | 7 - content/en/case-studies/nerdalize/index.html | 96 - .../nerdalize/nerdalize_featured_logo.png | Bin 10647 -> 0 bytes content/en/case-studies/netease/index.html | 3 - content/en/case-studies/nokia/index.html | 93 - .../nokia/nokia_featured_logo.png | Bin 4261 -> 0 bytes content/en/case-studies/pingcap/index.html | 96 - .../pingcap/pingcap_featured_logo.png | Bin 7082 -> 0 bytes content/en/case-studies/prowise/index.html | 99 - .../prowise/prowise_featured_logo.png | Bin 7621 -> 0 bytes content/en/case-studies/ricardo-ch/index.html | 98 - .../ricardo-ch/ricardo-ch_featured_logo.png | Bin 5248 -> 0 bytes content/en/case-studies/slamtec/index.html | 88 - .../slamtec/slamtec_featured_logo.png | Bin 16423 -> 0 bytes content/en/case-studies/sos/index.html | 99 - .../en/case-studies/sos/sos_featured_logo.png | Bin 6662 -> 0 bytes content/en/case-studies/thredup/index.html | 94 - .../thredup/thredup_featured_logo.png | Bin 4738 -> 0 bytes content/en/case-studies/vsco/index.html | 97 - .../case-studies/vsco/vsco_featured_logo.png | Bin 11065 -> 0 bytes content/en/case-studies/woorank/index.html | 96 - .../woorank/woorank_featured_logo.png | Bin 6438 -> 0 bytes content/en/community/_index.html | 295 +- content/en/community/code-of-conduct.md | 2 +- .../community/static/cncf-code-of-conduct.md | 5 +- content/en/docs/concepts/_index.md | 6 +- .../concepts/architecture/cloud-controller.md | 34 +- .../en/docs/concepts/architecture/nodes.md | 24 +- .../concepts/cluster-administration/addons.md | 2 +- .../cluster-administration/cloud-providers.md | 17 +- .../cluster-administration-overview.md | 2 +- .../cluster-administration/federation.md | 2 +- .../cluster-administration/logging.md | 2 +- .../manage-deployment.md | 3 +- .../cluster-administration/networking.md | 4 +- .../concepts/configuration/assign-pod-node.md | 6 +- .../manage-compute-resources-container.md | 2 +- .../configuration/pod-priority-preemption.md | 9 +- .../configuration/scheduler-perf-tuning.md | 2 +- .../en/docs/concepts/configuration/secret.md | 69 +- content/en/docs/concepts/containers/images.md | 18 +- .../docs/concepts/containers/runtime-class.md | 16 +- .../compute-storage-net/device-plugins.md | 11 +- .../extend-kubernetes/extend-cluster.md | 5 + content/en/docs/concepts/overview/_index.md | 3 +- .../en/docs/concepts/overview/components.md | 10 +- .../docs/concepts/overview/kubernetes-api.md | 14 +- .../object-management-kubectl/_index.md | 5 + .../declarative-config.md | 50 +- .../imperative-command.md | 27 +- .../imperative-config.md | 43 +- .../kustomization.md | 116 +- .../overview.md} | 12 +- .../concepts/overview/what-is-kubernetes.md | 10 +- .../working-with-objects/annotations.md | 19 - .../working-with-objects/field-selectors.md | 2 +- .../kubernetes-objects.md | 10 +- .../overview/working-with-objects/labels.md | 20 - .../working-with-objects/namespaces.md | 6 +- .../en/docs/concepts/policy/limit-range.md | 382 - .../concepts/policy/pod-security-policy.md | 29 +- .../docs/concepts/policy/resource-quotas.md | 7 +- content/en/docs/concepts/security/_index.md | 4 - content/en/docs/concepts/security/overview.md | 164 - ...ries-to-pod-etc-hosts-with-host-aliases.md | 2 +- .../services-networking/dns-pod-service.md | 19 +- .../concepts/services-networking/ingress.md | 133 +- .../services-networking/network-policies.md | 4 +- .../concepts/services-networking/service.md | 770 +- .../concepts/storage/dynamic-provisioning.md | 2 +- .../concepts/storage/persistent-volumes.md | 56 +- .../docs/concepts/storage/storage-classes.md | 30 +- .../docs/concepts/storage/storage-limits.md | 2 +- content/en/docs/concepts/storage/volumes.md | 10 +- .../workloads/controllers/cron-jobs.md | 4 +- .../workloads/controllers/daemonset.md | 4 +- .../workloads/controllers/deployment.md | 11 +- .../controllers/garbage-collection.md | 16 +- .../controllers/jobs-run-to-completion.md | 13 +- .../workloads/controllers/replicaset.md | 13 +- .../controllers/replicationcontroller.md | 10 +- .../workloads/controllers/statefulset.md | 3 +- .../concepts/workloads/pods/disruptions.md | 4 +- .../workloads/pods/init-containers.md | 9 +- .../concepts/workloads/pods/pod-lifecycle.md | 11 +- .../concepts/workloads/pods/pod-overview.md | 23 +- .../en/docs/concepts/workloads/pods/pod.md | 120 +- .../docs/concepts/workloads/pods/podpreset.md | 8 +- content/en/docs/contribute/_index.md | 15 +- content/en/docs/contribute/advanced.md | 151 +- .../generate-ref-docs/contribute-upstream.md | 246 - .../generate-ref-docs/federation-api.md | 89 + .../contribute/generate-ref-docs/kubectl.md | 2 +- .../generate-ref-docs/kubernetes-api.md | 209 +- .../kubernetes-components.md | 62 +- content/en/docs/contribute/intermediate.md | 40 +- content/en/docs/contribute/localization.md | 171 +- content/en/docs/contribute/participating.md | 36 +- content/en/docs/contribute/start.md | 38 +- .../contribute/style/content-organization.md | 2 +- .../contribute/style/hugo-shortcodes/index.md | 78 +- .../en/docs/contribute/style/style-guide.md | 104 +- .../docs/contribute/style/write-new-topic.md | 2 +- .../doc-contributor-tools/snippets/README.md | 2 +- .../fedora/fedora_manual_config.md | 7 +- .../en/docs/getting-started-guides/ubuntu.md | 41 - .../getting-started-guides/ubuntu/_index.md | 75 + .../getting-started-guides/ubuntu/backups.md | 144 + .../ubuntu/decommissioning.md | 80 + .../getting-started-guides/ubuntu/glossary.md | 24 + .../ubuntu/installation.md | 299 + .../getting-started-guides/ubuntu/local.md | 81 + .../getting-started-guides/ubuntu/logging.md | 63 + .../ubuntu/monitoring.md | 145 + .../ubuntu/networking.md | 63 + .../ubuntu/operational-considerations.md | 165 + .../getting-started-guides/ubuntu/rancher.md | 360 + .../getting-started-guides/ubuntu/scaling.md | 87 + .../getting-started-guides/ubuntu/security.md | 36 + .../getting-started-guides/ubuntu/storage.md | 95 + .../ubuntu/troubleshooting.md | 179 + .../getting-started-guides/ubuntu/upgrades.md | 164 + .../ubuntu/validation.md | 169 + content/en/docs/reference/_index.md | 4 +- .../docs/reference/access-authn-authz/abac.md | 4 - .../admission-controllers.md | 49 +- .../docs/reference/access-authn-authz/rbac.md | 31 +- .../service-accounts-admin.md | 2 +- .../cloud-controller-manager.md | 18 +- .../feature-gates.md | 27 +- .../federation-apiserver.md.orig | 154 - .../federation-controller-manager.md | 59 + .../kube-apiserver.md | 19 +- .../kube-controller-manager.md | 18 +- .../kube-proxy.md | 11 +- .../kube-scheduler.md | 22 +- .../kubelet-tls-bootstrapping.md | 14 +- .../command-line-tools-reference/kubelet.md | 315 +- .../en/docs/reference/federation/_index.html | 4 + .../extensions/v1beta1/definitions.html | 7592 +++++++++++++ .../extensions/v1beta1/operations.html | 9932 +++++++++++++++++ .../federation/v1beta1/definitions.html | 1606 +++ .../federation/v1beta1/operations.html | 1921 ++++ .../reference/federation/v1/definitions.html | 2550 +++++ .../reference/federation/v1/operations.html | 9529 ++++++++++++++++ .../docs/reference/glossary/applications.md | 13 - .../glossary/cluster-infrastructure.md | 13 - .../reference/glossary/cluster-operations.md | 13 - .../glossary/container-env-variables.md | 2 +- .../reference/glossary/container-runtime.md | 21 - .../en/docs/reference/glossary/containerd.md | 19 - .../docs/reference/glossary/control-plane.md | 13 - content/en/docs/reference/glossary/cri-o.md | 24 - content/en/docs/reference/glossary/cri.md | 18 - .../en/docs/reference/glossary/data-plane.md | 13 - content/en/docs/reference/glossary/docker.md | 13 +- content/en/docs/reference/glossary/etcd.md | 7 +- content/en/docs/reference/glossary/kops.md | 12 +- .../en/docs/reference/glossary/kube-proxy.md | 3 - .../en/docs/reference/glossary/limitrange.md | 23 - content/en/docs/reference/glossary/logging.md | 18 - .../en/docs/reference/glossary/mirror-pod.md | 22 - content/en/docs/reference/glossary/node.md | 3 +- .../en/docs/reference/glossary/qos-class.md | 24 - content/en/docs/reference/glossary/rkt.md | 2 +- content/en/docs/reference/glossary/service.md | 11 +- .../en/docs/reference/glossary/static-pod.md | 14 - content/en/docs/reference/glossary/taint.md | 6 +- .../en/docs/reference/glossary/toleration.md | 6 +- .../en/docs/reference/glossary/workload.md | 24 +- .../docs/reference/issues-security/issues.md | 9 +- .../reference/issues-security/security.md | 2 - .../en/docs/reference/kubectl/cheatsheet.md | 15 +- content/en/docs/reference/kubectl/kubectl.md | 309 +- content/en/docs/reference/kubectl/overview.md | 31 +- .../en/docs/reference/kubernetes-api/index.md | 4 +- .../kubeadm_init_phase_upload-certs.md | 22 +- .../kubeadm/generated/kubeadm_join_phase.md | 42 +- .../kubeadm_join_phase_control-plane-join.md | 42 +- ...beadm_join_phase_control-plane-join_all.md | 21 +- ...eadm_join_phase_control-plane-join_etcd.md | 22 +- ...e_control-plane-join_mark-control-plane.md | 22 +- ..._phase_control-plane-join_update-status.md | 22 +- ...ubeadm_join_phase_control-plane-prepare.md | 42 +- ...dm_join_phase_control-plane-prepare_all.md | 21 +- ..._join_phase_control-plane-prepare_certs.md | 21 +- ...ase_control-plane-prepare_control-plane.md | 21 +- ...se_control-plane-prepare_download-certs.md | 21 +- ..._phase_control-plane-prepare_kubeconfig.md | 21 +- .../kubeadm_join_phase_kubelet-start.md | 114 +- .../generated/kubeadm_join_phase_preflight.md | 22 +- .../kubeadm/implementation-details.md | 5 +- .../setup-tools/kubeadm/kubeadm-init.md | 10 +- .../setup-tools/kubeadm/kubeadm-join.md | 20 +- .../setup-tools/kubeadm/kubeadm-upgrade.md | 2 +- .../reference/setup-tools/kubeadm/kubeadm.md | 2 +- .../reference/setup-tools/kubefed/_index.md | 0 .../reference/setup-tools/kubefed/kubefed.md | 72 + .../setup-tools/kubefed/kubefed_init.md | 107 + .../setup-tools/kubefed/kubefed_join.md | 101 + .../setup-tools/kubefed/kubefed_options.md | 78 + .../setup-tools/kubefed/kubefed_unjoin.md | 88 + .../setup-tools/kubefed/kubefed_version.md | 81 + content/en/docs/reference/tools.md | 8 +- .../reference/using-api/client-libraries.md | 1 - .../reference/using-api/deprecation-policy.md | 44 +- content/en/docs/setup/_index.md | 165 +- .../en/docs/setup/best-practices/_index.md | 4 - .../{best-practices => }/certificates.md | 23 +- .../{best-practices => }/cluster-large.md | 4 +- .../container-runtimes.md => cri.md} | 15 +- content/en/docs/setup/custom-cloud/_index.md | 4 + .../tools => custom-cloud}/kops.md | 3 +- .../tools => custom-cloud}/kubespray.md | 5 +- content/en/docs/setup/independent/_index.md | 5 + .../control-plane-flags.md | 0 .../create-cluster-kubeadm.md | 34 +- .../kubeadm => independent}/ha-topology.md | 6 +- .../high-availability.md | 24 +- .../install-kubeadm.md | 19 +- .../kubelet-integration.md | 2 +- .../kubeadm => independent}/self-hosting.md | 0 .../setup-ha-etcd-with-kubeadm.md | 6 +- .../troubleshooting-kubeadm.md | 31 +- .../docs/setup/learning-environment/_index.md | 4 - .../{learning-environment => }/minikube.md | 353 +- .../{best-practices => }/multiple-zones.md | 8 +- .../{best-practices => }/node-conformance.md | 3 +- .../tools => on-premises-metal}/krib.md | 16 +- .../docs/setup/on-premises-vm/_index.md | 0 .../on-premises-vm/cloudstack.md | 5 +- .../on-premises-vm/dcos.md | 0 .../on-premises-vm/ovirt.md | 3 +- content/en/docs/setup/pick-right-solution.md | 314 + .../setup/production-environment/_index.md | 4 - .../on-premises-vm/_index.md | 4 - .../production-environment/tools/_index.md | 4 - .../tools/kubeadm/_index.md | 4 - .../production-environment/windows/_index.md | 4 - content/en/docs/setup/release/_index.md | 5 +- .../setup/release/building-from-source.md | 33 + content/en/docs/setup/release/notes.md | 15 +- .../turnkey/_index.md | 2 +- .../turnkey/alibaba-cloud.md | 2 +- .../turnkey/aws.md | 5 +- .../turnkey/azure.md | 0 .../turnkey/clc.md | 20 +- .../turnkey/gce.md | 5 +- .../turnkey/icp.md | 6 +- .../turnkey/stackpoint.md | 0 .../{release => }/version-skew-policy.md | 10 +- .../{de => en}/docs/setup/windows/_index.md | 0 .../flannel-master-kubeclt-get-pods.png | Bin .../windows/flannel-master-kubectl-get-ds.png | Bin .../windows/intro-windows-in-kubernetes.md | 48 +- .../windows/user-guide-windows-containers.md | 0 .../windows/user-guide-windows-nodes.md | 14 +- .../windows/windows-docker-error.png | Bin ...icate-containers-same-pod-shared-volume.md | 4 +- .../configure-access-multiple-clusters.md | 12 +- .../create-external-load-balancer.md | 2 +- .../ingress-minikube.md | 15 +- ...port-forward-access-application-cluster.md | 20 +- .../configure-aggregation-layer.md | 6 +- .../custom-resource-definition-versioning.md | 2 +- .../custom-resource-definitions.md | 2 +- .../administer-cluster/access-cluster-api.md | 8 +- .../administer-cluster/cluster-management.md | 6 +- .../configure-multiple-schedulers.md | 2 +- .../configure-upgrade-etcd.md | 2 +- .../declare-network-policy.md | 2 +- .../developing-cloud-controller-manager.md | 4 +- .../dns-custom-nameservers.md | 4 +- .../dns-horizontal-autoscaling.md | 51 +- .../tasks/administer-cluster/encrypt-data.md | 16 +- ...aranteed-scheduling-critical-addon-pods.md | 8 +- .../highly-available-master.md | 2 +- .../tasks/administer-cluster/kms-provider.md | 6 +- .../kubeadm/kubeadm-upgrade-1-13.md | 2 - .../kubeadm/kubeadm-upgrade-1-14.md | 18 +- .../kubeadm/kubeadm-upgrade-ha-1-13.md | 2 +- .../administer-cluster/kubelet-config-file.md | 4 +- .../namespaces-walkthrough.md | 4 - .../cilium-network-policy.md | 2 +- .../romana-network-policy.md | 2 +- .../administer-cluster/out-of-resource.md | 2 +- .../administer-cluster/reconfigure-kubelet.md | 6 +- .../administer-cluster/safely-drain-node.md | 14 +- .../administer-cluster/sysctl-cluster.md | 5 +- .../assign-memory-resource.md | 2 +- .../configure-pod-container/configure-gmsa.md | 4 +- .../configure-liveness-readiness-probes.md | 4 - .../configure-persistent-volume-storage.md | 6 +- .../configure-pod-configmap.md | 94 +- .../configure-projected-volume-storage.md | 65 +- .../pull-image-private-registry.md | 9 +- .../security-context.md | 8 +- .../share-process-namespace.md | 64 +- .../translate-compose-kubernetes.md | 6 +- .../tasks/debug-application-cluster/audit.md | 17 +- .../debug-service.md | 6 +- .../monitor-node-health.md | 2 +- .../resource-usage-monitoring.md | 8 - .../troubleshooting.md | 4 +- .../administer-federation/cluster.md | 4 +- .../administer-federation/configmap.md | 2 +- .../administer-federation/daemonset.md | 4 +- .../administer-federation/deployment.md | 2 +- .../administer-federation/events.md | 4 +- .../federation/administer-federation/hpa.md | 4 +- .../administer-federation/ingress.md | 4 +- .../federation/administer-federation/job.md | 4 +- .../administer-federation/namespaces.md | 2 +- .../administer-federation/replicaset.md | 4 +- .../administer-federation/secret.md | 4 +- .../federation-service-discovery.md | 4 +- .../set-up-cluster-federation-kubefed.md | 2 +- .../distribute-credentials-secure.md | 94 +- ...nward-api-volume-expose-pod-information.md | 15 +- .../job/automated-tasks-with-cron-jobs.md | 4 +- .../job/parallel-processing-expansion.md | 42 +- .../manage-daemon/rollback-daemon-set.md | 1 - .../tasks/manage-daemon/update-daemon-set.md | 5 +- .../docs/tasks/manage-gpus/scheduling-gpus.md | 6 +- .../tasks/manage-kubernetes-objects/_index.md | 4 - .../tasks/run-application/configure-pdb.md | 42 +- .../run-application/delete-stateful-set.md | 2 +- .../force-delete-stateful-set-pod.md | 4 +- .../horizontal-pod-autoscale-walkthrough.md | 12 +- .../horizontal-pod-autoscale.md | 6 +- .../rolling-update-replication-controller.md | 88 +- .../run-replicated-stateful-application.md | 16 +- .../update-api-object-kubectl-patch.md | 10 +- .../install-service-catalog-using-sc.md | 14 +- .../tasks/tls/managing-tls-in-a-cluster.md | 8 +- .../en/docs/tasks/tools/install-kubectl.md | 264 +- .../en/docs/tasks/tools/install-minikube.md | 145 +- content/en/docs/test.md | 4 +- .../configure-redis-using-configmap.md | 2 +- .../tutorials/kubernetes-basics/_index.html | 14 +- .../explore/explore-intro.html | 2 +- .../update/update-intro.html | 8 +- .../tutorials/online-training/overview.md | 34 +- .../en/docs/tutorials/services/source-ip.md | 115 +- .../stateful-application/cassandra.md | 2 +- .../expose-external-ip-address.md | 4 +- .../guestbook-logs-metrics-with-elk.md | 402 - .../stateless-application/guestbook.md | 28 +- .../application-developer/foundational.md | 2 +- .../users/cluster-operator/foundational.md | 8 +- .../en/examples/admin/cloud/ccm-example.yaml | 2 +- .../admin/dns/dns-horizontal-autoscaler.yaml | 2 +- content/en/examples/admin/namespace-dev.json | 2 +- content/en/examples/admin/namespace-prod.json | 2 +- .../resource/limit-mem-cpu-container.yaml | 19 - .../admin/resource/limit-mem-cpu-pod.yaml | 10 - .../resource/limit-memory-ratio-pod.yaml | 9 - .../admin/resource/limit-range-pod-1.yaml | 37 - .../admin/resource/limit-range-pod-2.yaml | 37 - .../admin/resource/limit-range-pod-3.yaml | 13 - .../admin/resource/pvc-limit-greater.yaml | 10 - .../admin/resource/pvc-limit-lower.yaml | 10 - .../admin/resource/quota-objects-pvc-2.yaml | 2 +- .../admin/resource/quota-objects-pvc.yaml | 2 +- .../admin/resource/storagelimits.yaml | 11 - .../en/examples/admin/sched/my-scheduler.yaml | 2 +- .../guestbook/redis-slave-deployment.yaml | 2 +- .../application/zookeeper/zookeeper.yaml | 2 +- .../en/examples/controllers/daemonset.yaml | 2 +- .../controllers/replication-nginx-1.7.9.yaml | 16 - .../controllers/replication-nginx-1.9.2.yaml | 21 - content/en/examples/examples_test.go | 40 +- .../en/examples/pods/config/redis-pod.yaml | 5 +- .../pod-multiple-secret-env-variable.yaml | 19 - .../pods/inject/pod-secret-envFrom.yaml | 11 - .../pod-single-secret-env-variable.yaml | 14 - .../pod-configmap-volume-specific-key.yaml | 2 +- .../examples/pods/pod-with-pod-affinity.yaml | 2 +- .../pods/security/security-context.yaml | 4 +- .../en/examples/policy/restricted-psp.yaml | 4 +- ...-pod-disruption-budget-maxunavailable.yaml | 9 - ...er-pod-disruption-budget-minavailable.yaml | 9 - .../examples/service/networking/ingress.yaml | 2 +- content/en/includes/partner-script.js | 2 +- content/en/partners/_index.html | 2 +- content/es/OWNERS | 13 - content/es/_common-resources/index.md | 3 - content/es/_index.html | 60 - content/es/blog/_index.md | 10 - content/es/case-studies/_index.html | 10 - content/es/community/_index.html | 62 - content/es/community/code-of-conduct.md | 31 - content/es/community/static/README.md | 11 - .../community/static/cncf-code-of-conduct.md | 29 - content/es/docs/_index.md | 23 - content/es/docs/_search.md | 4 - content/es/docs/concepts/_index.md | 77 - .../es/docs/concepts/architecture/_index.md | 4 - .../concepts/architecture/cloud-controller.md | 238 - .../architecture/master-node-communication.md | 59 - .../es/docs/concepts/architecture/nodes.md | 183 - .../concepts/cluster-administration/_index.md | 4 - .../es/docs/concepts/configuration/_index.md | 4 - content/es/docs/concepts/containers/_index.md | 4 - .../container-environment-variables.md | 60 - .../docs/concepts/extend-kubernetes/_index.md | 4 - .../extend-kubernetes/api-extension/_index.md | 4 - .../compute-storage-net/_index.md | 4 - content/es/docs/concepts/overview/_index.md | 4 - .../object-management-kubectl/_index.md | 4 - .../overview/working-with-objects/_index.md | 4 - .../working-with-objects/annotations.md | 77 - .../working-with-objects/common-labels.md | 174 - .../working-with-objects/field-selectors.md | 60 - .../kubernetes-objects.md | 78 - .../overview/working-with-objects/labels.md | 204 - .../overview/working-with-objects/names.md | 30 - .../working-with-objects/namespaces.md | 115 - content/es/docs/concepts/policy/_index.md | 4 - .../concepts/services-networking/_index.md | 4 - content/es/docs/concepts/storage/_index.md | 4 - content/es/docs/concepts/workloads/_index.md | 4 - .../concepts/workloads/controllers/_index.md | 4 - .../es/docs/concepts/workloads/pods/_index.md | 4 - content/es/docs/contribute/_index.md | 85 - .../contribute/generate-ref-docs/_index.md | 10 - content/es/docs/contribute/style/_index.md | 12 - .../es/docs/getting-started-guides/_index.md | 4 - .../getting-started-guides/fedora/_index.md | 4 - content/es/docs/home/_index.md | 57 - content/es/docs/reference/_index.md | 64 - .../reference/access-authn-authz/_index.md | 5 - .../command-line-tools-reference/_index.md | 5 - .../es/docs/reference/federation/_index.md | 4 - .../es/docs/reference/glossary/annotation.md | 17 - .../glossary/application-architect.md | 18 - .../glossary/application-developer.md | 18 - .../es/docs/reference/glossary/certificate.md | 17 - content/es/docs/reference/glossary/cla.md | 17 - content/es/docs/reference/glossary/cluster.md | 18 - content/es/docs/reference/glossary/docker.md | 17 - content/es/docs/reference/glossary/image.md | 17 - content/es/docs/reference/glossary/index.md | 11 - content/es/docs/reference/glossary/job.md | 20 - content/es/docs/reference/glossary/kops.md | 27 - content/es/docs/reference/glossary/kubeadm.md | 18 - content/es/docs/reference/glossary/name.md | 17 - content/es/docs/reference/glossary/node.md | 19 - content/es/docs/reference/glossary/pod.md | 19 - content/es/docs/reference/glossary/rkt.md | 18 - content/es/docs/reference/glossary/secret.md | 18 - .../es/docs/reference/glossary/selector.md | 18 - content/es/docs/reference/glossary/service.md | 18 - content/es/docs/reference/glossary/sysctl.md | 23 - content/es/docs/reference/glossary/uid.md | 17 - .../docs/reference/issues-security/_index.md | 5 - content/es/docs/reference/kubectl/_index.md | 4 - .../docs/reference/kubernetes-api/_index.md | 4 - .../es/docs/reference/kubernetes-api/index.md | 5 - .../es/docs/reference/setup-tools/_index.md | 5 - .../reference/setup-tools/kubeadm/_index.md | 5 - .../setup-tools/kubeadm/generated/_index.md | 5 - .../reference/setup-tools/kubefed/_index.md | 5 - content/es/docs/reference/using-api/_index.md | 5 - content/es/docs/setup/_index.md | 85 - content/es/docs/setup/custom-cloud/_index.md | 4 - content/es/docs/setup/independent/_index.md | 4 - .../es/docs/setup/on-premises-vm/_index.md | 4 - content/es/docs/setup/release/_index.md | 4 - .../setup/release/building-from-source.md | 37 - content/es/docs/setup/turnkey/_index.md | 4 - content/es/docs/setup/windows/_index.md | 4 - content/es/docs/sitemap.md | 115 - content/es/docs/tasks/_index.md | 87 - .../access-application-cluster/_index.md | 4 - .../tasks/access-kubernetes-api/_index.md | 4 - .../custom-resources/_index.md | 4 - .../docs/tasks/administer-cluster/_index.md | 4 - .../administer-cluster/kubeadm/_index.md | 5 - .../manage-resources/_index.md | 4 - .../network-policy-provider/_index.md | 4 - .../tasks/configure-pod-container/_index.md | 4 - .../configure-volume-storage.md | 131 - .../tasks/debug-application-cluster/_index.md | 4 - .../resource-metrics-pipeline.md | 57 - content/es/docs/tasks/federation/_index.md | 4 - .../administer-federation/_index.md | 4 - .../tasks/inject-data-application/_index.md | 4 - content/es/docs/tasks/job/_index.md | 4 - content/es/docs/tasks/manage-daemon/_index.md | 4 - .../es/docs/tasks/run-application/_index.md | 4 - .../tasks/run-application/configure-pdb.md | 230 - .../run-stateless-application-deployment.md | 151 - .../es/docs/tasks/service-catalog/_index.md | 4 - content/es/docs/tasks/tls/_index.md | 4 - content/es/docs/tasks/tools/_index.md | 4 - .../es/docs/tasks/tools/install-kubectl.md | 430 - .../es/docs/tasks/tools/install-minikube.md | 132 - .../es/docs/templates/feature-state-alpha.txt | 7 - .../es/docs/templates/feature-state-beta.txt | 9 - .../templates/feature-state-deprecated.txt | 1 - .../docs/templates/feature-state-stable.txt | 4 - content/es/docs/templates/index.md | 13 - content/es/docs/tutorials/_index.md | 76 - content/es/docs/tutorials/clusters/_index.md | 4 - .../es/docs/tutorials/configuration/_index.md | 4 - .../tutorials/kubernetes-basics/_index.md | 4 - .../create-cluster/_index.md | 4 - .../create-cluster/cluster-interactive.html | 37 - .../kubernetes-basics/deploy-app/_index.md | 4 - .../deploy-app/deploy-interactive.html | 41 - .../kubernetes-basics/explore/_index.md | 4 - .../kubernetes-basics/expose/_index.md | 4 - .../kubernetes-basics/scale/_index.md | 4 - .../kubernetes-basics/update/_index.md | 4 - .../docs/tutorials/online-training/_index.md | 4 - content/es/docs/tutorials/services/_index.md | 4 - .../tutorials/stateful-application/_index.md | 4 - .../tutorials/stateless-application/_index.md | 4 - content/es/docs/update-user-guide-links.py | 85 - .../application/deployment-scale.yaml | 19 - .../application/deployment-update.yaml | 19 - .../es/examples/application/deployment.yaml | 19 - content/es/examples/pods/storage/redis.yaml | 14 - content/es/includes/task-tutorial-prereqs.md | 5 - content/es/partners/_index.html | 91 - content/fr/_index.html | 8 +- content/fr/blog/_index.md | 10 - content/fr/case-studies/_index.html | 1 - content/fr/docs/_index.md | 1 - content/fr/docs/concepts/_index.md | 1 - .../fr/docs/concepts/architecture/_index.md | 1 - .../architecture/master-node-communication.md | 3 +- .../fr/docs/concepts/architecture/nodes.md | 3 +- .../concepts/cluster-administration/_index.md | 2 +- .../cluster-administration/certificates.md | 2 +- .../cluster-administration-overview.md | 5 +- .../fr/docs/concepts/configuration/_index.md | 4 - content/fr/docs/concepts/containers/_index.md | 3 +- .../container-environment-variables.md | 9 +- content/fr/docs/concepts/containers/images.md | 1 - .../docs/concepts/containers/runtime-class.md | 11 +- .../docs/concepts/extend-kubernetes/_index.md | 4 - .../extend-kubernetes/api-extension/_index.md | 4 - .../compute-storage-net/_index.md | 4 - content/fr/docs/concepts/overview/_index.md | 3 +- .../concepts/overview/what-is-kubernetes.md | 7 +- .../overview/working-with-objects/_index.md | 4 - content/fr/docs/concepts/policy/_index.md | 4 - content/fr/docs/concepts/security/_index.md | 4 - .../concepts/services-networking/_index.md | 5 - .../services-networking/dns-pod-service.md | 231 - .../concepts/services-networking/ingress.md | 438 - content/fr/docs/concepts/storage/_index.md | 4 - content/fr/docs/concepts/workloads/_index.md | 4 - .../concepts/workloads/controllers/_index.md | 4 - .../fr/docs/concepts/workloads/pods/_index.md | 4 - .../concepts/workloads/pods/pod-overview.md | 105 - .../fr/docs/concepts/workloads/pods/pod.md | 199 - content/fr/docs/contribute/_index.md | 62 - .../contribute/generate-ref-docs/_index.md | 1 - .../generate-ref-docs/federation-api.md | 75 - .../generate-ref-docs/kubernetes-api.md | 338 - content/fr/docs/contribute/start.md | 291 - content/fr/docs/contribute/style/_index.md | 8 - .../fr/docs/getting-started-guides/_index.md | 4 - .../getting-started-guides/fedora/_index.md | 4 - content/fr/docs/home/_index.md | 11 +- .../fr/docs/home/supported-doc-versions.md | 5 - content/fr/docs/reference/_index.md | 58 - .../reference/access-authn-authz/_index.md | 5 - .../command-line-tools-reference/_index.md | 5 - .../reference/glossary/aggregation-layer.md | 19 - .../reference/glossary/container-runtime.md | 20 - .../fr/docs/reference/glossary/container.md | 18 - .../docs/reference/issues-security/_index.md | 5 - content/fr/docs/reference/kubectl/_index.md | 2 +- .../fr/docs/reference/kubectl/cheatsheet.md | 1 - .../fr/docs/reference/kubectl/conventions.md | 1 - content/fr/docs/reference/kubectl/jsonpath.md | 1 - .../fr/docs/reference/kubectl/kubectl-cmds.md | 1 - content/fr/docs/reference/kubectl/kubectl.md | 6 +- content/fr/docs/reference/kubectl/overview.md | 1 - .../docs/reference/kubernetes-api/_index.md | 4 - .../fr/docs/reference/setup-tools/_index.md | 5 - .../reference/setup-tools/kubeadm/_index.md | 5 - .../setup-tools/kubeadm/generated/_index.md | 5 - .../reference/setup-tools/kubeadm/kubeadm.md | 23 - content/fr/docs/reference/using-api/_index.md | 5 - content/fr/docs/setup/_index.md | 17 +- content/fr/docs/setup/custom-cloud/_index.md | 1 - content/fr/docs/setup/custom-cloud/coreos.md | 8 +- content/fr/docs/setup/custom-cloud/kops.md | 1 - .../fr/docs/setup/custom-cloud/kubespray.md | 1 - content/fr/docs/setup/independent/_index.md | 4 +- .../setup/independent/control-plane-flags.md | 9 +- .../independent/create-cluster-kubeadm.md | 171 +- .../fr/docs/setup/independent/ha-topology.md | 1 - .../setup/independent/high-availability.md | 1 - .../docs/setup/independent/install-kubeadm.md | 3 +- .../setup/independent/kubelet-integration.md | 1 - .../independent/setup-ha-etcd-with-kubeadm.md | 1 - .../independent/troubleshooting-kubeadm.md | 3 +- content/fr/docs/setup/pick-right-solution.md | 5 +- content/fr/docs/setup/release/_index.md | 4 +- .../setup/release/building-from-source.md | 1 - content/fr/docs/setup/turnkey/_index.md | 4 - content/fr/docs/setup/windows/_index.md | 4 - content/fr/docs/tasks/_index.md | 86 - .../access-application-cluster/_index.md | 4 - .../tasks/access-kubernetes-api/_index.md | 4 - .../custom-resources/_index.md | 4 - .../docs/tasks/administer-cluster/_index.md | 4 - .../administer-cluster/kubeadm/_index.md | 4 - .../manage-resources/_index.md | 4 - .../network-policy-provider/_index.md | 4 - .../tasks/configure-pod-container/_index.md | 4 - .../tasks/debug-application-cluster/_index.md | 4 - content/fr/docs/tasks/federation/_index.md | 4 - .../administer-federation/_index.md | 4 - .../tasks/inject-data-application/_index.md | 4 - content/fr/docs/tasks/job/_index.md | 4 - content/fr/docs/tasks/manage-daemon/_index.md | 4 - .../tasks/manage-kubernetes-objects/_index.md | 4 - .../fr/docs/tasks/run-application/_index.md | 4 - .../fr/docs/tasks/service-catalog/_index.md | 4 - content/fr/docs/tasks/tls/_index.md | 4 - content/fr/docs/tasks/tools/_index.md | 4 - content/fr/docs/tutorials/_index.md | 75 - content/fr/docs/tutorials/clusters/_index.md | 4 - .../fr/docs/tutorials/configuration/_index.md | 4 - content/fr/docs/tutorials/hello-minikube.md | 47 +- .../tutorials/kubernetes-basics/_index.html | 118 - .../create-cluster/_index.md | 4 - .../create-cluster/cluster-interactive.html | 37 - .../create-cluster/cluster-intro.html | 108 - .../kubernetes-basics/deploy-app/_index.md | 4 - .../kubernetes-basics/explore/_index.md | 4 - .../kubernetes-basics/expose/_index.md | 4 - .../kubernetes-basics/scale/_index.md | 4 - .../kubernetes-basics/update/_index.md | 4 - .../docs/tutorials/online-training/_index.md | 4 - content/fr/docs/tutorials/services/_index.md | 4 - .../tutorials/stateful-application/_index.md | 4 - .../tutorials/stateless-application/_index.md | 4 - .../guestbook/redis-slave-deployment.yaml | 2 +- .../includes/default-storage-class-prereqs.md | 1 - .../federated-task-tutorial-prereqs.md | 3 - .../federation-deprecation-warning-note.md | 5 - content/fr/includes/index.md | 3 - content/fr/includes/partner-script.js | 1609 --- content/fr/includes/partner-style.css | 202 - content/fr/includes/task-tutorial-prereqs.md | 5 - .../fr/includes/user-guide-content-moved.md | 2 - .../includes/user-guide-migration-notice.md | 12 - content/fr/partners/_index.html | 92 - content/hi/OWNERS | 13 - content/hi/_common-resources/index.md | 3 - content/id/OWNERS | 13 - content/id/_common-resources/index.md | 3 - content/id/_index.html | 63 - content/id/case-studies/_index.html | 9 - content/id/docs/_index.md | 3 - content/id/docs/concepts/_index.md | 108 - .../id/docs/concepts/architecture/_index.md | 5 - .../architecture/master-node-communication.md | 77 - .../id/docs/concepts/architecture/nodes.md | 231 - .../concepts/cluster-administration/_index.md | 5 - .../concepts/cluster-administration/addons.md | 53 - .../cluster-administration/cloud-providers.md | 350 - .../cluster-administration-overview.md | 72 - .../controller-metrics.md | 42 - .../cluster-administration/federation.md | 195 - .../kubelet-garbage-collection.md | 96 - .../cluster-administration/proxies.md | 65 - .../id/docs/concepts/configuration/_index.md | 5 - .../configuration/taint-and-toleration.md | 314 - content/id/docs/concepts/containers/_index.md | 5 - .../container-environment-variables.md | 59 - .../containers/container-lifecycle-hooks.md | 119 - .../docs/concepts/containers/runtime-class.md | 161 - content/id/docs/concepts/overview/_index.md | 5 - .../id/docs/concepts/overview/components.md | 152 - .../docs/concepts/overview/kubernetes-api.md | 156 - .../object-management-kubectl/_index.md | 5 - .../declarative-config.md | 868 -- .../imperative-command.md | 132 - .../imperative-config.md | 116 - .../concepts/overview/what-is-kubernetes.md | 189 - .../overview/working-with-objects/_index.md | 5 - .../working-with-objects/annotations.md | 83 - .../working-with-objects/field-selectors.md | 68 - .../kubernetes-objects.md | 108 - .../overview/working-with-objects/names.md | 30 - .../working-with-objects/namespaces.md | 94 - .../concepts/services-networking/_index.md | 5 - .../connect-applications-service.md | 366 - .../ingress-controllers.md | 76 - .../concepts/services-networking/ingress.md | 474 - .../services-networking/network-policies.md | 285 - .../concepts/services-networking/service.md | 1065 -- content/id/docs/concepts/workloads/_index.md | 4 - .../concepts/workloads/controllers/_index.md | 4 - .../controllers/garbage-collection.md | 135 - .../id/docs/concepts/workloads/pods/_index.md | 4 - .../concepts/workloads/pods/disruptions.md | 185 - .../concepts/workloads/pods/pod-overview.md | 106 - .../docs/concepts/workloads/pods/podpreset.md | 56 - content/id/docs/home/_index.md | 56 - .../id/docs/home/supported-doc-versions.md | 29 - content/id/docs/reference/glossary/etcd.md | 19 - content/id/docs/reference/glossary/ingress.md | 20 - .../docs/reference/glossary/kube-apiserver.md | 19 - .../glossary/kube-controller-manager.md | 19 - .../docs/reference/glossary/kube-scheduler.md | 18 - content/id/docs/reference/glossary/kubelet.md | 15 - content/id/docs/reference/glossary/name.md | 17 - content/id/docs/reference/glossary/uid.md | 17 - content/id/docs/search.md | 5 - content/id/docs/setup/_index.md | 81 - content/id/docs/sitemap.md | 114 - .../id/docs/templates/feature-state-alpha.txt | 7 - .../id/docs/templates/feature-state-beta.txt | 10 - .../templates/feature-state-deprecated.txt | 2 - .../id/docs/templates/feaure-state-stable.txt | 4 - content/id/docs/templates/index.md | 13 - content/id/docs/tutorials/_index.md | 75 - content/id/docs/tutorials/hello-minikube.md | 270 - .../tutorials/kubernetes-basics/_index.html | 92 - .../id/examples/application/deployment.yaml | 19 - .../application/simple_deployment.yaml | 19 - .../application/update_deployment.yaml | 18 - .../id/examples/controllers/replicaset.yaml | 17 - content/id/examples/minikube/Dockerfile | 4 - content/id/examples/minikube/server.js | 9 - .../examples/service/networking/curlpod.yaml | 28 - .../examples/service/networking/ingress.yaml | 9 - .../service/networking/nginx-secure-app.yaml | 46 - .../service/networking/nginx-svc.yaml | 12 - .../service/networking/run-my-nginx.yaml | 20 - .../federation-deprecation-warning-note.md | 3 - content/id/includes/index.md | 3 - content/it/_index.html | 24 +- content/it/community/_index.html | 2 +- content/it/docs/concepts/_index.md | 77 - .../it/docs/concepts/architecture/_index.md | 5 - .../concepts/architecture/cloud-controller.md | 267 - .../architecture/master-node-communication.md | 94 - .../it/docs/concepts/architecture/nodes.md | 285 - .../concepts/cluster-administration/_index.md | 5 - .../concepts/cluster-administration/addons.md | 51 - .../cluster-administration/certificates.md | 248 - .../cluster-administration/cloud-providers.md | 399 - .../cluster-administration-overview.md | 72 - .../controller-metrics.md | 46 - .../cluster-administration/federation.md | 182 - .../kubelet-garbage-collection.md | 100 - .../cluster-administration/logging.md | 258 - .../manage-deployment.md | 446 - .../cluster-administration/networking.md | 343 - .../cluster-administration/proxies.md | 68 - .../docs/concepts/example-concept-template.md | 39 - .../concepts/overview/what-is-kubernetes.md | 2 +- .../admin/logging/fluentd-sidecar-config.yaml | 25 - .../two-files-counter-pod-agent-sidecar.yaml | 39 - ...o-files-counter-pod-streaming-sidecar.yaml | 38 - .../admin/logging/two-files-counter-pod.yaml | 26 - .../it/examples/application/nginx-app.yaml | 34 - content/it/examples/debug/counter-pod.yaml | 10 - .../federation-deprecation-warning-note.md | 5 - .../concepts/overview/what-is-kubernetes.md | 3 - content/ja/docs/home/_index.md | 47 +- .../ja/docs/home/supported-doc-versions.md | 4 - content/ja/docs/setup/certificates.md | 27 +- content/ja/docs/setup/cri.md | 108 +- .../setup/independent/control-plane-flags.md | 2 - .../independent/create-cluster-kubeadm.md | 151 +- .../setup/independent/high-availability.md | 198 +- .../docs/setup/independent/install-kubeadm.md | 20 +- .../setup/independent/kubelet-integration.md | 6 +- .../independent/setup-ha-etcd-with-kubeadm.md | 9 +- .../independent/troubleshooting-kubeadm.md | 43 +- content/ja/docs/setup/minikube.md | 268 +- content/ja/docs/setup/multiple-zones.md | 123 +- .../ja/docs/setup/on-premises-metal/krib.md | 4 +- content/ja/docs/setup/pick-right-solution.md | 211 +- .../setup/release/building-from-source.md | 17 +- .../ja/docs/setup/turnkey/alibaba-cloud.md | 4 +- content/ja/docs/setup/turnkey/azure.md | 14 +- content/ja/docs/setup/turnkey/clc.md | 2 +- content/ja/docs/setup/turnkey/gce.md | 4 +- content/ja/docs/setup/turnkey/icp.md | 67 - content/ja/docs/setup/version-skew-policy.md | 141 - content/ja/docs/tutorials/hello-minikube.md | 11 +- .../tutorials/kubernetes-basics/_index.html | 8 +- .../create-cluster/cluster-intro.html | 8 +- .../deploy-app/deploy-intro.html | 4 +- .../expose/expose-intro.html | 8 +- .../update/update-intro.html | 8 +- .../admin/cloud/pvl-initializer-config.yaml | 13 + .../guestbook/redis-slave-deployment.yaml | 2 +- .../ja/examples/controllers/daemonset.yaml | 2 +- content/ja/examples/examples_test.go | 4 + .../ja/examples/policy/restricted-psp.yaml | 4 +- .../examples/service/networking/ingress.yaml | 2 +- content/ko/_index.html | 6 +- content/ko/case-studies/ibm/index.html | 7 +- content/ko/case-studies/naic/index.html | 15 +- content/ko/case-studies/pinterest/index.html | 15 +- content/ko/docs/concepts/_index.md | 13 +- .../concepts/architecture/cloud-controller.md | 35 +- .../cluster-administration-overview.md | 69 - .../controller-metrics.md | 48 - .../cluster-administration/federation.md | 4 +- .../configuration/scheduler-perf-tuning.md | 52 +- content/ko/docs/concepts/containers/images.md | 28 +- content/ko/docs/concepts/overview/_index.md | 3 +- .../ko/docs/concepts/overview/components.md | 24 +- .../docs/concepts/overview/kubernetes-api.md | 8 +- .../object-management-kubectl/_index.md | 4 + .../imperative-command.md | 27 +- .../overview.md} | 13 +- .../concepts/overview/what-is-kubernetes.md | 162 +- .../working-with-objects/annotations.md | 76 - .../kubernetes-objects.md | 13 +- .../working-with-objects/namespaces.md | 49 +- .../concepts/workloads/controllers/_index.md | 4 - .../workloads/controllers/cron-jobs.md | 49 - .../workloads/pods/init-containers.md | 52 +- .../concepts/workloads/pods/pod-lifecycle.md | 246 +- .../concepts/workloads/pods/pod-overview.md | 24 +- .../ko/docs/concepts/workloads/pods/pod.md | 205 - content/ko/docs/contribute/_index.md | 37 +- content/ko/docs/contribute/participating.md | 291 - content/ko/docs/reference/_index.md | 20 +- .../ko/docs/reference/glossary/annotation.md | 18 - .../docs/reference/glossary/app-container.md | 20 - content/ko/docs/reference/glossary/cluster.md | 19 - .../glossary/container-env-variables.md | 17 - .../ko/docs/reference/glossary/container.md | 19 - .../ko/docs/reference/glossary/controller.md | 8 +- content/ko/docs/reference/glossary/cronjob.md | 19 - .../glossary/customresourcedefinition.md | 20 - .../ko/docs/reference/glossary/daemonset.md | 20 - .../ko/docs/reference/glossary/deployment.md | 20 - .../docs/reference/glossary/device-plugin.md | 17 - content/ko/docs/reference/glossary/docker.md | 18 - content/ko/docs/reference/glossary/etcd.md | 2 +- .../ko/docs/reference/glossary/extensions.md | 18 - content/ko/docs/reference/glossary/image.md | 18 - .../docs/reference/glossary/init-container.md | 18 - content/ko/docs/reference/glossary/job.md | 20 - .../docs/reference/glossary/kube-apiserver.md | 2 +- .../ko/docs/reference/glossary/kube-proxy.md | 19 - .../docs/reference/glossary/kube-scheduler.md | 2 +- content/ko/docs/reference/glossary/kubectl.md | 19 - content/ko/docs/reference/glossary/kubelet.md | 6 +- .../docs/reference/glossary/kubernetes-api.md | 19 - content/ko/docs/reference/glossary/label.md | 18 - .../ko/docs/reference/glossary/minikube.md | 19 - content/ko/docs/reference/glossary/name.md | 2 +- .../ko/docs/reference/glossary/namespace.md | 18 - content/ko/docs/reference/glossary/node.md | 18 - .../docs/reference/glossary/pod-lifecycle.md | 19 - .../reference/glossary/pod-security-policy.md | 19 - content/ko/docs/reference/glossary/pod.md | 19 - content/ko/docs/reference/glossary/rbac.md | 19 - .../ko/docs/reference/glossary/replica-set.md | 20 - .../glossary/replication-controller.md | 19 - .../docs/reference/glossary/resource-quota.md | 20 - .../ko/docs/reference/glossary/selector.md | 18 - .../reference/glossary/service-account.md | 19 - content/ko/docs/reference/glossary/service.md | 19 - .../ko/docs/reference/glossary/statefulset.md | 23 - content/ko/docs/reference/glossary/taint.md | 18 - .../ko/docs/reference/glossary/toleration.md | 18 - content/ko/docs/reference/glossary/volume.md | 19 - .../ko/docs/reference/glossary/workload.md | 28 - .../ko/docs/reference/kubectl/cheatsheet.md | 371 - content/ko/docs/setup/certificates.md | 4 +- content/ko/docs/setup/cri.md | 119 +- content/ko/docs/setup/minikube.md | 124 +- content/ko/docs/setup/multiple-zones.md | 8 +- content/ko/docs/setup/pick-right-solution.md | 297 + content/ko/docs/setup/scratch.md | 872 ++ .../access-application-cluster/_index.md | 5 - .../access-cluster.md | 372 - ...icate-containers-same-pod-shared-volume.md | 151 - .../configure-dns-cluster.md | 13 - .../tasks/manage-kubernetes-objects/_index.md | 4 - .../declarative-config.md | 998 -- .../imperative-config.md | 151 - .../horizontal-pod-autoscale-walkthrough.md | 54 +- .../horizontal-pod-autoscale.md | 4 +- .../ko/docs/tasks/tools/install-minikube.md | 99 +- content/ko/docs/tutorials/_index.md | 2 +- content/ko/docs/tutorials/clusters/_index.md | 5 - .../ko/docs/tutorials/clusters/apparmor.md | 468 - .../tutorials/clusters/deny-write.profile | 10 - .../configure-redis-using-configmap.md | 66 +- .../deploy-app/deploy-intro.html | 4 +- .../explore/explore-intro.html | 2 +- .../kubernetes-basics/scale/scale-intro.html | 7 +- .../update/update-intro.html | 8 +- .../tutorials/online-training/overview.md | 39 +- content/ko/docs/tutorials/services/_index.md | 5 - .../ko/docs/tutorials/services/source-ip.md | 342 - .../tutorials/stateful-application/_index.md | 5 - .../basic-stateful-set.md | 14 +- .../stateful-application/cassandra.md | 258 - .../mysql-wordpress-persistent-volume.md | 233 - .../stateful-application/zookeeper.md | 1095 -- .../expose-external-ip-address.md | 4 +- .../stateless-application/guestbook.md | 21 +- .../cassandra/cassandra-service.yaml | 12 - .../cassandra/cassandra-statefulset.yaml | 100 - .../guestbook/redis-slave-deployment.yaml | 2 +- .../application/mysql/mysql-configmap.yaml | 16 - .../application/mysql/mysql-deployment.yaml | 43 - .../examples/application/mysql/mysql-pv.yaml | 26 - .../application/mysql/mysql-services.yaml | 30 - .../application/mysql/mysql-statefulset.yaml | 167 - .../application/simple_deployment.yaml | 19 - .../application/update_deployment.yaml | 18 - .../wordpress/mysql-deployment.yaml | 65 - .../wordpress/wordpress-deployment.yaml | 67 - .../application/zookeeper/zookeeper.yaml | 133 - .../ko/examples/pods/config/redis-pod.yaml | 5 +- .../pods/security/hello-apparmor.yaml | 13 - .../ko/examples/pods/two-container-pod.yaml | 27 - .../federated-task-tutorial-prereqs.md | 5 - ...ng-note.md => federation-current-state.md} | 0 content/pt/OWNERS | 11 - content/pt/_common-resources/index.md | 3 - content/pt/_index.html | 62 - content/pt/blog/_index.md | 10 - content/pt/case-studies/_index.md | 9 - content/pt/community/_index.html | 71 - content/pt/community/code-of-conduct.md | 27 - content/pt/community/static/README.md | 2 - .../community/static/cncf-code-of-conduct.md | 44 - content/pt/docs/_index.md | 23 - content/pt/docs/_search.md | 4 - .../pt/docs/concepts/architecture/_index.md | 5 - .../concepts/architecture/cloud-controller.md | 240 - .../architecture/master-node-communication.md | 106 - .../cluster-administration-overview.md | 76 - content/pt/docs/home/_index.md | 58 - .../pt/docs/home/supported-doc-versions.md | 30 - content/pt/docs/sitemap.md | 114 - content/pt/includes/index.md | 3 - content/pt/partners/_index.html | 93 - .../2019-04-26-latest-on-localization.md | 53 - .../2019-06-12-contributor-summit-shanghai.md | 101 - .../zh/docs/concepts/architecture/nodes.md | 2 +- .../cluster-administration-overview.md | 2 +- .../zh/docs/concepts/configuration/secret.md | 4 +- content/zh/docs/concepts/containers/images.md | 2 +- .../docs/concepts/overview/kubernetes-api.md | 6 +- .../kubernetes-objects.md | 4 +- .../concepts/services-networking/ingress.yaml | 2 +- .../services-networking/network-policies.md | 2 +- .../workloads/controllers/cron-jobs.md | 2 +- .../workloads/controllers/daemonset.md | 2 +- .../workloads/controllers/daemonset.yaml | 4 +- .../workloads/controllers/deployment.md | 6 +- .../controllers/garbage-collection.md | 2 +- .../workloads/pods/init-containers.md | 8 +- content/zh/docs/home/_index.md | 110 +- .../kube-proxy.md | 4 +- .../kube-scheduler.md | 4 +- content/zh/docs/reference/kubectl/kubectl.md | 145 +- .../reference/setup-tools/kubeadm/kubeadm.md | 2 +- .../independent/create-cluster-kubeadm.md | 21 +- .../docs/setup/independent/install-kubeadm.md | 6 +- .../create-external-load-balancer.md | 2 +- .../administer-cluster/kubelet-config-file.md | 12 +- .../romana-network-policy.md | 2 +- .../attach-handler-lifecycle-event.md | 174 - ...nward-api-volume-expose-pod-information.md | 44 +- .../job/automated-tasks-with-cron-jobs.md | 4 +- .../kubernetes-basics/explore-intro.html | 16 +- .../stateful-application/cassandra.md | 175 +- content/zh/docs/user-guide/ingress.yaml | 2 +- .../zh/docs/user-guide/kubectl-overview.md | 2 +- content/zh/docs/whatisk8s.md | 10 + .../zh/examples/pods/lifecycle-events.yaml | 16 - content/zh/includes/task-tutorial-prereqs.md | 5 - data/setup.yml | 2 +- i18n/de.toml | 60 +- i18n/en.toml | 60 +- i18n/es.toml | 195 - i18n/fr.toml | 2 +- i18n/id.toml | 139 - i18n/it.toml | 2 +- i18n/ja.toml | 59 +- i18n/ko.toml | 63 +- i18n/nl.toml | 195 - i18n/no.toml | 2 +- i18n/pt.toml | 139 - layouts/_default/baseof.html | 2 +- layouts/blog/baseof.html | 6 +- layouts/blog/pager.html | 4 +- layouts/case-studies/list.html | 4 +- layouts/case-studies/single-baseof.html | 2 +- layouts/community/list.html | 8 +- layouts/docs/baseof.html | 2 +- layouts/docs/glossary.html | 12 +- layouts/docs/list.html | 8 +- layouts/docs/search.html | 2 +- layouts/index.html | 4 +- layouts/partials/css.html | 17 +- layouts/partials/docs/top-menu.html | 2 +- layouts/partials/feedback.html | 17 +- layouts/partials/git-info.html | 4 +- layouts/partials/head.html | 7 +- layouts/partials/templates/blocks.html | 6 +- layouts/shortcodes/capture.html | 1 - layouts/shortcodes/caution.html | 2 +- layouts/shortcodes/code.html | 4 +- layouts/shortcodes/codenew.html | 2 +- layouts/shortcodes/glossary_tooltip.html | 2 +- layouts/shortcodes/include.html | 2 +- layouts/shortcodes/note.html | 4 +- layouts/shortcodes/table.html | 6 - layouts/shortcodes/tabs.html | 2 +- layouts/shortcodes/upcoming-events.html | 11 - layouts/shortcodes/warning.html | 2 +- {assets/sass => sass}/OWNERS | 0 {assets/sass => sass}/_base.sass | 4 - {assets/sass => sass}/_case-studies.sass | 0 {assets/sass => sass}/_desktop.sass | 0 {assets/sass => sass}/_reset.sass | 0 {assets/sass => sass}/_size.sass | 0 {assets/sass => sass}/_skin.sass | 0 {assets/sass => sass}/_tablet.sass | 0 .../style.sass => sass/case-study-styles.sass | 6 +- sass/styles.sass | 7 + scripts/find_pr.py | 89 - scripts/sass.sh | 38 + scripts/test_examples.sh | 23 +- scripts/upstream_changes.py | 78 - static/_redirects | 51 +- static/css/blog.css | 22 +- static/css/case-study-styles.css | 1 + static/css/case-study-styles.css.map | 7 + static/css/newcommunity.css | 868 -- static/css/styles.css | 1 + static/css/styles.css.map | 7 + .../generated/kubectl/kubectl-commands.html | 997 +- .../reference/generated/kubectl/navData.js | 2 +- .../generated/kubernetes-api/v1.11/index.html | 2 +- .../generated/kubernetes-api/v1.12/index.html | 2 +- .../generated/kubernetes-api/v1.13/index.html | 2 +- .../generated/kubernetes-api/v1.14/index.html | 1189 +- .../generated/kubernetes-api/v1.14/navData.js | 2 +- .../images/CaseStudy_antfinancial_banner1.jpg | Bin 106474 -> 0 bytes .../images/CaseStudy_antfinancial_banner3.jpg | Bin 237788 -> 0 bytes .../images/CaseStudy_antfinancial_banner4.jpg | Bin 176309 -> 0 bytes static/images/CaseStudy_bose_banner1.jpg | Bin 31691 -> 0 bytes static/images/CaseStudy_bose_banner3.jpg | Bin 75495 -> 0 bytes static/images/CaseStudy_bose_banner4.jpg | Bin 32813 -> 0 bytes .../images/CaseStudy_chinaunicom_banner1.jpg | Bin 209711 -> 0 bytes .../images/CaseStudy_chinaunicom_banner3.jpg | Bin 95900 -> 0 bytes .../images/CaseStudy_chinaunicom_banner4.jpg | Bin 173940 -> 0 bytes static/images/CaseStudy_ft_banner1.jpg | Bin 256651 -> 0 bytes static/images/CaseStudy_ft_banner3.jpg | Bin 169917 -> 0 bytes static/images/CaseStudy_ft_banner4.jpg | Bin 439308 -> 0 bytes static/images/CaseStudy_jdcom_banner1.jpg | Bin 45538 -> 0 bytes static/images/CaseStudy_jdcom_banner3.jpg | Bin 54766 -> 0 bytes static/images/CaseStudy_jdcom_banner4.jpg | Bin 41251 -> 0 bytes static/images/CaseStudy_montreal_banner1.jpg | Bin 52407 -> 0 bytes static/images/CaseStudy_montreal_banner3.jpg | Bin 82510 -> 0 bytes static/images/CaseStudy_montreal_banner4.jpg | Bin 36412 -> 0 bytes static/images/CaseStudy_nerdalize_banner1.jpg | Bin 20975 -> 0 bytes static/images/CaseStudy_nerdalize_banner3.jpg | Bin 30756 -> 0 bytes static/images/CaseStudy_nerdalize_banner4.jpg | Bin 24769 -> 0 bytes static/images/CaseStudy_nokia_banner1.jpg | Bin 166855 -> 0 bytes static/images/CaseStudy_nokia_banner3.jpg | Bin 177286 -> 0 bytes static/images/CaseStudy_nokia_banner4.jpg | Bin 170337 -> 0 bytes static/images/CaseStudy_pingcap_banner1.jpg | Bin 36411 -> 0 bytes static/images/CaseStudy_pingcap_banner3.jpg | Bin 38337 -> 0 bytes static/images/CaseStudy_pingcap_banner4.jpg | Bin 41687 -> 0 bytes static/images/CaseStudy_prowise_banner1.jpg | Bin 60163 -> 0 bytes static/images/CaseStudy_prowise_banner3.jpg | Bin 14774 -> 0 bytes static/images/CaseStudy_prowise_banner4.jpg | Bin 21784 -> 0 bytes static/images/CaseStudy_ricardoch_banner1.png | Bin 134635 -> 0 bytes static/images/CaseStudy_ricardoch_banner3.png | Bin 77143 -> 0 bytes static/images/CaseStudy_ricardoch_banner4.png | Bin 99698 -> 0 bytes static/images/CaseStudy_slamtec_banner1.jpg | Bin 41407 -> 0 bytes static/images/CaseStudy_slamtec_banner3.jpg | Bin 11215 -> 0 bytes static/images/CaseStudy_slamtec_banner4.jpg | Bin 14759 -> 0 bytes static/images/CaseStudy_sos_banner1.jpg | Bin 47914 -> 0 bytes static/images/CaseStudy_sos_banner3.jpg | Bin 26283 -> 0 bytes static/images/CaseStudy_sos_banner4.jpg | Bin 36373 -> 0 bytes static/images/CaseStudy_thredup_banner1.jpg | Bin 13179 -> 0 bytes static/images/CaseStudy_thredup_banner3.jpg | Bin 22922 -> 0 bytes static/images/CaseStudy_thredup_banner4.jpg | Bin 18299 -> 0 bytes static/images/CaseStudy_vsco_banner1.jpg | Bin 17179 -> 0 bytes static/images/CaseStudy_vsco_banner2.jpg | Bin 38073 -> 0 bytes static/images/CaseStudy_vsco_banner4.jpg | Bin 26456 -> 0 bytes static/images/CaseStudy_woorank_banner1.jpg | Bin 17679 -> 0 bytes static/images/CaseStudy_woorank_banner3.jpg | Bin 45799 -> 0 bytes static/images/CaseStudy_woorank_banner4.jpg | Bin 52295 -> 0 bytes static/images/antfinancial_logo.png | Bin 8559 -> 0 bytes .../connection-reset-packet-flow.png | Bin 50565 -> 0 bytes .../good-packet-flow.png | Bin 36985 -> 0 bytes .../ihor-dvoretskyi-1470985-unsplash.jpg | Bin 3245604 -> 0 bytes .../module_01_cluster.png | Bin 136977 -> 0 bytes .../k8s-blog-fig1.png | Bin 18873 -> 0 bytes .../k8s-blog-fig2.png | Bin 29587 -> 0 bytes .../ac-s-sc.svg | 3 - .../arch.png | Bin 214320 -> 0 bytes .../asyncApiSpec.json | 1 - .../grafana-lambda.png | Bin 157083 -> 0 bytes .../kyma-center.png | Bin 82029 -> 0 bytes .../panel.png | Bin 782034 -> 0 bytes static/images/blog/OWNERS | 1 + static/images/bose_logo.png | Bin 4039 -> 0 bytes static/images/chinaunicom_logo.png | Bin 10959 -> 0 bytes static/images/community/discuss.png | Bin 4944 -> 0 bytes static/images/community/event-bg.jpg | Bin 199686 -> 0 bytes static/images/community/github.png | Bin 30026 -> 0 bytes .../kubernetes-community-02-mobile.jpg | Bin 147080 -> 0 bytes .../kubernetes-community-04-mobile.jpg | Bin 312271 -> 0 bytes .../kubernetes-community-contributor.jpg | Bin 968284 -> 0 bytes .../kubernetes-community-final-02.jpg | Bin 173219 -> 0 bytes .../kubernetes-community-final-03.jpg | Bin 466479 -> 0 bytes .../kubernetes-community-final-04.jpg | Bin 265438 -> 0 bytes .../kubernetes-community-final-05.jpg | Bin 309774 -> 0 bytes .../kubernetes-community-final-06.jpg | Bin 6702785 -> 0 bytes .../kubernetes-community-final-07.jpg | Bin 4349835 -> 0 bytes .../kubernetes-community-final-08.jpg | Bin 222061 -> 0 bytes .../community/kubernetes-community-final.jpg | Bin 634159 -> 0 bytes static/images/community/slack.png | Bin 18595 -> 0 bytes static/images/community/stack.png | Bin 17618 -> 0 bytes static/images/community/twitter.png | Bin 9134 -> 0 bytes static/images/docs/4c.png | Bin 21381 -> 0 bytes static/images/docs/KubernetesSolutions.svg | 620 - static/images/docs/contribute/claim-host.png | Bin 424037 -> 0 bytes static/images/docs/ip-masq.png | Bin 72249 -> 71060 bytes .../logging-with-streaming-sidecar.png | Bin 51146 -> 37555 bytes static/images/ft_logo.png | Bin 9843 -> 0 bytes static/images/jdcom_logo.png | Bin 6342 -> 0 bytes static/images/montreal_logo.png | Bin 6802 -> 0 bytes static/images/nerdalize_logo.png | Bin 7747 -> 0 bytes static/images/nokia_logo.png | Bin 4616 -> 0 bytes static/images/pingcap_logo.png | Bin 5419 -> 0 bytes static/images/prowise_logo.png | Bin 7843 -> 0 bytes static/images/ricardoch_logo.png | Bin 6397 -> 0 bytes static/images/slamtec_logo.png | Bin 5583 -> 0 bytes static/images/sos_logo.png | Bin 7575 -> 0 bytes static/images/thredup_logo.png | Bin 3569 -> 0 bytes static/images/vsco_logo.png | Bin 9336 -> 0 bytes static/images/woorank_logo.png | Bin 18017 -> 0 bytes static/js/bootstrap-3.3.7.min.js | 7 + static/js/bootstrap-4.3.1.min.js | 7 - update-imported-docs/reference.yml | 2 +- 1318 files changed, 43221 insertions(+), 48932 deletions(-) rename .github/{ISSUE_TEMPLATE/bug-report.md => ISSUE_TEMPLATE.md} (79%) delete mode 100644 .github/ISSUE_TEMPLATE/feature-request.md delete mode 100644 .github/ISSUE_TEMPLATE/support.md delete mode 100644 README-es.md delete mode 100644 README-hi.md delete mode 100644 README-id.md delete mode 100644 README-pt.md delete mode 100644 content/de/blog/_index.md delete mode 100644 content/de/community/_index.html delete mode 100644 content/de/docs/concepts/_index.md delete mode 100644 content/de/docs/concepts/architecture/_index.md delete mode 100644 content/de/docs/concepts/architecture/master-node-communication.md delete mode 100644 content/de/docs/concepts/architecture/nodes.md delete mode 100755 content/de/docs/concepts/cluster-administration/_index.md delete mode 100755 content/de/docs/concepts/configuration/_index.md delete mode 100755 content/de/docs/concepts/containers/_index.md delete mode 100644 content/de/docs/concepts/example-concept-template.md delete mode 100644 content/de/docs/concepts/extend-kubernetes/_index.md delete mode 100755 content/de/docs/concepts/overview/_index.md delete mode 100644 content/de/docs/concepts/overview/components.md delete mode 100755 content/de/docs/concepts/policy/_index.md delete mode 100755 content/de/docs/concepts/services-networking/_index.md delete mode 100755 content/de/docs/concepts/storage/_index.md delete mode 100644 content/de/docs/concepts/workloads/_index.md delete mode 100644 content/de/docs/contribute/_index.md delete mode 100644 content/de/docs/home/_index.md delete mode 100644 content/de/docs/home/supported-doc-versions.md delete mode 100644 content/de/docs/reference/_index.md delete mode 100644 content/de/docs/reference/access-authn-authz/_index.md delete mode 100644 content/de/docs/reference/command-line-tools-reference/_index.md delete mode 100644 content/de/docs/reference/federation/_index.html delete mode 100755 content/de/docs/reference/glossary/etcd.md delete mode 100755 content/de/docs/reference/glossary/index.md delete mode 100755 content/de/docs/reference/glossary/kube-apiserver.md delete mode 100755 content/de/docs/reference/glossary/kube-controller-manager.md delete mode 100755 content/de/docs/reference/glossary/kube-scheduler.md delete mode 100755 content/de/docs/reference/glossary/kubelet.md delete mode 100644 content/de/docs/reference/issues-security/_index.md delete mode 100755 content/de/docs/reference/kubectl/_index.md delete mode 100644 content/de/docs/reference/kubectl/cheatsheet.md delete mode 100644 content/de/docs/reference/kubernetes-api/_index.md delete mode 100644 content/de/docs/reference/setup-tools/_index.md delete mode 100644 content/de/docs/reference/tools.md delete mode 100644 content/de/docs/reference/using-api/_index.md delete mode 100644 content/de/docs/search.md delete mode 100644 content/de/docs/setup/_index.md delete mode 100644 content/de/docs/setup/custom-cloud/_index.md delete mode 100755 content/de/docs/setup/independent/_index.md delete mode 100644 content/de/docs/setup/minikube.md delete mode 100644 content/de/docs/setup/on-permises-vm/_index.md delete mode 100755 content/de/docs/setup/release/_index.md delete mode 100644 content/de/docs/setup/release/building-from-source.md delete mode 100644 content/de/docs/setup/turnkey/_index.md delete mode 100644 content/de/docs/sitemap.md delete mode 100644 content/de/docs/tasks/_index.md delete mode 100755 content/de/docs/tasks/access-application-cluster/_index.md delete mode 100755 content/de/docs/tasks/access-kubernetes-api/_index.md delete mode 100755 content/de/docs/tasks/administer-cluster/_index.md delete mode 100755 content/de/docs/tasks/configure-pod-container/_index.md delete mode 100755 content/de/docs/tasks/debug-application-cluster/_index.md delete mode 100755 content/de/docs/tasks/federation/_index.md delete mode 100755 content/de/docs/tasks/inject-data-application/_index.md delete mode 100644 content/de/docs/tasks/job/_index.md delete mode 100755 content/de/docs/tasks/manage-daemon/_index.md delete mode 100755 content/de/docs/tasks/run-application/_index.md delete mode 100644 content/de/docs/tasks/run-application/horizontal-pod-autoscale.md delete mode 100755 content/de/docs/tasks/service-catalog/_index.md delete mode 100755 content/de/docs/tasks/tls/_index.md delete mode 100755 content/de/docs/tasks/tools/_index.md delete mode 100644 content/de/docs/tasks/tools/install-kubectl.md delete mode 100644 content/de/docs/tasks/tools/install-minikube.md delete mode 100644 content/de/docs/templates/feature-state-beta.txt delete mode 100644 content/de/docs/templates/index.md delete mode 100644 content/de/docs/tutorials/_index.md delete mode 100644 content/de/docs/tutorials/hello-minikube.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/_index.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/deploy-app/_index.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/explore/_index.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/explore/explore-interactive.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/explore/explore-intro.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/expose/_index.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/expose/expose-interactive.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/expose/expose-intro.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/scale/_index.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/scale/scale-interactive.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/scale/scale-intro.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/update/_index.md delete mode 100644 content/de/docs/tutorials/kubernetes-basics/update/update-interactive.html delete mode 100644 content/de/docs/tutorials/kubernetes-basics/update/update-intro.html delete mode 100644 content/de/examples/minikube/Dockerfile delete mode 100644 content/de/examples/minikube/server.js delete mode 100644 content/de/includes/default-storage-class-prereqs.md delete mode 100644 content/de/includes/federated-task-tutorial-prereqs.md delete mode 100644 content/de/includes/federation-deprecation-warning-note.md delete mode 100644 content/de/includes/index.md delete mode 100644 content/de/includes/user-guide-migration-notice.md rename content/{es/includes => de}/index.md (100%) delete mode 100644 content/de/partners/_index.html delete mode 100644 content/en/blog/_posts/2019-03-28-PID-Limiting.md delete mode 100644 content/en/blog/_posts/2019-03-28-running-kubernetes-locally-on-linux-with-minikube.md delete mode 100644 content/en/blog/_posts/2019-03-29-kube-proxy-subtleties-debugging-an-intermittent-connection-resets.md delete mode 100644 content/en/blog/_posts/2019-04-01-kubernetes-v1-14-delivers-production-level-support-for-nodes-and-windows-containers.md delete mode 100644 content/en/blog/_posts/2019-04-04-local-persistent-volumes-ga.md delete mode 100644 content/en/blog/_posts/2019-04-16-pod-priority-and-preemption-in-kubernetes.md delete mode 100644 content/en/blog/_posts/2019-04-24-Hardware-Accelerated-SSLTLS-Termination-in-Ingress-Controllers-using-Kubernetes-Device-Plugins-and-RuntimeClass.md delete mode 100644 content/en/blog/_posts/2019-04-26-latest-on-localization.md delete mode 100644 content/en/blog/_posts/2019-05-02-kubecon-diversity-lunch-and-hack.md delete mode 100644 content/en/blog/_posts/2019-05-13-kubernetes-1-14-release-interview.md delete mode 100644 content/en/blog/_posts/2019-05-14-expanding-our-contributor-workshops.md delete mode 100644 content/en/blog/_posts/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease.md delete mode 100644 content/en/blog/_posts/2019-06-12-contributor-summit-shanghai.md delete mode 100644 content/en/blog/_posts/Introducing-kube-iptables-tailer-Better-Networking-Visibility-in-Kubernetes-Clusters.md delete mode 100644 content/en/blog/_posts/Kubernetes-Cloud-Native-and-the-Future-of-Software.md delete mode 100644 content/en/blog/_posts/future-of-cloud-providers.md delete mode 100644 content/en/case-studies/ant-financial/ant-financial_featured_logo.png delete mode 100644 content/en/case-studies/ant-financial/index.html delete mode 100644 content/en/case-studies/bose/bose_featured_logo.png delete mode 100644 content/en/case-studies/bose/index.html delete mode 100644 content/en/case-studies/chinaunicom/chinaunicom_featured_logo.png delete mode 100644 content/en/case-studies/chinaunicom/index.html delete mode 100644 content/en/case-studies/city-of-montreal/city-of-montreal_featured_logo.png delete mode 100644 content/en/case-studies/city-of-montreal/index.html delete mode 100644 content/en/case-studies/jd-com/index.html delete mode 100644 content/en/case-studies/jd-com/jd-com_featured_logo.png delete mode 100644 content/en/case-studies/nerdalize/index.html delete mode 100644 content/en/case-studies/nerdalize/nerdalize_featured_logo.png delete mode 100644 content/en/case-studies/nokia/index.html delete mode 100644 content/en/case-studies/nokia/nokia_featured_logo.png delete mode 100644 content/en/case-studies/pingcap/index.html delete mode 100644 content/en/case-studies/pingcap/pingcap_featured_logo.png delete mode 100644 content/en/case-studies/prowise/index.html delete mode 100644 content/en/case-studies/prowise/prowise_featured_logo.png delete mode 100644 content/en/case-studies/ricardo-ch/index.html delete mode 100644 content/en/case-studies/ricardo-ch/ricardo-ch_featured_logo.png delete mode 100644 content/en/case-studies/slamtec/index.html delete mode 100644 content/en/case-studies/slamtec/slamtec_featured_logo.png delete mode 100644 content/en/case-studies/sos/index.html delete mode 100644 content/en/case-studies/sos/sos_featured_logo.png delete mode 100644 content/en/case-studies/thredup/index.html delete mode 100644 content/en/case-studies/thredup/thredup_featured_logo.png delete mode 100644 content/en/case-studies/vsco/index.html delete mode 100644 content/en/case-studies/vsco/vsco_featured_logo.png delete mode 100644 content/en/case-studies/woorank/index.html delete mode 100644 content/en/case-studies/woorank/woorank_featured_logo.png create mode 100755 content/en/docs/concepts/overview/object-management-kubectl/_index.md rename content/en/docs/{tasks/manage-kubernetes-objects => concepts/overview/object-management-kubectl}/declarative-config.md (95%) rename content/en/docs/{tasks/manage-kubernetes-objects => concepts/overview/object-management-kubectl}/imperative-command.md (88%) rename content/en/docs/{tasks/manage-kubernetes-objects => concepts/overview/object-management-kubectl}/imperative-config.md (83%) rename content/en/docs/{tasks/manage-kubernetes-objects => concepts/overview/object-management-kubectl}/kustomization.md (94%) rename content/en/docs/concepts/overview/{working-with-objects/object-management.md => object-management-kubectl/overview.md} (95%) delete mode 100644 content/en/docs/concepts/policy/limit-range.md delete mode 100644 content/en/docs/concepts/security/_index.md delete mode 100644 content/en/docs/concepts/security/overview.md delete mode 100644 content/en/docs/contribute/generate-ref-docs/contribute-upstream.md create mode 100644 content/en/docs/contribute/generate-ref-docs/federation-api.md delete mode 100644 content/en/docs/getting-started-guides/ubuntu.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/_index.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/backups.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/decommissioning.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/glossary.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/installation.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/local.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/logging.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/monitoring.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/networking.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/operational-considerations.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/rancher.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/scaling.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/security.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/storage.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/troubleshooting.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/upgrades.md create mode 100644 content/en/docs/getting-started-guides/ubuntu/validation.md delete mode 100644 content/en/docs/reference/command-line-tools-reference/federation-apiserver.md.orig create mode 100644 content/en/docs/reference/command-line-tools-reference/federation-controller-manager.md create mode 100644 content/en/docs/reference/federation/_index.html create mode 100755 content/en/docs/reference/federation/extensions/v1beta1/definitions.html create mode 100755 content/en/docs/reference/federation/extensions/v1beta1/operations.html create mode 100755 content/en/docs/reference/federation/federation/v1beta1/definitions.html create mode 100755 content/en/docs/reference/federation/federation/v1beta1/operations.html create mode 100755 content/en/docs/reference/federation/v1/definitions.html create mode 100755 content/en/docs/reference/federation/v1/operations.html delete mode 100644 content/en/docs/reference/glossary/applications.md delete mode 100644 content/en/docs/reference/glossary/cluster-infrastructure.md delete mode 100644 content/en/docs/reference/glossary/cluster-operations.md delete mode 100644 content/en/docs/reference/glossary/container-runtime.md delete mode 100644 content/en/docs/reference/glossary/containerd.md delete mode 100644 content/en/docs/reference/glossary/control-plane.md delete mode 100644 content/en/docs/reference/glossary/cri-o.md delete mode 100644 content/en/docs/reference/glossary/cri.md delete mode 100644 content/en/docs/reference/glossary/data-plane.md delete mode 100755 content/en/docs/reference/glossary/limitrange.md delete mode 100644 content/en/docs/reference/glossary/logging.md delete mode 100755 content/en/docs/reference/glossary/mirror-pod.md delete mode 100755 content/en/docs/reference/glossary/qos-class.md delete mode 100755 content/en/docs/reference/glossary/static-pod.md mode change 100644 => 100755 content/en/docs/reference/kubectl/kubectl.md rename content/{fr => en}/docs/reference/setup-tools/kubefed/_index.md (100%) create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed.md create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed_init.md create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed_join.md create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed_options.md create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed_unjoin.md create mode 100644 content/en/docs/reference/setup-tools/kubefed/kubefed_version.md delete mode 100644 content/en/docs/setup/best-practices/_index.md rename content/en/docs/setup/{best-practices => }/certificates.md (88%) rename content/en/docs/setup/{best-practices => }/cluster-large.md (99%) rename content/en/docs/setup/{production-environment/container-runtimes.md => cri.md} (92%) create mode 100644 content/en/docs/setup/custom-cloud/_index.md rename content/en/docs/setup/{production-environment/tools => custom-cloud}/kops.md (99%) rename content/en/docs/setup/{production-environment/tools => custom-cloud}/kubespray.md (97%) create mode 100755 content/en/docs/setup/independent/_index.md rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/control-plane-flags.md (100%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/create-cluster-kubeadm.md (95%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/ha-topology.md (94%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/high-availability.md (93%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/install-kubeadm.md (92%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/kubelet-integration.md (99%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/self-hosting.md (100%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/setup-ha-etcd-with-kubeadm.md (98%) rename content/en/docs/setup/{production-environment/tools/kubeadm => independent}/troubleshooting-kubeadm.md (90%) delete mode 100644 content/en/docs/setup/learning-environment/_index.md rename content/en/docs/setup/{learning-environment => }/minikube.md (62%) rename content/en/docs/setup/{best-practices => }/multiple-zones.md (99%) rename content/en/docs/setup/{best-practices => }/node-conformance.md (98%) rename content/en/docs/setup/{production-environment/tools => on-premises-metal}/krib.md (90%) rename content/{fr => en}/docs/setup/on-premises-vm/_index.md (100%) rename content/en/docs/setup/{production-environment => }/on-premises-vm/cloudstack.md (93%) rename content/en/docs/setup/{production-environment => }/on-premises-vm/dcos.md (100%) rename content/en/docs/setup/{production-environment => }/on-premises-vm/ovirt.md (91%) create mode 100644 content/en/docs/setup/pick-right-solution.md delete mode 100644 content/en/docs/setup/production-environment/_index.md delete mode 100644 content/en/docs/setup/production-environment/on-premises-vm/_index.md delete mode 100644 content/en/docs/setup/production-environment/tools/_index.md delete mode 100644 content/en/docs/setup/production-environment/tools/kubeadm/_index.md delete mode 100644 content/en/docs/setup/production-environment/windows/_index.md create mode 100644 content/en/docs/setup/release/building-from-source.md rename content/en/docs/setup/{production-environment => }/turnkey/_index.md (78%) rename content/en/docs/setup/{production-environment => }/turnkey/alibaba-cloud.md (96%) rename content/en/docs/setup/{production-environment => }/turnkey/aws.md (92%) rename content/en/docs/setup/{production-environment => }/turnkey/azure.md (100%) rename content/en/docs/setup/{production-environment => }/turnkey/clc.md (95%) rename content/en/docs/setup/{production-environment => }/turnkey/gce.md (97%) rename content/en/docs/setup/{production-environment => }/turnkey/icp.md (97%) rename content/en/docs/setup/{production-environment => }/turnkey/stackpoint.md (100%) rename content/en/docs/setup/{release => }/version-skew-policy.md (95%) rename content/{de => en}/docs/setup/windows/_index.md (100%) rename content/en/docs/setup/{production-environment => }/windows/flannel-master-kubeclt-get-pods.png (100%) rename content/en/docs/setup/{production-environment => }/windows/flannel-master-kubectl-get-ds.png (100%) rename content/en/docs/setup/{production-environment => }/windows/intro-windows-in-kubernetes.md (98%) rename content/en/docs/setup/{production-environment => }/windows/user-guide-windows-containers.md (100%) rename content/en/docs/setup/{production-environment => }/windows/user-guide-windows-nodes.md (95%) rename content/en/docs/setup/{production-environment => }/windows/windows-docker-error.png (100%) delete mode 100644 content/en/docs/tasks/manage-kubernetes-objects/_index.md delete mode 100644 content/en/docs/tutorials/stateless-application/guestbook-logs-metrics-with-elk.md delete mode 100644 content/en/examples/admin/resource/limit-mem-cpu-container.yaml delete mode 100644 content/en/examples/admin/resource/limit-mem-cpu-pod.yaml delete mode 100644 content/en/examples/admin/resource/limit-memory-ratio-pod.yaml delete mode 100644 content/en/examples/admin/resource/limit-range-pod-1.yaml delete mode 100644 content/en/examples/admin/resource/limit-range-pod-2.yaml delete mode 100644 content/en/examples/admin/resource/limit-range-pod-3.yaml delete mode 100644 content/en/examples/admin/resource/pvc-limit-greater.yaml delete mode 100644 content/en/examples/admin/resource/pvc-limit-lower.yaml delete mode 100644 content/en/examples/admin/resource/storagelimits.yaml delete mode 100644 content/en/examples/controllers/replication-nginx-1.7.9.yaml delete mode 100644 content/en/examples/controllers/replication-nginx-1.9.2.yaml delete mode 100644 content/en/examples/pods/inject/pod-multiple-secret-env-variable.yaml delete mode 100644 content/en/examples/pods/inject/pod-secret-envFrom.yaml delete mode 100644 content/en/examples/pods/inject/pod-single-secret-env-variable.yaml delete mode 100644 content/en/examples/policy/zookeeper-pod-disruption-budget-maxunavailable.yaml delete mode 100644 content/en/examples/policy/zookeeper-pod-disruption-budget-minavailable.yaml delete mode 100644 content/es/OWNERS delete mode 100644 content/es/_common-resources/index.md delete mode 100644 content/es/_index.html delete mode 100644 content/es/blog/_index.md delete mode 100644 content/es/case-studies/_index.html delete mode 100644 content/es/community/_index.html delete mode 100644 content/es/community/code-of-conduct.md delete mode 100644 content/es/community/static/README.md delete mode 100644 content/es/community/static/cncf-code-of-conduct.md delete mode 100644 content/es/docs/_index.md delete mode 100644 content/es/docs/_search.md delete mode 100644 content/es/docs/concepts/_index.md delete mode 100755 content/es/docs/concepts/architecture/_index.md delete mode 100644 content/es/docs/concepts/architecture/cloud-controller.md delete mode 100644 content/es/docs/concepts/architecture/master-node-communication.md delete mode 100644 content/es/docs/concepts/architecture/nodes.md delete mode 100755 content/es/docs/concepts/cluster-administration/_index.md delete mode 100755 content/es/docs/concepts/configuration/_index.md delete mode 100755 content/es/docs/concepts/containers/_index.md delete mode 100644 content/es/docs/concepts/containers/container-environment-variables.md delete mode 100644 content/es/docs/concepts/extend-kubernetes/_index.md delete mode 100644 content/es/docs/concepts/extend-kubernetes/api-extension/_index.md delete mode 100644 content/es/docs/concepts/extend-kubernetes/compute-storage-net/_index.md delete mode 100755 content/es/docs/concepts/overview/_index.md delete mode 100755 content/es/docs/concepts/overview/object-management-kubectl/_index.md delete mode 100755 content/es/docs/concepts/overview/working-with-objects/_index.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/annotations.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/common-labels.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/field-selectors.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/kubernetes-objects.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/labels.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/names.md delete mode 100644 content/es/docs/concepts/overview/working-with-objects/namespaces.md delete mode 100755 content/es/docs/concepts/policy/_index.md delete mode 100755 content/es/docs/concepts/services-networking/_index.md delete mode 100755 content/es/docs/concepts/storage/_index.md delete mode 100644 content/es/docs/concepts/workloads/_index.md delete mode 100755 content/es/docs/concepts/workloads/controllers/_index.md delete mode 100755 content/es/docs/concepts/workloads/pods/_index.md delete mode 100644 content/es/docs/contribute/_index.md delete mode 100644 content/es/docs/contribute/generate-ref-docs/_index.md delete mode 100644 content/es/docs/contribute/style/_index.md delete mode 100755 content/es/docs/getting-started-guides/_index.md delete mode 100755 content/es/docs/getting-started-guides/fedora/_index.md delete mode 100644 content/es/docs/home/_index.md delete mode 100644 content/es/docs/reference/_index.md delete mode 100644 content/es/docs/reference/access-authn-authz/_index.md delete mode 100644 content/es/docs/reference/command-line-tools-reference/_index.md delete mode 100644 content/es/docs/reference/federation/_index.md delete mode 100644 content/es/docs/reference/glossary/annotation.md delete mode 100755 content/es/docs/reference/glossary/application-architect.md delete mode 100755 content/es/docs/reference/glossary/application-developer.md delete mode 100755 content/es/docs/reference/glossary/certificate.md delete mode 100644 content/es/docs/reference/glossary/cla.md delete mode 100755 content/es/docs/reference/glossary/cluster.md delete mode 100755 content/es/docs/reference/glossary/docker.md delete mode 100755 content/es/docs/reference/glossary/image.md delete mode 100755 content/es/docs/reference/glossary/index.md delete mode 100755 content/es/docs/reference/glossary/job.md delete mode 100755 content/es/docs/reference/glossary/kops.md delete mode 100755 content/es/docs/reference/glossary/kubeadm.md delete mode 100644 content/es/docs/reference/glossary/name.md delete mode 100755 content/es/docs/reference/glossary/node.md delete mode 100755 content/es/docs/reference/glossary/pod.md delete mode 100644 content/es/docs/reference/glossary/rkt.md delete mode 100755 content/es/docs/reference/glossary/secret.md delete mode 100755 content/es/docs/reference/glossary/selector.md delete mode 100644 content/es/docs/reference/glossary/service.md delete mode 100755 content/es/docs/reference/glossary/sysctl.md delete mode 100644 content/es/docs/reference/glossary/uid.md delete mode 100644 content/es/docs/reference/issues-security/_index.md delete mode 100755 content/es/docs/reference/kubectl/_index.md delete mode 100644 content/es/docs/reference/kubernetes-api/_index.md delete mode 100644 content/es/docs/reference/kubernetes-api/index.md delete mode 100644 content/es/docs/reference/setup-tools/_index.md delete mode 100755 content/es/docs/reference/setup-tools/kubeadm/_index.md delete mode 100644 content/es/docs/reference/setup-tools/kubeadm/generated/_index.md delete mode 100644 content/es/docs/reference/setup-tools/kubefed/_index.md delete mode 100644 content/es/docs/reference/using-api/_index.md delete mode 100644 content/es/docs/setup/_index.md delete mode 100644 content/es/docs/setup/custom-cloud/_index.md delete mode 100755 content/es/docs/setup/independent/_index.md delete mode 100644 content/es/docs/setup/on-premises-vm/_index.md delete mode 100755 content/es/docs/setup/release/_index.md delete mode 100644 content/es/docs/setup/release/building-from-source.md delete mode 100644 content/es/docs/setup/turnkey/_index.md delete mode 100644 content/es/docs/setup/windows/_index.md delete mode 100644 content/es/docs/sitemap.md delete mode 100644 content/es/docs/tasks/_index.md delete mode 100755 content/es/docs/tasks/access-application-cluster/_index.md delete mode 100755 content/es/docs/tasks/access-kubernetes-api/_index.md delete mode 100755 content/es/docs/tasks/access-kubernetes-api/custom-resources/_index.md delete mode 100755 content/es/docs/tasks/administer-cluster/_index.md delete mode 100755 content/es/docs/tasks/administer-cluster/kubeadm/_index.md delete mode 100644 content/es/docs/tasks/administer-cluster/manage-resources/_index.md delete mode 100644 content/es/docs/tasks/administer-cluster/network-policy-provider/_index.md delete mode 100755 content/es/docs/tasks/configure-pod-container/_index.md delete mode 100644 content/es/docs/tasks/configure-pod-container/configure-volume-storage.md delete mode 100644 content/es/docs/tasks/debug-application-cluster/_index.md delete mode 100644 content/es/docs/tasks/debug-application-cluster/resource-metrics-pipeline.md delete mode 100755 content/es/docs/tasks/federation/_index.md delete mode 100755 content/es/docs/tasks/federation/administer-federation/_index.md delete mode 100755 content/es/docs/tasks/inject-data-application/_index.md delete mode 100644 content/es/docs/tasks/job/_index.md delete mode 100755 content/es/docs/tasks/manage-daemon/_index.md delete mode 100755 content/es/docs/tasks/run-application/_index.md delete mode 100644 content/es/docs/tasks/run-application/configure-pdb.md delete mode 100644 content/es/docs/tasks/run-application/run-stateless-application-deployment.md delete mode 100755 content/es/docs/tasks/service-catalog/_index.md delete mode 100755 content/es/docs/tasks/tls/_index.md delete mode 100644 content/es/docs/tasks/tools/_index.md delete mode 100644 content/es/docs/tasks/tools/install-kubectl.md delete mode 100644 content/es/docs/tasks/tools/install-minikube.md delete mode 100644 content/es/docs/templates/feature-state-alpha.txt delete mode 100644 content/es/docs/templates/feature-state-beta.txt delete mode 100644 content/es/docs/templates/feature-state-deprecated.txt delete mode 100644 content/es/docs/templates/feature-state-stable.txt delete mode 100644 content/es/docs/templates/index.md delete mode 100644 content/es/docs/tutorials/_index.md delete mode 100755 content/es/docs/tutorials/clusters/_index.md delete mode 100755 content/es/docs/tutorials/configuration/_index.md delete mode 100755 content/es/docs/tutorials/kubernetes-basics/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/create-cluster/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive.html delete mode 100644 content/es/docs/tutorials/kubernetes-basics/deploy-app/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive.html delete mode 100644 content/es/docs/tutorials/kubernetes-basics/explore/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/expose/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/scale/_index.md delete mode 100644 content/es/docs/tutorials/kubernetes-basics/update/_index.md delete mode 100755 content/es/docs/tutorials/online-training/_index.md delete mode 100755 content/es/docs/tutorials/services/_index.md delete mode 100755 content/es/docs/tutorials/stateful-application/_index.md delete mode 100755 content/es/docs/tutorials/stateless-application/_index.md delete mode 100644 content/es/docs/update-user-guide-links.py delete mode 100644 content/es/examples/application/deployment-scale.yaml delete mode 100644 content/es/examples/application/deployment-update.yaml delete mode 100644 content/es/examples/application/deployment.yaml delete mode 100644 content/es/examples/pods/storage/redis.yaml delete mode 100644 content/es/includes/task-tutorial-prereqs.md delete mode 100644 content/es/partners/_index.html delete mode 100644 content/fr/blog/_index.md delete mode 100644 content/fr/docs/concepts/configuration/_index.md delete mode 100644 content/fr/docs/concepts/extend-kubernetes/_index.md delete mode 100644 content/fr/docs/concepts/extend-kubernetes/api-extension/_index.md delete mode 100644 content/fr/docs/concepts/extend-kubernetes/compute-storage-net/_index.md delete mode 100644 content/fr/docs/concepts/overview/working-with-objects/_index.md delete mode 100644 content/fr/docs/concepts/policy/_index.md delete mode 100644 content/fr/docs/concepts/security/_index.md delete mode 100755 content/fr/docs/concepts/services-networking/_index.md delete mode 100644 content/fr/docs/concepts/services-networking/dns-pod-service.md delete mode 100644 content/fr/docs/concepts/services-networking/ingress.md delete mode 100644 content/fr/docs/concepts/storage/_index.md delete mode 100644 content/fr/docs/concepts/workloads/_index.md delete mode 100644 content/fr/docs/concepts/workloads/controllers/_index.md delete mode 100644 content/fr/docs/concepts/workloads/pods/_index.md delete mode 100644 content/fr/docs/concepts/workloads/pods/pod-overview.md delete mode 100644 content/fr/docs/concepts/workloads/pods/pod.md delete mode 100644 content/fr/docs/contribute/_index.md delete mode 100644 content/fr/docs/contribute/generate-ref-docs/federation-api.md delete mode 100644 content/fr/docs/contribute/generate-ref-docs/kubernetes-api.md delete mode 100644 content/fr/docs/contribute/start.md delete mode 100644 content/fr/docs/contribute/style/_index.md delete mode 100644 content/fr/docs/getting-started-guides/_index.md delete mode 100644 content/fr/docs/getting-started-guides/fedora/_index.md delete mode 100644 content/fr/docs/reference/_index.md delete mode 100644 content/fr/docs/reference/access-authn-authz/_index.md delete mode 100644 content/fr/docs/reference/command-line-tools-reference/_index.md delete mode 100644 content/fr/docs/reference/glossary/aggregation-layer.md delete mode 100644 content/fr/docs/reference/glossary/container-runtime.md delete mode 100644 content/fr/docs/reference/glossary/container.md delete mode 100644 content/fr/docs/reference/issues-security/_index.md delete mode 100644 content/fr/docs/reference/kubernetes-api/_index.md delete mode 100644 content/fr/docs/reference/setup-tools/_index.md delete mode 100644 content/fr/docs/reference/setup-tools/kubeadm/_index.md delete mode 100644 content/fr/docs/reference/setup-tools/kubeadm/generated/_index.md delete mode 100644 content/fr/docs/reference/setup-tools/kubeadm/kubeadm.md delete mode 100644 content/fr/docs/reference/using-api/_index.md delete mode 100644 content/fr/docs/setup/turnkey/_index.md delete mode 100644 content/fr/docs/setup/windows/_index.md delete mode 100644 content/fr/docs/tasks/_index.md delete mode 100644 content/fr/docs/tasks/access-application-cluster/_index.md delete mode 100644 content/fr/docs/tasks/access-kubernetes-api/_index.md delete mode 100644 content/fr/docs/tasks/access-kubernetes-api/custom-resources/_index.md delete mode 100644 content/fr/docs/tasks/administer-cluster/_index.md delete mode 100644 content/fr/docs/tasks/administer-cluster/kubeadm/_index.md delete mode 100644 content/fr/docs/tasks/administer-cluster/manage-resources/_index.md delete mode 100644 content/fr/docs/tasks/administer-cluster/network-policy-provider/_index.md delete mode 100644 content/fr/docs/tasks/configure-pod-container/_index.md delete mode 100644 content/fr/docs/tasks/debug-application-cluster/_index.md delete mode 100644 content/fr/docs/tasks/federation/_index.md delete mode 100644 content/fr/docs/tasks/federation/administer-federation/_index.md delete mode 100644 content/fr/docs/tasks/inject-data-application/_index.md delete mode 100644 content/fr/docs/tasks/job/_index.md delete mode 100644 content/fr/docs/tasks/manage-daemon/_index.md delete mode 100644 content/fr/docs/tasks/manage-kubernetes-objects/_index.md delete mode 100644 content/fr/docs/tasks/run-application/_index.md delete mode 100644 content/fr/docs/tasks/service-catalog/_index.md delete mode 100644 content/fr/docs/tasks/tls/_index.md delete mode 100644 content/fr/docs/tasks/tools/_index.md delete mode 100644 content/fr/docs/tutorials/_index.md delete mode 100644 content/fr/docs/tutorials/clusters/_index.md delete mode 100644 content/fr/docs/tutorials/configuration/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/_index.html delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/create-cluster/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive.html delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro.html delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/deploy-app/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/explore/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/expose/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/scale/_index.md delete mode 100644 content/fr/docs/tutorials/kubernetes-basics/update/_index.md delete mode 100644 content/fr/docs/tutorials/online-training/_index.md delete mode 100644 content/fr/docs/tutorials/services/_index.md delete mode 100644 content/fr/docs/tutorials/stateful-application/_index.md delete mode 100644 content/fr/docs/tutorials/stateless-application/_index.md delete mode 100644 content/fr/includes/default-storage-class-prereqs.md delete mode 100644 content/fr/includes/federated-task-tutorial-prereqs.md delete mode 100644 content/fr/includes/federation-deprecation-warning-note.md delete mode 100644 content/fr/includes/index.md delete mode 100644 content/fr/includes/partner-script.js delete mode 100644 content/fr/includes/partner-style.css delete mode 100644 content/fr/includes/task-tutorial-prereqs.md delete mode 100644 content/fr/includes/user-guide-content-moved.md delete mode 100644 content/fr/includes/user-guide-migration-notice.md delete mode 100644 content/fr/partners/_index.html delete mode 100644 content/hi/OWNERS delete mode 100644 content/hi/_common-resources/index.md delete mode 100644 content/id/OWNERS delete mode 100644 content/id/_common-resources/index.md delete mode 100644 content/id/_index.html delete mode 100644 content/id/case-studies/_index.html delete mode 100644 content/id/docs/_index.md delete mode 100644 content/id/docs/concepts/_index.md delete mode 100644 content/id/docs/concepts/architecture/_index.md delete mode 100644 content/id/docs/concepts/architecture/master-node-communication.md delete mode 100644 content/id/docs/concepts/architecture/nodes.md delete mode 100644 content/id/docs/concepts/cluster-administration/_index.md delete mode 100644 content/id/docs/concepts/cluster-administration/addons.md delete mode 100644 content/id/docs/concepts/cluster-administration/cloud-providers.md delete mode 100644 content/id/docs/concepts/cluster-administration/cluster-administration-overview.md delete mode 100644 content/id/docs/concepts/cluster-administration/controller-metrics.md delete mode 100644 content/id/docs/concepts/cluster-administration/federation.md delete mode 100644 content/id/docs/concepts/cluster-administration/kubelet-garbage-collection.md delete mode 100644 content/id/docs/concepts/cluster-administration/proxies.md delete mode 100644 content/id/docs/concepts/configuration/_index.md delete mode 100644 content/id/docs/concepts/configuration/taint-and-toleration.md delete mode 100644 content/id/docs/concepts/containers/_index.md delete mode 100644 content/id/docs/concepts/containers/container-environment-variables.md delete mode 100644 content/id/docs/concepts/containers/container-lifecycle-hooks.md delete mode 100644 content/id/docs/concepts/containers/runtime-class.md delete mode 100644 content/id/docs/concepts/overview/_index.md delete mode 100644 content/id/docs/concepts/overview/components.md delete mode 100644 content/id/docs/concepts/overview/kubernetes-api.md delete mode 100644 content/id/docs/concepts/overview/object-management-kubectl/_index.md delete mode 100644 content/id/docs/concepts/overview/object-management-kubectl/declarative-config.md delete mode 100644 content/id/docs/concepts/overview/object-management-kubectl/imperative-command.md delete mode 100644 content/id/docs/concepts/overview/object-management-kubectl/imperative-config.md delete mode 100644 content/id/docs/concepts/overview/what-is-kubernetes.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/_index.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/annotations.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/field-selectors.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/kubernetes-objects.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/names.md delete mode 100644 content/id/docs/concepts/overview/working-with-objects/namespaces.md delete mode 100644 content/id/docs/concepts/services-networking/_index.md delete mode 100644 content/id/docs/concepts/services-networking/connect-applications-service.md delete mode 100644 content/id/docs/concepts/services-networking/ingress-controllers.md delete mode 100644 content/id/docs/concepts/services-networking/ingress.md delete mode 100644 content/id/docs/concepts/services-networking/network-policies.md delete mode 100644 content/id/docs/concepts/services-networking/service.md delete mode 100644 content/id/docs/concepts/workloads/_index.md delete mode 100644 content/id/docs/concepts/workloads/controllers/_index.md delete mode 100644 content/id/docs/concepts/workloads/controllers/garbage-collection.md delete mode 100644 content/id/docs/concepts/workloads/pods/_index.md delete mode 100644 content/id/docs/concepts/workloads/pods/disruptions.md delete mode 100644 content/id/docs/concepts/workloads/pods/pod-overview.md delete mode 100644 content/id/docs/concepts/workloads/pods/podpreset.md delete mode 100644 content/id/docs/home/_index.md delete mode 100644 content/id/docs/home/supported-doc-versions.md delete mode 100644 content/id/docs/reference/glossary/etcd.md delete mode 100644 content/id/docs/reference/glossary/ingress.md delete mode 100644 content/id/docs/reference/glossary/kube-apiserver.md delete mode 100644 content/id/docs/reference/glossary/kube-controller-manager.md delete mode 100644 content/id/docs/reference/glossary/kube-scheduler.md delete mode 100644 content/id/docs/reference/glossary/kubelet.md delete mode 100755 content/id/docs/reference/glossary/name.md delete mode 100755 content/id/docs/reference/glossary/uid.md delete mode 100644 content/id/docs/search.md delete mode 100644 content/id/docs/setup/_index.md delete mode 100644 content/id/docs/sitemap.md delete mode 100644 content/id/docs/templates/feature-state-alpha.txt delete mode 100644 content/id/docs/templates/feature-state-beta.txt delete mode 100644 content/id/docs/templates/feature-state-deprecated.txt delete mode 100644 content/id/docs/templates/feaure-state-stable.txt delete mode 100644 content/id/docs/templates/index.md delete mode 100644 content/id/docs/tutorials/_index.md delete mode 100644 content/id/docs/tutorials/hello-minikube.md delete mode 100644 content/id/docs/tutorials/kubernetes-basics/_index.html delete mode 100644 content/id/examples/application/deployment.yaml delete mode 100644 content/id/examples/application/simple_deployment.yaml delete mode 100644 content/id/examples/application/update_deployment.yaml delete mode 100644 content/id/examples/controllers/replicaset.yaml delete mode 100644 content/id/examples/minikube/Dockerfile delete mode 100644 content/id/examples/minikube/server.js delete mode 100644 content/id/examples/service/networking/curlpod.yaml delete mode 100644 content/id/examples/service/networking/ingress.yaml delete mode 100644 content/id/examples/service/networking/nginx-secure-app.yaml delete mode 100644 content/id/examples/service/networking/nginx-svc.yaml delete mode 100644 content/id/examples/service/networking/run-my-nginx.yaml delete mode 100644 content/id/includes/federation-deprecation-warning-note.md delete mode 100644 content/id/includes/index.md delete mode 100644 content/it/docs/concepts/_index.md delete mode 100755 content/it/docs/concepts/architecture/_index.md delete mode 100644 content/it/docs/concepts/architecture/cloud-controller.md delete mode 100644 content/it/docs/concepts/architecture/master-node-communication.md delete mode 100644 content/it/docs/concepts/architecture/nodes.md delete mode 100755 content/it/docs/concepts/cluster-administration/_index.md delete mode 100644 content/it/docs/concepts/cluster-administration/addons.md delete mode 100644 content/it/docs/concepts/cluster-administration/certificates.md delete mode 100644 content/it/docs/concepts/cluster-administration/cloud-providers.md delete mode 100644 content/it/docs/concepts/cluster-administration/cluster-administration-overview.md delete mode 100644 content/it/docs/concepts/cluster-administration/controller-metrics.md delete mode 100644 content/it/docs/concepts/cluster-administration/federation.md delete mode 100644 content/it/docs/concepts/cluster-administration/kubelet-garbage-collection.md delete mode 100644 content/it/docs/concepts/cluster-administration/logging.md delete mode 100644 content/it/docs/concepts/cluster-administration/manage-deployment.md delete mode 100644 content/it/docs/concepts/cluster-administration/networking.md delete mode 100644 content/it/docs/concepts/cluster-administration/proxies.md delete mode 100644 content/it/docs/concepts/example-concept-template.md delete mode 100644 content/it/examples/admin/logging/fluentd-sidecar-config.yaml delete mode 100644 content/it/examples/admin/logging/two-files-counter-pod-agent-sidecar.yaml delete mode 100644 content/it/examples/admin/logging/two-files-counter-pod-streaming-sidecar.yaml delete mode 100644 content/it/examples/admin/logging/two-files-counter-pod.yaml delete mode 100644 content/it/examples/application/nginx-app.yaml delete mode 100644 content/it/examples/debug/counter-pod.yaml delete mode 100644 content/it/includes/federation-deprecation-warning-note.md delete mode 100644 content/ja/docs/setup/turnkey/icp.md delete mode 100644 content/ja/docs/setup/version-skew-policy.md create mode 100644 content/ja/examples/admin/cloud/pvl-initializer-config.yaml delete mode 100644 content/ko/docs/concepts/cluster-administration/cluster-administration-overview.md delete mode 100644 content/ko/docs/concepts/cluster-administration/controller-metrics.md create mode 100644 content/ko/docs/concepts/overview/object-management-kubectl/_index.md rename content/ko/docs/{tasks/manage-kubernetes-objects => concepts/overview/object-management-kubectl}/imperative-command.md (89%) rename content/ko/docs/concepts/overview/{working-with-objects/object-management.md => object-management-kubectl/overview.md} (91%) delete mode 100644 content/ko/docs/concepts/overview/working-with-objects/annotations.md delete mode 100644 content/ko/docs/concepts/workloads/controllers/_index.md delete mode 100644 content/ko/docs/concepts/workloads/controllers/cron-jobs.md delete mode 100644 content/ko/docs/concepts/workloads/pods/pod.md delete mode 100644 content/ko/docs/contribute/participating.md delete mode 100755 content/ko/docs/reference/glossary/annotation.md delete mode 100644 content/ko/docs/reference/glossary/app-container.md delete mode 100755 content/ko/docs/reference/glossary/cluster.md delete mode 100755 content/ko/docs/reference/glossary/container-env-variables.md delete mode 100755 content/ko/docs/reference/glossary/container.md delete mode 100755 content/ko/docs/reference/glossary/cronjob.md delete mode 100755 content/ko/docs/reference/glossary/customresourcedefinition.md delete mode 100755 content/ko/docs/reference/glossary/daemonset.md delete mode 100755 content/ko/docs/reference/glossary/deployment.md delete mode 100644 content/ko/docs/reference/glossary/device-plugin.md delete mode 100755 content/ko/docs/reference/glossary/docker.md delete mode 100644 content/ko/docs/reference/glossary/extensions.md delete mode 100755 content/ko/docs/reference/glossary/image.md delete mode 100755 content/ko/docs/reference/glossary/init-container.md delete mode 100755 content/ko/docs/reference/glossary/job.md delete mode 100755 content/ko/docs/reference/glossary/kube-proxy.md delete mode 100755 content/ko/docs/reference/glossary/kubectl.md delete mode 100755 content/ko/docs/reference/glossary/kubernetes-api.md delete mode 100755 content/ko/docs/reference/glossary/label.md delete mode 100755 content/ko/docs/reference/glossary/minikube.md delete mode 100755 content/ko/docs/reference/glossary/namespace.md delete mode 100755 content/ko/docs/reference/glossary/node.md delete mode 100644 content/ko/docs/reference/glossary/pod-lifecycle.md delete mode 100755 content/ko/docs/reference/glossary/pod-security-policy.md delete mode 100755 content/ko/docs/reference/glossary/pod.md delete mode 100755 content/ko/docs/reference/glossary/rbac.md delete mode 100755 content/ko/docs/reference/glossary/replica-set.md delete mode 100755 content/ko/docs/reference/glossary/replication-controller.md delete mode 100755 content/ko/docs/reference/glossary/resource-quota.md delete mode 100755 content/ko/docs/reference/glossary/selector.md delete mode 100755 content/ko/docs/reference/glossary/service-account.md delete mode 100755 content/ko/docs/reference/glossary/service.md delete mode 100755 content/ko/docs/reference/glossary/statefulset.md delete mode 100644 content/ko/docs/reference/glossary/taint.md delete mode 100644 content/ko/docs/reference/glossary/toleration.md delete mode 100755 content/ko/docs/reference/glossary/volume.md delete mode 100644 content/ko/docs/reference/glossary/workload.md delete mode 100644 content/ko/docs/reference/kubectl/cheatsheet.md create mode 100644 content/ko/docs/setup/pick-right-solution.md create mode 100644 content/ko/docs/setup/scratch.md delete mode 100755 content/ko/docs/tasks/access-application-cluster/_index.md delete mode 100644 content/ko/docs/tasks/access-application-cluster/access-cluster.md delete mode 100644 content/ko/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md delete mode 100644 content/ko/docs/tasks/access-application-cluster/configure-dns-cluster.md delete mode 100644 content/ko/docs/tasks/manage-kubernetes-objects/_index.md delete mode 100644 content/ko/docs/tasks/manage-kubernetes-objects/declarative-config.md delete mode 100644 content/ko/docs/tasks/manage-kubernetes-objects/imperative-config.md delete mode 100644 content/ko/docs/tutorials/clusters/_index.md delete mode 100644 content/ko/docs/tutorials/clusters/apparmor.md delete mode 100644 content/ko/docs/tutorials/clusters/deny-write.profile delete mode 100644 content/ko/docs/tutorials/services/_index.md delete mode 100644 content/ko/docs/tutorials/services/source-ip.md delete mode 100644 content/ko/docs/tutorials/stateful-application/_index.md delete mode 100644 content/ko/docs/tutorials/stateful-application/cassandra.md delete mode 100644 content/ko/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume.md delete mode 100644 content/ko/docs/tutorials/stateful-application/zookeeper.md delete mode 100644 content/ko/examples/application/cassandra/cassandra-service.yaml delete mode 100644 content/ko/examples/application/cassandra/cassandra-statefulset.yaml delete mode 100644 content/ko/examples/application/mysql/mysql-configmap.yaml delete mode 100644 content/ko/examples/application/mysql/mysql-deployment.yaml delete mode 100644 content/ko/examples/application/mysql/mysql-pv.yaml delete mode 100644 content/ko/examples/application/mysql/mysql-services.yaml delete mode 100644 content/ko/examples/application/mysql/mysql-statefulset.yaml delete mode 100644 content/ko/examples/application/simple_deployment.yaml delete mode 100644 content/ko/examples/application/update_deployment.yaml delete mode 100644 content/ko/examples/application/wordpress/mysql-deployment.yaml delete mode 100644 content/ko/examples/application/wordpress/wordpress-deployment.yaml delete mode 100644 content/ko/examples/application/zookeeper/zookeeper.yaml delete mode 100644 content/ko/examples/pods/security/hello-apparmor.yaml delete mode 100644 content/ko/examples/pods/two-container-pod.yaml delete mode 100644 content/ko/includes/federated-task-tutorial-prereqs.md rename content/ko/includes/{federation-deprecation-warning-note.md => federation-current-state.md} (100%) delete mode 100644 content/pt/OWNERS delete mode 100644 content/pt/_common-resources/index.md delete mode 100644 content/pt/_index.html delete mode 100644 content/pt/blog/_index.md delete mode 100644 content/pt/case-studies/_index.md delete mode 100644 content/pt/community/_index.html delete mode 100644 content/pt/community/code-of-conduct.md delete mode 100644 content/pt/community/static/README.md delete mode 100644 content/pt/community/static/cncf-code-of-conduct.md delete mode 100644 content/pt/docs/_index.md delete mode 100644 content/pt/docs/_search.md delete mode 100755 content/pt/docs/concepts/architecture/_index.md delete mode 100644 content/pt/docs/concepts/architecture/cloud-controller.md delete mode 100644 content/pt/docs/concepts/architecture/master-node-communication.md delete mode 100644 content/pt/docs/concepts/cluster-administration/cluster-administration-overview.md delete mode 100644 content/pt/docs/home/_index.md delete mode 100644 content/pt/docs/home/supported-doc-versions.md delete mode 100644 content/pt/docs/sitemap.md delete mode 100644 content/pt/includes/index.md delete mode 100644 content/pt/partners/_index.html delete mode 100644 content/zh/blog/_posts/2019-04-26-latest-on-localization.md delete mode 100644 content/zh/blog/_posts/2019-06-12-contributor-summit-shanghai.md delete mode 100644 content/zh/docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md create mode 100644 content/zh/docs/whatisk8s.md delete mode 100644 content/zh/examples/pods/lifecycle-events.yaml delete mode 100644 i18n/es.toml delete mode 100644 i18n/id.toml delete mode 100644 i18n/nl.toml delete mode 100644 i18n/pt.toml delete mode 100644 layouts/shortcodes/table.html delete mode 100644 layouts/shortcodes/upcoming-events.html rename {assets/sass => sass}/OWNERS (100%) rename {assets/sass => sass}/_base.sass (99%) rename {assets/sass => sass}/_case-studies.sass (100%) rename {assets/sass => sass}/_desktop.sass (100%) rename {assets/sass => sass}/_reset.sass (100%) rename {assets/sass => sass}/_size.sass (100%) rename {assets/sass => sass}/_skin.sass (100%) rename {assets/sass => sass}/_tablet.sass (100%) rename assets/sass/style.sass => sass/case-study-styles.sass (73%) mode change 100755 => 100644 create mode 100755 sass/styles.sass delete mode 100755 scripts/find_pr.py create mode 100755 scripts/sass.sh mode change 100755 => 100644 scripts/test_examples.sh delete mode 100755 scripts/upstream_changes.py create mode 100644 static/css/case-study-styles.css create mode 100644 static/css/case-study-styles.css.map delete mode 100644 static/css/newcommunity.css create mode 100644 static/css/styles.css create mode 100644 static/css/styles.css.map delete mode 100644 static/images/CaseStudy_antfinancial_banner1.jpg delete mode 100644 static/images/CaseStudy_antfinancial_banner3.jpg delete mode 100644 static/images/CaseStudy_antfinancial_banner4.jpg delete mode 100644 static/images/CaseStudy_bose_banner1.jpg delete mode 100644 static/images/CaseStudy_bose_banner3.jpg delete mode 100644 static/images/CaseStudy_bose_banner4.jpg delete mode 100644 static/images/CaseStudy_chinaunicom_banner1.jpg delete mode 100644 static/images/CaseStudy_chinaunicom_banner3.jpg delete mode 100644 static/images/CaseStudy_chinaunicom_banner4.jpg delete mode 100644 static/images/CaseStudy_ft_banner1.jpg delete mode 100644 static/images/CaseStudy_ft_banner3.jpg delete mode 100644 static/images/CaseStudy_ft_banner4.jpg delete mode 100644 static/images/CaseStudy_jdcom_banner1.jpg delete mode 100644 static/images/CaseStudy_jdcom_banner3.jpg delete mode 100644 static/images/CaseStudy_jdcom_banner4.jpg delete mode 100644 static/images/CaseStudy_montreal_banner1.jpg delete mode 100644 static/images/CaseStudy_montreal_banner3.jpg delete mode 100644 static/images/CaseStudy_montreal_banner4.jpg delete mode 100644 static/images/CaseStudy_nerdalize_banner1.jpg delete mode 100644 static/images/CaseStudy_nerdalize_banner3.jpg delete mode 100644 static/images/CaseStudy_nerdalize_banner4.jpg delete mode 100644 static/images/CaseStudy_nokia_banner1.jpg delete mode 100644 static/images/CaseStudy_nokia_banner3.jpg delete mode 100644 static/images/CaseStudy_nokia_banner4.jpg delete mode 100644 static/images/CaseStudy_pingcap_banner1.jpg delete mode 100644 static/images/CaseStudy_pingcap_banner3.jpg delete mode 100644 static/images/CaseStudy_pingcap_banner4.jpg delete mode 100644 static/images/CaseStudy_prowise_banner1.jpg delete mode 100644 static/images/CaseStudy_prowise_banner3.jpg delete mode 100644 static/images/CaseStudy_prowise_banner4.jpg delete mode 100644 static/images/CaseStudy_ricardoch_banner1.png delete mode 100644 static/images/CaseStudy_ricardoch_banner3.png delete mode 100644 static/images/CaseStudy_ricardoch_banner4.png delete mode 100644 static/images/CaseStudy_slamtec_banner1.jpg delete mode 100644 static/images/CaseStudy_slamtec_banner3.jpg delete mode 100644 static/images/CaseStudy_slamtec_banner4.jpg delete mode 100644 static/images/CaseStudy_sos_banner1.jpg delete mode 100644 static/images/CaseStudy_sos_banner3.jpg delete mode 100644 static/images/CaseStudy_sos_banner4.jpg delete mode 100644 static/images/CaseStudy_thredup_banner1.jpg delete mode 100644 static/images/CaseStudy_thredup_banner3.jpg delete mode 100644 static/images/CaseStudy_thredup_banner4.jpg delete mode 100644 static/images/CaseStudy_vsco_banner1.jpg delete mode 100644 static/images/CaseStudy_vsco_banner2.jpg delete mode 100644 static/images/CaseStudy_vsco_banner4.jpg delete mode 100644 static/images/CaseStudy_woorank_banner1.jpg delete mode 100644 static/images/CaseStudy_woorank_banner3.jpg delete mode 100644 static/images/CaseStudy_woorank_banner4.jpg delete mode 100644 static/images/antfinancial_logo.png delete mode 100644 static/images/blog/2019-03-26-kube-proxy-subtleties-debugging-an-intermittent-connection-resets/connection-reset-packet-flow.png delete mode 100644 static/images/blog/2019-03-26-kube-proxy-subtleties-debugging-an-intermittent-connection-resets/good-packet-flow.png delete mode 100644 static/images/blog/2019-03-28-running-kubernetes-locally-on-linux-with-minikube/ihor-dvoretskyi-1470985-unsplash.jpg delete mode 100644 static/images/blog/2019-03-28-running-kubernetes-locally-on-linux-with-minikube/module_01_cluster.png delete mode 100644 static/images/blog/2019-04-23-hardware-accelerated-tls-termination/k8s-blog-fig1.png delete mode 100644 static/images/blog/2019-04-23-hardware-accelerated-tls-termination/k8s-blog-fig2.png delete mode 100644 static/images/blog/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease/ac-s-sc.svg delete mode 100644 static/images/blog/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease/arch.png delete mode 100644 static/images/blog/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease/asyncApiSpec.json delete mode 100644 static/images/blog/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease/grafana-lambda.png delete mode 100644 static/images/blog/2019-05-23-Kyma-extend-and-build-on-kubernetes-with-ease/kyma-center.png delete mode 100644 static/images/blog/2019-06-11-contributor-summit-shanghai/panel.png delete mode 100644 static/images/bose_logo.png delete mode 100644 static/images/chinaunicom_logo.png delete mode 100644 static/images/community/discuss.png delete mode 100644 static/images/community/event-bg.jpg delete mode 100644 static/images/community/github.png delete mode 100644 static/images/community/kubernetes-community-02-mobile.jpg delete mode 100644 static/images/community/kubernetes-community-04-mobile.jpg delete mode 100644 static/images/community/kubernetes-community-contributor.jpg delete mode 100644 static/images/community/kubernetes-community-final-02.jpg delete mode 100644 static/images/community/kubernetes-community-final-03.jpg delete mode 100644 static/images/community/kubernetes-community-final-04.jpg delete mode 100644 static/images/community/kubernetes-community-final-05.jpg delete mode 100644 static/images/community/kubernetes-community-final-06.jpg delete mode 100644 static/images/community/kubernetes-community-final-07.jpg delete mode 100644 static/images/community/kubernetes-community-final-08.jpg delete mode 100644 static/images/community/kubernetes-community-final.jpg delete mode 100644 static/images/community/slack.png delete mode 100644 static/images/community/stack.png delete mode 100644 static/images/community/twitter.png delete mode 100644 static/images/docs/4c.png delete mode 100644 static/images/docs/KubernetesSolutions.svg delete mode 100644 static/images/docs/contribute/claim-host.png delete mode 100644 static/images/ft_logo.png delete mode 100644 static/images/jdcom_logo.png delete mode 100644 static/images/montreal_logo.png delete mode 100644 static/images/nerdalize_logo.png delete mode 100644 static/images/nokia_logo.png delete mode 100644 static/images/pingcap_logo.png delete mode 100644 static/images/prowise_logo.png delete mode 100644 static/images/ricardoch_logo.png delete mode 100644 static/images/slamtec_logo.png delete mode 100644 static/images/sos_logo.png delete mode 100644 static/images/thredup_logo.png delete mode 100644 static/images/vsco_logo.png delete mode 100644 static/images/woorank_logo.png create mode 100644 static/js/bootstrap-3.3.7.min.js delete mode 100644 static/js/bootstrap-4.3.1.min.js diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE.md similarity index 79% rename from .github/ISSUE_TEMPLATE/bug-report.md rename to .github/ISSUE_TEMPLATE.md index 88498bdbcb21d..55625565c9109 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ b/.github/ISSUE_TEMPLATE.md @@ -1,19 +1,19 @@ ---- -name: Bug Report -about: Report a bug encountered with Kubernetes Website -labels: -- kind/bug ---- -**This is a Bug Report** - + +**This is a...** + +- [ ] Feature Request +- [ ] Bug Report + **Problem:** + **Proposed Solution:** + **Page to Update:** https://kubernetes.io/... diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md deleted file mode 100644 index 3e9ad93ccc228..0000000000000 --- a/.github/ISSUE_TEMPLATE/feature-request.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -name: Feature Request -about: Suggest a/an feature/enhancement to the Kubernetes Website project -labels: -- kind/feature ---- -**This is a Feature Request** - - - - -**What would you like to be added** - - -**Why is this needed** - -**Comments** - diff --git a/.github/ISSUE_TEMPLATE/support.md b/.github/ISSUE_TEMPLATE/support.md deleted file mode 100644 index 6c55d7737bb09..0000000000000 --- a/.github/ISSUE_TEMPLATE/support.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -name: Support Request -about: Support request or question relating to Kubernetes Dashboard project -labels: -- triage/support ---- -**This is Support** - - diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 3444bf3b2c044..85229c98efab3 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,16 +1,16 @@ >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -> Remember to delete this note before submitting your pull request. +> Please delete this note before submitting the pull request. > -> For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15 +> For 1.14 Features: set Milestone to 1.14 and Base Branch to dev-1.14 > -> For pull requests on Chinese localization, set Base Branch to release-1.14 +> For Chinese localization, base branch to release-1.12 > -> For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.\ +> For Korean Localization: set Base Branch to dev-1.13-ko. > -> If you need Help on editing and submitting pull requests, visit: +> Help editing and submitting pull requests: > https://kubernetes.io/docs/contribute/start/#improve-existing-content. > -> If you need Help on choosing which branch to use, visit: +> Help choosing which branch to use: > https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use. >^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > diff --git a/.gitignore b/.gitignore index 01a54c0679220..50d954cf3d921 100644 --- a/.gitignore +++ b/.gitignore @@ -1,6 +1,7 @@ **/.DS_Store **/desktop.ini _site/** +.sass-cache/** CNAME .travis.yml .idea/ diff --git a/Dockerfile b/Dockerfile index fd02b02d7eb0b..d8a60ea07f522 100644 --- a/Dockerfile +++ b/Dockerfile @@ -20,7 +20,7 @@ ARG HUGO_VERSION RUN mkdir -p /usr/local/src && \ cd /usr/local/src && \ - curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_extended_${HUGO_VERSION}_Linux-64bit.tar.gz | tar -xz && \ + curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz && \ mv hugo /usr/local/bin/hugo && \ addgroup -Sg 1000 hugo && \ adduser -Sg hugo -u 1000 -h /src hugo diff --git a/Makefile b/Makefile index 6543bdc41738b..f44e04b46eb62 100644 --- a/Makefile +++ b/Makefile @@ -5,7 +5,7 @@ DOCKER_RUN = $(DOCKER) run --rm --interactive --tty --volume $(CURDIR):/src NODE_BIN = node_modules/.bin NETLIFY_FUNC = $(NODE_BIN)/netlify-lambda -.PHONY: all build build-preview help serve +.PHONY: all build sass build-preview help serve help: ## Show this help. @awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {sub("\\\\n",sprintf("\n%22c"," "), $$2);printf "\033[36m%-20s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST) @@ -26,9 +26,15 @@ check-headers-file: production-build: check-hugo-versions build check-headers-file ## Build the production site and ensure that noindex headers aren't added -non-production-build: test-examples check-hugo-versions ## Build the non-production site, which adds noindex headers to prevent indexing +non-production-build: check-hugo-versions ## Build the non-production site, which adds noindex headers to prevent indexing hugo --enableGitInfo +sass-build: + scripts/sass.sh build + +sass-develop: + scripts/sass.sh develop + serve: ## Boot the development server. hugo server --buildFuture @@ -41,9 +47,12 @@ docker-build: docker-serve: $(DOCKER_RUN) -p 1313:1313 $(DOCKER_IMAGE) hugo server --buildFuture --bind 0.0.0.0 -test-examples: - scripts/test_examples.sh install - scripts/test_examples.sh run +# This command is used only by Travis CI; do not run this locally +travis-hugo-build: + curl -L https://github.com/gohugoio/hugo/releases/download/v${HUGO_VERSION}/hugo_${HUGO_VERSION}_linux-64bit.tar.gz | tar -xz + mkdir -p ${TRAVIS_HOME}/bin + mv hugo ${TRAVIS_HOME}/bin + export PATH=${TRAVIS_HOME}/bin:$PATH check-hugo-versions: scripts/hugo-version-check.sh $(HUGO_VERSION) diff --git a/OWNERS_ALIASES b/OWNERS_ALIASES index 6201e027e9aba..2fc655ee06605 100644 --- a/OWNERS_ALIASES +++ b/OWNERS_ALIASES @@ -20,11 +20,9 @@ aliases: - dixudx sig-docs-de-owners: # Admins for German content - bene2k1 - - mkorbi - rlenferink sig-docs-de-reviews: # PR reviews for German content - bene2k1 - - mkorbi - rlenferink sig-docs-en-owners: # Admins for English content - bradamant3 @@ -50,18 +48,11 @@ aliases: - stewart-yu - xiangpengzhao - zhangxiaoyu-zidif - sig-docs-es-owners: # Admins for Spanish content - - raelga - - alexbrand - sig-docs-es-reviews: # PR reviews for Spanish content - - raelga - - alexbrand - - glo-pena - - electrocucaracha sig-docs-fr-owners: # Admins for French content - - remyleone + - sieben - perriea - rekcah78 + - lledru - yastij - smana - rbenzair @@ -71,9 +62,10 @@ aliases: - awkif - oussemos sig-docs-fr-reviews: # PR reviews for French content - - remyleone + - sieben - perriea - rekcah78 + - lledru - yastij - smana - rbenzair @@ -82,34 +74,20 @@ aliases: - jygastaud - awkif - oussemos - sig-docs-hi-owners: # Admins for Hindi content - - avidLearnerInProgress - - daminisatya - - mittalyashu - - Rajakavitha1 - sig-docs-hi-reviews: # PR reviews for Hindi content - - avidLearnerInProgress - - daminisatya - - mittalyashu - - Rajakavitha1 - sig-docs-id-owners: # Admins for Indonesian content - - girikuncoro - - irvifa - sig-docs-id-reviews: # PR reviews for Indonesian content - - girikuncoro - - irvifa sig-docs-it-owners: # Admins for Italian content - rlenferink + - lledru - micheleberardi sig-docs-it-reviews: # PR reviews for Italian content - rlenferink + - lledru - micheleberardi sig-docs-ja-owners: # Admins for Japanese content - cstoku - nasa9084 - tnir - zacharysarah - sig-docs-ja-reviews: # PR reviews for Japanese content + sig-docs-ja-reviews: # PR reviews for Italian content - cstoku - makocchi-git - MasayaAoyama @@ -124,7 +102,6 @@ aliases: - ClaudiaJKang - gochist - ianychoi - - seokho-son sig-docs-maintainers: # Website maintainers - bradamant3 - chenopis @@ -163,9 +140,4 @@ aliases: - xichengliudui - zhangxiaoyu-zidif - pigletfly - sig-docs-pt-owners: # Admins for Portuguese content - - femrtnz - - jcjesus - sig-docs-pt-reviews: # PR reviews for Portugese content - - femrtnz - - jcjesus + \ No newline at end of file diff --git a/README-de.md b/README-de.md index 76087f403eda5..200837259f9d9 100644 --- a/README-de.md +++ b/README-de.md @@ -7,9 +7,9 @@ Herzlich willkommen! Dieses Repository enthält alle Assets, die zur Erstellung ## Beiträge zur Dokumentation -Sie können auf die Schaltfläche **Fork** im oberen rechten Bereich des Bildschirms klicken, um eine Kopie dieses Repositorys in Ihrem GitHub-Konto zu erstellen. Diese Kopie wird als *Fork* bezeichnet. Nehmen Sie die gewünschten Änderungen an Ihrem Fork vor. Wenn Sie bereit sind, diese Änderungen an uns zu senden, gehen Sie zu Ihrem Fork und erstellen Sie eine neue Pull-Anforderung, um uns darüber zu informieren. +Sie können auf die Schaltfläche **Fork** im oberen rechten Bereich des Bildschirms klicken, um eine Kopie dieses Repositorys in Ihrem GitHub-Konto zu erstellen. Diese Kopie wird als *Fork* bezeichnet. Nehmen Sie die gewünschten Änderungen an Ihrem Fork vor. Wenn Sie bereit sind, diese Änderungen an uns zu senden, gehen Sie zu Ihrem Form und erstellen Sie eine neue Pull-Anforderung, um uns darüber zu informieren. -Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest enstsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Ãœberprüfung von einem [Kubernetes Tech-Reviewer](https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren. +Sobald Ihre Pull-Anfrage erstellt wurde, übernimmt ein Rezensent von Kubernetes die Verantwortung für klares, umsetzbares Feedback. Als Eigentümer des Pull-Request **liegt es in Ihrer Verantwortung Ihren Pull-Reqest enstsprechend des Feedbacks, dass Sie vom Kubernetes-Reviewer erhalten haben abzuändern.** Beachten Sie auch, dass Sie am Ende mehr als einen Rezensenten von Kubernetes erhalten, der Ihnen Feedback gibt, oder dass Sie Rückmeldungen von einem Rezensenten von Kubernetes erhalten, der sich von demjenigen unterscheidet, der ursprünglich für das Feedback zugewiesen wurde. In einigen Fällen kann es vorkommen, dass einer Ihrer Prüfer bei Bedarf eine technische Ãœberprüfung von einem [Kubernetes Techn-Reviewer] (https://github.com/kubernetes/website/wiki/tech-reviewers) anfordert. Reviewer geben ihr Bestes, um zeitnah Feedback zu geben, die Antwortzeiten können jedoch je nach den Umständen variieren. Weitere Informationen zum Beitrag zur Kubernetes-Dokumentation finden Sie unter: @@ -21,12 +21,14 @@ Weitere Informationen zum Beitrag zur Kubernetes-Dokumentation finden Sie unter: ## `README.md`'s Localizing Kubernetes Documentation -### Deutsch -Die Betreuer der deutschen Lokalisierung erreichen Sie unter: +### Koreanisch -* Benedikt Rollik ([@bene2k1](https://github.com/bene2k1)) -* Max Körbächer ([@mkorbi](https://github.com/mkorbi)) -* [Slack Kanal](https://kubernetes.slack.com/messages/kubernetes-docs-de) +Lesen Sie die Ãœbersetzung von `README.md` und detailliertere Anleitungen für koreanische Mitwirkende auf der Seite [Koreanischen README] (README-ko.md). + +Sie können die Betreuer der koreanischen Lokalisierung erreichen unter: + +* June Yi ([GitHub - @gochist](https://github.com/gochist)) +* [Slack Kanal](https://kubernetes.slack.com/messages/kubernetes-docs-ko) ## Site lokal mit Docker ausführen @@ -74,7 +76,7 @@ Sie können die Betreuer dieses Projekts unter folgender Adresse erreichen: ### Verhaltensregeln -Die Teilnahme an der Kubernetes-Community unterliegt dem [Kubernetes-Verhaltenskodex](code-of-conduct.md). +Die Teilnahme an der Kubernetes-Community unterliegt dem [Kubernetes-Verhaltenskodex] (code-of-conduct.md). ## Vielen Dank! diff --git a/README-es.md b/README-es.md deleted file mode 100644 index 15bf9ed2fb2a4..0000000000000 --- a/README-es.md +++ /dev/null @@ -1,76 +0,0 @@ -# La documentación de Kubernetes - -[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website) -[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) - -Bienvenido! -Este repositorio contiene todos los recursos necesarios para construir el [sitio web de Kubernetes y su documentación](https://kubernetes.io/). ¡Estamos encantados de que quiera contribuir! - -## Contribuyendo con la documentación - -Puede hacer clic en el botón **Fork** situado en la esquina superior derecha de la pantalla para crear una copia de este repositorio en su cuenta de GitHub. A ese tipo de copia se le llama **Fork** (bifurcación) y le permite editar el contenido del repositorio en su copia personal. Realice los cambios que quiera en su **fork** y, cuando esté listo para enviarnos esos cambios, vaya a **fork** en repositorio en su GitHub y cree una nueva **pull request** para que tengamos constancia de la propuesta de cambios. - -Una vez la **pull request** ha sido creada, un revisor de Kubernetes asumirá la responsabilidad de proporcionar comentarios claros y prácticos sobre como continuar. Como propietario de la PR, **es su responsabilidad modificar la pull request para abordar los comentarios proporcionados por el revisor de Kubernetes.** Tenga en cuenta que algunas veces puede terminar teniendo más de un revisor de Kubernetes participando en la revisión, por lo que es posible que reciba comentarios de más revisores a parte del asignado originalmente en la creación de la **pull request**. Además, en algunas ocasiones, es posible que uno de sus revisores solicite una revisión técnica por parte de un [revisor técnico de Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) si lo considera necesario. - -Los revisores harán todo lo posible para proporcionar toda la información necesaria para que la **pull request** siga adelante en un tiempo razonable, pero este tiempo de respuesta puede variar según las circunstancias. - -Para obtener más información sobre cómo contribuir a la documentación de Kubernetes, puede consultar: - -* [Empezando a contribuir](https://kubernetes.io/docs/contribute/start/) -* [Visualizando sus cambios en su entorno local](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally) -* [Utilizando las plantillas de las páginas](http://kubernetes.io/docs/contribute/style/page-templates/) -* [Guía de estilo de la documentación](http://kubernetes.io/docs/contribute/style/style-guide/) -* [Traduciendo la documentación de Kubernetes](https://kubernetes.io/docs/contribute/localization/) - -## Levantando el sitio web kubernetes.io en su entorno local con Docker - -El método recomendado para levantar una copia local del sitio web kubernetes.io es utilizando la imagen de [Docker](https://docker.com) que incluye el generador de sitios estáticos [Hugo](https://gohugo.io). - -> Para Windows, algunas otras herramientas como Make son necesarias. Puede instalarlas utilizando el gestor [Chocolatey](https://chocolatey.org). `choco install make` o siguiendo las instrucciones de [Make for Windows](http://gnuwin32.sourceforge.net/packages/make.htm). - -> Si prefiere levantar el sitio web sin utilizar **Docker**, puede seguir las instrucciones disponibles en la sección [Levantando kubernetes.io en local con Hugo](#levantando-kubernetes.io-en-local-con-hugo). - -Una vez tenga Docker [configurado en su máquina](https://www.docker.com/get-started), puede construir la imagen de Docker `kubernetes-hugo` localmente ejecutando el siguiente comando en la raíz del repositorio: - -```bash -make docker-image -``` - -Una vez tenga la imagen construida, puede levantar el sitio web ejecutando: - -```bash -make docker-serve -``` - -Abra su navegador y visite http://localhost:1313 para acceder a su copia local del sitio. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador. - -## Levantando kubernetes.io en local con Hugo - -Revise la [documentación oficial de Hugo](https://gohugo.io/getting-started/installing/) para obtener las instrucciones de instalación en su sistema operativo. Asegúrese de instalar la versión de Hugo especificada en la variable de entorno `HUGO_VERSION` del fichero [`netlify.toml`](netlify.toml#L9). - -Para levantar el sitio localmente una vez Hugo está instalado en su sistema, puede ejecutar el siguiente comando: - -```bash -make serve -``` - -Este comando levantará un servidor de Hugo en el puerto **1313** al que podrá acceder visitando http://localhost:1313 y dónde podrá visualizar su copia local del sitio web. A medida que vaya haciendo cambios en el código fuente, Hugo irá actualizando la página y forzará la actualización en el navegador. - -## Comunidad, discusión, contribuir y soporte - -Aprenda como participar en la comunidad de Kubernetes visitando la [página de comunidad](http://kubernetes.io/community/). - -Puede ponerse en contacto con los mantenedores de este proyecto en: - -- [Slack](https://kubernetes.slack.com/messages/sig-docs) -- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) - -### Código de conducta - -La participación en la comunidad de Kubernetes está regulada por el [Código de Conducta de Kubernetes](code-of-conduct.md). - -## ¡Muchas gracias! - -Kubernetes es posible gracias a la participación de la comunidad y la documentación es vital para facilitar el acceso al proyecto. - -Agradecemos muchísimo sus contribuciones a nuestro sitio web y nuestra documentación. \ No newline at end of file diff --git a/README-hi.md b/README-hi.md deleted file mode 100644 index 12bfeee63c976..0000000000000 --- a/README-hi.md +++ /dev/null @@ -1,84 +0,0 @@ -# कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ पà¥à¤°à¤²à¥‡à¤–न - -[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website) -[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) - -सà¥à¤µà¤¾à¤—त हे! इस रिपॉजिटरी में [कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ वेबसाइट और दसà¥à¤¤à¤¾à¤µà¥‡à¤œ](https://kubernetes.io/) बनाने के लिठआवशà¥à¤¯à¤• सभी संपतà¥à¤¤à¤¿à¤¯à¤¾à¤‚ हैं। हम बहà¥à¤¤ खà¥à¤¶ हैं कि आप योगदान करना चाहते हैं! - -## डॉकà¥à¤¸ में योगदान देना - -आप अपने GitHub खाते में इस रिपॉजिटरी की à¤à¤• copy बनाने के लिठसà¥à¤•à¥à¤°à¥€à¤¨ के ऊपरी-दाà¤à¤ कà¥à¤·à¥‡à¤¤à¥à¤° में **Fork** बटन पर कà¥à¤²à¤¿à¤• करें। इस copy को *Fork* कहा जाता है। अपने fork में कोई भी परिवरà¥à¤¤à¤¨ करना चाहते हैं, और जब आप उन परिवरà¥à¤¤à¤¨à¥‹à¤‚ को हमारे पास भेजने के लिठतैयार हों, तो अपने fork पर जाà¤à¤‚ और हमें इसके बारे में बताने के लिठà¤à¤• नया pull request बनाà¤à¤‚। - -à¤à¤• बार जब आपका pull request बन जाता है, तो à¤à¤• कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समीकà¥à¤·à¤• सà¥à¤ªà¤·à¥à¤Ÿ, कारà¥à¤°à¤µà¤¾à¤ˆ योगà¥à¤¯ पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ पà¥à¤°à¤¦à¤¾à¤¨ करने की जिमà¥à¤®à¥‡à¤¦à¤¾à¤°à¥€ लेगा। pull request के मालिक के रूप में, **यह आपकी जिमà¥à¤®à¥‡à¤¦à¤¾à¤°à¥€ है कि आप कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समीकà¥à¤·à¤• दà¥à¤µà¤¾à¤°à¤¾ पà¥à¤°à¤¦à¤¾à¤¨ की गई पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ को संबोधित करने के लिठअपने pull request को संशोधित करें।** - -यह भी धà¥à¤¯à¤¾à¤¨ दें कि आप à¤à¤• से अधिक कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समीकà¥à¤·à¤• आपको पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ पà¥à¤°à¤¦à¤¾à¤¨ कर सकते हैं या आप à¤à¤• कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समीकà¥à¤·à¤• से पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ पà¥à¤°à¤¾à¤ªà¥à¤¤ कर सकते हैं जो मूल रूप से आपको पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ पà¥à¤°à¤¦à¤¾à¤¨ करने के लिठदिठगठà¤à¤• से भिनà¥à¤¨ है। इसके अलावा, कà¥à¤› मामलों में, आपका à¤à¤• समीकà¥à¤·à¤• जरूरत पड़ने पर [कà¥à¤¬à¥‡à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ टेक समीकà¥à¤·à¤•](https://github.com/kubernetes/website/wiki/Tech-reviewers) से तकनीकी समीकà¥à¤·à¤¾ पà¥à¤°à¤¾à¤ªà¥à¤¤ कर सकता है। समीकà¥à¤·à¤• समय पर पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ देने के लिठपूरी कोशिश करेंगे, लेकिन परिसà¥à¤¥à¤¿à¤¤à¤¿à¤¯à¥‹à¤‚ के आधार पर पà¥à¤°à¤¤à¤¿à¤•à¥à¤°à¤¿à¤¯à¤¾ समय अलग-अलग हो सकता है। - -कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ पà¥à¤°à¤²à¥‡à¤–न में योगदान देने के बारे में अधिक जानकारी के लिà¤, देखें: - -* [योगदान देना शà¥à¤°à¥‚ करें](https://kubernetes.io/docs/contribute/start/) -* [परिवरà¥à¤¤à¤¨à¥‹à¤‚ को अंतिम चरण में लेजाà¤à¤‚](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally) -* [पेज टेमà¥à¤ªà¤²à¥‡à¤Ÿ](http://kubernetes.io/docs/contribute/style/page-templates/) -* [पà¥à¤°à¤²à¥‡à¤–न शैली गाइड](http://kubernetes.io/docs/contribute/style/style-guide/) -* [सà¥à¤¥à¤¾à¤¨à¥€à¤¯à¤•à¤°à¤£ कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ पà¥à¤°à¤²à¥‡à¤–न](https://kubernetes.io/docs/contribute/localization/) - -## `README.md`'s सà¥à¤¥à¤¾à¤¨à¥€à¤¯à¤•à¤°à¤£ कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ पà¥à¤°à¤²à¥‡à¤–न - -आप पर हिंदी सà¥à¤¥à¤¾à¤¨à¥€à¤¯à¤•à¤°à¤£ के maintainers तक पहà¥à¤à¤š सकते हैं: - -* Yashu Mittal ([Twitter](https://twitter.com/mittalyashu77), [GitHub](https://github.com/mittalyashu)) -* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-hi) - -## सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से डॉकर का उपयोग करके साइट चलाना - -कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ वेबसाइट को सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से चलाने के लिठअनà¥à¤¶à¤‚सित तरीका à¤à¤• विशेष [डॉकर](https://docker.com) image को चलाना है, जिसमें [Hugo](https://gohugo.io) सà¥à¤Ÿà¥‡à¤Ÿà¤¿à¤• साइट जनरेटर शामिल है। - -> यदि आप विंडोज पर हैं, तो आपको कà¥à¤› और टूलà¥à¤¸ की आवशà¥à¤¯à¤•à¤¤à¤¾ होगी जिनà¥à¤¹à¥‡à¤‚ आप [Chocolatey](https://chocolatey.org) के साथ इंसà¥à¤Ÿà¥‰à¤² कर सकते हैं। - -> यदि आप डॉकर के बिना सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे Hugo का उपयोग करके सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से साइट चलाना देखें। - -यदि आप डॉकर के बिना सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से वेबसाइट चलाना पसंद करते हैं, तो नीचे दिठगठHugo का उपयोग करके सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से [साइट को चलाने](#running-the-site-locally-using-hugo) का तरीका देखें। - -यदि आप [डॉकर](https://www.docker.com/get-started) चला रहे हैं, तो सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से `कà¥à¤¬à¥‡à¤°à¤¨à¥‡à¤Ÿà¥à¤¸-हà¥à¤¯à¥‚गो` Docker image बनाà¤à¤: - -```bash -make docker-image -``` - -à¤à¤• बार image बन जाने के बाद, आप साइट को सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से चला सकते हैं: - -```bash -make docker-serve -``` - -साइट देखने के लिठअपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवरà¥à¤¤à¤¨ करते हैं, Hugo साइट को अपडेट करता है और browser को refresh करने पर मजबूर करता है। - -## Hugo का उपयोग करते हà¥à¤ सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से साइट चलाना - -Hugo निरà¥à¤¦à¥‡à¤¶à¥‹à¤‚ के लिठ[आधिकारिक Hugo पà¥à¤°à¤²à¥‡à¤–न](https://gohugo.io/getting-started/installing/) देखें। [`Netlify.toml`](netlify.toml#L9) फ़ाइल में `HUGO_VERSION` environment variable दà¥à¤µà¤¾à¤°à¤¾ निरà¥à¤¦à¤¿à¤·à¥à¤Ÿ Hugo version को install करना सà¥à¤¨à¤¿à¤¶à¥à¤šà¤¿à¤¤ करें। - -जब आप Hugo को install करते हैं तो सà¥à¤¥à¤¾à¤¨à¥€à¤¯ रूप से साइट को चलाने के लिà¤: - -```bash -make serve -``` - -यह पोरà¥à¤Ÿ `1313` पर Hugo सरà¥à¤µà¤° को शà¥à¤°à¥‚ करेगा। साइट देखने के लिठअपने browser को `http://localhost:1313` पर खोलें। जैसा कि आप source फ़ाइलों में परिवरà¥à¤¤à¤¨ करते हैं, Hugo साइट को अपडेट करता है और à¤à¤• browser को refresh करने पर मजबूर करता है। - -## समà¥à¤¦à¤¾à¤¯, चरà¥à¤šà¤¾, योगदान और समरà¥à¤¥à¤¨ - -[Community page](http://kubernetes.io/community/) पर कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समà¥à¤¦à¤¾à¤¯ के साथ जà¥à¤¡à¤¼à¤¨à¤¾ सीखें। - -आप इस परियोजना के सà¥à¤¥à¤¾à¤¨à¥€à¤¯à¤•à¤°à¤£ तक पहà¥à¤à¤š सकते हैं: - -- [Slack](https://kubernetes.slack.com/messages/sig-docs) -- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) - -## कोड ओफ़ कंडकà¥à¤Ÿ - -कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ समà¥à¤¦à¤¾à¤¯ में भागीदारी [कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ कोड ओफ़ कंडकà¥à¤Ÿ](https://github.com/cncf/foundation/blob/master/code-of-conduct-languages/hi.md) दà¥à¤µà¤¾à¤°à¤¾ शासित है. - -## धनà¥à¤¯à¤µà¤¾à¤¦! - -कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ सामà¥à¤¦à¤¾à¤¯à¤¿à¤• भागीदारी पर पनपती है, और हम वासà¥à¤¤à¤µ में हमारी साइट और हमारे पà¥à¤°à¤²à¥‡à¤–न में आपके योगदान की सराहना करते हैं! - -कà¥à¤¬à¤°à¤¨à¥‡à¤Ÿà¥à¤¸ आपकी भागीदारी पर निरà¥à¤­à¤° है, और हम हमारी साइट और पà¥à¤°à¤²à¥‡à¤–न में आपके योगदान का मान करते हैं! \ No newline at end of file diff --git a/README-id.md b/README-id.md deleted file mode 100644 index b178b220bc38e..0000000000000 --- a/README-id.md +++ /dev/null @@ -1,72 +0,0 @@ -# Dokumentasi Kubernetes - -[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website) -[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) - -Selamat datang! Repositori ini merupakan wadah bagi semua komponen yang dibutuhkan untuk membuat [dokumentasi Kubernetes](https://kubernetes.io/). Kami merasa sangat senang apabila kamu berminat untuk menjadi kontributor! - -## Kontribusi pada dokumentasi - -Pertama, kamu dapat menekan tombol **Fork** yang berada pada bagian atas layar, untuk menyalin repositori pada akun Github-mu. Salinan ini disebut sebagai **fork**. Kamu dapat menambahkan konten pada **fork** yang kamu miliki, setelah kamu merasa cukup untuk menambahkan konten yang kamu miliki dan ingin memberikan konten tersebut pada kami, kamu dapat melihat **fork** yang telah kamu buat dan membuat **pull request** untuk memberi tahu kami bahwa kamu ingin menambahkan konten yang telah kamu buat. - -Setelah kamu membuat sebuah **pull request**, seorang **reviewer** akan memberikan masukan terhadap konten yang kamu sediakan serta beberapa hal yang dapat kamu lakukan apabila perbaikan diperlukan terhadap konten yang telah kamu sediakan. Sebagai seorang yang membuat **pull request**, **sudah menjadi kewajiban kamu untuk melakukan modifikasi terhadap konten yang kamu berikan sesuai dengan masukan yang diberikan oleh seorang reviewer Kubernetes**. Perlu kamu ketahui bahwa kamu dapat saja memiliki lebih dari satu orang **reviewer Kubernetes** atau dalam kasus kamu bisa saja mendapatkan **reviewer Kubernetes** yang berbeda dengan **reviewer Kubernetes** awal yang ditugaskan untuk memberikan masukan terhadap konten yang kamu sediakan. Selain itu, seorang **reviewer Kubernetes** bisa saja meminta masukan teknis dari [reviewer teknis Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) jika diperlukan. - -Untuk informasi lebih lanjut mengenai tata cara melakukan kontribusi, kamu dapat melihat tautan di bawah ini: - -* [Petunjuk Melakukan Kontribusi](https://kubernetes.io/docs/contribute/start/) -* [Melakukan Tahap Staging pada Konten Dokumentasi yang telah Kamu Sediakan](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally) -* [Petunjuk Menggunakan Page Templates](http://kubernetes.io/docs/contribute/style/page-templates/) -* [Petunjuk untuk Documentation Style](http://kubernetes.io/docs/contribute/style/style-guide/) -* [Petunjuk untuk Melakukan Lokalisasi Dokumentasi Kubernetes](https://kubernetes.io/docs/contribute/localization/) - -## Menjalankan Dokumentasi Kubernetes pada Mesin Lokal Kamu - -Petunjuk yang disarankan untuk menjalankan Dokumentasi Kubernetes pada mesin lokal kamus adalah dengan menggunakan [Docker](https://docker.com) **image** yang memiliki **package** [Hugo](https://gohugo.io), **Hugo** sendiri merupakan generator website statis. - -> Jika kamu menggunakan Windows, kamu mungkin membutuhkan beberapa langkah tambahan untuk melakukan instalasi perangkat lunak yang dibutuhkan. Instalasi ini dapat dilakukan dengan menggunakan [Chocolatey](https://chocolatey.org). `choco install make` - -> Jika kamu ingin menjalankan **website** tanpa menggunakan **Docker**, kamu dapat melihat tautan berikut [Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo](#petunjuk-untuk-menjalankan-website-pada-mesin-lokal-denga-menggunakan-hugo) di bagian bawah. - -Jika kamu sudah memiliki **Docker** [yang sudah dapat digunakan](https://www.docker.com/get-started), kamu dapat melakukan **build** `kubernetes-hugo` **Docker image** secara lokal: - -```bash -make docker-image -``` - -Setelah **image** berhasil di-**build**, kamu dapat menjalankan website tersebut pada mesin lokal-mu: - -```bash -make docker-serve -``` - -Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**. - - -## Petunjuk untuk menjalankan website pada mesin lokal dengan menggunakan Hugo - -Kamu dapat melihat [dokumentasi resmi Hugo](https://gohugo.io/getting-started/installing/) untuk mengetahui langkah yang diperlukan untuk melakukan instalasi **Hugo**. Pastikan kamu melakukan instalasi versi **Hugo** sesuai dengan versi yang tersedia pada **environment variable** `HUGO_VERSION` pada **file**[`netlify.toml`](netlify.toml#L9). - -Untuk menjalankan laman pada mesin lokal setelah instalasi **Hugo**, kamu dapat menjalankan perintah berikut: - -```bash -make serve -``` - -Buka **browser** kamu ke http://localhost:1313 untuk melihat laman dokumentasi. Selama kamu melakukan penambahan konten, **Hugo** akan secara otomatis melakukan perubahan terhadap laman dokumentasi apabila **browser** melakukan proses **refresh**. - -## Komunitas, Diskusi, Kontribusi, dan Bantuan - -Kamu dapat belajar bagaimana tata cara untuk ikut terlibat dalam komunitas Kubernetes melalui [laman komunitas](http://kubernetes.io/community/). - -Kamu dapat berinteraksi dengan **maintainers** project ini melalui: - -- [Slack](https://kubernetes.slack.com/messages/sig-docs) -- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) - -### Etika dalam Berkontribusi - -Partisipasi dalam komunitas Kubernetes diatur dalam [Etika dalam Berkontribusi pada Kubernetes](code-of-conduct.md). - -## Terima Kasih! - -Kubernetes sangat menjunjung tinggi partisipasi dari komunitas, dan kami sangat mengapresiasi kontribusi kamu pada laman dan dokumentasi kami! diff --git a/README-ko.md b/README-ko.md index 4846b08c97eb6..5ac8d1e61721a 100644 --- a/README-ko.md +++ b/README-ko.md @@ -23,9 +23,9 @@ ### 한국어 -`README.md` 번역 ë° í•œêµ­ì–´ 기여ìžë¥¼ 위한 보다 ìžì„¸í•œ ê°€ì´ë“œë¥¼ [한국어 README](README-ko.md) 페ì´ì§€ í˜¹ì€ [쿠버네티스 문서 한글화 ê°€ì´ë“œ](https://kubernetes.io/ko/docs/contribute/localization_ko/)ì—ì„œ 살펴봅니다. +`README.md` 번역 ë° í•œêµ­ì–´ 기여ìžë¥¼ 위한 보다 ìžì„¸í•œ ê°€ì´ë“œë¥¼ [한국어 README](README-ko.md) 페ì´ì§€ì—ì„œ 살펴봅니다. -한국어 번역 ë©”ì¸í…Œì´ë„ˆì—게 다ìŒì„ 통해 ì—°ë½ ê°€ëŠ¥í•©ë‹ˆë‹¤. +한국어 번역 ë©”ì¸í…Œì´ë„ˆì—게 다ìŒì„ 통해 ì—°ë½ ê°€ëŠ¥í•©ë‹ˆë‹¤: * ì´ë•ì¤€ ([GitHub - @gochist](https://github.com/gochist)) * [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko) diff --git a/README-pt.md b/README-pt.md deleted file mode 100644 index 5f726d39b4d3a..0000000000000 --- a/README-pt.md +++ /dev/null @@ -1,82 +0,0 @@ -# A documentação do Kubernetes - -[![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website) -[![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) - -Bem vindos! Este repositório abriga todos os recursos necessários para criar o [site e documentação do Kubernetes](https://kubernetes.io/). Estamos muito satisfeitos por você querer contribuir! - -## Contribuindo com os documentos - -Você pode clicar no botão **Fork** na área superior direita da tela para criar uma cópia desse repositório na sua conta do GitHub. Esta cópia é chamada de *fork*. Faça as alterações desejadas no seu fork e, quando estiver pronto para enviar as alterações para nós, vá até o fork e crie uma nova solicitação de pull para nos informar sobre isso. - -Depois que seu **pull request** for criada, um revisor do Kubernetes assumirá a responsabilidade de fornecer um feedback claro e objetivo. Como proprietário do pull request, **é sua responsabilidade modificar seu pull request para abordar o feedback que foi fornecido a você pelo revisor do Kubernetes.** Observe também que você pode acabar tendo mais de um revisor do Kubernetes para fornecer seu feedback ou você pode acabar obtendo feedback de um revisor do Kubernetes que é diferente daquele originalmente designado para lhe fornecer feedback. Além disso, em alguns casos, um de seus revisores pode solicitar uma revisão técnica de um [revisor de tecnologia Kubernetes](https://github.com/kubernetes/website/wiki/Tech-reviewers) quando necessário. Os revisores farão o melhor para fornecer feedback em tempo hábil, mas o tempo de resposta pode variar de acordo com as circunstâncias. - -Para mais informações sobre como contribuir com a documentação do Kubernetes, consulte: - -* [Comece a contribuir](https://kubernetes.io/docs/contribute/start/) -* [Preparando suas alterações na documentação](http://kubernetes.io/docs/contribute/intermediate#view-your-changes-locally) -* [Usando Modelos de Página](http://kubernetes.io/docs/contribute/style/page-templates/) -* [Guia de Estilo da Documentação](http://kubernetes.io/docs/contribute/style/style-guide/) -* [Localizando documentação do Kubernetes](https://kubernetes.io/docs/contribute/localization/) - -## Documentação do Kubernetes Localizando o `README.md` - -### coreano - -Veja a tradução de `README.md` e mais orientações sobre detalhes para contribuidores coreanos na página [README coreano](README-ko.md). - -Você pode alcançar os mantenedores da localização coreana em: - -* June Yi ([GitHub - @gochist](https://github.com/gochist)) -* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko) - -## Executando o site localmente usando o Docker - -A maneira recomendada de executar o site do Kubernetes localmente é executar uma imagem especializada do [Docker](https://docker.com) que inclui o gerador de site estático [Hugo](https://gohugo.io). - -> Se você está rodando no Windows, você precisará de mais algumas ferramentas que você pode instalar com o [Chocolatey](https://chocolatey.org). `choco install make` - -> Se você preferir executar o site localmente sem o Docker, consulte [Executando o site localmente usando o Hugo](#executando-o-site-localmente-usando-o-hugo) abaixo. - -Se você tiver o Docker [em funcionamento](https://www.docker.com/get-started), crie a imagem do Docker do `kubernetes-hugo` localmente: - -```bash -make docker-image -``` - -Depois que a imagem foi criada, você pode executar o site localmente: - -```bash -make docker-serve -``` - -Abra seu navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador. - -## Executando o site localmente usando o Hugo - -Veja a [documentação oficial do Hugo](https://gohugo.io/getting-started/installing/) para instruções de instalação do Hugo. Certifique-se de instalar a versão do Hugo especificada pela variável de ambiente `HUGO_VERSION` no arquivo [`netlify.toml`](netlify.toml#L9). - -Para executar o site localmente quando você tiver o Hugo instalado: - -```bash -make serve -``` - -Isso iniciará o servidor Hugo local na porta 1313. Abra o navegador para http://localhost:1313 para visualizar o site. Conforme você faz alterações nos arquivos de origem, Hugo atualiza o site e força a atualização do navegador. - -## Comunidade, discussão, contribuição e apoio - -Aprenda a se envolver com a comunidade do Kubernetes na [página da comunidade](http://kubernetes.io/community/). - -Você pode alcançar os mantenedores deste projeto em: - -- [Slack](https://kubernetes.slack.com/messages/sig-docs) -- [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) - -### Código de conduta - -A participação na comunidade Kubernetes é regida pelo [Código de Conduta da Kubernetes](code-of-conduct.md). - -## Obrigado! - -A Kubernetes prospera com a participação da comunidade e nós realmente apreciamos suas contribuições para o nosso site e nossa documentação! diff --git a/README.md b/README.md index de89c4fd658ff..fd22b3342c853 100644 --- a/README.md +++ b/README.md @@ -3,13 +3,13 @@ [![Build Status](https://api.travis-ci.org/kubernetes/website.svg?branch=master)](https://travis-ci.org/kubernetes/website) [![GitHub release](https://img.shields.io/github/release/kubernetes/website.svg)](https://github.com/kubernetes/website/releases/latest) -Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're glad that you want to contribute! +Welcome! This repository houses all of the assets required to build the [Kubernetes website and documentation](https://kubernetes.io/). We're very pleased that you want to contribute! ## Contributing to the docs You can click the **Fork** button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a *fork*. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it. -Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.** Also, note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one initially assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances. +Once your pull request is created, a Kubernetes reviewer will take responsibility for providing clear, actionable feedback. As the owner of the pull request, **it is your responsibility to modify your pull request to address the feedback that has been provided to you by the Kubernetes reviewer.** Also note that you may end up having more than one Kubernetes reviewer provide you feedback or you may end up getting feedback from a Kubernetes reviewer that is different than the one originally assigned to provide you feedback. Furthermore, in some cases, one of your reviewers might ask for a technical review from a [Kubernetes tech reviewer](https://github.com/kubernetes/website/wiki/Tech-reviewers) when needed. Reviewers will do their best to provide feedback in a timely fashion but response time can vary based on circumstances. For more information about contributing to the Kubernetes documentation, see: @@ -19,22 +19,24 @@ For more information about contributing to the Kubernetes documentation, see: * [Documentation Style Guide](http://kubernetes.io/docs/contribute/style/style-guide/) * [Localizing Kubernetes Documentation](https://kubernetes.io/docs/contribute/localization/) -## Localization `README.md`'s -| | | -|---|---| -|[French README](README-fr.md)|[Korean README](README-ko.md)| -|[German README](README-de.md)|[Portuguese README](README-pt.md)| -|[Hindi README](README-hi.md)|[Spanish README](README-es.md)| -|[Indonesian README](README-id.md)| -||| +## `README.md`'s Localizing Kubernetes Documentation -## Running the website locally using Docker +### Korean -The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static website generator. +See translation of `README.md` and more detail guidance for Korean contributors on the [Korean README](README-ko.md) page. + +You can reach the maintainers of Korean localization at: + +* June Yi ([GitHub - @gochist](https://github.com/gochist)) +* [Slack channel](https://kubernetes.slack.com/messages/kubernetes-docs-ko) + +## Running the site locally using Docker + +The recommended way to run the Kubernetes website locally is to run a specialized [Docker](https://docker.com) image that includes the [Hugo](https://gohugo.io) static site generator. > If you are running on Windows, you'll need a few more tools which you can install with [Chocolatey](https://chocolatey.org). `choco install make` -> If you'd prefer to run the website locally without Docker, see [Running the website locally using Hugo](#running-the-site-locally-using-hugo) below. +> If you'd prefer to run the website locally without Docker, see [Running the site locally using Hugo](#running-the-site-locally-using-hugo) below. If you have Docker [up and running](https://www.docker.com/get-started), build the `kubernetes-hugo` Docker image locally: @@ -42,25 +44,25 @@ If you have Docker [up and running](https://www.docker.com/get-started), build t make docker-image ``` -Once the image has been built, you can run the website locally: +Once the image has been built, you can run the site locally: ```bash make docker-serve ``` -Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh. +Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh. -## Running the website locally using Hugo +## Running the site locally using Hugo See the [official Hugo documentation](https://gohugo.io/getting-started/installing/) for Hugo installation instructions. Make sure to install the Hugo version specified by the `HUGO_VERSION` environment variable in the [`netlify.toml`](netlify.toml#L9) file. -To run the website locally when you have Hugo installed: +To run the site locally when you have Hugo installed: ```bash make serve ``` -This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the website. As you make changes to the source files, Hugo updates the website and forces a browser refresh. +This will start the local Hugo server on port 1313. Open up your browser to http://localhost:1313 to view the site. As you make changes to the source files, Hugo updates the site and forces a browser refresh. ## Community, discussion, contribution, and support @@ -77,4 +79,4 @@ Participation in the Kubernetes community is governed by the [Kubernetes Code of ## Thank you! -Kubernetes thrives on community participation, and we appreciate your contributions to our website and our documentation! +Kubernetes thrives on community participation, and we really appreciate your contributions to our site and our documentation! diff --git a/config.toml b/config.toml index cadc842717dc9..7ba856cef69a2 100644 --- a/config.toml +++ b/config.toml @@ -212,46 +212,3 @@ contentDir = "content/de" time_format_blog = "02.01.2006" # A list of language codes to look for untranslated content, ordered from left to right. language_alternatives = ["en"] - -[languages.es] -title = "Kubernetes" -description = "Production-Grade Container Orchestration" -languageName ="Español" -weight = 9 -contentDir = "content/es" - -[languages.es.params] -time_format_blog = "02.01.2006" -# A list of language codes to look for untranslated content, ordered from left to right. -language_alternatives = ["en"] - -[languages.pt] -title = "Kubernetes" -description = "Orquestração de contêineres em nível de produção" -languageName ="Português" -weight = 9 -contentDir = "content/pt" - -[languages.pt.params] -time_format_blog = "02.01.2006" -# A list of language codes to look for untranslated content, ordered from left to right. -language_alternatives = ["en"] - -[languages.id] -title = "Kubernetes" -description = "Production-Grade Container Orchestration" -languageName ="Bahasa Indonesia" -weight = 10 -contentDir = "content/id" - -[languages.id.params] -time_format_blog = "02.01.2006" -# A list of language codes to look for untranslated content, ordered from left to right. -language_alternatives = ["en"] - -[languages.hi] -title = "Kubernetes" -description = "Production-Grade Container Orchestration" -languageName ="Hindi" -weight = 11 -contentDir = "content/hi" \ No newline at end of file diff --git a/content/de/_index.html b/content/de/_index.html index 90c04a2185ad5..4d47a647569bc 100644 --- a/content/de/_index.html +++ b/content/de/_index.html @@ -44,7 +44,7 @@

Die Herausforderungen bei der Migration von über 150 Microservices auf Kube


- KubeCon vom 20-23. Mai 2019 in Barcelona + KubeCon am 20. und 23. Mai 2019 in Barcelona


diff --git a/content/de/blog/_index.md b/content/de/blog/_index.md deleted file mode 100644 index 0a2e18c7add12..0000000000000 --- a/content/de/blog/_index.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Kubernetes Blog -linkTitle: Blog -menu: - main: - title: "Blog" - weight: 40 - post: > -

Lesen Sie die neuesten Nachrichten über Kubernetes und das Containeruniversum im Allgemeinen. Erhalten Sie druckfrisch die neuesten Tutorials und technische Anleitungen.

---- diff --git a/content/de/community/_index.html b/content/de/community/_index.html deleted file mode 100644 index dd95bd7f39f54..0000000000000 --- a/content/de/community/_index.html +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Community -layout: basic -cid: community ---- - -
-
-
-

Die Gewissheit, dass Kubernetes überall und für alle gut funktioniert.

-

Verbinden Sie sich mit der Kubernetes-Community in unserem Slack Kanal, Diskussionsforum, oder beteiligen Sie sich an der Kubernetes-dev-Google-Gruppe. Eine wöchentliches Community-Meeting findet per Videokonferenz statt, um den Stand der Dinge zu diskutieren, folgen Sie - diesen Anweisungen für Informationen wie Sie teilnehmen können.

-

Sie können Kubernetes auch auf der ganzen Welt über unsere - Kubernetes Meetup Community und der - Kubernetes Cloud Native Meetup Community beitreten.

-
-
-

Special Interest Groups (SIGs)

-

Haben Sie ein besonderes Interesse daran, wie Kubernetes mit einer anderen Technologie arbeitet? Werfen Sie einen Blick auf unsere kontinuierlich wachsende - Listen von SIGs, von AWS und Openstack bis hin zu Big Data und Skalierbarkeit, es gibt einen Platz für Sie, an dem Sie mitwirken können, und Anweisungen zur Gründung einer neuen SIG finden, wenn Ihr besonderes Interesse (noch) nicht abgedeckt ist. -

- -

Als Mitglied der Kubernetes-Community sind Sie herzlich eingeladen, an allen SIG-Treffen teilzunehmen, die Sie interessieren. Eine Registrierung ist nicht erforderlich.

- -
- -
-

Verhaltensregeln

-

Die Kubernetes-Community schätzt Respekt und Inklusivität und setzt einen Verhaltenskodex - in allen Interaktionen durch. Wenn Sie einen Verstoß gegen den Verhaltenskodex bei einer Veranstaltung oder Sitzung, - in Slack oder in einem anderen Kommunikationsmechanismus feststellen, wenden Sie sich - bitte an das Kubernetes Code of Conduct Committee conduct@kubernetes.io. Ihre Anonymität wird geschützt. -

-
-
-
- -
-
-

Talk to Us!

-

Wir würden uns freuen, von Ihnen zu hören, wie Sie Kubernetes verwenden
und was wir tun können, um es besser zu machen.

-
-
- @kubernetesio -

Erhalten Sie die neuesten Nachrichten und Updates.

-
-
- Github Project -

Informieren Sie sich über das Projekt und erwägen Sie, einen Beitrag zu leisten.

-
-
- #kubernetes-users -

Unser Slack-Kanal ist der beste Weg, um unsere Ingenieure zu kontaktieren und Ihre Ideen mit ihnen zu teilen.

-
-
- Stack Overflow -

Unser Benutzerforum ist ein großartiger Ort, um Community-Support zu erhalten.

-
-
-
-
diff --git a/content/de/docs/concepts/_index.md b/content/de/docs/concepts/_index.md deleted file mode 100644 index a5f7788f5ad8b..0000000000000 --- a/content/de/docs/concepts/_index.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: Konzepte -main_menu: true -content_template: templates/concept -weight: 40 ---- - -{{% capture overview %}} - -Im Abschnitt Konzepte erfahren Sie mehr über die Teile des Kubernetes-Systems und die Abstraktionen, die Kubernetes zur Darstellung Ihres Clusters verwendet, und Sie erhalten ein tieferes Verständnis der Funktionsweise von Kubernetes. - -{{% /capture %}} - -{{% capture body %}} - -## Überblick - -Um mit Kubernetes zu arbeiten, verwenden Sie *Kubernetes-API-Objekte*, um den *gewünschten Status Ihres Clusters* zu beschreiben: -welche Anwendungen oder anderen Workloads Sie ausführen möchten, welche Containerimages sie verwenden, die Anzahl der Replikate, welche Netzwerk- und Festplattenressourcen Sie zur Verfügung stellen möchten, und vieles mehr. Sie legen den gewünschten Status fest, indem Sie Objekte mithilfe der Kubernetes-API erstellen, normalerweise über die Befehlszeilenschnittstelle `kubectl`. Sie können die Kubernetes-API auch direkt verwenden, um mit dem Cluster zu interagieren und den gewünschten Status festzulegen oder zu ändern. - -Sobald Sie den gewünschten Status eingestellt haben, wird das *Kubernetes Control Plane* dafür sorgen, dass der aktuelle Status des Clusters mit dem gewünschten Status übereinstimmt. Zu diesem Zweck führt Kubernetes verschiedene Aufgaben automatisch aus, z. B. Starten oder Neustarten von Containern, Skalieren der Anzahl der Repliken einer bestimmten Anwendung und vieles mehr. Das Kubernetes Control Plane besteht aus einer Reihe von Prozessen, die in Ihrem Cluster ausgeführt werden: - -* Der **Kubernetes Master** bestehet aus drei Prozessen, die auf einem einzelnen Node in Ihrem Cluster ausgeführt werden, der als Master-Node bezeichnet wird. Diese Prozesse sind:[kube-apiserver](/docs/admin/kube-apiserver/), [kube-controller-manager](/docs/admin/kube-controller-manager/) und [kube-scheduler](/docs/admin/kube-scheduler/). -* Jeder einzelne Node in Ihrem Cluster, welcher nicht der Master ist, führt zwei Prozesse aus: - * **[kubelet](/docs/admin/kubelet/)**, das mit dem Kubernetes Master kommuniziert. - * **[kube-proxy](/docs/admin/kube-proxy/)**, ein Netzwerk-Proxy, der die Netzwerkdienste von Kubernetes auf jedem Node darstellt. - -## Kubernetes Objects - -Kubernetes enthält eine Reihe von Abstraktionen, die den Status Ihres Systems darstellen: implementierte containerisierte Anwendungen und Workloads, die zugehörigen Netzwerk- und Festplattenressourcen sowie weitere Informationen zu den Aufgaben Ihres Clusters. Diese Abstraktionen werden durch Objekte in der Kubernetes-API dargestellt; Lesen Sie [Kubernetes Objects Überblick](/docs/concepts/abstractions/overview/) für weitere Details. - -Die grundlegenden Objekte von Kubernetes umfassen: - -* [Pod](/docs/concepts/workloads/pods/pod-overview/) -* [Service](/docs/concepts/services-networking/service/) -* [Volume](/docs/concepts/storage/volumes/) -* [Namespace](/docs/concepts/overview/working-with-objects/namespaces/) - -Darüber hinaus enthält Kubernetes eine Reihe von Abstraktionen auf höherer Ebene, die als Controller bezeichnet werden. Controller bauen auf den Basisobjekten auf und bieten zusätzliche Funktionen und Komfortfunktionen. Sie beinhalten: - -* [ReplicaSet](/docs/concepts/workloads/controllers/replicaset/) -* [Deployment](/docs/concepts/workloads/controllers/deployment/) -* [StatefulSet](/docs/concepts/workloads/controllers/statefulset/) -* [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) -* [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) - -## Kubernetes Control Plane - -Die verschiedenen Teile der Kubernetes-Steuerungsebene (Control Plane), wie der Kubernetes Master- und der Kubelet-Prozess, bestimmen, wie Kubernetes mit Ihrem Cluster kommuniziert. Das Control Plane führt ein Inventar aller Kubernetes-Objekte im System und führt fortlaufende Steuerkreise aus, um den Status dieser Objekte zu verwalten. Zu jeder Zeit reagieren die Steuerkreise des Control Plane auf Änderungen im Cluster und arbeiten daran, dass der tatsächliche Status aller Objekte im System mit dem gewünschten Status, den Sie definiert haben, übereinstimmt. - -Wenn Sie beispielsweise mit der Kubernetes-API ein Deployment-Objekt erstellen, geben Sie einen neuen gewünschten Status für das System an. Das Kubernetes Control Plane zeichnet die Objekterstellung auf und führt Ihre Anweisungen aus, indem es die erforderlichen Anwendungen startet und sie für auf den Cluster-Nodes plant--Dadurch wird der tatsächliche Status des Clusters an den gewünschten Status angepasst. - -### Kubernetes Master - -Der Kubernetes-Master ist für die Aufrechterhaltung des gewünschten Status für Ihren Cluster verantwortlich. Wenn Sie mit Kubernetes interagieren, beispielsweise mit dem Kommanduzeilen-Tool `kubectl`, kommunizieren Sie mit dem Kubernetes-Master Ihres Clusters. - -> Der "Master" bezieht sich auf eine Reihe von Prozessen, die den Clusterstatus verwalten. Normalerweise werden diese Prozesse alle auf einem einzigen Node im Cluster ausgeführt. Dieser Node wird auch als Master bezeichnet. Der Master kann repliziert werden um Verfügbarkeit und Redundanz zu erhöhen. - -### Kubernetes Nodes - -Die Nodes in einem Cluster sind die Maschinen (VMs, physische Server usw.), auf denen Ihre Anwendungen und Cloud-Workflows ausgeführt werden. Der Kubernetes-Master steuert jeden Master. Sie werden selten direkt mit Nodes interagieren. - -#### Objekt Metadata - - -* [Anmerkungen](/docs/concepts/overview/working-with-objects/annotations/) - -{{% /capture %}} - -{{% capture whatsnext %}} - -Wenn Sie eine Konzeptseite schreiben möchten, lesen Sie [Seitenvorlagen verwenden](/docs/home/contribute/page-templates/) -für Informationen zum Konzeptseitentyp und zur Dokumentations Vorlage. - -{{% /capture %}} diff --git a/content/de/docs/concepts/architecture/_index.md b/content/de/docs/concepts/architecture/_index.md deleted file mode 100644 index 1e9f717f4d07c..0000000000000 --- a/content/de/docs/concepts/architecture/_index.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: "Kubernetes Architekur" -weight: 30 ---- \ No newline at end of file diff --git a/content/de/docs/concepts/architecture/master-node-communication.md b/content/de/docs/concepts/architecture/master-node-communication.md deleted file mode 100644 index efa357124847b..0000000000000 --- a/content/de/docs/concepts/architecture/master-node-communication.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Master-Node Kommunikation -content_template: templates/concept -weight: 20 ---- - -{{% capture overview %}} - -Dieses Dokument katalogisiert die Kommunikationspfade zwischen dem Master (eigentlich dem Apiserver) und des Kubernetes-Clusters. -Die Absicht besteht darin, Benutzern die Möglichkeit zu geben, ihre Installation so anzupassen, dass die Netzwerkkonfiguration so abgesichert wird, dass der Cluster in einem nicht vertrauenswürdigen Netzwerk (oder mit vollständig öffentlichen IP-Adressen eines Cloud-Providers) ausgeführt werden kann. - -{{% /capture %}} - - -{{% capture body %}} - -## Cluster zum Master - -Alle Kommunikationspfade vom Cluster zum Master enden beim Apiserver (keine der anderen Master-Komponenten ist dafür ausgelegt, Remote-Services verfügbar zu machen). -In einem typischen Setup ist der Apiserver so konfiguriert, dass er Remote-Verbindungen an einem sicheren HTTPS-Port (443) mit einer oder mehreren Formen der [Clientauthentifizierung](/docs/reference/access-authn-authz/authentication/) überwacht. -Eine oder mehrere Formene von [Autorisierung](/docs/reference/access-authn-authz/authorization/) sollte aktiviert sein, insbesondere wenn [anonyme Anfragen](/docs/reference/access-authn-authz/authentication/#anonymous-requests) oder [Service Account Tokens](/docs/reference/access-authn-authz/authentication/#service-account-tokens) aktiviert sind. - -Nodes sollten mit dem öffentlichen Stammzertifikat für den Cluster konfigurirert werden, sodass sie eine sichere Verbindung zum Apiserver mit gültigen Client-Anmeldeinformationen herstellen können. -Beispielsweise bei einer gewöhnlichen GKE-Konfiguration enstprechen die dem kubelet zur Verfügung gestellten Client-Anmeldeinformationen eines Client-Zertifikats. -Lesen Sie über [kubelet TLS bootstrapping](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/) zur automatisierten Bereitstellung von kubelet-Client-Zertifikaten. - -Pods, die eine Verbindung zum Apiserver herstellen möchten, können dies auf sichere Weise tun, indem sie ein Dienstkonto verwenden, sodass Kubernetes das öffentliche Stammzertifikat und ein gültiges Trägertoken automatisch in den Pod einfügt, wenn er instanziert wird. -Der `kubernetes`-Dienst (in allen Namespaces) ist mit einer virtuellen IP-Adresse konfiguriert, die (über den Kube-Proxy) an den HTTPS-Endpunkt auf dem Apiserver umgeleitet wird. - -Die Master-Komponenten kommunizieren auch über den sicheren Port mit dem Cluster-Apiserver. - -Der Standardbetriebsmodus für Verbindungen vom Cluster (Knoten und Pods, die auf den Knoten ausgeführt werden) zum Master ist daher standardmäßig gesichert und kann über nicht vertrauenswürdige und/oder öffentliche Netzwerke laufen. - -## Master zum Cluster - -Es gibt zwei primäre Kommunikationspfade vom Master (Apiserver) zum Cluster. -Der erste ist vom Apiserver bis zum Kubelet-Prozess, der auf jedem Node im Cluster ausgeführt wird. -Der zweite ist vom Apiserver zu einem beliebigen Node, Pod oder Dienst über die Proxy-Funktionalität des Apiservers. - -### Apiserver zum kubelet - -Die Verbindungen vom Apiserver zum Kubelet werden verwendet für: - - * Abrufen von Protokollen für Pods. - * Verbinden (durch kubectl) mit laufenden Pods. - * Bereitstellung der Portweiterleitungsfunktion des kubelet. - -Diese Verbindungen enden am HTTPS-Endpunkt des kubelet. -Standardmäßig überprüft der Apiserver das Serverzertifikat des Kubelet nicht, was die Verbindung von angreifbar für Man-in-the-Middle-Angriffe macht, und ist es ist daher **unsicher** wenn die Verbindungen über nicht vertrauenswürdige und/oder öffentliche Netzwerke laufen. - -Um diese Verbindung zu überprüfen, verwenden Sie das Flag `--kubelet-certificate-authority`, um dem Apiserver ein Stammzertifikatbündel bereitzustellen, das zur Überprüfung des Server-Zertifikats des kubelet verwendet wird. - -Wenn dies nicht möglich ist, verwenden Sie [SSH tunneling](/docs/concepts/architecture/master-node-communication/#ssh-tunnels) -zwischen dem Apiserver und kubelet, falls erforderlich, um eine Verbindung über ein nicht vertrauenswürdiges oder öffentliches Netz zu vermeiden. - -Ausserdem sollte, [Kubelet Authentifizierung und/oder Autorisierung](/docs/admin/kubelet-authentication-authorization/) sollte aktiviert sein, um die kubelet-API zu sichern. - -### Apiserver zu Nodes, Pods und Services - -Die Verbindungen vom Apiserver zu einem Node, Pod oder Dienst verwenden standardmäßig einfache HTTP-Verbindungen und werden daher weder authentifiziert noch verschlüsselt. -Sie können über eine sichere HTTPS-Verbindung ausgeführt werden, indem dem Node, dem Pod oder dem Servicenamen in der API-URL "https:" vorangestellt wird. Das vom HTTPS-Endpunkt bereitgestellte Zertifikat wird jedoch nicht überprüft, und es werden keine Clientanmeldeinformationen bereitgestellt. Die Verbindung wird zwar verschlüsselt, garantiert jedoch keine Integrität. -Diese Verbindungen **sind derzeit nicht sicher** innerhalb von nicht vertrauenswürdigen und/oder öffentlichen Netzen. - -### SSH Tunnels - -Kubernetes unterstützt SSH-Tunnel zum Schutz der Kommunikationspfade von Master -> Cluster. -In dieser Konfiguration initiiert der Apiserver einen SSH-Tunnel zu jedem Nodem im Cluster (Verbindung mit dem SSH-Server, der Port 22 läuft), und leitet den gesamten Datenverkehr für ein kubelet, einen Node, einen Pod oder einen Dienst durch den Tunnel. -Dieser Tunnel stellt sicher, dass der Datenverkehr nicht außerhalb des Netzwerks sichtbar ist, in dem die Knoten ausgeführt werden. - -SSH-Tunnel sind derzeit nicht mehr unterstützt. Sie sollten sie also nicht verwenden, es sei denn, Sie wissen, was Sie tun. Ein Ersatz für diesen Kommunikationskanal wird entwickelt. - -{{% /capture %}} diff --git a/content/de/docs/concepts/architecture/nodes.md b/content/de/docs/concepts/architecture/nodes.md deleted file mode 100644 index faf5e5decb048..0000000000000 --- a/content/de/docs/concepts/architecture/nodes.md +++ /dev/null @@ -1,247 +0,0 @@ ---- -title: Nodes -content_template: templates/concept -weight: 10 ---- - -{{% capture overview %}} - -Ein Knoten (Node in Englisch) ist eine Arbeitsmaschine in Kubernetes, früher als `minion` bekannt. Ein Node -kann je nach Cluster eine VM oder eine physische Maschine sein. Jeder Node enthält -die für den Betrieb von [Pods](/docs/concepts/workloads/pods/pod/) notwendigen Dienste -und wird von den Master-Komponenten verwaltet. -Die Dienste auf einem Node umfassen die [Container Runtime](/docs/concepts/overview/components/#node-components), das Kubelet und den Kube-Proxy. -Weitere Informationen finden Sie im Abschnitt Kubernetes Node in der Architekturdesign-Dokumentation. - -{{% /capture %}} - - -{{% capture body %}} - -## Node Status - -Der Status eines Nodes enthält folgende Informationen: - -* [Adressen](#adressen) -* [Zustand](#zustand) -* [Kapazität](#kapazität) -* [Info](#info) - -Jeder Abschnitt wird folgend detailliert beschrieben. - -### Adressen - -Die Verwendung dieser Felder hängt von Ihrem Cloud-Anbieter oder der Bare-Metal-Konfiguration ab. - -* HostName: Der vom Kernel des Nodes gemeldete Hostname. Kann mit dem kubelet-Parameter `--hostname-override` überschrieben werden. -* ExternalIP: In der Regel die IP-Adresse des Nodes, die extern geroutet werden kann (von außerhalb des Clusters verfügbar). -* InternalIP: In der Regel die IP-Adresse des Nodes, die nur innerhalb des Clusters routbar ist. - - -### Zustand - -Das `conditions` Feld beschreibt den Zustand, aller `Running` Nodes. - -| Node Condition | Beschreibung | -|----------------|-------------| -| `OutOfDisk` | `True` wenn auf dem Node nicht genügend freier Speicherplatz zum Hinzufügen neuer Pods vorhanden ist, andernfalls `False` | -| `Ready` | `True` wenn der Node in einem guten Zustand und bereit ist Pods aufzunehmen, `False` wenn der Node nicht in einem guten Zustand ist und nicht bereit ist Pods aufzunehmeb, und `Unknown` wenn der Node-Controller seit der letzten `node-monitor-grace-period` nichts von dem Node gehört hat (Die Standardeinstellung beträgt 40 Sekunden) | -| `MemoryPressure` | `True` wenn der verfügbare Speicher des Nodes niedrig ist; Andernfalls`False` | -| `PIDPressure` | `True` wenn zu viele Prozesse auf dem Node vorhanden sind; Andernfalls`False` | -| `DiskPressure` | `True` wenn die Festplattenkapazität niedrig ist. Andernfalls `False` | -| `NetworkUnavailable` | `True` wenn das Netzwerk für den Node nicht korrekt konfiguriert ist, andernfalls `False` | - -Der Zustand eines Nodes wird als JSON-Objekt dargestellt. Die folgende Antwort beschreibt beispielsweise einen fehlerfreien Node. - -```json -"conditions": [ - { - "type": "Ready", - "status": "True" - } -] -``` - -Wenn der Status der `Ready`-Bedingung `Unknown` oder `False` länger als der `pod-eviction-timeout` bleibt, wird ein Parameter an den [kube-controller-manager](/docs/admin/kube-controller-manager/) übergeben und alle Pods auf dem Node werden vom Node Controller gelöscht. - -Die voreingestellte Zeit vor der Entfernung beträgt **fünf Minuten**. -In einigen Fällen, in denen der Node nicht erreichbar ist, kann der Apiserver nicht mit dem Kubelet auf dem Node kommunizieren. -Die Entscheidung, die Pods zu löschen, kann dem Kublet erst mitgeteilt werden, wenn die Kommunikation mit dem Apiserver wiederhergestellt ist. -In der Zwischenzeit können Pods, deren Löschen geplant ist, weiterhin auf dem unzugänglichen Node laufen. - - -In Versionen von Kubernetes vor 1.5 würde der Node Controller das Löschen dieser unerreichbaren Pods vom Apiserver [erzwingen](/docs/concepts/workloads/pods/pod/#force-deletion-of-pods). In Version 1.5 und höher erzwingt der Node Controller jedoch keine Pod Löschung, bis bestätigt wird, dass sie nicht mehr im Cluster ausgeführt werden. Pods die auf einem unzugänglichen Node laufen sind eventuell in einem einem `Terminating` oder `Unkown` Status. In Fällen, in denen Kubernetes nicht aus der zugrunde liegenden Infrastruktur schließen kann, ob ein Node einen Cluster dauerhaft verlassen hat, muss der Clusteradministrator den Node möglicherweise manuell löschen. -Das Löschen des Kubernetes-Nodeobjekts bewirkt, dass alle auf dem Node ausgeführten Pod-Objekte gelöscht und deren Namen freigegeben werden. - -In Version 1.12 wurde die Funktion `TaintNodesByCondition` als Beta-Version eingeführt, die es dem Node-Lebenszyklus-Controller ermöglicht, automatisch [Markierungen](/docs/concepts/configuration/taint-and-toleration/) (*taints* in Englisch) zu erstellen, die Bedingungen darstellen. - -Ebenso ignoriert der Scheduler die Bedingungen, wenn er einen Node berücksichtigt; stattdessen betrachtet er die Markierungen (taints) des Nodes und die Toleranzen eines Pod. - -Anwender können jetzt zwischen dem alten Scheduling-Modell und einem neuen, flexibleren Scheduling-Modell wählen. - -Ein Pod, der keine Toleranzen aufweist, wird gemäß dem alten Modell geplant. -Aber ein Pod, die die Taints eines bestimmten Node toleriert, kann auf diesem Node geplant werden. - -{{< caution >}} -Wenn Sie diese Funktion aktivieren, entsteht eine kleine Verzögerung zwischen der Zeit, -in der eine Bedingung beobachtet wird, und der Zeit, in der ein Taint entsteht. -Diese Verzögerung ist in der Regel kürzer als eine Sekunde, aber sie kann die Anzahl -der Pods erhöhen, die erfolgreich geplant, aber vom Kubelet abgelehnt werden. -{{< /caution >}} - -### Kapazität - -Beschreibt die auf dem Node verfügbaren Ressourcen: CPU, Speicher und die maximale -Anzahl der Pods, die auf dem Node ausgeführt werden können. - -### Info - -Allgemeine Informationen zum Node, z. B. Kernelversion, Kubernetes-Version -(kubelet- und kube-Proxy-Version), Docker-Version (falls verwendet), Betriebssystemname. -Die Informationen werden von Kubelet vom Node gesammelt. - -## Management - -Im Gegensatz zu [Pods](/docs/concepts/workloads/pods/pod/) und [Services](/docs/concepts/services-networking/service/), -ein Node wird nicht von Kubernetes erstellt: Er wird extern von Cloud-Anbietern wie Google Compute Engine erstellt oder ist in Ihrem Pool physischer oder virtueller Maschinen vorhanden. -Wenn Kubernetes also einen Node erstellt, wird ein Objekt erstellt, das den Node darstellt. -Nach der Erstellung überprüft Kubernetes, ob der Node gültig ist oder nicht. - -Wenn Sie beispielsweise versuchen, einen Node aus folgendem Inhalt zu erstellen: - -```json -{ - "kind": "Node", - "apiVersion": "v1", - "metadata": { - "name": "10.240.79.157", - "labels": { - "name": "my-first-k8s-node" - } - } -} -``` - - -Kubernetes erstellt intern ein Node-Oject (die Darstellung) und validiert den Node durch Zustandsprüfung basierend auf dem Feld `metadata.name`. -Wenn der Node gültig ist, d.h. wenn alle notwendigen Dienste ausgeführt werden, ist er berechtigt, einen Pod auszuführen. -Andernfalls wird er für alle Clusteraktivitäten ignoriert, bis er gültig wird. - - -{{< note >}} -Kubernetes behält das Objekt für den ungültigen Node und prüft ständig seine Gültigkeit. -Sie müssen das Node-Objekt explizit löschen, um diesen Prozess zu stoppen. -{{< /note >}} - -Aktuell gibt es drei Komponenten, die mit dem Kubernetes Node-Interface interagieren: Node Controller, Kubelet und Kubectl. - - -### Node Controller - -Der Node Controller ist eine Kubernetes-Master-Komponente, die verschiedene Aspekte von Nodes verwaltet. - -Der Node Controller hat mehrere Rollen im Leben eines Nodes. -Der erste ist die Zuordnung eines CIDR-Blocks zu dem Node, wenn er registriert ist (sofern die CIDR-Zuweisung aktiviert ist). - -Die zweite ist, die interne Node-Liste des Node Controllers mit der Liste der verfügbaren Computer des Cloud-Anbieters auf dem neuesten Stand zu halten. -Wenn ein Node in einer Cloud-Umgebung ausgeführt wird und sich in einem schlechten Zustand befindet, fragt der Node Controller den Cloud-Anbieter, ob die virtuelle Maschine für diesen Node noch verfügbar ist. Wenn nicht, löscht der Node Controller den Node aus seiner Node-Liste. - -Der dritte ist die Überwachung des Zustands der Nodes. Der Node Controller ist dafür verantwortlich, -die NodeReady-Bedingung von NodeStatus auf ConditionUnknown zu aktualisieren, wenn ein wenn ein Node unerreichbar wird (der Node Controller empfängt aus irgendeinem Grund keine Herzschläge mehr, z.B. weil der Node heruntergefahren ist) und später alle Pods aus dem Node zu entfernen (und diese ordnungsgemäss zu beenden), wenn der Node weiterhin unzugänglich ist. (Die Standard-Timeouts sind 40s, um ConditionUnknown zu melden und 5 Minuten, um mit der Evakuierung der Pods zu beginnen). -Der Node Controller überprüft den Zustand jedes Nodes alle `--node-monitor-period` Sekunden. - - -In Versionen von Kubernetes vor 1.13 ist NodeStatus der Herzschlag des Nodes. -Ab Kubernetes 1.13 wird das Node-Lease-Feature als Alpha-Feature eingeführt (Feature-Gate `NodeLease`, [KEP-0009](https://github.com/kubernetes/community/blob/master/keps/sig-node/0009-node-heartbeat.md)). - -Wenn die Node Lease Funktion aktiviert ist, hat jeder Node ein zugeordnetes `Lease`-Objekt im `kube-node-lease`-Namespace, das vom Node regelmäßig erneuert wird. -Sowohl NodeStatus als auch Node Lease werden als Herzschläge vom Node aus behandelt. -Node Leases werden häufig erneuert, während NodeStatus nur dann vom Node zu Master gemeldet wird, wenn sich etwas ändert oder genügend Zeit vergangen ist (Standard ist 1 Minute, was länger ist als der Standard-Timeout von 40 Sekunden für unerreichbare Nodes). -Da Node Leases viel lastärmer sind als NodeStatus, macht diese Funktion den Node Herzschlag sowohl in Bezug auf Skalierbarkeit als auch auf die Leistung deutlich effizienter. - -In Kubernetes 1.4 haben wir die Logik der Node-Steuerung aktualisiert, um Fälle besser zu handhaben, in denen eine große Anzahl von Nodes Probleme hat, den Master zu erreichen (z.B. weil der Master Netzwerkprobleme hat). -Ab 1.4 betrachtet der Node-Controller den Zustand aller Nodes im Cluster, wenn er eine Entscheidung über die Enterfung eines Pods trifft. - -In den meisten Fällen begrenzt der Node-Controller die Entfernungsrate auf `--node-eviction-rate` (Standard 0,1) pro Sekunde, was bedeutet, dass er die Pods nicht von mehr als einem Node pro 10 Sekunden entfernt. - -Das Entfernungsverhalten von Nodes ändert sich, wenn ein Node in einer bestimmten Verfügbarkeitszone ungesund wird. -Der Node-Controller überprüft gleichzeitig, wie viel Prozent der Nodes in der Zone ungesund sind (NodeReady-Bedingung ist ConditionUnknown oder ConditionFalse). -Wenn der Anteil der ungesunden Nodes mindestens `--unhealthy-zone-threshold` (Standard 0,55) beträgt, wird die Entfernungsrate reduziert: - -Wenn der Cluster klein ist (d.h. weniger als oder gleich `--large-cluster-size-threshold` Node - Standard 50), werden die Entfernungen gestoppt. Andernfalls wird die Entfernungsrate auf `--secondary-node-eviction-rate` (Standard 0,01) pro Sekunde reduziert. - -Der Grund, warum diese Richtlinien pro Verfügbarkeitszone implementiert werden, liegt darin, dass eine Verfügbarkeitszone vom Master unerreichbar werden könnte, während die anderen verbunden bleiben. Wenn Ihr Cluster nicht mehrere Verfügbarkeitszonen von Cloud-Anbietern umfasst, gibt es nur eine Verfügbarkeitszone (den gesamten Cluster). - -Ein wichtiger Grund für die Verteilung Ihrer Nodes auf Verfügbarkeitszonen ist, dass die Arbeitsbelastung auf gesunde Zonen verlagert werden kann, wenn eine ganze Zone ausfällt. -Wenn also alle Nodes in einer Zone ungesund sind, entfernt Node Controller mit der normalen `--node-eviction-rate` Geschwindigkeit. -Der Ausnahmefall ist, wenn alle Zonen völlig ungesund sind (d.h. es gibt keine gesunden Node im Cluster). -In diesem Fall geht der Node-Controller davon aus, dass es ein Problem mit der Master-Konnektivität gibt und stoppt alle Entfernungen, bis die Verbindung wiederhergestellt ist. - -Ab Kubernetes 1.6 ist der Node-Controller auch für die Entfernung von Pods zuständig, die auf Nodes mit `NoExecute`-Taints laufen, wenn die Pods die Markierungen nicht tolerieren. -Zusätzlich ist der NodeController als Alpha-Funktion, die standardmäßig deaktiviert ist, dafür verantwortlich, Taints hinzuzufügen, die Node Probleme, wie `Node unreachable` oder `not ready` entsprechen. -Siehe [diese Dokumentation](/docs/concepts/configuration/taint-and-toleration/) für Details über `NoExecute` Taints und die Alpha-Funktion. - - -Ab Version 1.8 kann der Node-Controller für die Erzeugung von Taints, die Node Bedingungen darstellen, verantwortlich gemacht werden. Dies ist eine Alpha-Funktion der Version 1.8. - -### Selbstregistrierung von Nodes - -Wenn das Kubelet-Flag `--register-node` aktiv ist (Standard), versucht das Kubelet, sich beim API-Server zu registrieren. Dies ist das bevorzugte Muster, das von den meisten Distributionen verwendet wird. - -Zur Selbstregistrierung wird das kubelet mit den folgenden Optionen gestartet: - - - `--kubeconfig` - Pfad zu Anmeldeinformationen, um sich beim Apiserver zu authentifizieren. - - `--cloud-provider` - Wie man sich mit einem Cloud-Anbieter unterhält, um Metadaten über sich selbst zu lesen. - - `--register-node` - Automatisch beim API-Server registrieren. - - `--register-with-taints` - Registrieren Sie den Node mit der angegebenen Taints-Liste (Kommagetrennt `=:`). No-op wenn `register-node` false ist. - - `--node-ip` - IP-Adresse des Nodes. - - `--node-labels` - Labels, die bei der Registrierung des Nodes im Cluster hinzugefügt werden sollen (Beachten Sie die Richlinien des [NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) in 1.13+). - - `--node-status-update-frequency` - Gibt an, wie oft kubelet den Nodestatus an den Master übermittelt. - -Wenn der [Node authorization mode](/docs/reference/access-authn-authz/node/) und -[NodeRestriction admission plugin](/docs/reference/access-authn-authz/admission-controllers/#noderestriction) aktiviert sind, -dürfen kubelets nur ihre eigene Node-Ressource erstellen / ändern. - -#### Manuelle Nodeverwaltung - -Ein Cluster-Administrator kann Nodeobjekte erstellen und ändern. - -Wenn der Administrator Nodeobjekte manuell erstellen möchte, setzen Sie das kubelet Flag `--register-node=false`. - -Der Administrator kann Node-Ressourcen ändern (unabhängig von der Einstellung von `--register-node`). -Zu den Änderungen gehören das Setzen von Labels und das Markieren des Nodes. - -Labels auf Nodes können in Verbindung mit node selectors auf Pods verwendet werden, um die Planung zu steuern, z.B. um einen Pod so zu beschränken, dass er nur auf einer Teilmenge der Nodes ausgeführt werden darf. - -Das Markieren eines Nodes als nicht geplant, verhindert, dass neue Pods für diesen Node geplant werden. Dies hat jedoch keine Auswirkungen auf vorhandene Pods auf dem Node. -Dies ist nützlich als vorbereitender Schritt vor einem Neustart eines Nodes usw. -Um beispielsweise einen Node als nicht geplant zu markieren, führen Sie den folgenden Befehl aus: - -```shell -kubectl cordon $NODENAME -``` - -{{< note >}} -Pods, die von einem DaemonSet-Controller erstellt wurden, umgehen den Kubernetes-Scheduler und respektieren nicht das _unschedulable_ Attribut auf einem Node. -Dies setzt voraus, dass Daemons auf dem Computer verbleiben, auch wenn während der Vorbereitung eines Neustarts keine Anwendungen mehr vorhanden sind. -{{< /note >}} - -### Node Kapazität - -Die Kapazität des Nodes (Anzahl der CPU und Speichermenge) ist Teil des Nodeobjekts. -Normalerweise registrieren sich Nodes selbst und melden ihre Kapazität beim Erstellen des Nodeobjekts. -Sofern Sie [Manuelle Nodeverwaltung](#Manuelle-Nodeverwaltung) betreiben, müssen Sie die Node Kapazität setzen, wenn Sie einen Node hinzufügen. - -Der Kubernetes-Scheduler stellt sicher, dass für alle Pods auf einem Nodes genügend Ressourcen vorhanden sind. -Er prüft, dass die Summe der Requests von Containern auf dem Node nicht größer ist als die Kapazität des Nodes. -Er beinhaltet alle Container die vom kubelet gestarted worden, aber keine Container die direkt von der [container runtime](/docs/concepts/overview/components/#node-components) gestartet wurden, noch jegleiche Prozesse die ausserhalb von Containern laufen. - -Wenn Sie Ressourcen explizit für Nicht-Pod-Prozesse reservieren möchten, folgen Sie diesem Lernprogramm um [Ressourcen für Systemdaemons zu reservieren](/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved). - - -## API-Objekt - -Node ist eine Top-Level-Ressource in der Kubernetes-REST-API. Weitere Details zum API-Objekt finden Sie unter: -[Node API object](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#node-v1-core). - -{{% /capture %}} diff --git a/content/de/docs/concepts/cluster-administration/_index.md b/content/de/docs/concepts/cluster-administration/_index.md deleted file mode 100755 index 72af40feecca1..0000000000000 --- a/content/de/docs/concepts/cluster-administration/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Cluster Administration" -weight: 100 ---- - diff --git a/content/de/docs/concepts/configuration/_index.md b/content/de/docs/concepts/configuration/_index.md deleted file mode 100755 index b6d701ca6df52..0000000000000 --- a/content/de/docs/concepts/configuration/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Konfiguration" -weight: 80 ---- - diff --git a/content/de/docs/concepts/containers/_index.md b/content/de/docs/concepts/containers/_index.md deleted file mode 100755 index 0d8dd77ad0871..0000000000000 --- a/content/de/docs/concepts/containers/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Container" -weight: 40 ---- - diff --git a/content/de/docs/concepts/example-concept-template.md b/content/de/docs/concepts/example-concept-template.md deleted file mode 100644 index 9f3a2bcfac80c..0000000000000 --- a/content/de/docs/concepts/example-concept-template.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Konzept Dokumentations-Vorlage -content_template: templates/concept -toc_hide: true ---- - -{{% capture overview %}} - -{{< note >}} -Stellen Sie auch sicher [einen Eintrag im Inhaltsverzeichnis](/docs/home/contribute/write-new-topic/#creating-an-entry-in-the-table-of-contents) für Ihr neues Dokument zu erstellen. -{{< /note >}} - -Diese Seite erklärt ... - -{{% /capture %}} - -{{% capture body %}} - -## Verstehen ... - -Kubernetes bietet ... - -## Verwenden ... - -Benutzen Sie ... - -{{% /capture %}} - -{{% capture whatsnext %}} - -**[Optionaler Bereich]** - -* Lernen Sie mehr über [ein neues Thema schreiben](/docs/home/contribute/write-new-topic/). -* Besuchen Sie [Seitenvorlagen verwenden - Konzeptvorlage](/docs/home/contribute/page-templates/#concept_template) wie Sie diese Vorlage verwenden. - -{{% /capture %}} - - diff --git a/content/de/docs/concepts/extend-kubernetes/_index.md b/content/de/docs/concepts/extend-kubernetes/_index.md deleted file mode 100644 index 5e389601ea642..0000000000000 --- a/content/de/docs/concepts/extend-kubernetes/_index.md +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: "Kubernets erweitern" -weight: 110 ---- diff --git a/content/de/docs/concepts/overview/_index.md b/content/de/docs/concepts/overview/_index.md deleted file mode 100755 index eaa0a00b2ffa1..0000000000000 --- a/content/de/docs/concepts/overview/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Überblick" -weight: 20 ---- - diff --git a/content/de/docs/concepts/overview/components.md b/content/de/docs/concepts/overview/components.md deleted file mode 100644 index 092c213fdaed5..0000000000000 --- a/content/de/docs/concepts/overview/components.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: Kubernetes Komponenten -content_template: templates/concept -weight: 20 -card: - name: concepts - weight: 20 ---- - -{{% capture overview %}} -In diesem Dokument werden die verschiedenen binären Komponenten beschrieben, die zur Bereitstellung eines funktionsfähigen Kubernetes-Clusters erforderlich sind. -{{% /capture %}} - -{{% capture body %}} -## Master-Komponenten - -Master-Komponenten stellen die Steuerungsebene des Clusters bereit. Master-Komponenten treffen globale Entscheidungen über den Cluster (z. B. Zeitplanung) und das Erkennen und Reagieren auf Clusterereignisse (Starten eines neuen Pods, wenn das `replicas`-Feld eines Replikationscontrollers nicht zufriedenstellend ist). - -Master-Komponenten können auf jedem Computer im Cluster ausgeführt werden. -Der Einfachheit halber starten Setup-Skripts normalerweise alle Master-Komponenten auf demselben Computer, und es werden keine Benutzercontainer auf diesem Computer ausgeführt. -Lesen Sie [Cluster mit hoher Verfügbarkeit erstellen](/docs/admin/high-availability/) für ein Beispiel für ein Multi-Master-VM-Setup. - -### kube-apiserver - -{{< glossary_definition term_id="kube-apiserver" length="all" >}} - -### etcd - -{{< glossary_definition term_id="etcd" length="all" >}} - -### kube-scheduler - -{{< glossary_definition term_id="kube-scheduler" length="all" >}} - -### kube-controller-manager - -{{< glossary_definition term_id="kube-controller-manager" length="all" >}} - -Diese Controller umfassen: - - * Node Controller: Verantwortlich für das Erkennen und Reagieren, wenn Nodes ausfallen. - * Replication Controller: Verantwortlich für die Aufrechterhaltung der korrekten Anzahl von Pods für jedes Replikationscontrollerobjekt im System. - * Endpoints Controller: Füllt das Endpoints-Objekt aus (d.h. verbindet Services & Pods). - * Service Account & Token Controllers: Erstellt Standardkonten und API-Zugriffstoken für neue Namespaces. - -### cloud-controller-manager - -[cloud-controller-manager](/docs/tasks/administer-cluster/running-cloud-controller/) führt Controller aus, die mit den entsprechenden Cloud-Anbietern interagieren. -Der cloud-controller-manager ist eine Alpha-Funktion, die in Kubernetes Version 1.6 eingeführt wurde. - -cloud-controller-manager führt nur Cloud-Provider-spezifische Controller-Schleifen aus. Sie müssen diese Controller-Schleifen im Cube-Controller-Manager deaktivieren. Sie können die Controller-Schleifen deaktivieren, indem Sie beim Starten des kube-controller-manager das Flag `--cloud-provider` auf `external` setzen. - -cloud-controller-manager erlaubt es dem Cloud-Anbieter Code und dem Kubernetes-Code, sich unabhängig voneinander zu entwickeln. -In früheren Versionen war der Kerncode von Kubernetes für die Funktionalität von Cloud-Provider-spezifischem Code abhängig. -In zukünftigen Versionen sollte der für Cloud-Anbieter spezifische Code vom Cloud-Anbieter selbst verwaltet und mit dem Cloud-Controller-Manager verknüpft werden, während Kubernetes ausgeführt wird. - -Die folgenden Controller haben Abhängigkeiten von Cloud-Anbietern: - - * Node Controller: Zum Überprüfen, ob ein Node in der Cloud beim Cloud-Anbieter gelöscht wurde, nachdem er nicht mehr reagiert - * Route Controller: Zum Einrichten von Routen in der zugrunde liegenden Cloud-Infrastruktur - * Service Controller: Zum Erstellen, Aktualisieren und Löschen von Lastverteilern von Cloud-Anbietern - * Volume Controller: Zum Erstellen, Verbinden und Bereitstellen von Volumes und zur Interaktion mit dem Cloud-Provider zum Orchestrieren von Volumes - -## Node-Komponenten - -Node Komponenten werden auf jedem Knoten ausgeführt, halten laufende Pods aufrecht und stellen die Kubernetes-Laufzeitumgebung bereit. - -### kubelet - -{{< glossary_definition term_id="kubelet" length="all" >}} - -### kube-proxy - -[kube-proxy](/docs/admin/kube-proxy/) ermöglicht die Kubernetes Service-Abstraktion, indem die Netzwerkregeln auf dem Host beibehalten und die Verbindungsweiterleitung durchgeführt wird. - -### Container Runtime - -Die Containerlaufzeit ist die Software, die für das Ausführen von Containern verantwortlich ist. -Kubernetes unterstützt mehrere Laufzeiten: [Docker](http://www.docker.com), [containerd](https://containerd.io), [cri-o](https://cri-o.io/), [rktlet](https://github.com/kubernetes-incubator/rktlet) und jede Implementierung des [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md). - -## Addons - -Addons sind Pods und Dienste, die Clusterfunktionen implementieren. Die Pods können verwaltet werden -durch Deployments, ReplicationControllers, und so wieter. -Namespace-Addon-Objekte werden im Namespace `kube-system` erstellt. - -Ausgewählte Addons werden unten beschrieben. Eine erweiterte Liste verfügbarer Addons finden Sie unter [Addons](/docs/concepts/cluster-administration/addons/). - -### DNS - -Während die anderen Addons nicht unbedingt erforderlich sind, sollte [cluster DNS](/docs/concepts/services-networking/dns-pod-service/) in allen Kubernetes-Cluster vorhanden sein, da viele Beispiele davon abhängen. - -Cluster-DNS ist neben anderen DNS-Servern in Ihrer Umgebung ein DNS-Server, der DNS-Einträge für Kubernetes-Dienste bereitstellt. - -Von Kubernetes gestartete Container schließen diesen DNS-Server automatisch in ihre DNS-Suchen ein. - -### Web UI (Dashboard) - -[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) ist eine allgemeine, webbasierte Benutzeroberfläche für Kubernetes-Cluster. Benutzer können damit Anwendungen, die im Cluster ausgeführt werden, sowie den Cluster selbst verwalten und Fehler beheben. - -### Container Resource Monitoring - -[Container Resource Monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/) zeichnet generische Zeitreihenmessdaten zu Containern in einer zentralen Datenbank auf und stellt eine Benutzeroberfläche zum Durchsuchen dieser Daten bereit. - - -### Cluster-level Logging - -Ein [Cluster-level logging](/docs/concepts/cluster-administration/logging/) Mechanismus ist für das Speichern von Containerprotokollen in einem zentralen Protokollspeicher mit Such- / Browsing-Schnittstelle verantwortlich. - -{{% /capture %}} - - diff --git a/content/de/docs/concepts/policy/_index.md b/content/de/docs/concepts/policy/_index.md deleted file mode 100755 index 67588bb6fa0c9..0000000000000 --- a/content/de/docs/concepts/policy/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Richtlinien" -weight: 90 ---- - diff --git a/content/de/docs/concepts/services-networking/_index.md b/content/de/docs/concepts/services-networking/_index.md deleted file mode 100755 index 46d6492e1ad41..0000000000000 --- a/content/de/docs/concepts/services-networking/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Dienste, Lastverteilung und Netzwerkfunktionen" -weight: 60 ---- - diff --git a/content/de/docs/concepts/storage/_index.md b/content/de/docs/concepts/storage/_index.md deleted file mode 100755 index 4133c701af272..0000000000000 --- a/content/de/docs/concepts/storage/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Speicher" -weight: 70 ---- - diff --git a/content/de/docs/concepts/workloads/_index.md b/content/de/docs/concepts/workloads/_index.md deleted file mode 100644 index ca394ebd0029d..0000000000000 --- a/content/de/docs/concepts/workloads/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "Workloads" -weight: 50 ---- - diff --git a/content/de/docs/contribute/_index.md b/content/de/docs/contribute/_index.md deleted file mode 100644 index efe4b2af03d79..0000000000000 --- a/content/de/docs/contribute/_index.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -content_template: templates/concept -title: Zur Kubernets-Dokumentation beitragen -linktitle: Mitmachen -main_menu: true -weight: 80 ---- - -{{% capture overview %}} - -Wenn Sie an der Dokumentation oder der Website von Kubernetes mitwirken möchten, freuen wir uns über Ihre Hilfe! -Jeder kann seinen Beitrag leisten, unabhängig davon ob Sie neu im Projekt sind oder schon lange dabei sind, und ob Sie sich als -Entwickler, Endbenutzer oder einfach jemanden, der es einfach nicht aushält, Tippfehler zu sehen sehen. - -Weitere Möglichkeiten, sich in der Kubernetes-Community zu engagieren oder mehr über uns zu erfahren, finden Sie auf der [Kubernetes-Community-Seite](/community/). -Informationen zum Handbuch zur Dokumentation von Kubernetes finden Sie im [Gestaltungshandbuch](/docs/contribute/style/style-guide/). - -{{% capture body %}} - -## Arten von Mitwirkenden - -- Ein _Member_ der Kubernetes Organisation, hat die [CLA unterzeichnet](/docs/contribute/start#sign-the-cla) - und etwas Zeit und Energie zum Projekt beigetragen. - Siehe [Community-Mitgliedschaft](https://github.com/kubernetes/community/blob/master/community-membership.md) für spezifische Kriterien bezüglich der Mitgliedschaft. -- Ein SIG Docs _Reviewer_ ist ein Mitglied der Kubernetes-Organisation, das Interesse an der Überprüfung von - Dokumentationsanfragen geäußert hat und von einem SIG Docs Approver zu der entsprechenden Github-Gruppe - und den `OWNERS`-Dateien im Github-Repository hinzugefügt wurde. -- Ein SIG Docs _approver_ ist ein Mitglied mit gutem Ansehen, das sich kontinuierlich für das Projekt engagiert hat. - Ein Approver kann Pull-Anfragen zusammenführen und Inhalte im Namen der Kubernetes-Organisation veröffentlichen. - Approver können SIG Docs auch in der größeren Kubernetes-Community vertreten. Einige der Aufgaben eines SIG Docs Approvers, wie z.B. die Koordination einer Freigabe, erfordern einen erheblichen Zeitaufwand. - -## Möglichkeiten, einen Beitrag zu leisten - -Diese Liste ist in Funktionen unterteilt, die jeder tun kann, die von Mitgliedern der Kubernetes-Organisation durchgeführt werden können, und Dinge, die ein höheres Maß an Zugriff und eine bessere Kenntnis der SIG Docs-Prozesse erfordern. Wenn Sie im Laufe der Zeit einen konstanten Beitrag leisten, können Sie einige der bereits getroffenen Tools und organisatorischen Entscheidungen nachvollziehen. - -Dies ist keine vollständige Liste von Möglichkeiten, wie Sie zur Kubernetes-Dokumentation beitragen können, aber sie sollte Ihnen den Einstieg erleichtern. - -- [Jeder](/docs/contribute/start/) - - Umsetzbare issues eröffnen -- [Member](/docs/contribute/start/) - - Vorhandene Dokumente verbessern - - Ideen zur Verbesserung in [Slack](http://slack.k8s.io/) oder der [SIG docs Mailingliste](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) einbringen - - Den Zugriff auf Dokumente verbessern - - Unverbindliches Feedback zu PRs verfassen - - Enen Blogbeitrag oder eine Fallstudie schreiben -- [Reviewer](/docs/contribute/intermediate/) - - Neue Funktionen dokumentieren - - Auswerten und Kategorisieren von Problemen - - PRs überprüfen - - Diagramme, Grafiken und einbettbare Screencasts / Videos erstellen - - Lokalisierung - - Als Vertreter von docs zu anderen Repos beitragen - - An Benutzer gerichtete Zeichenfolgen im Code bearbeiten - - Code-Kommentare verbessern, Godoc -- [Approver](/docs/contribute/advanced/) - - Veröffentlichen Sie den Inhalt von Members, indem Sie PRs genehmigen und zusammenführen - - Nehmen Sie als Docs-Vertreter an einem Kubernetes-Release-Team teil - - Verbesserungsvorschläge für den Style Guide - - Verbesserungsvorschläge für Dokumentprüfungen vorschlagen - - Vorschläge für Verbesserungen der Kubernetes-Website oder anderer Tools - -{{% /capture %}} diff --git a/content/de/docs/home/_index.md b/content/de/docs/home/_index.md deleted file mode 100644 index e8d87597a622e..0000000000000 --- a/content/de/docs/home/_index.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: Kubernetes Dokumentation -noedit: true -cid: docsHome -layout: docsportal_home -class: gridPage -linkTitle: "Home" -main_menu: true -weight: 10 -hide_feedback: true -menu: - main: - title: "Dokumentation" - weight: 20 - post: > -

Erfahren Sie, wie Sie Kubernetes mit Konzept-, Tutorial- und Referenzdokumentation verwenden. Sie können sogar zur mithelfen und zur Dokumentation beitragen!

-overview: > - Kubernetes ist ein Open-Source-System zur Automatisierung der Bereitstellung, Skalierung und Verwaltung von containerisierten Anwendungen. Das Open-Source Project wird von der Cloud Native Computing Foundation (CNCF) gehosted. -cards: -- name: concepts - title: "Verstehen Sie die Grundlagen" - description: "Lernen Sie Kubernetes und seine grundlegenden Konzepte kennen." - button: "Konzepte lernen" - button_path: "/docs/concepts" -- name: tutorials - title: "Kubernetes ausprobieren" - description: "Folgen Sie den Tutorials, um zu erfahren, wie Sie Anwendungen in Kubernetes bereitstellen." - button: "Tutorials entdecken" - button_path: "/docs/tutorials" -- name: setup - title: "Richten Sie einen Cluster ein" - description: "Holen Sie sich Kubernetes basierend auf Ihren Ressourcen und Bedürfnissen." - button: "Kubernetes Einrichten" - button_path: "/docs/setup" -- name: tasks - title: "Erfahren Sie, wie Sie Kubernetes verwenden" - description: "Informieren Sie sich über häufig verwendete Aufgaben und deren Durchführung anhand einer kurzen Abfolge von Schritten." - button: "Tasks anzeigen" - button_path: "/docs/tasks" -- name: reference - title: Referenzinformationen nachschlagen - description: Durchsuchen Sie Terminologie, Befehlszeilensyntax, API-Ressourcentypen und Dokumentation zum Setup-Tool. - button: Referenz anzeigen - button_path: /docs/reference -- name: contribute - title: Tragen Sie zur Dokumentation bei - description: Jeder kann einen Beitrag leisten, unabhängig davon, ob Sie neu in dem Projekt oder schon lange dabei sind. - button: Zur Dokumentation beitragen - button_path: /docs/contribute -- name: download - title: Kubernetes Herunterladen - description: Wenn Sie Kubernetes installieren oder auf die neueste Version aktualisieren, lesen Sie die aktuellen Versionshinweise. -- name: about - title: Über die Dokumentation - description: Diese Website enthält Dokumentation zu den aktuellen und vorherigen 4 Versionen von Kubernetes. ---- diff --git a/content/de/docs/home/supported-doc-versions.md b/content/de/docs/home/supported-doc-versions.md deleted file mode 100644 index 8463d1bcd9207..0000000000000 --- a/content/de/docs/home/supported-doc-versions.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Unterstützte Versionen der Kubernetes-Dokumentation -content_template: templates/concept -card: - name: about - weight: 10 - title: Unterstützte Versionen der Dokumentation ---- - -{{% capture overview %}} - -Diese Website enthält Dokumentation für die aktuelle Version von Kubernetes -und die vier vorherigen Versionen von Kubernetes. - -{{% /capture %}} - -{{% capture body %}} - -## Aktuelle Version - -Die aktuelle Version ist -[{{< param "version" >}}](/). - -## Vorherige Versionen - -{{< versions-other >}} - -{{% /capture %}} - - diff --git a/content/de/docs/reference/_index.md b/content/de/docs/reference/_index.md deleted file mode 100644 index dd98038ebbcb4..0000000000000 --- a/content/de/docs/reference/_index.md +++ /dev/null @@ -1,61 +0,0 @@ ---- -title: Referenzen -approvers: -- chenopis -linkTitle: "Referenzen" -main_menu: true -weight: 70 -content_template: templates/concept ---- - -{{% capture overview %}} - -Dieser Abschnitt der Kubernetes-Dokumentation enthält Referenzinformationen. - -{{% /capture %}} - -{{% capture body %}} - -## API-Referenz - -* [Kubernetes API Überblick](/docs/reference/using-api/api-overview/) - Übersicht über die API für Kubernetes. -* Kubernetes API Versionen - * [1.14](/docs/reference/generated/kubernetes-api/v1.14/) - * [1.13](/docs/reference/generated/kubernetes-api/v1.13/) - * [1.12](/docs/reference/generated/kubernetes-api/v1.12/) - * [1.11](/docs/reference/generated/kubernetes-api/v1.11/) - * [1.10](/docs/reference/generated/kubernetes-api/v1.10/) - -## API-Clientbibliotheken - -Um die Kubernetes-API aus einer Programmiersprache aufzurufen, können Sie -[Clientbibliotheken](/docs/reference/using-api/client-libraries/) verwenden. -Offiziell unterstützte Clientbibliotheken: - -- [Kubernetes Go Clientbibliothek](https://github.com/kubernetes/client-go/) -- [Kubernetes Python Clientbibliothek](https://github.com/kubernetes-client/python) -- [Kubernetes Java Clientbibliothek](https://github.com/kubernetes-client/java) -- [Kubernetes JavaScript Clientbibliothek](https://github.com/kubernetes-client/javascript) - -## CLI-Referenz - -* [kubectl](/docs/user-guide/kubectl-overview) - Haupt-CLI-Tool zum Ausführen von Befehlen und zum Verwalten von Kubernetes-Clustern. - * [JSONPath](/docs/user-guide/jsonpath/) - Syntax-Anleitung zur Verwendung von [JSONPath expressionen](http://goessner.net/articles/JsonPath/) mit kubectl. -* [kubeadm](/docs/admin/kubeadm/) - CLI-Tool zur einfachen Bereitstellung eines sicheren Kubernetes-Clusters. -* [kubefed](/docs/admin/kubefed/) - CLI-Tool zur Verwaltung Ihres Clusterverbunds. - -## Konfigurationsreferenz - -* [kubelet](/docs/admin/kubelet/) - Der primäre *Node-Agent*, der auf jedem Node ausgeführt wird. Das Kubelet betrachtet eine Reihe von PodSpecs und stellt sicher, dass die beschriebenen Container ordnungsgemäß ausgeführt werden. -* [kube-apiserver](/docs/admin/kube-apiserver/) - REST-API zur Überprüfung und Konfiguration von Daten für API-Objekte wie Pods, Services und Replikationscontroller. -* [kube-controller-manager](/docs/admin/kube-controller-manager/) - Daemon, der die mit Kubernetes gelieferten zentralen Regelkreise einbettet. -* [kube-proxy](/docs/admin/kube-proxy/) - Kann einfache TCP/UDP-Stream-Weiterleitung oder Round-Robin-TCP/UDP-Weiterleitung über eine Reihe von Back-Ends durchführen. -* [kube-scheduler](/docs/admin/kube-scheduler/) - Scheduler, der Verfügbarkeit, Leistung und Kapazität verwaltet. -* [federation-apiserver](/docs/admin/federation-apiserver/) - API-Server für Cluster Föderationen. -* [federation-controller-manager](/docs/admin/federation-controller-manager/) - Daemon, der die zentralen Regelkreise einbindet, die mit der Kubernetes-Föderation ausgeliefert werden. - -## Design Dokumentation - -Ein Archiv der Designdokumente für Kubernetes-Funktionalität. Gute Ansatzpunkte sind [Kubernetes Architektur](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md) und [Kubernetes Design Übersicht](https://git.k8s.io/community/contributors/design-proposals). - -{{% /capture %}} diff --git a/content/de/docs/reference/access-authn-authz/_index.md b/content/de/docs/reference/access-authn-authz/_index.md deleted file mode 100644 index bf85bb6337583..0000000000000 --- a/content/de/docs/reference/access-authn-authz/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: API Zugriff -weight: 20 -toc-hide: true ---- \ No newline at end of file diff --git a/content/de/docs/reference/command-line-tools-reference/_index.md b/content/de/docs/reference/command-line-tools-reference/_index.md deleted file mode 100644 index b5bb56510735b..0000000000000 --- a/content/de/docs/reference/command-line-tools-reference/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Befehlszeilen-Werkzeug Referenzinformationen -weight: 60 -toc-hide: true ---- diff --git a/content/de/docs/reference/federation/_index.html b/content/de/docs/reference/federation/_index.html deleted file mode 100644 index e3cc29c005a7c..0000000000000 --- a/content/de/docs/reference/federation/_index.html +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: "Föderation API" -weight: 40 ---- diff --git a/content/de/docs/reference/glossary/etcd.md b/content/de/docs/reference/glossary/etcd.md deleted file mode 100755 index cdc5820bd866d..0000000000000 --- a/content/de/docs/reference/glossary/etcd.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: etcd -id: etcd -date: 2018-04-12 -full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/ -short_description: > - Konsistenter und hochverfügbarer Key-Value Speicher, der als Backupspeicher von Kubernetes für alle Clusterdaten verwendet wird. - -aka: -tags: -- architecture -- storage ---- - Konsistenter und hochverfügbarer Key-Value Speicher, der als Backupspeicher von Kubernetes für alle Clusterdaten verwendet wird. - - - -Halten Sie immer einen Sicherungsplan für etcds Daten für Ihren Kubernetes-Cluster bereit. Ausführliche Informationen zu etcd finden Sie in der [etcd Dokumentation](https://github.com/coreos/etcd/blob/master/Documentation/docs.md). - diff --git a/content/de/docs/reference/glossary/index.md b/content/de/docs/reference/glossary/index.md deleted file mode 100755 index a830aa0ad48c0..0000000000000 --- a/content/de/docs/reference/glossary/index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Standardisiertes Glossar -layout: glossary -noedit: true -default_active_tag: fundamental -weight: 5 -card: - name: reference - weight: 10 - title: Glossary ---- - diff --git a/content/de/docs/reference/glossary/kube-apiserver.md b/content/de/docs/reference/glossary/kube-apiserver.md deleted file mode 100755 index 4dbe38937b551..0000000000000 --- a/content/de/docs/reference/glossary/kube-apiserver.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: kube-apiserver -id: kube-apiserver -date: 2018-04-12 -full_link: /docs/reference/generated/kube-apiserver/ -short_description: > - Komponente auf dem Master, der die Kubernetes-API verfügbar macht. Es ist das Frontend für die Kubernetes-Steuerebene. - -aka: -tags: -- architecture -- fundamental ---- - Komponente auf dem Master, der die Kubernetes-API verfügbar macht. Es ist das Frontend für die Kubernetes-Steuerebene. - - - -Es ist für die horizontale Skalierung konzipiert, d. H. Es skaliert durch die Bereitstellung von mehr Instanzen. Mehr informationen finden Sie unter [Cluster mit hoher Verfügbarkeit erstellen](/docs/admin/high-availability/). - diff --git a/content/de/docs/reference/glossary/kube-controller-manager.md b/content/de/docs/reference/glossary/kube-controller-manager.md deleted file mode 100755 index 38a743212bffa..0000000000000 --- a/content/de/docs/reference/glossary/kube-controller-manager.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: kube-controller-manager -id: kube-controller-manager -date: 2018-04-12 -full_link: /docs/reference/generated/kube-controller-manager/ -short_description: > - Komponente auf dem Master, auf dem Controller ausgeführt werden. - -aka: -tags: -- architecture -- fundamental ---- - Komponente auf dem Master, auf dem {{< glossary_tooltip text="controllers" term_id="controller" >}} ausgeführt werden. - - - -Logisch gesehen ist jeder {{< glossary_tooltip text="controller" term_id="controller" >}} ein separater Prozess, aber zur Vereinfachung der Komplexität werden sie alle zu einer einzigen Binärdatei zusammengefasst und in einem einzigen Prozess ausgeführt. - diff --git a/content/de/docs/reference/glossary/kube-scheduler.md b/content/de/docs/reference/glossary/kube-scheduler.md deleted file mode 100755 index 19715863452b2..0000000000000 --- a/content/de/docs/reference/glossary/kube-scheduler.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: kube-scheduler -id: kube-scheduler -date: 2018-04-12 -full_link: /docs/reference/generated/kube-scheduler/ -short_description: > - Komponente auf dem Master, die neu erstellte Pods überwacht, denen kein Node zugewiesen ist. Sie wählt den Node aus, auf dem sie ausgeführt werden sollen. - -aka: -tags: -- architecture ---- - Komponente auf dem Master, die neu erstellte Pods überwacht, denen kein Node zugewiesen ist. Sie wählt den Node aus, auf dem sie ausgeführt werden sollen. - - - -Zu den Faktoren, die bei Planungsentscheidungen berücksichtigt werden, zählen individuelle und kollektive Ressourcenanforderungen, Hardware- / Software- / Richtlinieneinschränkungen, Affinitäts- und Anti-Affinitätsspezifikationen, Datenlokalität, Interworkload-Interferenz und Deadlines. - - diff --git a/content/de/docs/reference/glossary/kubelet.md b/content/de/docs/reference/glossary/kubelet.md deleted file mode 100755 index edd72dbe57ce6..0000000000000 --- a/content/de/docs/reference/glossary/kubelet.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Kubelet -id: kubelet -date: 2018-04-12 -full_link: /docs/reference/generated/kubelet -short_description: > - Ein Agent, der auf jedem Node im Cluster ausgeführt wird. Er stellt sicher, dass Container in einem Pod ausgeführt werden. - -aka: -tags: -- fundamental -- core-object ---- - Ein Agent, der auf jedem Node im Cluster ausgeführt wird. Er stellt sicher, dass Container in einem Pod ausgeführt werden. - - - -Das Kubelet verwendet eine Reihe von PodSpecs, die über verschiedene Mechanismen bereitgestellt werden, und stellt sicher, dass die in diesen PodSpecs beschriebenen Container ordnungsgemäß ausgeführt werden. Das kubelet verwaltet keine Container, die nicht von Kubernetes erstellt wurden. diff --git a/content/de/docs/reference/issues-security/_index.md b/content/de/docs/reference/issues-security/_index.md deleted file mode 100644 index 6ce79934c1385..0000000000000 --- a/content/de/docs/reference/issues-security/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Kubernetes Probleme und Sicherheit -weight: 10 -toc-hide: true ---- \ No newline at end of file diff --git a/content/de/docs/reference/kubectl/_index.md b/content/de/docs/reference/kubectl/_index.md deleted file mode 100755 index 7b6c2d720b12a..0000000000000 --- a/content/de/docs/reference/kubectl/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: "kubectl CLI" -weight: 60 ---- - diff --git a/content/de/docs/reference/kubectl/cheatsheet.md b/content/de/docs/reference/kubectl/cheatsheet.md deleted file mode 100644 index a3968a213b897..0000000000000 --- a/content/de/docs/reference/kubectl/cheatsheet.md +++ /dev/null @@ -1,351 +0,0 @@ ---- -title: kubectl Spickzettel -content_template: templates/concept -card: - name: reference - weight: 30 ---- - -{{% capture overview %}} - -Siehe auch: [Kubectl Überblick](/docs/reference/kubectl/overview/) und [JsonPath Dokumentation](/docs/reference/kubectl/jsonpath). - -Diese Seite ist eine Übersicht über den Befehl `kubectl`. - -{{% /capture %}} - -{{% capture body %}} - -# kubectl - Spickzettel - -## Kubectl Autovervollständigung - -### BASH - -```bash -source <(kubectl completion bash) # Wenn Sie autocomplete in bash in der aktuellen Shell einrichten, sollte zuerst das bash-completion-Paket installiert werden. -echo "source <(kubectl completion bash)" >> ~/.bashrc # Fügen Sie der Bash-Shell dauerhaft Autocomplete hinzu. -``` - -Sie können auch ein Abkürzungsalias für `kubectl` verwenden, weleches auch mit Vervollständigung funktioniert: - -```bash -alias k=kubectl -complete -F __start_kubectl k -``` - -### ZSH - -```bash -source <(kubectl completion zsh) # Richten Sie Autocomplete in zsh in der aktuellen Shell ein -echo "if [ $commands[kubectl] ]; then source <(kubectl completion zsh); fi" >> ~/.zshrc # Fügen Sie der Zsh-Shell dauerhaft Autocomplete hinzu -``` - -## Kubectl Kontext und Konfiguration - -Legen Sie fest, welcher Kubernetes-Cluster mit `kubectl` kommuniziert und dessen Konfiguration ändert. Lesen Sie die Dokumentation [Authentifizierung mit kubeconfig über mehrere Cluster hinweg](/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) für ausführliche Informationen zur Konfigurationsdatei. - -```bash -kubectl config view # Zusammengeführte kubeconfig-Einstellungen anzeigen. - -# Verwenden Sie mehrere kubeconfig-Dateien gleichzeitig und zeigen Sie die zusammengeführte Konfiguration an -KUBECONFIG=~/.kube/config:~/.kube/kubconfig2 kubectl config view - -# Zeigen Sie das Passwort für den e2e-Benutzer an -kubectl config view -o jsonpath='{.users[?(@.name == "e2e")].user.password}' - -kubectl config view -o jsonpath='{.users[].name}' # eine Liste der Benutzer erhalten -kubectl config current-context # den aktuellen Kontext anzeigen -kubectl config use-context my-cluster-name # Setzen Sie den Standardkontext auf my-cluster-name - -# Fügen Sie Ihrer kubeconf einen neuen Cluster hinzu, der basic auth unterstützt -kubectl config set-credentials kubeuser/foo.kubernetes.com --username=kubeuser --password=kubepassword - -# Legen Sie einen Kontext fest, indem Sie einen bestimmten Benutzernamen und einen bestimmten Namespace verwenden. -kubectl config set-context gce --user=cluster-admin --namespace=foo \ - && kubectl config use-context gce - -kubectl config unset users.foo # delete user foo -``` - -## Apply -`apply` verwaltet Anwendungen durch Dateien, die Kubernetes-Ressourcen definieren. Es erstellt und aktualisiert Ressourcen in einem Cluster durch Ausführen von `kubectl apply`. Dies ist die empfohlene Methode zur Verwaltung von Kubernetes-Anwendungen in der Produktion. Lesen Sie die ausführliche [Kubectl Dokumentation](https://kubectl.docs.kubernetes.io) für weitere Informationen. - -## Objekte erstellen - -Kubernetes Manifeste können in Json oder Yaml definiert werden. Die Dateierweiterungen `.yaml`, -`.yml`, und `.json` können verwendet werden. - -```bash -kubectl apply -f ./my-manifest.yaml # Ressource(n) erstellen -kubectl apply -f ./my1.yaml -f ./my2.yaml # aus mehreren Dateien erstellen -kubectl apply -f ./dir # Erstellen Sie Ressourcen in allen Manifestdateien in Verzeichnis -kubectl apply -f https://git.io/vPieo # Ressource(n) aus URL erstellen -kubectl create deployment nginx --image=nginx # Starten Sie eine einzelne Instanz von Nginx -kubectl explain pods,svc # Zeigen Sie die Dokumentation für Pod und SVC Manifeste an - -# Erstellen Sie mehrere YAML-Objekte aus stdin -cat </dev/null; printf "\n"; done - -# Prüfen Sie, welche Nodes bereit sind -JSONPATH='{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}' \ - && kubectl get nodes -o jsonpath="$JSONPATH" | grep "Ready=True" - -# Listen Sie alle Secrets auf, die derzeit von einem Pod verwendet werden -kubectl get pods -o json | jq '.items[].spec.containers[].env[]?.valueFrom.secretKeyRef.name' | grep -v null | sort | uniq - -# Ereignisse nach Zeitstempel sortiert auflisten -kubectl get events --sort-by=.metadata.creationTimestamp -``` - -## Ressourcen aktualisieren - -Ab Version 1.11 ist das `rolling-update` veraltet (Lesen Sie [CHANGELOG-1.11.md](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md) für weitere Informationen), verwenden Sie stattdessen `rollout`. - -```bash -kubectl set image deployment/frontend www=image:v2 # Fortlaufende Aktualisierung der "www" Container der "Frontend"-Bereitstellung, Aktualisierung des Images -kubectl rollout undo deployment/frontend # Rollback zur vorherigen Bereitstellung -kubectl rollout status -w deployment/frontend # Beobachten Sie den fortlaufenden Aktualisierungsstatus der "Frontend"-Bereitstellung bis zum Abschluss. - -# veraltet ab Version 1.11 -kubectl rolling-update frontend-v1 -f frontend-v2.json # (veraltet) Fortlaufendes Update der Pods von Frontend-v1 -kubectl rolling-update frontend-v1 frontend-v2 --image=image:v2 # (veraltet) Ändern Sie den Namen der Ressource und aktualisieren Sie das Image -kubectl rolling-update frontend --image=image:v2 # (veraltet) Aktualisieren Sie das Pod-Image des Frontends -kubectl rolling-update frontend-v1 frontend-v2 --rollback # (veraltet) Bricht das laufende Rollout ab - -cat pod.json | kubectl replace -f - # Ersetzen Sie einen Pod basierend auf der in std übergebenen JSON - -# Ersetzen, löschen und Ressource neu erstellen. Dies führt zu einer temprären Unerreichbarkeit des Dienstes. -kubectl replace --force -f ./pod.json - -# Erstellen Sie einen Dienst für eien replizierten nginx Webserver, der an Port 80 und in den Containern an Port 8000 lauscht -kubectl expose rc nginx --port=80 --target-port=8000 - -# Aktualisieren Sie die Image-Version (Tag) eines Einzelcontainer-Pods auf Version 4 -kubectl get pod mypod -o yaml | sed 's/\(image: myimage\):.*$/\1:v4/' | kubectl replace -f - - -kubectl label pods my-pod new-label=awesome # Label hinzufügen -kubectl annotate pods my-pod icon-url=http://goo.gl/XXBTWq # Eine Anmerkung hinzufügen -kubectl autoscale deployment foo --min=2 --max=10 # Automatische Skalierung einer Bereitstellung "Foo" -``` - -## Ressourcen patchen - -```bash -kubectl patch node k8s-node-1 -p '{"spec":{"unschedulable":true}}' # Aktualisieren Sie einen Node teilweise - -# Aktualisieren Sie das Image eines Containers; spec.containers[*].name ist erforderlich, da es sich um einen Merge-Schlüssel handelt -kubectl patch pod valid-pod -p '{"spec":{"containers":[{"name":"kubernetes-serve-hostname","image":"new image"}]}}' - -# Aktualisieren Sie das Image eines Containers mithilfe eines Json-Patches mit Positionsarrays -kubectl patch pod valid-pod --type='json' -p='[{"op": "replace", "path": "/spec/containers/0/image", "value":"new image"}]' - -# Deaktivieren Sie eine Bereitstellung von livenessProbe durch verwenden eines Json-Patches mit Positionsarrays -kubectl patch deployment valid-deployment --type json -p='[{"op": "remove", "path": "/spec/template/spec/containers/0/livenessProbe"}]' - -# Fügen Sie einem Positionsarray ein neues Element hinzu -kubectl patch sa default --type='json' -p='[{"op": "add", "path": "/secrets/1", "value": {"name": "whatever" } }]' -``` - -## Ressourcen bearbeiten -Bearbeiten Sie eine beliebige API-Ressource in einem Editor. - -```bash -kubectl edit svc/docker-registry # Bearbeiten Sie den Dienst docker-registry -KUBE_EDITOR="nano" kubectl edit svc/docker-registry # Verwenden Sie einen alternativen Texteditor -``` - -## Ressourcen skalieren - -```bash -kubectl scale --replicas=3 rs/foo # Skaliert ein Replikat mit dem Namen 'foo' auf 3 -kubectl scale --replicas=3 -f foo.yaml # Skaliert eine in "foo.yaml" angegebene Ressource auf 3 -kubectl scale --current-replicas=2 --replicas=3 deployment/mysql # Wenn die aktuelle Konfiguration der Replikation von mysql 2 ist, skaliert mysql auf 3 -kubectl scale --replicas=5 rc/foo rc/bar rc/baz # Skaliert mehrere Replikationscontroller -``` - -## Ressourcen löschen - -```bash -kubectl delete -f ./pod.json # Löscht einen Pod mit dem in pod.json angegebenen Typ und Namen -kubectl delete pod,service baz foo # Löscht Pods und Services mit den gleichen Namen "baz" und "foo" -kubectl delete pods,services -l name=myLabel # Löscht Pods und Services mit dem Label name=myLabel -kubectl delete pods,services -l name=myLabel --include-uninitialized # Löscht Pods und Services, einschließlich nicht initialisierter, mit dem Label name=myLabel -kubectl -n my-ns delete po,svc --all # Löscht alle Pods und Dienste, einschließlich nicht initialisierter, im Namespace my-ns, -``` - -## Interaktion mit laufenden Pods - -```bash -kubectl logs my-pod # Pod-Logdatei ausgeben (stdout) -kubectl logs my-pod --previous # Pod-Logdatei für eine vorherige Instantiierung eines Containers ausgeben (stdout) -kubectl logs my-pod -c my-container # Pod Container-Logdatei ausgeben (stdout, multi-container case) -kubectl logs my-pod -c my-container --previous # Pod Container-Logdatei für eine vorherige Instantiierung eines Containers ausgeben (stdout, multi-container case) -kubectl logs -f my-pod # Pod-Logdatei streamen (stdout) -kubectl logs -f my-pod -c my-container # Pod Container-Logdatei streamen (stdout, multi-container case) -kubectl run -i --tty busybox --image=busybox -- sh # Pod als interaktive Shell ausführen -kubectl attach my-pod -i # An laufenden Container anhängen -kubectl port-forward my-pod 5000:6000 # Lauscht auf Port 5000 auf dem lokalen Computer und leitet den Port 6000 auf my-pod weiter -kubectl exec my-pod -- ls / # Befehl in vorhandenem Pod ausführen (1 Container) -kubectl exec my-pod -c my-container -- ls / # Befehl in vorhandenem Pod ausführen (Mehrere Container) -kubectl top pod POD_NAME --containers # Zeigt Metriken für einen bestimmten Pod und seine Container an -``` - -## Mit Nodes und Clustern interagieren - -```bash -kubectl cordon my-node # Markiert "my-node" als unplanbar -kubectl drain my-node # Entleert "my-node" zur Vorbereitung der Wartung -kubectl uncordon my-node # Markiert "my-node" als planbar -kubectl top node my-node # Metriken für einen bestimmten Node anzeigen -kubectl cluster-info # Adressen des Masters und der Services anzeigen -kubectl cluster-info dump # Ausgabe des aktuellen Clusterstatus in stdout -kubectl cluster-info dump --output-directory=/pfad/zum/cluster-status # Aktuellen Cluster-Status in /pfad/zum/cluster-status ausgeben - -# Wenn bereits ein Taint mit diesem Key und Effekt vorhanden ist, wird sein Wert wie angegeben ersetzt. -kubectl taint nodes foo dedicated=special-user:NoSchedule -``` - -### Ressourcentypen - -Liste aller unterstützten Ressourcentypen mit ihren Kurzbezeichnungen, der [API-Gruppe](/docs/concepts/overview/kubernetes-api/#api-groups), unabhängig davon ob sie im Namespace liegen, und der [Art](/docs/concepts/overview/working-with-objects/kubernetes-objects): - -```bash -kubectl api-resources -``` - -Andere Operationen zum Erkunden von API-Ressourcen: - -```bash -kubectl api-resources --namespaced=true # Alle Ressourcen im Namespace -kubectl api-resources --namespaced=false # Alle nicht im Namespace befindlichen Ressourcen -kubectl api-resources -o name # Alle Ressourcen mit einfacher Ausgabe (nur der Ressourcenname) -kubectl api-resources -o wide # Alle Ressourcen mit erweiterter Ausgabe (aka "Wide") -kubectl api-resources --verbs=list,get # Alle Ressourcen, die "list" und "get" Verben unterstützen anfordern -kubectl api-resources --api-group=extensions # Alle Ressourcen in der API-Gruppe "extensions" -``` - -### Ausgabe formatieren - -Um Details in einem bestimmten Format an Ihr Terminalfenster auszugeben, können Sie entweder das `-o` oder `--output` Flag zu einem unterstützten `kubectl` Befehl anhängens. - -Ausgabeformat | Beschreibung ---------------| ----------- -`-o=custom-columns=` | Ausgabe einer Tabelle mit einer durch Kommas getrennten Liste benutzerdefinierter Spalten -`-o=custom-columns-file=` | Drucken Sie eine Tabelle mit der benutzerdefinierten Spaltenvorlage in der `` Datei -`-o=json` | Ausgabe eines JSON-formatierten API-Objekts -`-o=jsonpath=