zh-trans: merge zh content from release-1.16-temporary into release-1.16 (#18216)
* Update http-proxy-access-api.md (#16932) * Update coredns.md (#16930) * zh-trans:/docs/docs/concepts/workloads/pods/ephemeral-containers.md (#16948) * update zh-trans of define-environment-variable-container.md (#16999) Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> * update chinese docs (#16985) * Fix ordered list (#16988) Signed-off-by: PingWang <wang.ping5@zte.com.cn> update Signed-off-by: PingWang <wang.ping5@zte.com.cn> * zh-trans:/docs/reference/setup-tools/kubeadm/kubeadm-upgrade-phase.md (#16951) Signed-off-by: PingWang <wang.ping5@zte.com.cn> update Signed-off-by: PingWang <wang.ping5@zte.com.cn> update Signed-off-by: PingWang <wang.ping5@zte.com.cn> * Remove redundant symbol and fix some ordered list (#17000) Signed-off-by: PingWang <wang.ping5@zte.com.cn> update Signed-off-by: PingWang <wang.ping5@zte.com.cn> * update-zh-translation/docs/reference/setup-tools/kubeadm/kubeadm-init.md (#16997) * update zh translation kubeadm-reset.md kubeadm-upgrade.md (#16992) * Create kubeadm_join_phase_control-plane-join_all.md (#16987) * Update web-ui-dashboard.md (#16976) * update format problem (#16956) Signed-off-by: PingWang <wang.ping5@zte.com.cn> update Signed-off-by: PingWang <wang.ping5@zte.com.cn> * zh-trans:/docs/docs/concepts/storage/volume-pvc-datasource.md (#17021) * update zh translation /docs/reference/access-authn-authz/webhook.md (#16860) * fix confict update zh translation (#16863) * zh-trans:/docs/concepts/workloads/pods/disruptions.md (#16983) * zh-trans:/docs/concepts/workloads/pods/disruptions.md * Update content/zh/docs/concepts/workloads/pods/disruptions.md Co-Authored-By: Qiming <tengqim@cn.ibm.com> * update zh translation content/zh/docs/reference/command-line-tools-reference/kube-scheduler.md (#17006) * Update RC's link (#16935) Signed-off-by: PingWang <wang.ping5@zte.com.cn> Update Signed-off-by: PingWang <wang.ping5@zte.com.cn> update the style Signed-off-by: PingWang <wang.ping5@zte.com.cn> * Update the links for /zh/docs/setup (#16938) Signed-off-by: PingWang <wang.ping5@zte.com.cn> * zh-trans:/docs/docs/concepts/services-networking/dual-stack.md (#17024) * update zh translation /reference/setup-tools/kubeadm/generated/kubeadm.md (#17036) * update zh tanslation /reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_download.md (#17037) * update zh translation -/reference/setup-tools/kubeadm/generated/kubeadm_alpha.md (#17038) * update zh translation /docs/contribute/participating.md (#17040) * Fix cri-o's links to match English docs (#16936) Signed-off-by: PingWang <wang.ping5@zte.com.cn> * update zh translation content/zh/docs/reference/kubectl/jsonpath.md (#16862) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md (#17049) * update Unkown -> Unknown (#17062) * zh-translation:high-availability.md (#16960) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * update Runnning -> Running (#17061) * zh-trans:/docs/docs/concepts/storage/volume-snapshots.md (#17054) * update zh transation /docs/reference/setup-tools/kubeadm/generated/kubeadm_reset.md (#17060) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_token_create.md (#17052) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_token.md (#17055) * update zh translation update-zh-translation-/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_list.md (#17048) * update zh-translation:ha-topology.md (#17099) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * zh-trans /reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md (#17093) * update zh translation /reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_all.md (#17083) * Add Chinese translation for scheduler-perf-tuning (#17087) Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for scheduler-perf-tuning Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for scheduler-perf-tuning Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for scheduler-perf-tuning Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> * zh trans content/zh/docs/setup/production-environment/tools/kubeadm/control-plane-flags.md (#17121) * update zh trans content/zh/docs/tasks/access-application-cluster/service-access-application-cluster.md (#17122) * zh-translation:content/zh/docs/tasks/administer-cluster/namespaces-walkthrough.md (#17105) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * update-zh-translation-/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_migrate.md (#17091) * update zh trans /docs/setup/learning-environment/minikube.md (#17143) * update zh trans /zh/docs/reference/_index.md (#17146) * update zh trans /docs/tasks/access-application-cluster/port-forward-access-application-cluster.md (#17134) * update zh translation 20191020-update-zh-translation-/docs/contribute/localization.md (#17046) * update zh trans /docs/reference/using-api/client-libraries.md (#17144) * update zh trans /docs/reference/setup-tools/kubeadm/generated/kubeadm_version.md (#17145) * update zh /docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_node.md (#17131) * update zh translation /reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-client.md (#17081) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig.md (#17078) * add zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_update-status.md (#17076) * update zh trans content/zh/docs/contribute/generate-ref-docs/kubectl.md (#17165) * update zh translation /reference/command-line-tools-reference/kube-proxy.md (#17107) * zh-trans:/docs/docs/concepts/workloads/pods/pod-topology-spread-const… (#16955) * zh-trans:/docs/docs/concepts/workloads/pods/pod-topology-spread-constraints.md * Update pod-topology-spread-constraints.md * zh-trans:/docs/concepts/configuration/scheduling-framework.md (#17088) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md (#17079) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md (#17077) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join.md (#17075) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md (#17050) * update zh trans /docs/concepts/overview/working-with-objects/namespaces.md (#17205) * update zh trans /docs/concepts/overview/what-is-kubernetes.md (#17203) * pr_release-1.16_crictl (#17201) * update zh docs/tasks/administer-cluster/dns-debugging-resolution.md (#17186) * update zh trans content/zh/docs/concepts/overview/working-with-objects/field-selectors.md (#17191) * translate configure_upgrade_etcd (#17160) * translate kubeadm_upgrade_apply (#17159) * update zh /docs/tasks/job/coarse-parallel-processing-work-queue.md (#17155) * translate docs/setup/release/version-skew-policy.md to Chinese (#17142) * update zh trans content/zh/docs/tasks/access-application-cluster/create-external-load-balancer.md (#17124) * zh-trans replace the wrong translation (#17103) zh-trans replace the wrong translation * Merged 1.14~1.16 changes (#17117) * zh-trans:/docs/concepts/configuration/assign-pod-node.md (#17129) * update zh trans /docs/contribute/generate-ref-docs/kubernetes-api.md (#17161) * pr_release-1.16_basic-ss (#17169) * Add zh-trans of assign-cpu-resource.md (#17063) Signed-off-by: heqg <he.qingguo@zte.com.cn> Add zh-trans of assign-cpu-resource.md Signed-off-by: heqg <he.qingguo@zte.com.cn> Add zh-trans of assign-cpu-resource.md Signed-off-by: heqg <he.qingguo@zte.com.cn> Add zh-trans of assign-cpu-resource.md Signed-off-by: heqg <he.qingguo@zte.com.cn> Add zh-trans of assign-cpu-resource.md Signed-off-by: heqg <he.qingguo@zte.com.cn> * update zh trans content/zh/docs/concepts/overview/working-with-objects/common-labels.md (#17193) * update zh translation /docs/contribute/intermediate.md (#17041) * zh-trans:docs/setup/production-environment/turnkey/tencent.md (#17207) * pr_release-1.16_mysql-wordpress-pv (#17202) * pr_release-1.16_reconfig-kubelet (#17200) * zh-trans:/docs/docs/concepts/workloads/controllers/jobs-run-completio… (#17020) * zh-trans:/docs/docs/concepts/workloads/controllers/jobs-run-completion.md * Update jobs-run-completion.md * Update jobs-run-completion.md * update zh trans content/zh/docs/concepts/extend-kubernetes/extend-cluster.md (#17212) * update zh trans content/zh/docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation.md (#17213) * add zh trans /docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_kubeconfig.md (#17220) kubeadm_join_phase_control-plane-prepare_download-certs.md * add zh trans /reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs.md and /reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare.md (#17219) * update zh trans content/zh/docs/concepts/containers/images.md (#17216) * ZH-trans: add _index.md (#17214) * ZH-trans: add _index.md * add _index.md file * add _index.md files * pr_release-1.16_crd-versions (#17198) * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md (#17092) * zh-trans /reference/setup-tools/kubeadm/generated/kubeadm_config_images.md (#17094) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_kube-proxy.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_sa.md (#17222) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_all.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_certs.md (#17221) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md (#17223) * 013 /docs/concepts/services networking/ingress.md (#17185) * x * update zh trans content/zh/docs/concepts/services-networking/ingress.md * zh-trans:/reference/setup-tools/kubeadm/generated/kubeadm_completion.md and kubeadm_config.md (#17097) * add zh trans reference/glossary/pod-lifecycle (#17226) * update zh-translation document (#17096) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * update zh-translation:setup-ha-etcd-with-kubeadm.md (#17098) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * add zh trans /docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_selfhosting.md and /docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_enable-dynamic.md (#17227) * add zh trans /docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubeconfig_user.md and /docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md (#17228) * zh-translation:content/zh/docs/tasks/extend-kubectl/kubectl-plugins.md (#17089) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * update zh translation /docs/reference/setup-tools/kubeadm/generated/kubeadm_join.md (#17080) * update zh translation /reference/setup-tools/kubeadm/generated/kubeadm_config_view.md (#17085) * zh-translation:troubleshooting-kubeadm.md (#17069) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * zh-trans: docs/concepts/scheduling/kube-scheduler.md (#17067) * Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> Add Chinese translation for kube-scheduler Signed-off-by: GeorgeSen <wang.sen2@zte.com.cn> * Update kube-scheduler.md * Add Chinese translation for kube-scheduler * Update kube-scheduler.md * Update kube-scheduler.md * Update kube-scheduler.md * translate pods.md and init-containers.md for branch release-1.16 (#17208) * update zh translation /docs/contribute/start.md (#17039) * zh-translation:2017-10-00-Five-Days-Of-Kubernetes-18.md (#17229) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * translate kubeadm-certs.md (#17090) * update the Illegal comment such as : (<！--、<--) (#17266) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-ca.md (#17268) * update zh /docs/concepts/architecture/cloud-controller.md (#17263) * update zh /docs/concepts/cluster-administration/logging.md (#17247) * modify the show of zh translation /concepts/overview/what-is-kubernetes.md /reference/setup-tools/kubeadm/generated/kubeadm_init.md /reference/setup-tools/kubeadm/kubeadm-init.md (#17246) * zh-translation:kubeadm_init_phase_control-plane_all.md (#17243) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * zh-translation:kubeadm_join_phase_control-plane-join_etcd.md (#17236) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-certs.md (#17230) * add content/zh/docs/reference/glossary/container-runtime.md file fix-up to pass the ci and trans content/zh/docs/reference/glossary/container-runtime.md、content/zh/docs/concepts/overview/components.md (#17211) * zh-translation:mirror-pod.md (#17231) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * zh-translation:kubeadm_init_phase_upload-config.md (#17238) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * update zh /docs/concepts/workloads/pods/pod-overview.md (#17239) * update the format of zh translation content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_plan.md content/zh/docs/reference/setup-tools/kubeadm/kubeadm-config.md content/zh/docs/reference/setup-tools/kubeadm/kubeadm-reset.md content/zh/docs/reference/setup-tools/kubeadm/kubeadm-token.md content/zh/docs/reference/setup-tools/kubeadm/kubeadm-upgrade.md (#17248) * Create advanced.md (#17256) * Create advanced.md * trans the advanced.md and fix the build bugs * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_scheduler.md (#17269) * zh-translation:kubelet-integration.md (#17272) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * pr_release-1.16_out-of-resource (#17199) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-ca.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_controller-manager.md (#17267) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_admin.md (#17271) * pr_release-1.16_ext-admission-ctl (#17196) * update zh translation /docs/contribute/advanced.md (#17042) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-etcd-client.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_ca.md (#17275) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print.md update zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_init-defaults.md (#17282) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated… (#17287) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md update zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane.md * Update kubeadm_init_phase_etcd.md * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/… (#17285) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-server.md content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet.md update zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver.md * Update kubeadm_alpha_kubelet.md * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon.md fix-up bad comment kubeadm_alpha_certs_renew.md、kubeadm_alpha_certs_renew_apiserver-etcd-client.md、kubeadm_init_phase_addon_all.md (#17276) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/… (#17281) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd_local.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_join-defaults.md * Update kubeadm_init_phase_etcd_local.md * zh trans update-daemon-set.md (#16872) * zh trans update-daemon-set.md * Update update-daemon-set.md * managing-tls-in-a-cluster.md (#16874) * update-api-object-kubectl-patch.md (#16875) * improve the zh trans /kubeadm/generated/kubeadm_init_phase_.* 1 (#17295) * improve the zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_.* (#17294) * modify the zh translation content/zh/docs/reference/setup-tools/kubea… (#17293) * modify the zh translation content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_.* * Update kubeadm_alpha.md * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_all.md and content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md (#17280) * add zh /docs/reference/glossary/cgroup.md (#17291) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-kubelet-client.md (#17288) * improve zh trans of command in /kubeadm/generated/kubeadm_init_phase_.* files (#17297) * improve zh command translation /kubeadm/generated/kubeadm_init_.* files (#17298) * update zh trans in /kubeadm/generated/kubeadm_.* files (#17306) * add zh trans /reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-healthcheck-client.md、/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-peer.md、/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubeconfig.md (#17308) * Improve previously translated documents (#17327) Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * zh-trans: docs/setup/production-environment/turnkey/aws.md (#17320) * Update zh.toml * update zh trans /generated/kubeadm_join_phase_.* files (#17301) * Update zh.toml * add zh /docs/reference/glossary/pod-disruption-budget.md (#17344) * pr_release-1.16_config-aggregation-layer (#17197) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_controller-manager.conf.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_scheduler.conf.md (#17390) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_scheduler.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_control-plane.md (#17381) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-kubelet-client.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_mark-control-plane.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_kubelet-start.md (#17380) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver.md (#17383) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_certificate-key.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_preflight.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_update-cluster-status.md (#17385) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_admin.conf.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_cleanup-node.md (#17387) * add zh trans content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-kubelet-client.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_front-proxy-client.md、content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_selfhosting_pivot.md (#17384) * add zh /docs/reference/glossary/limitrange.md (#17324) * add zh trans content/zh/docs/setup/best-practices/cluster-large.md (#17321) * add zh trans content/zh/docs/setup/best-practices/cluster-large.md * Update cluster-large.md * add zh trans /docs/reference/setup-tools/kubeadm/kubeadm-alpha.md、/do… (#17403) * add zh trans /docs/reference/setup-tools/kubeadm/kubeadm-alpha.md、/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_preflight.md、/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-server.md * Update kubeadm_init_phase_certs_etcd-server.md * add zh /docs/reference/glossary/cluster-operations.md (#17300) * add zh /docs/reference/glossary/applications.md (#17419) * update zh trans kubelet (#17379) * update zh trans kubelet * update the file according to feedback from reviewer tengqm * update 1000-1757 lines * update the advice zh trans * add zh /docs/reference/glossary/static-pod.md (#17418) * add zh /docs/reference/glossary/preemption.md (#17423) * add zh /docs/reference/glossary/pod-priority.md (#17421) * add zh /docs/reference/glossary/control-plane.md (#17425) * add zh /docs/reference/glossary/cluster-infrastructure.md (#17424) * pr_release-1.16_api-overview (#17444) * pr_release-1.16_daemonset (#17435) * pr_release-1.16_gc (#17445) * pr_release-1.16_qos-class (#17442) * fix QoS Class to QoS 类 (#17464) * pr_release-1.16-abac (#17427) * zh-trans:docs/setup/production-environment/turnkey/alibaba-cloud.md (#17345) * pr_release-1.16_endpoint-slice (#17468) * pr_release-1.16_taint (#17469) * pr_release-1.16_operator-pattern (#17467) * pr_release-1.16_ss (#17433) * pr_release-1.16_admission-controller (#17440) * pr_release-1.16_containerd (#17441) * pr_release-1.16_app-container (#17466) * add zh-trans content/zh/docs/setup/_index.md、content/zh/docs/setup/release/_index.md (#17503) * pr-release-1.16_enabling-endpoint-slices (#17504) * update zh trans content/zh/docs/reference/setup-tools/kubeadm/kubeadm… (#17495) * update zh trans content/zh/docs/reference/setup-tools/kubeadm/kubeadm-upgrade-phase.md、content/zh/docs/reference/setup-tools/kubeadm/kubeadm-init-phase.md * add content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_kubelet.md * pr-release-1.16_logging (#17491) * pr-release-1.16_cri (#17486) * add zh-trans:docs/setup/production-environment/turnkey/azure.md (#17482) * pattern translate into 模式 (#17485) * fix zk affinity description in zh trans (#17393) * pr-release-1.16_ephemeral-container (#17487) * pr-release-1.16_data-plane (#17489) * pr-release-1.16_cncf (#17490) * zh-trans add content\zh\docs\tools\install-minikube.md (#16920) * zh-trans add content\zh\docs\tools\install-minikube.md * zh-trans update content\zh\docs\tools\install-minikube.md * zh-trans update content\zh\docs\tools\install-minikube.md * update \docs\tasks\tools\install-minikube.md * update docs\concepts\workloads\controllers\deployment.md * update deployment.md * pr-release-1.16_extensions (#17492) * pr-release-1.16_toleration (#17493) * Revert "update zh trans content/zh/docs/reference/setup-tools/kubeadm/kubeadm… (#17495)" (#17521) This reverts commit 1134c14e0a39bdc3d1a920ac9797139a6dcccf4b. * motidy extensions in content/zh/docs/reference/glossary/extensions (#17524) * motidy toleration in content/zh/docs/reference/glossary/toleration.md (#17523) * motidy toleration in content/zh/docs/reference/glossary/toleration.md * Update toleration.md * improve zh-trans in content/zh/docs/setup/_index.md (#17526) * add zh-trans /zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_kubelet.md (#17527) * Broken Link (#17546) Issue available at https://kubernetes.io/zh/docs/concepts/containers/runtime-class/ and introduced by original English documentation (see #17543) * Update trans kubeadm_upgrade_plan.md (#17395) * Update kubeadm_upgrade_plan.md * Update kubeadm_upgrade_plan.md * Update kubeadm_upgrade_plan.md * Update kubeadm_upgrade_plan.md * Update kubeadm_upgrade_plan.md * Update kubeadm_upgrade_plan.md * update zh-trans of define-command-argument-container.md (#17022) Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> update zh-trans of define-command-argument-container.md Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> Add back the Original English Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> update title of define-command-argument-container.md Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> update table title and reference Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> update reference of define-command-argument-container.md Signed-off-by: Yixiang2019 <wang.yixiang@zte.com.cn> * ZH-trans: fix multiple jump links and update files (#17603) * ZH-trans: fix multiple jump links and update files * Update _index.html * update zh trans content/zh/docs/reference/setup-tools/kubeadm/kubeadm-init-phase.md (#17528) * update zh trans /doc/concepts/architecture/nodes.md (#17617) * update zh trans content/zh/docs/concepts/architecture/nodes.md * fix-up content/zh/docs/concepts/architecture/nodes.md * add zh-trans /docs/setup/release/notes.md (#17519) * add zh-trans /docs/setup/release/notes.md update-750 * fix-up 1575 line and udpate 2483 line * update to line 2980 * update to the last line 3160 * add zh-trans:docs/setup/production-environment/turnkey/icp.md (#17568) * zh-trans: /docs/setup/production-environment/container-runtimes.md (#17646) * zh-trs:container-runtimes.md Signed-off-by: yuxiaobo <yuxiaobogo@163.com> * Update container-runtimes.md * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md into Chinese (#17791) * Translate /docs/concepts/cluster-administration/cloud-providers.md into Chinese * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md into Chinese * Sorry, wrong commit, roll back... * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md into Chinese * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md into Chinese * Create trans kubeadm_upgrade_diff.md (#17392) * Update kubeadm_upgrade_diff.md * Update kubeadm_upgrade_diff.md * Update kubeadm_upgrade_diff.md * Create _index.md (#17831) * zh-trans zh-trans-/docs/reference/command-line-tools-reference/feature-gates.md (#17658) * Update volume-snapshots.md (#17829) * Update volume-snapshots.md * Update volume-snapshots.md * Update volume-snapshots.md * Create ovirt.md (#17849) * Create ovirt.md * Update ovirt.md * Translate /docs/concepts/cluster-administration/cloud-providers.md into Chinese (#17761) * Translate /docs/concepts/cluster-administration/cloud-providers.md into Chinese * Translate /docs/concepts/workloads/controllers/ttlafterfinished.md into Chinese * Sorry, wrong commit, roll back... * Update translation after tengqm's review. * Update cloud-providers.md * Update dual-stack.md (#17836) * Update dual-stack.md * Update dual-stack.md * Update dual-stack.md * Update dual-stack.md * Create validate-dual-stack.md (#17833) * Create validate-dual-stack.md * Update validate-dual-stack.md * translation content/zh/docs/reference/setup-tools/kubeadm/ kubeadm-join-phase、kubeadm-reset-phase (#17881) * zh-trans content/zh/docs/contribute/generate-ref-docs/contribute-upstream.md (#17882) * Chinese translation /docs/tasks/administer-cluster/highly-available-master.md (#17884) * Chinese translation /docs/tasks/administer-cluster/highly-available-master.md * Apply suggestions from code review Co-Authored-By: Qiming <tengqim@cn.ibm.com> * Fix format issue (#17921) * Create topology-manager.md (#17901) * Create topology-manager.md * Update topology-manager.md * add zh-trans:docs/setup/production-environment/windows/user-guide-windows-containers.md (#17876) * Update pod-overhead.md (#17931) * Update scheduler-perf-tuning.md (#17934) * Create dcos.md (#17932) * Create dcos.md * Update dcos.md * Update object-management.md (#17937) * zh-translation content/zh/docs/setup/production-environment/tools/kops.md (#17991) * Create imperative-config.md (#17956) * Create imperative-config.md * Update imperative-config.md * Create self-hosting.md (#17950) * Create resource-bin-packing.md (#17935) * Create nodelocaldns.md (#17938) * Update config.toml(release-1.16) for 1.17 (#18025) * Update config.toml(release-1.16) for 1.17 * Update config.toml * Remove ru language * fix shotcode mismatch Co-authored-by: zhangx501 <zhang0000xun@gmail.com> Co-authored-by: ZhongliangXiong <xiong.zhongliang@zte.com.cn> Co-authored-by: Yixiang Wang <wang.yixiang@zte.com.cn> Co-authored-by: li mengyang <hwdef97@gmail.com> Co-authored-by: PingWang <wang.ping5@zte.com.cn> Co-authored-by: chentanjun <tanjunchen20@gmail.com> Co-authored-by: Sophy417 <53026875+Sophy417@users.noreply.github.com> Co-authored-by: Qiming <tengqim@cn.ibm.com> Co-authored-by: yuxiaobo96 <41496192+yuxiaobo96@users.noreply.github.com> Co-authored-by: senwang <wang.sen2@zte.com.cn> Co-authored-by: lichuqiang <lichuqiang@huawei.com> Co-authored-by: lpf7551321 <liupengfei20@huawei.com> Co-authored-by: Hongcai Ren <renhongcai@huawei.com> Co-authored-by: jiajie <jiaj12@chinaunicom.cn> Co-authored-by: heqg <56527988+heqg@users.noreply.github.com> Co-authored-by: IreneByron <zhangbingqing7@huawei.com> Co-authored-by: LiuDui <1693291525@qq.com> Co-authored-by: Wang Bing <wangbing.adam@gmail.com> Co-authored-by: Damini Satya <daminisatya@gmail.com> Co-authored-by: liufangwai <liufangwai@huawei.com> Co-authored-by: wangcong <congfairy2536@gmail.com> Co-authored-by: XuefeiWang2 <wangxuefei2@huawei.com> Co-authored-by: Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> Co-authored-by: Ziqiu Zhu <zzqshu@126.com> Co-authored-by: ten2ton <50288981+ten2ton@users.noreply.github.com> Co-authored-by: Oleg Butuzov <butuzov@users.noreply.github.com> Co-authored-by: jiazxjason <52809535+jiazxjason@users.noreply.github.com> Co-authored-by: Coffey Gao <coffiney@qq.com> Co-authored-by: Bingshen Wang <bingshen.wbs@alibaba-inc.com>
This commit is contained in:
SataQiu
committed by
Kubernetes Prow Robot
Kubernetes Prow Robot
parent
6be3e1414d
commit
0f2bd2871b
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 准入控制器
|
||||
id: admission-controller
|
||||
date: 2019-06-28
|
||||
full_link: /docs/reference/access-authn-authz/admission-controllers/
|
||||
short_description: >
|
||||
在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
- security
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Admission Controller
|
||||
id: admission-controller
|
||||
date: 2019-06-28
|
||||
full_link: /docs/reference/access-authn-authz/admission-controllers/
|
||||
short_description: >
|
||||
A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
在对象持久化之前拦截 Kubernetes Api 服务器请求的一段代码
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Admission controllers are configurable for the Kubernetes API server and may be “validating”, “mutating”, or
|
||||
both. Any admission controller may reject the request. Mutating controllers may modify the objects they admit;
|
||||
validating controllers may not.
|
||||
|
||||
* [Admission controllers in the Kubernetes documentation](/docs/reference/access-authn-authz/admission-controllers/)
|
||||
-->
|
||||
|
||||
准入控制器可针对 Kubernetes Api 服务器进行配置，可以执行验证，变更或两者都执行。任何准入控制器都可以拒绝访问请求。
|
||||
变更（mutating）控制器可以修改其允许的对象，验证（validating）控制器则不可以。
|
||||
|
||||
* [Kubernetes 文档中的准入控制器](/docs/reference/access-authn-authz/admission-controllers/)
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: 聚合层
|
||||
id: aggregation-layer
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
short_description: >
|
||||
聚合层允许您在自己的集群上安装额外的 Kubernetes 风格的 API。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- extension
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Aggregation Layer
|
||||
id: aggregation-layer
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/extend-kubernetes/api-extension/apiserver-aggregation/
|
||||
short_description: >
|
||||
The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- extension
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
|
||||
-->
|
||||
|
||||
聚合层允许您在自己的集群上安装额外的 Kubernetes 风格的 API。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
When you've configured the {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} to [support additional APIs](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/), you can add `APIService` objects to "claim" a URL path in the Kubernetes API.
|
||||
-->
|
||||
|
||||
当您配置了 {{< glossary_tooltip text="Kubernetes API Server" term_id="kube-apiserver" >}} 来 [支持额外的 API](/docs/tasks/access-kubernetes-api/configure-aggregation-layer/)，您就可以在 Kubernetes API 中增加 `APIService` 对象来 "申领（Claim）" 一个 URL 路径。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 注解
|
||||
id: annotation
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/annotations
|
||||
short_description: >
|
||||
注解是以键值对的形式给资源对象附加随机的无法标识的元数据。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Annotation
|
||||
id: annotation
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/annotations
|
||||
short_description: >
|
||||
A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
|
||||
-->
|
||||
|
||||
注解是以键值对的形式给资源对象附加随机的无法标识的元数据。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.
|
||||
-->
|
||||
|
||||
注解中的元数据可大可小，可以是结构化的也可以是非结构化的，并且能包含标签不允许使用的字符。像工具和软件库这样的客户端可以检索这些元数据。
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 应用程序容器
|
||||
id: app-container
|
||||
date: 2019-02-12
|
||||
full_link:
|
||||
short_description: >
|
||||
用于运行部分工作负载的容器。与初始化容器比较而言。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
---
|
||||
应用程序容器（或 app 容器）{{< glossary_tooltip text="容器" term_id="container" >}} 在 {{< glossary_tooltip text="pod" term_id="pod" >}} 中，在 {{< glossary_tooltip text="初始化容器" term_id="init-container" >}} 启动完毕后才开始启动。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: App Container
|
||||
id: app-container
|
||||
date: 2019-02-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A container used to run part of a workload. Compare with init container.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
---
|
||||
Application containers (or app containers) are the {{< glossary_tooltip text="containers" term_id="container" >}} in a {{< glossary_tooltip text="pod" term_id="pod" >}} that are started after any {{< glossary_tooltip text="init containers" term_id="init-container" >}} have completed.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
An init container lets you separate initialization details that are important for the overall
|
||||
{{< glossary_tooltip text="workload" term_id="workload" >}}, and that don't need to keep running
|
||||
once the application container has started.
|
||||
If a pod doesn't have any init containers configured, all the containers in that pod are app containers.
|
||||
-->
|
||||
|
||||
初始化容器使您可以分离对于 {{< glossary_tooltip text="工作负载" term_id="workload" >}} 整体而言很重要的初始化细节，并且一旦应用容器启动，它不需要继续运行。
|
||||
如果 pod 没有配置任何初始化容器，则该 pod 中的所有容器都是应用程序容器。
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: 应用架构师
|
||||
id: application-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
应用架构师是负责应用高级设计的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
应用架构师是负责应用高级设计的人。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Application Architect
|
||||
id: application-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person responsible for the high-level design of an application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
A person responsible for the high-level design of an application.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
An architect ensures that an app's implementation allows it to interact with its surrounding components in a scalable, maintainable way. Surrounding components include databases, logging infrastructure, and other microservices.
|
||||
-->
|
||||
|
||||
应用架构师确保应用的实现允许它和周边组件进行可扩展的、可持续的交互。周边组件包括数据库、日志基础设施和其他微服务。
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 应用开发者
|
||||
id: application-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
编写可以在 Kubernetes 集群上运行的应用的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Application Developer
|
||||
id: application-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who writes an application that runs in a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who writes an application that runs in a Kubernetes cluster.
|
||||
-->
|
||||
|
||||
编写可以在 Kubernetes 集群上运行的应用的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
An application developer focuses on one part of an application. The scale of their focus may vary significantly in size.
|
||||
-->
|
||||
|
||||
应用开发者专注于应用的某一部分。他们工作范围的大小有明显的差异。
|
||||
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: 应用
|
||||
id: applications
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
各种容器化应用运行所在的层。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Applications
|
||||
id: applications
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The layer where various containerized applications run.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
各种容器化应用运行所在的层。
|
||||
+40
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 批准者
|
||||
id: approver
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
可以审核并批准 Kubernetes 代码贡献的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Approver
|
||||
id: approver
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who can review and approve Kubernetes code contributions.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
可以审核并批准 Kubernetes 代码贡献的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
While code review is focused on code quality and correctness, approval is focused on the holistic acceptance of a contribution. Holistic acceptance includes backwards/forwards compatibility, adhering to API and flag conventions, subtle performance and correctness issues, interactions with other parts of the system, and others. Approver status is scoped to a part of the codebase. Approvers were previously referred to as maintainers.
|
||||
-->
|
||||
|
||||
代码审核的重点是代码质量和正确性，而批准的重点是对贡献的整体接受。
|
||||
整体接受包括向后/向前兼容性、遵守 API 和参数约定、细微的性能和正确性问题、与系统其他部分的交互等。
|
||||
批准者状态的作用域是代码库的一部分。
|
||||
审批者以前被称为维护者。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 证书
|
||||
id: certificate
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
short_description: >
|
||||
证书是个安全加密文件，用来确认对 Kubernetes 集群访问的合法性。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Certificate
|
||||
id: certificate
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/tls/managing-tls-in-a-cluster/
|
||||
short_description: >
|
||||
A cryptographically secure file used to validate access to the Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A cryptographically secure file used to validate access to the Kubernetes cluster.
|
||||
-->
|
||||
|
||||
证书是个安全加密文件，用来确认对 Kubernetes 集群访问的合法性。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Certificates enable applications within a Kubernetes cluster to access the Kubernetes API securely. Certificates validate that clients are allowed to access the API.
|
||||
-->
|
||||
|
||||
证书可以让 Kubernetes 集群中运行的应用程序安全的访问 Kubernetes API。证书可以确认客户端是否被允许访问 API。
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: cgroup (控制组)
|
||||
id: cgroup
|
||||
date: 2019-06-25
|
||||
full_link:
|
||||
short_description: >
|
||||
一组具有可选资源隔离、审计和限制的 Linux 进程。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: cgroup (control group)
|
||||
id: cgroup
|
||||
date: 2019-06-25
|
||||
full_link:
|
||||
short_description: >
|
||||
A group of Linux processes with optional resource isolation, accounting and limits.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A group of Linux processes with optional resource isolation, accounting and limits.
|
||||
-->
|
||||
一组具有可选资源隔离、审计和限制的 Linux 进程。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
cgroup is a Linux kernel feature that limits, accounts for, and isolates the resource usage (CPU, memory, disk I/O, network) for a collection of processes.
|
||||
-->
|
||||
|
||||
Cgroup 是一个 Linux 内核特性，对一组进程的资源使用（CPU、内存、磁盘 I/O 和网络等）进行限制、审计和隔离。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: CLA (贡献者许可协议)
|
||||
id: cla
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/CLA.md
|
||||
short_description: >
|
||||
贡献者对他们在开源项目中所贡献的代码的授权许可条款。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CLA (Contributor License Agreement)
|
||||
id: cla
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/community/blob/master/CLA.md
|
||||
short_description: >
|
||||
Terms under which a contributor grants a license to an open source project for their contributions.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
{{< glossary_tooltip text="贡献者" term_id="contributor" >}} 对他们在开源项目中所贡献的代码的授权许可条款。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
CLAs help resolve legal disputes involving contributed material and intellectual property (IP).
|
||||
-->
|
||||
|
||||
CLA 对解决贡献者在开源社区所贡献的资料和智力资产（IP）导致的法律纠纷很有帮助。
|
||||
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 云控制器管理器
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/administer-cluster/running-cloud-controller/
|
||||
short_description: >
|
||||
云控制器管理器是 1.8 的 alpha 特性。在未来发布的版本中，这是将 Kubernetes 与任何其他云集成的最佳方式。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- architecture
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Controller Manager
|
||||
id: cloud-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/administer-cluster/running-cloud-controller/
|
||||
short_description: >
|
||||
Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- architecture
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Cloud Controller Manager is an alpha feature in 1.8. In upcoming releases it will be the preferred way to integrate Kubernetes with any cloud.
|
||||
-->
|
||||
|
||||
云控制器管理器是 1.8 的 alpha 特性。在未来发布的版本中，这是将 Kubernetes 与任何其他云集成的最佳方式。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes v1.6 contains a new binary called cloud-controller-manager. cloud-controller-manager is a daemon that embeds cloud-specific control loops. These cloud-specific control loops were originally in the kube-controller-manager. Since cloud providers develop and release at a different pace compared to the Kubernetes project, abstracting the provider-specific code to the cloud-controller-manager binary allows cloud vendors to evolve independently from the core Kubernetes code.
|
||||
-->
|
||||
|
||||
Kubernetes v1.6 包含一个新的可执行文件叫做 cloud-controller-manager。cloud-controller-manager 是一个守护进程，其中嵌入了特定于某云环境的控制环。
|
||||
这些特定于云环境的控制环最初位于 kube-controller-manager 中。
|
||||
由于云供应商的开发和发布节奏与 Kubernetes 项目不同步，将特定于供应商的代码抽象到 cloud-controller-manager 可执行文件可以允许云供应商独立于核心 Kubernetes 代码进行演进。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 云供应商
|
||||
id: cloud-provider
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/cluster-administration/cloud-providers
|
||||
short_description: >
|
||||
云供应商是提供可以用来运行 Kubernetes 集群的云计算平台的公司。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Provider
|
||||
id: cloud-provider
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/cluster-administration/cloud-providers
|
||||
short_description: >
|
||||
Cloud provider is a company that offers cloud computing platform that can run Kubernetes clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Cloud provider is a company that offers cloud computing platform that can run Kubernetes clusters.
|
||||
-->
|
||||
云供应商是提供可以用来运行 Kubernetes 集群的云计算平台的公司。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Cloud providers or sometime called Cloud Service Provider (CSPs) provides cloud computing platforms. They may offer services such as Infrastructure as a Service (IaaS) or Platform as a Service (PaaS). Cloud providers host the Kubernetes cluster and also provide services that interact with the cluster, such as Load Balancers, Storage Classes etc.
|
||||
-->
|
||||
|
||||
云供应商也叫云服务供应商（CSPs），他们可以为用户提供云计算平台。他们提供的服务可以是基础设施即服务（IaaS）或者平台即服务（PaaS）。云供应商除了运行 Kubernetes 集群，还提供一些集群交互的服务，例如负载均衡（Load Balancers）、存储类别（Storage Classes）等。
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: 集群架构师
|
||||
id: cluster-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
集群架构师负责设计集群的基础设施，可能包含一个或多个 Kubernetes 集群。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Architect
|
||||
id: cluster-architect
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who designs infrastructure that involves one or more Kubernetes clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
集群架构师负责设计集群的基础设施，可能包含一个或多个 Kubernetes 集群。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Cluster architects are concerned with best practices for distributed systems, for example: high availability and security.
|
||||
-->
|
||||
|
||||
集群架构师要具备分布式系统的最佳实践经验，例如：高可用性和安全性。
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: 集群基础设施
|
||||
id: cluster-infrastructure
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
基础设施层提供并维护虚拟机、网络、安全组及其他资源。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Infrastructure
|
||||
id: cluster-infrastructure
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The infrastructure layer provides and maintains VMs, networking, security groups and others.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
The infrastructure layer provides and maintains VMs, networking, security groups and others.
|
||||
-->
|
||||
基础设施层提供并维护虚拟机、网络、安全组及其他资源。
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: 集群操作
|
||||
id: cluster-operations
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
诸如升级集群、实现安全、存储、Ingress、网络、日志和监控之类的活动，以及管理 Kubernetes 集群所涉及的其他操作。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Operations
|
||||
id: cluster-operations
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Activities such as upgrading the clusters, implementing security, storage, ingress, networking, logging and monitoring, and other operations involved in managing a Kubernetes cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operations
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Activities such as upgrading the clusters, implementing security, storage, ingress, networking, logging and monitoring, and other operations involved in managing a Kubernetes cluster.
|
||||
-->
|
||||
诸如升级集群、实现安全、存储、Ingress、网络、日志和监控之类的活动，以及管理 Kubernetes 集群所涉及的其他操作。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 集群操作者
|
||||
id: cluster-operator
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
配置、控制、监控集群的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cluster Operator
|
||||
id: cluster-operator
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who configures, controls, and monitors clusters.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who configures, controls, and monitors clusters.
|
||||
-->
|
||||
配置、控制、监控集群的人。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Their primary responsibility is keeping a cluster up and running, which may involve periodic maintenance activities or upgrades.<br>
|
||||
|
||||
**NOTE:** Cluster operators are different from the [Operator pattern](https://coreos.com/operators) that extends the Kubernetes API.
|
||||
-->
|
||||
|
||||
他们的主要责任是保持集群正常运行，可能需要进行周期性的维护和升级活动。<br>
|
||||
|
||||
**注意：** 集群操作者不同于[操作者模式（Operator Pattern）](https://coreos.com/operators)，操作者模式是用来扩展 Kubernetes API 的。
|
||||
|
||||
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: 集群
|
||||
id: cluster
|
||||
date: 2019-06-15
|
||||
full_link:
|
||||
short_description: >
|
||||
集群由一组被称作节点的机器组成。这些节点上运行 Kubernetes 所管理的容器化应用。集群具有至少一个工作节点和至少一个主节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
title: Cluster
|
||||
id: cluster
|
||||
date: 2019-06-15
|
||||
full_link:
|
||||
short_description: >
|
||||
A set of machines, called nodes, that run containerized applications managed by Kubernetes. A cluster has at least one worker node and at least one master node.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
--- -->
|
||||
<!-- A set of machines, called nodes, that run containerized applications managed by Kubernetes. A cluster has at least one worker node and at least one master node. -->
|
||||
集群由一组被称作节点的机器组成。这些节点上运行 Kubernetes 所管理的容器化应用。集群具有至少一个工作节点和至少一个主节点。
|
||||
|
||||
<!--more-->
|
||||
<!-- The worker node(s) host the pods that are the components of the application. The master node(s) manages the worker nodes and the pods in the cluster. Multiple master nodes are used to provide a cluster with failover and high availability. -->
|
||||
工作节点托管作为应用程序组件的 Pod 。主节点管理集群中的工作节点和 Pod 。多个主节点用于为集群提供故障转移和高可用性。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 云原生计算基金会 (CNCF)
|
||||
id: cncf
|
||||
date: 2019-05-26
|
||||
full_link: https://cncf.io/
|
||||
short_description: >
|
||||
云原生计算基金会
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
云原生计算基金会（CNCF）建立了可持续的生态系统，并在围绕着 [项目](https://www.cncf.io/projects/) 建立一个社区，将容器编排微服务架构的一部分。
|
||||
|
||||
Kubernetes 是一个云原生计算基金会项目.
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Cloud Native Computing Foundation (CNCF)
|
||||
id: cncf
|
||||
date: 2019-05-26
|
||||
full_link: https://cncf.io/
|
||||
short_description: >
|
||||
Cloud Native Computing Foundation
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
The Cloud Native Computing Foundation (CNCF) builds sustainable ecosystems and
|
||||
fosters a community around [projects](https://www.cncf.io/projects/) that
|
||||
orchestrate containers as part of a microservices architecture.
|
||||
|
||||
Kubernetes is a CNCF project.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The CNCF is a sub-foundation of [the Linux Foundation](https://www.linuxfoundation.org/).
|
||||
Its mission is to make cloud native computing ubiquitous.
|
||||
-->
|
||||
云原生计算基金会（CNCF）是 [Linux 基金会](https://www.linuxfoundation.org/) 的下属基金会。它的使命是让云原生计算无处不在。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: CNI (容器网络接口)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CNI (Container network interface)
|
||||
id: cni
|
||||
date: 2018-05-25
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni
|
||||
short_description: >
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
-->
|
||||
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* For information on Kubernetes and CNI refer to [this](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
-->
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 代码贡献者
|
||||
id: code-contributor
|
||||
date: 2018-04-12
|
||||
full_link: /docs/community/devel/
|
||||
short_description: >
|
||||
为 Kubernetes 开源代码库开发并贡献代码的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Code Contributor
|
||||
id: code-contributor
|
||||
date: 2018-04-12
|
||||
full_link: /docs/community/devel/
|
||||
short_description: >
|
||||
A person who develops and contributes code to the Kubernetes open source codebase.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who develops and contributes code to the Kubernetes open source codebase.
|
||||
-->
|
||||
|
||||
为 Kubernetes 开源代码库开发并贡献代码的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
They are also an active {{< glossary_tooltip text="community member" term_id="member" >}} who participates in one or more {{< glossary_tooltip text="Special Interest Groups (SIGs)" term_id="sig" >}}.
|
||||
-->
|
||||
|
||||
代码贡献者也是加入一个或多个 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}} 的活跃的 {{< glossary_tooltip text="社区成员" term_id="member" >}}。
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
short_description: >
|
||||
ConfigMap 是一种 API 对象，用来将非机密性的数据保存到健值对中。使用时可以用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: ConfigMap
|
||||
id: configmap
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/configure-pod-configmap/
|
||||
short_description: >
|
||||
An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a volume.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or config files in a {{< glossary_tooltip text="volume" term_id="volume" >}}.
|
||||
-->
|
||||
|
||||
ConfigMap 是一种 API 对象，用来将非机密性的数据保存到健值对中。使用时可以用作环境变量、命令行参数或者存储卷中的配置文件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Allows you to decouple environment-specific configuration from your {{< glossary_tooltip text="container images" term_id="container" >}}, so that your applications are easily portable. When storing confidential data use a [Secret](/docs/concepts/configuration/secret/).
|
||||
-->
|
||||
|
||||
ConfigMap 将您的环境配置信息和 {{< glossary_tooltip text="容器镜像" term_id="container" >}} 解耦，便于应用配置的修改。当您需要储存机密信息时可以使用 [Secret](/docs/concepts/configuration/secret/) 对象。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 容器环境变量
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/containers/container-environment-variables.md
|
||||
short_description: >
|
||||
容器环境变量提供了运行容器化应用所必须的一些重要信息。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container Environment Variables
|
||||
id: container-env-variables
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/containers/container-environment-variables.md
|
||||
short_description: >
|
||||
Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
|
||||
-->
|
||||
|
||||
容器环境变量提供了运行容器化应用所必须的一些重要信息。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Container environment variables provide information that is required by the running containerized applications along with information about important resources to the {{< glossary_tooltip text="Containers" term_id="container" >}}. For example, file system details, information about the container itself, and other cluster resources such as service endpoints.
|
||||
-->
|
||||
|
||||
容器环境变量为运行中的容器化应用提供必要的信息，同时还提供与 {{< glossary_tooltip text="容器" term_id="container" >}} 重要资源相关的其他信息，例如：文件系统信息、容器自身的信息以及其他像服务端点（Service endpoints）这样的集群资源信息。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 容器生命周期钩子
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/containers/container-lifecycle-hooks/
|
||||
short_description: >
|
||||
生命周期钩子暴露容器管理生命周期中的事件，允许用户在事件发生时运行代码。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Container Lifecycle Hooks
|
||||
id: container-lifecycle-hooks
|
||||
date: 2018-10-08
|
||||
full_link: /docs/concepts/containers/container-lifecycle-hooks/
|
||||
short_description: >
|
||||
The lifecycle hooks expose events in the container management lifecycle and let the user run code when the events occur.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
生命周期钩子暴露{{< glossary_tooltip text="容器" term_id="container" >}}管理生命周期中的事件，允许用户在事件发生时运行代码。
|
||||
<!--
|
||||
The lifecycle hooks expose events in the {{< glossary_tooltip text="Container" term_id="container" >}}container management lifecycle and let the user run code when the events occur.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
针对容器暴露了两个钩子：PostStart 在容器创建之后立即执行，PreStop 在容器停止之前立即阻塞并被调用。
|
||||
<!--
|
||||
Two hooks are exposed to Containers: PostStart which executes immediately after a container is created and PreStop which is blocking and is called immediately before a container is terminated.
|
||||
-->
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: 容器运行环境（Container Runtime）
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /docs/reference/generated/container-runtime
|
||||
short_description: >
|
||||
容器运行环境是负责运行容器的软件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Container Runtime
|
||||
id: container-runtime
|
||||
date: 2019-06-05
|
||||
full_link: /docs/reference/generated/container-runtime
|
||||
short_description: >
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The container runtime is the software that is responsible for running containers.
|
||||
-->
|
||||
容器运行环境是负责运行容器的软件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes supports several container runtimes: [Docker](http://www.docker.com),
|
||||
[containerd](https://containerd.io), [cri-o](https://cri-o.io/),
|
||||
[rktlet](https://github.com/kubernetes-incubator/rktlet) and any implementation of
|
||||
the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md).
|
||||
-->
|
||||
Kubernetes 支持多个容器运行环境: [Docker](http://www.docker.com)、
|
||||
[containerd](https://containerd.io)、[cri-o](https://cri-o.io/)、
|
||||
[rktlet](https://github.com/kubernetes-incubator/rktlet) 以及任何实现 [Kubernetes CRI (容器运行环境接口)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)。
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 容器
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
short_description: >
|
||||
容器是可移植、可执行的轻量级的镜像，镜像中包含软件及其相关依赖。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container
|
||||
id: container
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/what-is-kubernetes/#why-containers
|
||||
short_description: >
|
||||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A lightweight and portable executable image that contains software and all of its dependencies.
|
||||
-->
|
||||
|
||||
容器是可移植、可执行的轻量级的镜像，镜像中包含软件及其相关依赖。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Containers decouple applications from underlying host infrastructure to make deployment easier in different cloud or OS environments, and for easier scaling.
|
||||
-->
|
||||
|
||||
容器使应用和底层的主机基础设施解耦，降低了应用在不同云环境或者操作系统上的部署难度，便于应用扩展。
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: containerd
|
||||
id: containerd
|
||||
date: 2019-05-14
|
||||
full_link: https://containerd.io/docs/
|
||||
short_description: >
|
||||
强调简单性、健壮性和可移植性的一种容器运行时
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: containerd
|
||||
id: containerd
|
||||
date: 2019-05-14
|
||||
full_link: https://containerd.io/docs/
|
||||
short_description: >
|
||||
A container runtime with an emphasis on simplicity, robustness and portability
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
强调简单性、健壮性和可移植性的一种容器运行时
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
containerd is a {{< glossary_tooltip text="container" term_id="container" >}} runtime
|
||||
that runs as a daemon on Linux or Windows. containerd takes care of fetching and
|
||||
storing container images, executing containers, providing network access, and more.
|
||||
-->
|
||||
|
||||
containerd 是一种 {{< glossary_tooltip text="容器" term_id="container" >}} 运行时，能在 Linux 或者 Windows 后台运行。
|
||||
containerd 能取回、存储容器镜像，执行容器实例，提供网络访问等。
|
||||
+39
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 贡献者
|
||||
id: contributor
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Contributor
|
||||
id: contributor
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
-->
|
||||
|
||||
<!--
|
||||
Someone who donates code, documentation, or their time to help the Kubernetes project or community.
|
||||
-->
|
||||
|
||||
通过贡献代码、文档或者投入时间等方式来帮助 Kubernetes 项目或社区的人。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
Contributions include pull requests (PRs), issues, feedback, {{< glossary_tooltip text="special interest groups (SIG)" term_id="sig" >}} participation, or organizing community events.
|
||||
-->
|
||||
|
||||
贡献形式包括提交拉取请求（PRs）、问题报告（Issues）、反馈、参与{{< glossary_tooltip text="特别兴趣小组（SIG）" term_id="sig" >}}或者组织社区活动等等。
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: 控制平面
|
||||
id: control-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Control Plane
|
||||
id: control-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
|
||||
-->
|
||||
容器编排层，它暴露 API 和接口来定义、部署容器和管理容器的生命周期。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 控制器
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kube-controller-manager/
|
||||
short_description: >
|
||||
控制器通过 apiserver 监控集群的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Controller
|
||||
id: controller
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kube-controller-manager/
|
||||
short_description: >
|
||||
A control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
控制器通过 {{< glossary_tooltip text="apiserver" term_id="kube-apiserver" >}} 监控集群的公共状态，并致力于将当前状态转变为期望的状态。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Examples of controllers that ship with Kubernetes today are the replication controller, endpoints controller, namespace controller, and serviceaccounts controller.
|
||||
-->
|
||||
|
||||
Kubernetes 当前提供的部分控制器例子包括：副本控制器（replication controller）、端点控制器（endpoints controller）、命名空间控制器（namespace controller）、服务账号控制器（serviceaccounts controller）。
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/docs/
|
||||
short_description: >
|
||||
专用于 Kubernetes 的轻量级容器运行环境
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
title: CRI-O
|
||||
id: cri-o
|
||||
date: 2019-05-14
|
||||
full_link: https://cri-o.io/docs/
|
||||
short_description: >
|
||||
A lightweight container runtime specifically for Kubernetes
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
--- -->
|
||||
<!-- A tool that lets you use OCI container runtimes with Kubernetes CRI. -->
|
||||
该工具可让您通过 Kubernetes CRI 使用 OCI 容器运行环境。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- CRI-O is an implementation of the {{< glossary_tooltip term_id="cri" >}}
|
||||
to enable using {{< glossary_tooltip text="container" term_id="container" >}}
|
||||
runtimes that are compatible with the Open Container Initiative (OCI)
|
||||
[runtime spec](http://www.github.com/opencontainers/runtime-spec). -->
|
||||
CRI-O 是 {{< glossary_tooltip term_id="cri" >}} 的实现，可启用与开放容器倡议 Open Container Initiative（OCI）兼容的 {{< glossary_tooltip text="container" term_id="container" >}} 运行环境[运行时规范](http://www.github.com/opencontainers/runtime-spec)。
|
||||
|
||||
<!-- Deploying CRI-O allows Kubernetes to use any OCI-compliant runtime as the container
|
||||
runtime for running {{< glossary_tooltip text="Pods" term_id="pod" >}}, and to fetch
|
||||
OCI container images from remote registries. -->
|
||||
部署 CRI-O 允许 Kubernetes 使用任何符合 OCI 运行环境，作为容器运行环境去运行 {{< glossary_tooltip text="Pods" term_id="pod" >}}，并从远程注册表获取 OCI 容器镜像。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 容器运行时接口 (CRI)
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
一组与 kubelet 集成的容器运行时 API
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
容器运行时接口 (CRI) 是一组与节点上 kubelet 集成的容器运行时 API
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container runtime interface (CRI)
|
||||
id: cri
|
||||
date: 2019-03-07
|
||||
full_link: /docs/concepts/overview/components/#container-runtime
|
||||
short_description: >
|
||||
An API for container runtimes to integrate with kubelet
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
The container runtime interface (CRI) is an API for container runtimes
|
||||
to integrate with kubelet on a node.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
For more information, see the [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API and specifications.
|
||||
-->
|
||||
|
||||
更多信息， 请参考 [容器运行时接口](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md) API 与规格。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: CronJob
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
管理定期运行的 [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CronJob
|
||||
id: cronjob
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/cron-jobs/
|
||||
short_description: >
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Manages a [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/) that runs on a periodic schedule.
|
||||
-->
|
||||
|
||||
管理定期运行的 [Job](/docs/concepts/workloads/controllers/jobs-run-to-completion/)。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Similar to a line in a *crontab* file, a Cronjob object specifies a schedule using the [Cron](https://en.wikipedia.org/wiki/Cron) format.
|
||||
-->
|
||||
|
||||
Cronjob 对象类似 *crontab* 文件中的一行命令，它声明了一个遵循 [Cron](https://en.wikipedia.org/wiki/Cron) 格式的调度任务。
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: 容器存储接口 (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
容器存储接口 （CSI）定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Container Storage Interface (CSI)
|
||||
id: csi
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#csi
|
||||
short_description: >
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
|
||||
-->
|
||||
|
||||
容器存储接口 （CSI）定义了存储系统暴露给容器的标准接口。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
CSI allows vendors to create custom storage plugins for Kubernetes without adding them to the Kubernetes repository (out-of-tree plugins). To use a CSI driver from a storage provider, you must first [deploy it to your cluster](https://kubernetes-csi.github.io/docs/Setup.html). You will then be able to create a {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} that uses that CSI driver.
|
||||
|
||||
* [CSI in the Kubernetes documentation](/docs/concepts/storage/volumes/#csi)
|
||||
* [List of available CSI drivers](https://kubernetes-csi.github.io/docs/Drivers.html)
|
||||
-->
|
||||
|
||||
CSI 允许存储驱动提供商为 Kubernetes 创建定制化的存储插件，而无需将这些插件的代码添加到 Kubernetes 代码仓库（外部插件）。要使用某个存储提供商的 CSI 驱动，你首先要[将它部署到你的集群上](https://kubernetes-csi.github.io/docs/Setup.html)。然后你才能创建使用该 CSI 驱动的 {{< glossary_tooltip text="Storage Class" term_id="storage-class" >}} 。
|
||||
|
||||
* [Kubernetes 文档中关于 CSI 的描述](/docs/concepts/storage/volumes/#csi)
|
||||
* [可用的 CSI 驱动列表](https://kubernetes-csi.github.io/docs/Drivers.html)
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
|
||||
short_description: >
|
||||
通过定制化的代码给您的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: CustomResourceDefinition
|
||||
id: CustomResourceDefinition
|
||||
date: 2018-04-12
|
||||
full_link: docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/
|
||||
short_description: >
|
||||
Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
|
||||
-->
|
||||
|
||||
通过定制化的代码给您的 Kubernetes API 服务器增加资源对象，而无需编译完整的定制 API 服务器。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Custom Resource Definitions let you extend the Kubernetes API for your environment if the publicly supported API resources can't meet your needs.
|
||||
-->
|
||||
|
||||
当 Kubernetes 公开支持的 API 资源不能满足您的需要时，定制资源对象（Custom Resource Definitions）让您可以在您的环境上扩展 Kubernetes API。
|
||||
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/daemonset
|
||||
short_description: >
|
||||
确保 Pod 的副本在集群中的一组节点上运行。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: DaemonSet
|
||||
id: daemonset
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/daemonset
|
||||
short_description: >
|
||||
Ensures a copy of a Pod is running across a set of nodes in a cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Ensures a copy of a {{< glossary_tooltip text="Pod" term_id="pod" >}} is running across a set of nodes in a {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
|
||||
-->
|
||||
确保 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的副本在{{< glossary_tooltip text="集群" term_id="cluster" >}}中的一组节点上运行。
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Used to deploy system daemons such as log collectors and monitoring agents that typically must run on every {{< glossary_tooltip term_id="node" >}}.
|
||||
-->
|
||||
|
||||
用来部署系统守护进程，例如日志搜集和监控代理，这些进程通常必须运行在每个{{< glossary_tooltip text="节点" term_id="node" >}}上。
|
||||
|
||||
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: 数据平面
|
||||
id: data-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
提供诸如 CPU，内存，网络和存储的能力，以便容器可以运行并连接到网络。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
提供诸如 CPU，内存，网络和存储的能力，以便容器可以运行并连接到网络。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Data Plane
|
||||
id: data-plane
|
||||
date: 2019-05-12
|
||||
full_link:
|
||||
short_description: >
|
||||
The layer that provides capacity such as CPU, memory, network, and storage so that the containers can run and connect to a network.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
The layer that provides capacity such as CPU, memory, network, and storage so that the containers can run and connect to a network.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
Deployment 是管理应用副本的 API 对象。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Deployment
|
||||
id: deployment
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/deployment/
|
||||
short_description: >
|
||||
An API object that manages a replicated application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that manages a replicated application.
|
||||
-->
|
||||
|
||||
Deployment 是管理应用副本的 API 对象。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Each replica is represented by a {{< glossary_tooltip term_id="pod" >}}, and the Pods are distributed among the nodes of a cluster.
|
||||
-->
|
||||
|
||||
应用的每个副本就是一个 {{< glossary_tooltip term_id="pod" >}}，并且这些 Pod 会分散运行在集群的节点上。
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 开发者 (释疑)
|
||||
id: developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
指的是：应用开发者、代码贡献者、或平台开发者。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Developer (disambiguation)
|
||||
id: developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: Application Developer, Code Contributor, or Platform Developer.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
指的是： {{< glossary_tooltip text="应用开发者" term_id="application-developer" >}}、 {{< glossary_tooltip text="代码贡献者" term_id="code-contributor" >}}、或 {{< glossary_tooltip text="平台开发者" term_id="platform-developer" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
This overloaded term may have different meanings depending on the context
|
||||
-->
|
||||
|
||||
根据上下文的不同，“开发者”这个被多处使用的词条会有不同的含义。
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: 驱动插件
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
在 Kubernetes 中运行的容器提供对供应商特定资源的访问权限。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
title: Device Plugin
|
||||
id: device-plugin
|
||||
date: 2019-02-02
|
||||
full_link: /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
|
||||
short_description: >
|
||||
Containers running in Kubernetes that provide access to a vendor specific resource.
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
--- -->
|
||||
<!-- Device Plugins are containers running in Kubernetes that provide access to a vendor specific resource. -->
|
||||
设备插件是在 Kubernetes 中运行的容器，可用于访问供应商特定资源。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- [Device Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) are containers running in Kubernetes that provide access to a vendor-specific resource. Device Plugins advertise these resources to {{< glossary_tooltip term_id="kubelet" >}}. They can be deployed manually or as a {{< glossary_tooltip term_id="daemonset" >}}, rather than writing custom Kubernetes code. -->
|
||||
[驱动插件](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/) 是运行在 Kubernetes 中的容器，它提供对供应商特定资源的访问。驱动插件将这些资源发布到 {{< glossary_tooltip term_id="kubelet" >}}。并且可以手动部署或做为 {{< glossary_tooltip term_id="daemonset" >}}，而不用编写定制的 Kubernetes 代码。
|
||||
Executable
+41
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
short_description: >
|
||||
Docker 是一种可以提供操作系统级别虚拟化（也称作容器）的软件技术。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: docker
|
||||
id: docker
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/kubectl/docker-cli-to-kubectl/
|
||||
short_description: >
|
||||
Docker is a software technology providing operating-system-level virtualization also known as containers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Docker is a software technology providing operating-system-level virtualization also known as containers.
|
||||
-->
|
||||
|
||||
Docker 是一种可以提供操作系统级别虚拟化（也称作容器）的软件技术
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Docker uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines (VMs).
|
||||
-->
|
||||
|
||||
Docker 使用了 Linux 内核中的资源隔离特性（如 cgroup 和内核命名空间）以及支持联合文件系统（如 OverlayFS 和其他），允许多个相互独立的“容器”一起运行在同一 Linux 实例上，从而避免启动和维护虚拟机（VMs）的开销。
|
||||
+44
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 下游(消除歧义)
|
||||
id: downstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
可以指：Kubernetes 生态系统中依赖于核心 Kubernetes 代码库或分支代码库的代码。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Downstream (disambiguation)
|
||||
id: downstream
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
|
||||
-->
|
||||
|
||||
可以指：Kubernetes 生态系统中依赖于核心 Kubernetes 代码库或分支代码库的代码。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* In the **Kubernetes Community**: Conversations often use *downstream* to mean the ecosystem, code, or third-party tools that rely on the core Kubernetes codebase. For example, a new feature in Kubernetes may be adopted by applications *downstream* to improve their functionality.
|
||||
* In **GitHub** or **git**: The convention is to refer to a forked repo as *downstream*, whereas the source repo is considered *upstream*.
|
||||
-->
|
||||
|
||||
* 在 **Kubernetes 社区**中：*下游(downstream)* 在人们交流中常用来表示那些依赖核心 Kubernetes 代码库的生态系统、代码或者第三方工具。例如，Kubernete 的一个新特性可以被*下游(downstream)* 应用采用，以提升它们的功能性。
|
||||
* 在 **GitHub** 或 **git** 中：约定用*下游(downstream)* 表示分支代码库，源代码库被认为是*上游(upstream)*。
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 动态卷供应
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/dynamic-provisioning
|
||||
short_description: >
|
||||
允许用户请求自动创建存储卷。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Dynamic Volume Provisioning
|
||||
id: dynamicvolumeprovisioning
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/dynamic-provisioning
|
||||
short_description: >
|
||||
Allows users to request automatic creation of storage Volumes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Allows users to request automatic creation of storage {{< glossary_tooltip text="Volumes" term_id="volume" >}}.
|
||||
-->
|
||||
|
||||
允许用户请求自动创建存储 {{< glossary_tooltip text="卷" term_id="volume" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Dynamic provisioning eliminates the need for cluster administrators to pre-provision storage. Instead, it automatically provisions storage by user request. Dynamic volume provisioning is based on an API object, {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}}, referring to a {{< glossary_tooltip text="Volume Plugin" term_id="volume-plugin" >}} that provisions a {{< glossary_tooltip text="Volume" term_id="volume" >}} and the set of parameters to pass to the Volume Plugin.
|
||||
-->
|
||||
|
||||
动态供应让集群管理员无需再预先供应存储。相反，它通过用户请求自动地供应存储。
|
||||
动态卷供应是基于 API 对象 {{< glossary_tooltip text="StorageClass" term_id="storage-class" >}} 的，StorageClass 可以引用 {{< glossary_tooltip text="卷插件（Volume Plugin）" term_id="volume-plugin" >}} 提供的 {{< glossary_tooltip text="卷（Volume）" term_id="volume" >}} ，也可以引用传递给卷插件（Volume Plugin）的参数集。
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: 端点切片
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/endpoint-slices/
|
||||
short_description: >
|
||||
一种将网络端点与 Kubernetes 资源组合在一起的方法。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
一种将网络端点与 Kubernetes 资源组合在一起的方法。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Endpoint Slice
|
||||
id: endpoint-slice
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/endpoint-slices/
|
||||
short_description: >
|
||||
A way to group network endpoints together with Kubernetes resources.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
---
|
||||
A way to group network endpoints together with Kubernetes resources.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A scalable and extensible way to group network endpoints together. These can be
|
||||
used by {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} to
|
||||
establish network routes on each {{< glossary_tooltip text="node" term_id="node" >}}.
|
||||
-->
|
||||
|
||||
|
||||
一种将网络端点组合在一起的可扩缩、可扩展方式。它们将被 {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}} 用于在每个 {{< glossary_tooltip text="节点" term_id="node">}} 上建立网络路由。
|
||||
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: 临时容器
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /docs/concepts/workloads/pods/ephemeral-containers/
|
||||
short_description: >
|
||||
您可以在 Pod 中临时运行的一种容器类型
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
您可以在 {{< glossary_tooltip term_id="pod" >}} 中临时运行的一种 {{< glossary_tooltip term_id="container" >}} 类型
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Ephemeral Container
|
||||
id: ephemeral-container
|
||||
date: 2019-08-26
|
||||
full_link: /docs/concepts/workloads/pods/ephemeral-containers/
|
||||
short_description: >
|
||||
A type of container type that you can temporarily run inside a Pod
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
A {{< glossary_tooltip term_id="container" >}} type that you can temporarily run inside a {{< glossary_tooltip term_id="pod" >}}.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
If you want to investigate a Pod that's running with problems, you can add an ephemeral container to that Pod and carry out diagnostics. Ephemeral containers have no resource or scheduling guarantees, and you should not use them to run any part of the workload itself.
|
||||
-->
|
||||
|
||||
如果想要调查运行中有问题的 Pod，可以向该 Pod 添加一个临时容器并进行诊断。临时容器没有资源或调度保证，因此不应该使用它们来运行任何部分的工作负荷本身。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: etcd
|
||||
id: etcd
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/
|
||||
short_description: >
|
||||
etcd 是兼具一致性和高可用性的键值数据库，用作保存 Kubernetes 所有集群数据的后台数据库。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: etcd
|
||||
id: etcd
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/administer-cluster/configure-upgrade-etcd/
|
||||
short_description: >
|
||||
Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Consistent and highly-available key value store used as Kubernetes' backing store for all cluster data.
|
||||
-->
|
||||
|
||||
etcd 是兼具一致性和高可用性的键值数据库，可以作为保存 Kubernetes 所有集群数据的后台数据库。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Always have a backup plan for etcd's data for your Kubernetes cluster. For in-depth information on etcd, see [etcd documentation](https://github.com/coreos/etcd/blob/master/Documentation/docs.md).
|
||||
-->
|
||||
|
||||
您的 Kubernetes 集群的 etcd 数据库通常需要有个备份计划。要了解 etcd 更深层次的信息，请参考 [etcd 文档](https://github.com/coreos/etcd/blob/master/Documentation/docs.md)。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 扩展组件
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
short_description: >
|
||||
扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
扩展组件是扩展并与 Kubernetes 深度集成以支持新型硬件的软件组件。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Extensions
|
||||
id: Extensions
|
||||
date: 2019-02-01
|
||||
full_link: /docs/concepts/extend-kubernetes/extend-cluster/#extensions
|
||||
short_description: >
|
||||
Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- extension
|
||||
---
|
||||
Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Most cluster administrators will use a hosted or distribution instance of Kubernetes. As a result, most Kubernetes users will need to install [extensions](/docs/concepts/extend-kubernetes/extend-cluster/#extensions) and fewer will need to author new ones.
|
||||
-->
|
||||
|
||||
大多数集群管理员会使用托管的 Kubernetes 或其某种发行包。因此，大多数 Kubernetes 用户将需要安装 [扩展组件](/docs/concepts/extend-kubernetes/extend-cluster/#extensions)，较少用户会需要编写新的扩展组件。
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: FlexVolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}} 是比 Flexvolume 更新的接口，它解决了 Flexvolumes 的一些问题。
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
---
|
||||
|
||||
<!-- ---
|
||||
title: FlexVolume
|
||||
id: flexvolume
|
||||
date: 2018-06-25
|
||||
full_link: /docs/concepts/storage/volumes/#flexvolume
|
||||
short_description: >
|
||||
FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes.
|
||||
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- storage
|
||||
--- -->
|
||||
<!-- FlexVolume is an interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface which addresses several problems with FlexVolumes. -->
|
||||
Flexvolume 是创建 out-of-tree 卷插件的一种接口。 {{< glossary_tooltip text="容器存储接口（CSI）" term_id="csi" >}} 是比 Flexvolume 更新的接口，它解决了 Flexvolume 的一些问题。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- FlexVolumes enable users to write their own drivers and add support for their volumes in Kubernetes. FlexVolume driver binaries and dependencies must be installed on host machines. This requires root access. The Storage SIG suggests implementing a {{< glossary_tooltip text="CSI" term_id="csi" >}} driver if possible since it addresses the limitations with FlexVolumes. -->
|
||||
Flexvolume 允许用户编写自己的驱动程序，并在 Kubernetes 中加入对用户自己的数据卷的支持。FlexVolume 驱动程序的二进制文件和依赖项必须安装在主机上。这需要 root 权限。如果可能的话，SIG Storage 建议实现 {{< glossary_tooltip text="CSI" term_id="csi" >}} 驱动程序，因为它解决了 Flexvolumes 的限制。
|
||||
|
||||
<!-- * [FlexVolume in the Kubernetes documentation](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [More information on FlexVolumes](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
|
||||
* [Volume Plugin FAQ for Storage Vendors](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md) -->
|
||||
* [Kubernetes 文档中的 Flexvolume](/docs/concepts/storage/volumes/#flexvolume)
|
||||
* [更多关于 Flexvolumes 的信息](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
|
||||
* [存储供应商的卷插件 FAQ](https://github.com/kubernetes/community/blob/master/sig-storage/volume-plugin-faq.md)
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Helm Chart
|
||||
id: helm-chart
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
|
||||
short_description: >
|
||||
Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Helm Chart
|
||||
id: helm-chart
|
||||
date: 2018-04-12
|
||||
full_link: https://github.com/kubernetes/helm/blob/master/docs/charts.md
|
||||
short_description: >
|
||||
A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A package of pre-configured Kubernetes resources that can be managed with the Helm tool.
|
||||
-->
|
||||
|
||||
Helm Chart 是一组预先配置的 Kubernetes 资源所构成的包，可以使用 Helm 工具对其进行管理。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Charts provide a reproducible way of creating and sharing Kubernetes applications.
|
||||
A single chart can be used to deploy something simple, like a memcached Pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
|
||||
-->
|
||||
|
||||
Chart 提供了一种可重现的用来创建和共享 Kubernetes 应用的方法。
|
||||
单个 Chart 可用来部署简单的系统（例如一个 memcached Pod），也可以用来部署复杂的系统（例如包含 HTTP 服务器、数据库、缓存等组件的完整 Web 应用堆栈）。
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: Pod 水平自动扩缩器
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
short_description: >
|
||||
Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Horizontal Pod Autoscaler
|
||||
id: horizontal-pod-autoscaler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/run-application/horizontal-pod-autoscale/
|
||||
short_description: >
|
||||
An API resource that automatically scales the number of pod replicas based on targeted CPU utilization or custom metric targets.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
Pod 水平自动扩缩器（Horizontal Pod Autoscaler）是一种 API 资源，它根据目标 CPU 利用率或自定义度量目标扩缩 Pod 副本的数量。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
HPA is typically used with {{< glossary_tooltip text="Replication Controllers" term_id="replication-controller" >}}, {{< glossary_tooltip text="Deployments" term_id="deployment" >}}, or Replica Sets. It cannot be applied to objects that cannot be scaled, for example {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}.
|
||||
-->
|
||||
|
||||
HPA 通常用于 {{< glossary_tooltip text="Replication Controllers" term_id="replication-controller" >}}、{{< glossary_tooltip text="Deployments" term_id="deployment" >}} 或者 Replica Sets 上。HPA 不能用于不支持扩缩的对象，例如 {{< glossary_tooltip text="DaemonSets" term_id="daemonset" >}}。
|
||||
Executable
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 镜像
|
||||
id: image
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
镜像是保存的容器实例，它打包了应用运行所需的一组软件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Image
|
||||
id: image
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Stored instance of a container that holds a set of software needed to run an application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Stored instance of a container that holds a set of software needed to run an application.
|
||||
-->
|
||||
|
||||
镜像是保存的容器实例，它打包了应用运行所需的一组软件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A way of packaging software that allows it to be stored in a container registry, pulled to a local system, and run as an application. Meta data is included in the image that can indicate what executable to run, who built it, and other information.
|
||||
-->
|
||||
|
||||
镜像是软件打包的一种方式，可以将镜像存储在容器镜像仓库、拉取到本地系统并作为应用来运行。
|
||||
镜像中包含的元数据指明了运行什么可执行程序、是由谁构建的以及其他信息。
|
||||
@@ -1,4 +1,7 @@
|
||||
---
|
||||
approvers:
|
||||
- chenopis
|
||||
- abiogenesis-now
|
||||
title: 标准化词汇表
|
||||
layout: glossary
|
||||
noedit: true
|
||||
|
||||
Executable → Regular
+26
-4
@@ -3,22 +3,44 @@ title: Ingress
|
||||
id: ingress
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/ingress/
|
||||
short_description: >
|
||||
Ingress 是对集群中服务的外部访问进行管理的 API 对象，典型的访问方式是 HTTP。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Ingress
|
||||
id: ingress
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/ingress/
|
||||
short_description: >
|
||||
An API object that manages external access to the services in a cluster, typically HTTP.
|
||||
|
||||
aka:
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that manages external access to the services in a cluster, typically HTTP.
|
||||
-->
|
||||
一个 API 对象，用于管理对集群中服务的外部访问，通常是 HTTP。
|
||||
|
||||
<!--more-->
|
||||
Ingress 是对集群中服务的外部访问进行管理的 API 对象，典型的访问方式是 HTTP。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Ingress can provide load balancing, SSL termination and name-based virtual hosting.
|
||||
-->
|
||||
Ingress 可以提供负载平衡，SSL 终端和基于名称的虚拟主机。
|
||||
|
||||
Ingress 可以提供负载均衡、SSL 终结和基于名称的虚拟托管。
|
||||
|
||||
|
||||
+41
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 初始化容器
|
||||
id: init-container
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
应用容器运行前必须先运行完成的一个或多个初始化容器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Init Container
|
||||
id: init-container
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
One or more initialization containers that must run to completion before any app containers run.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
One or more initialization containers that must run to completion before any app containers run.
|
||||
-->
|
||||
|
||||
应用容器运行前必须先运行完成的一个或多个初始化容器。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Initialization (init) containers are like regular app containers, with one difference: init containers must run to completion before any app containers can start. Init containers run in series: each init container must run to completion before the next init container begins.
|
||||
-->
|
||||
|
||||
初始化（init）容器像常规应用容器一样，只有一点不同：初始化（init）容器必须在应用容器启动前运行完成。Init 容器的运行顺序：一个初始化（init）容器必须在下一个初始化（init）容器开始前运行完成。
|
||||
Executable
+45
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/overview.html
|
||||
short_description: >
|
||||
Istio 是个开放平台（非 Kubernetes 特有），提供了一种统一的方式来集成微服务、管理流量、实施策略和汇总度量数据。
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Istio
|
||||
id: istio
|
||||
date: 2018-04-12
|
||||
full_link: https://istio.io/docs/concepts/what-is-istio/overview.html
|
||||
short_description: >
|
||||
An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
|
||||
-->
|
||||
|
||||
Istio 是个开放平台（非 Kubernetes 特有），提供了一种统一的方式来集成微服务、管理流量、实施策略和汇总度量数据。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Adding Istio does not require changing application code. It is a layer of infrastructure between a service and the network, which when combined with service deployments, is commonly referred to as a service mesh. Istio's control plane abstracts away the underlying cluster management platform, which may be Kubernetes, Mesosphere, etc.
|
||||
-->
|
||||
|
||||
添加 Istio 时不需要修改应用代码。它是基础设施的一层，介于服务和网络之间。当它和服务的 Deployment 相结合时，就构成了通常所谓的服务网格（Service Mesh）。Istio 的控制面抽象掉了底层的集群管理平台，这一集群管理平台可以是 Kubernetes、Mesosphere 等。
|
||||
|
||||
Executable
+45
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/jobs-run-to-completion
|
||||
short_description: >
|
||||
Job 是需要运行完成的确定性的或批量的任务。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Job
|
||||
id: job
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/jobs-run-to-completion
|
||||
short_description: >
|
||||
A finite or batch task that runs to completion.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A finite or batch task that runs to completion.
|
||||
-->
|
||||
|
||||
Job 是需要运行完成的确定性的或批量的任务。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Creates one or more {{< glossary_tooltip term_id="pod" >}} objects and ensures that a specified number of them successfully terminate. As Pods successfully complete, the Job tracks the successful completions.
|
||||
-->
|
||||
|
||||
Job 创建一个或多个 {{< glossary_tooltip term_id="Pod" >}} 对象，并确保指定数量的 Pod 成功终止。随着各 Pod 成功结束，Job 会跟踪记录成功完成的个数。
|
||||
Executable
+63
@@ -0,0 +1,63 @@
|
||||
---
|
||||
title: Kops
|
||||
id: kops
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/kops/
|
||||
short_description: >
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。注意：官方仅支持 AWS，GCE 和 VMware vSphere 的支持还处于 alpha* 阶段。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kops
|
||||
id: kops
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/kops/
|
||||
short_description: >
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A CLI tool that helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters. *NOTE: Officially supports AWS only, with GCE and VMware vSphere in alpha*.
|
||||
-->
|
||||
|
||||
kops 是一个命令行工具，可以帮助您创建、销毁、升级和维护生产级，高可用性的 Kubernetes 集群。*注意：官方仅支持 AWS，GCE 和 VMware vSphere 的支持还处于 alpha 阶段*。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
`kops` provisions your cluster with:
|
||||
|
||||
* Fully automated installation
|
||||
* DNS-based cluster identification
|
||||
* Self-healing: everything runs in Auto-Scaling Groups
|
||||
* Limited OS support (Debian preferred, Ubuntu 16.04 supported, early support for CentOS & RHEL)
|
||||
* High availability (HA) support
|
||||
* The ability to directly provision, or generate terraform manifests
|
||||
-->
|
||||
|
||||
`kops` 为您的集群提供了：
|
||||
|
||||
* 全自动化安装
|
||||
* 基于 DNS 的集群标识
|
||||
* 自愈功能：所有组件都在自动伸缩组（Auto-Scaling Groups）中运行
|
||||
* 有限的操作系统支持 (推荐使用 Debian，支持 Ubuntu 16.04，试验性支持 CentOS & RHEL)
|
||||
* 高可用 (HA) 支持
|
||||
* 直接提供或者生成 Terraform 清单文件的能力
|
||||
|
||||
<!--
|
||||
You can also build your own cluster using {{< glossary_tooltip term_id="kubeadm" >}} as a building block. `kops` builds on the kubeadm work.
|
||||
-->
|
||||
|
||||
您也可以将自己的集群作为一个构造块，使用 {{< glossary_tooltip term_id="kubeadm" >}} 构造集群。`kops` 是建立在 kubeadm 之上的。
|
||||
+44
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: kube-apiserver
|
||||
id: kube-apiserver
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-apiserver/
|
||||
short_description: >
|
||||
主节点上负责提供 Kubernetes API 服务的组件；它是 Kubernetes 控制面的前端。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: kube-apiserver
|
||||
id: kube-apiserver
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-apiserver/
|
||||
short_description: >
|
||||
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
Component on the master that exposes the Kubernetes API. It is the front-end for the Kubernetes control plane.
|
||||
-->
|
||||
|
||||
主节点上负责提供 Kubernetes API 服务的组件；它是 Kubernetes 控制面的前端。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
It is designed to scale horizontally - that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).
|
||||
-->
|
||||
|
||||
kube-apiserver 在设计上考虑了水平扩缩的需要。
|
||||
换言之，通过部署多个实例可以实现扩缩。
|
||||
参见[构造高可用集群](/docs/admin/high-availability/)。
|
||||
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: kube-controller-manager
|
||||
id: kube-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-controller-manager/
|
||||
short_description: >
|
||||
主节点上运行控制器的组件。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: kube-controller-manager
|
||||
id: kube-controller-manager
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-controller-manager/
|
||||
short_description: >
|
||||
Component on the master that runs controllers.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Component on the master that runs {{< glossary_tooltip text="controllers" term_id="controller" >}}.
|
||||
-->
|
||||
在主节点上运行{{< glossary_tooltip text="控制器" term_id="controller" >}}的组件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
从逻辑上讲，每个{{< glossary_tooltip text="控制器" term_id="controller" >}}都是一个单独的进程，但是为了降低复杂性，它们都被编译到同一个可执行文件，并在一个进程中运行。
|
||||
|
||||
+41
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: kube-proxy
|
||||
id: kube-proxy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/command-line-tools-reference/kube-proxy/
|
||||
short_description: >
|
||||
`kube-proxy` 是集群中每个节点上运行的网络代理。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- networking
|
||||
---
|
||||
<!-- ---
|
||||
title: kube-proxy
|
||||
id: kube-proxy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/command-line-tools-reference/kube-proxy/
|
||||
short_description: >
|
||||
`kube-proxy` is a network proxy that runs on each node in the cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- networking
|
||||
--- -->
|
||||
<!-- [kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) is a
|
||||
network proxy that runs on each node in your cluster, implementing part of
|
||||
the Kubernetes {{< glossary_tooltip term_id="service">}} concept. -->
|
||||
[kube-proxy](/docs/reference/command-line-tools-reference/kube-proxy/) 是集群中每个节点上运行的网络代理,实现 Kubernetes {{< glossary_tooltip term_id="service">}} 概念的一部分。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!-- kube-proxy maintains network rules on nodes. These network rules allow
|
||||
network communication to your Pods from network sessions inside or outside
|
||||
of your cluster. -->
|
||||
kube-proxy 维护节点上的网络规则。这些网络规则允许从集群内部或外部的网络会话与 Pod 进行网络通信。
|
||||
|
||||
<!-- kube-proxy uses the operating system packet filtering layer if there is one
|
||||
and it's available. Otherwise, kube-proxy forwards the traffic itself. -->
|
||||
如果有 kube-proxy 可用，它将使用操作系统数据包过滤层。否则，kube-proxy 会转发流量本身。
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: kube-scheduler
|
||||
id: kube-scheduler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-scheduler/
|
||||
short_description: >
|
||||
主节点上的组件，该组件监视那些新创建的未指定运行节点的 Pod，并选择节点让 Pod 在上面运行。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- scheduler
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: kube-scheduler
|
||||
id: kube-scheduler
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kube-scheduler/
|
||||
short_description: >
|
||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Component on the master that watches newly created pods that have no node assigned, and selects a node for them to run on.
|
||||
-->
|
||||
|
||||
主节点上的组件，该组件监视那些新创建的未指定运行节点的 Pod，并选择节点让 Pod 在上面运行。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Factors taken into account for scheduling decisions include individual and collective resource requirements, hardware/software/policy constraints, affinity and anti-affinity specifications, data locality, inter-workload interference and deadlines.
|
||||
-->
|
||||
|
||||
调度决策考虑的因素包括单个 Pod 和 Pod 集合的资源需求、硬件/软件/策略约束、亲和性和反亲和性规范、数据位置、工作负载间的干扰和最后时限。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Kubeadm
|
||||
id: kubeadm
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kubeadm/
|
||||
short_description: >
|
||||
用来快速安装 Kubernetes 并搭建安全稳定的集群的工具。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kubeadm
|
||||
id: kubeadm
|
||||
date: 2018-04-12
|
||||
full_link: /docs/admin/kubeadm/
|
||||
short_description: >
|
||||
A tool for quickly installing Kubernetes and setting up a secure cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A tool for quickly installing Kubernetes and setting up a secure cluster.
|
||||
-->
|
||||
|
||||
用来快速安装 Kubernetes 并搭建安全稳定的集群的工具。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can use kubeadm to install both the control plane and the worker node components.
|
||||
-->
|
||||
|
||||
您可以使用 kubeadm 安装控制面和工作节点组件。
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Kubectl
|
||||
id: kubectl
|
||||
date: 2018-04-12
|
||||
full_link: /docs/user-guide/kubectl-overview/
|
||||
short_description: >
|
||||
kubectl 是用来和 Kubernetes API 服务器进行通信的命令行工具。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kubectl
|
||||
id: kubectl
|
||||
date: 2018-04-12
|
||||
full_link: /docs/user-guide/kubectl-overview/
|
||||
short_description: >
|
||||
A command line tool for communicating with a Kubernetes API server.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- tool
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A command line tool for communicating with a {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}} server.
|
||||
-->
|
||||
|
||||
kubectl 是用来和 {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}} 服务器进行通信的命令行工具。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can use kubectl to create, inspect, update, and delete Kubernetes objects.
|
||||
-->
|
||||
|
||||
您可以使用 kubectl 创建、检查、更新和删除 Kubernetes 对象。
|
||||
+40
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Kubelet
|
||||
id: kubelet
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kubelet
|
||||
short_description: >
|
||||
一个在集群中每个节点上运行的代理。它保证容器都运行在 Pod 中。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Kubelet
|
||||
id: kubelet
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/generated/kubelet
|
||||
short_description: >
|
||||
An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
|
||||
-->
|
||||
一个在集群中每个节点上运行的代理。它保证容器都运行在 Pod 中。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The kubelet takes a set of PodSpecs that are provided through various mechanisms and ensures that the containers described in those PodSpecs are running and healthy. The kubelet doesn’t manage containers which were not created by Kubernetes.
|
||||
-->
|
||||
|
||||
kubelet 接收一组通过各类机制提供给它的 PodSpecs，确保这些 PodSpecs 中描述的容器处于运行状态且健康。kubelet 不会管理不是由 Kubernetes 创建的容器。
|
||||
+47
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: Kubernetes API
|
||||
id: kubernetes-api
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/kubernetes-api/
|
||||
short_description: >
|
||||
Kubernetes API 是通过 RESTful 接口提供 Kubernetes 功能服务并负责集群状态存储的应用程序。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Kubernetes API
|
||||
id: kubernetes-api
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/kubernetes-api/
|
||||
short_description: >
|
||||
The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
|
||||
-->
|
||||
|
||||
Kubernetes API 是通过 RESTful 接口提供 Kubernetes 功能服务并负责集群状态存储的应用程序。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Kubernetes resources and "records of intent" are all stored as API objects, and modified via RESTful calls to the API. The API allows configuration to be managed in a declarative way. Users can interact with the Kubernetes API directly, or via tools like `kubectl`. The core Kubernetes API is flexible and can also be extended to support custom resources.
|
||||
-->
|
||||
|
||||
Kubernetes 资源和"意向记录"都是作为 API 对象储存的，并可以通过对 API 的 RESTful 调用进行修改。
|
||||
API 允许以声明方式管理配置。
|
||||
用户可以直接和 Kubernetes API 交互，也可以通过 `kubectl` 这样的工具进行交互。
|
||||
核心的 Kubernetes API 是很灵活的，可以扩展以支持定制资源。
|
||||
|
||||
Executable
+41
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 标签
|
||||
id: label
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/labels
|
||||
short_description: >
|
||||
用来为对象设置可标识的属性标记；这些标记对用户而言是有意义且重要的。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Label
|
||||
id: label
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/labels
|
||||
short_description: >
|
||||
Tags objects with identifying attributes that are meaningful and relevant to users.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
Tags objects with identifying attributes that are meaningful and relevant to users.
|
||||
-->
|
||||
|
||||
用来为对象设置可标识的属性标记；这些标记对用户而言是有意义且重要的。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Labels are key/value pairs that are attached to objects such as {{< glossary_tooltip text="Pods" term_id="pod" >}}. They are used to organize and to select subsets of objects.
|
||||
-->
|
||||
|
||||
标签是一些关联到 {{< glossary_tooltip text="Pods" term_id="pod" >}} 这类对象上的键值对。
|
||||
它们通常用来组织和选择对象子集。
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: LimitRange
|
||||
id: limitrange
|
||||
date: 2019-04-15
|
||||
full_link: /docs/concepts/policy/limit-range/
|
||||
short_description: >
|
||||
提供约束来限制命名空间中每个容器或 Pod 的资源消耗。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: LimitRange
|
||||
id: limitrange
|
||||
date: 2019-04-15
|
||||
full_link: /docs/concepts/policy/limit-range/
|
||||
short_description: >
|
||||
Provides constraints to limit resource consumption per Containers or Pods in a namespace.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Provides constraints to limit resource consumption per {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
|
||||
-->
|
||||
提供约束来限制命名空间中每个 {{< glossary_tooltip text="容器" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 的资源消耗。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
LimitRange limits the quantity of objects that can be created by type,
|
||||
as well as the amount of compute resources that may be requested/consumed by individual {{< glossary_tooltip text="Containers" term_id="container" >}} or {{< glossary_tooltip text="Pods" term_id="pod" >}} in a namespace.
|
||||
-->
|
||||
LimitRange 按照类型来限制命名空间中对象能够创建的数量，以及单个 {{< glossary_tooltip text="容器" term_id="container" >}} 或 {{< glossary_tooltip text="Pod" term_id="pod" >}} 可以请求/使用的计算资源量。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 日志
|
||||
id: logging
|
||||
date: 2019-04-04
|
||||
full_link: /docs/concepts/cluster-administration/logging/
|
||||
short_description: >
|
||||
日志是集群或应用程序记录的事件列表。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
日志是 {{< glossary_tooltip text="集群" term_id="cluster" >}} 或应用程序记录的事件列表。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Logging
|
||||
id: logging
|
||||
date: 2019-04-04
|
||||
full_link: /docs/concepts/cluster-administration/logging/
|
||||
short_description: >
|
||||
Logs are the list of events that are logged by cluster or application.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
- fundamental
|
||||
---
|
||||
Logs are the list of events that are logged by {{< glossary_tooltip text="cluster" term_id="cluster" >}} or application.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Application and systems logs can help you understand what is happening inside your cluster. The logs are particularly useful for debugging problems and monitoring cluster activity.
|
||||
-->
|
||||
|
||||
应用程序和系统日志可以帮助您了解集群内部发生的情况。日志对于调试问题和监视集群活动非常有用。
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 托管服务
|
||||
id: managed-service
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
由第三方供应商负责维护的一种软件产品。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Managed Service
|
||||
id: managed-service
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A software offering maintained by a third-party provider.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
-->
|
||||
|
||||
<!--
|
||||
A software offering maintained by a third-party provider.
|
||||
-->
|
||||
|
||||
由第三方供应商负责维护的一种软件产品。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Some examples of Managed Services are AWS EC2, Azure SQL Database, and GCP Pub/Sub, but they can be any software offering that can be used by an application. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by {{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}}.
|
||||
-->
|
||||
|
||||
托管服务的一些例子有 AWS EC2、Azure SQL 数据库和 GCP Pub/Sub 等，
|
||||
不过它们也可以是可以被某应用使用的任何软件交付件。
|
||||
[服务目录](/docs/concepts/service-catalog/)提供了一种方法用来列举、供应和绑定到
|
||||
{{< glossary_tooltip text="服务代理商" term_id="service-broker" >}}所提供的托管服务。
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 成员
|
||||
id: member
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
K8s 社区中持续活跃的贡献者。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Member
|
||||
id: member
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A continuously active contributor in the K8s community.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A continuously active {{< glossary_tooltip text="contributor" term_id="contributor" >}} in the K8s community.
|
||||
-->
|
||||
|
||||
K8s 社区中持续活跃的贡献者。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Members can have issues and PRs assigned to them and participate in {{< glossary_tooltip text="special interest groups (SIGs)" term_id="sig" >}} through GitHub teams. Pre-submit tests are automatically run for members' PRs. A member is expected to remain an active contributor to the community.
|
||||
-->
|
||||
|
||||
可以将问题单（issue）和 PR 指派给成员，成员也可以通过 GitHub 小组加入 {{< glossary_tooltip text="特别兴趣小组 (SIGs)" term_id="sig" >}}。针对成员所提交的 PR，系统自动运行提交前测试。成员应该是持续活跃的社区贡献者。
|
||||
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Minikube
|
||||
id: minikube
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/minikube/
|
||||
short_description: >
|
||||
Minikube 是用来在本地运行 Kubernetes 的一种工具。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- tool
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Minikube
|
||||
id: minikube
|
||||
date: 2018-04-12
|
||||
full_link: /docs/getting-started-guides/minikube/
|
||||
short_description: >
|
||||
A tool for running Kubernetes locally.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- tool
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A tool for running Kubernetes locally.
|
||||
-->
|
||||
|
||||
Minikube 是用来在本地运行 Kubernetes 的一种工具。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Minikube runs a single-node cluster inside a VM on your computer.
|
||||
-->
|
||||
|
||||
Minikube 在用户计算机上的一个虚拟机内运行单节点 Kubernetes 集群。
|
||||
+46
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: 静态 Pod
|
||||
id: 静态-pod
|
||||
date: 2019-08-06
|
||||
short_description: >
|
||||
API 服务器中的一个对象，用于跟踪 kubelet 上的静态容器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- 基本的
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Mirror Pod
|
||||
id: mirror-pod
|
||||
date: 2019-08-06
|
||||
short_description: >
|
||||
An object in the API server that tracks a static pod on a kubelet.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A {{< glossary_tooltip text="pod" term_id="pod" >}} object that a kubelet uses
|
||||
to represent a {{< glossary_tooltip text="static pod" term_id="static-pod" >}}
|
||||
-->
|
||||
kubelet 使用一个对象 {{< glossary_tooltip text="pod" term_id="pod" >}} 来代表 {{< glossary_tooltip text="static pod" term_id="static-pod" >}}
|
||||
|
||||
<!--more-->
|
||||
<!--更多-->
|
||||
|
||||
<!--
|
||||
When the kubelet finds a static pod in its configuration, it automatically tries to
|
||||
create a Pod object on the Kubernetes API server for it. This means that the pod
|
||||
will be visible on the API server, but cannot be controlled from there.
|
||||
|
||||
(For example, removing a mirror pod will not stop the kubelet daemon from running it).
|
||||
-->
|
||||
当 kubelet 在其配置中发现一个静态容器时，
|
||||
它会自动地尝试在 Kubernetes API 服务器上为它创建 Pod 对象。
|
||||
这意味着 pod 在 API 服务器上将是可见的，但不能在其上进行控制。
|
||||
|
||||
（例如，删除静态 pod 将不会停止 kubelet 守护程序的运行）。
|
||||
@@ -1,4 +1,18 @@
|
||||
---
|
||||
title: 名称
|
||||
id: name
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/names
|
||||
short_description: >
|
||||
客户端提供的字符串，用来指代资源 URL 中的对象，如 `/api/v1/pods/some-name`。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Name
|
||||
id: name
|
||||
date: 2018-04-12
|
||||
@@ -10,6 +24,8 @@ aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
|
||||
-->
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 命名空间
|
||||
id: namespace
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/namespaces
|
||||
short_description: >
|
||||
命名空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Namespace
|
||||
id: namespace
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/namespaces
|
||||
short_description: >
|
||||
An abstraction used by Kubernetes to support multiple virtual clusters on the same physical cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An abstraction used by Kubernetes to support multiple virtual clusters on the same physical {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
|
||||
-->
|
||||
|
||||
命名空间是 Kubernetes 为了在同一物理集群上支持多个虚拟集群而使用的一种抽象。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces.
|
||||
-->
|
||||
|
||||
命名空间用来组织集群中对象，并为集群资源划分提供了一种方法。同一命名空间内的资源名称必须唯一，但跨命名空间时不作要求。
|
||||
+44
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: 网络策略
|
||||
id: network-policy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/network-policies/
|
||||
short_description: >
|
||||
网络策略是一种规范，规定了允许 Pod 组之间、Pod 与其他网络端点之间以怎样的方式进行通信。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Network Policy
|
||||
id: network-policy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/services-networking/network-policies/
|
||||
short_description: >
|
||||
A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- networking
|
||||
- architecture
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
|
||||
-->
|
||||
|
||||
网络策略是一种规范，规定了允许 Pod 组之间、Pod 与其他网络端点之间以怎样的方式进行通信。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Network Policies help you declaratively configure which Pods are allowed to connect to each other, which namespaces are allowed to communicate, and more specifically which port numbers to enforce each policy on. `NetworkPolicy` resources use labels to select Pods and define rules which specify what traffic is allowed to the selected Pods. Network Policies are implemented by a supported network plugin provided by a network provider. Be aware that creating a network resource without a controller to implement it will have no effect.
|
||||
-->
|
||||
|
||||
网络策略帮助您声明式地配置允许哪些 Pod 之间接、哪些命名空间之间允许进行通信，并具体配置了哪些端口号来执行各个策略。`NetworkPolicy` 资源使用标签来选择 Pod，并定义了所选 Pod 可以接受什么样的流量。网络策略由网络提供商提供的并被 Kubernetes 支持的网络插件实现。请注意，当没有控制器实现网络资源时，创建网络资源将不会生效。
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 节点
|
||||
id: node
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/architecture/nodes/
|
||||
short_description: >
|
||||
Kubernetes 中的工作机器称作节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Node
|
||||
id: node
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/architecture/nodes/
|
||||
short_description: >
|
||||
A node is a worker machine in Kubernetes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
-->
|
||||
|
||||
<!--
|
||||
A node is a worker machine in Kubernetes.
|
||||
-->
|
||||
|
||||
Kubernetes 中的工作机器称作节点。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A worker machine may be a VM or physical machine, depending on the cluster. It has the {{< glossary_tooltip text="Services" term_id="service" >}} necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} and is managed by the master components. The {{< glossary_tooltip text="Services" term_id="service" >}} on a node include Docker, kubelet and kube-proxy.
|
||||
-->
|
||||
|
||||
工作机器可以是虚拟机也可以是物理机，取决于集群的配置。
|
||||
其上部署了运行 {{< glossary_tooltip text="Pods" term_id="pod" >}} 所必需的{{< glossary_tooltip text="服务" term_id="service" >}}，
|
||||
并由主控组件来管理。
|
||||
节点上的{{< glossary_tooltip text="服务" term_id="service" >}}包括 Docker、kubelet 和 kube-proxy。
|
||||
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Operator 模式
|
||||
id: operator-pattern
|
||||
date: 2019-05-21
|
||||
full_link: /docs/concepts/extend-kubernetes/operator/
|
||||
short_description: >
|
||||
一种用于管理自定义资源的专用控制器
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
[operator 模式](/docs/concepts/extend-kubernetes/operator/) 是一个系统设计, 将 {{< glossary_tooltip term_id="controller" >}} 关联到一个或多个自定义资源。
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Operator pattern
|
||||
id: operator-pattern
|
||||
date: 2019-05-21
|
||||
full_link: /docs/concepts/extend-kubernetes/operator/
|
||||
short_description: >
|
||||
A specialized controller used to manage a custom resource
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- architecture
|
||||
---
|
||||
The [operator pattern](/docs/concepts/extend-kubernetes/operator/) is a system
|
||||
design that links a {{< glossary_tooltip term_id="controller" >}} to one or more custom
|
||||
resources.
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
You can extend Kubernetes by adding controllers to your cluster, beyond the built-in
|
||||
controllers that come as part of Kubernetes itself.
|
||||
|
||||
If a running application acts as a controller and has API access to carry out tasks
|
||||
against a custom resource that's defined in the control plane, that's an example of
|
||||
the Operator pattern.
|
||||
-->
|
||||
|
||||
除了使用作为 Kubernetes 自身一部分的内置控制器之外，您还可以通过将控制器添加到集群中来扩展 Kubernetes。
|
||||
|
||||
如果正在运行的应用程序能够充当控制器并通过 API 访问的方式来执行任务操控那些在控制平面中定义的自定义资源，这就是一个 operator 模式的示例。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: 持久卷申领
|
||||
id: persistent-volume-claim
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
声明在持久卷中定义的存储资源，以便可以将其挂载为容器中的卷。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Persistent Volume Claim
|
||||
id: persistent-volume-claim
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
-->
|
||||
|
||||
<!--
|
||||
Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
|
||||
-->
|
||||
申领持久卷中定义的存储资源，以便可以将其挂载为容器中的卷。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Specifies the amount of storage, how the storage will be accessed (read-only, read-write and/or exclusive) and how it is reclaimed (retained, recycled or deleted). Details of the storage itself are in the PersistentVolume specification.
|
||||
-->
|
||||
指定存储的数量，如何访问存储（只读、读写或独占）以及如何回收存储（保留、回收或删除）。存储本身的详细信息在 PersistentVolume 规范中。
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: 持久卷
|
||||
id: persistent-volume
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Persistent Volume
|
||||
id: persistent-volume
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/storage/persistent-volumes/
|
||||
short_description: >
|
||||
An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- storage
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that represents a piece of storage in the cluster. Available as a general, pluggable resource that persists beyond the lifecycle of any individual {{< glossary_tooltip text="Pod" term_id="pod" >}}.
|
||||
-->
|
||||
|
||||
持久卷是代表集群中一块存储空间的 API 对象。 它是通用的、可插拔的、并且不受单个 Pod 生命周期约束的持久化资源。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
PersistentVolumes (PVs) provide an API that abstracts details of how storage is provided from how it is consumed.
|
||||
PVs are used directly in scenarios where storage can be created ahead of time (static provisioning).
|
||||
For scenarios that require on-demand storage (dynamic provisioning), PersistentVolumeClaims (PVCs) are used instead.
|
||||
-->
|
||||
|
||||
持久卷（PersistentVolumes，PV）提供了一个 API，该 API 对存储的供应方式细节进行抽象，令其与使用方式相分离。
|
||||
在提前创建存储（静态供应）的场景中，PV 可以直接使用。
|
||||
在按需提供存储（动态供应）的场景中，需要使用 PersistentVolumeClaims (PVCs)。
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 平台开发者
|
||||
id: platform-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
定制 Kubernetes 平台以满足自己的项目需求的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Platform Developer
|
||||
id: platform-developer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who customizes the Kubernetes platform to fit the needs of their project.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- user-type
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who customizes the Kubernetes platform to fit the needs of their project.
|
||||
-->
|
||||
|
||||
定制 Kubernetes 平台以满足自己的项目需求的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A platform developer may, for example, use [Custom Resources](/docs/concepts/api-extension/custom-resources/) or [Extend the Kubernetes API with the aggregation layer](/docs/concepts/api-extension/apiserver-aggregation/) to add functionality to their instance of Kubernetes, specifically for their application. Some Platform Developers are also {{< glossary_tooltip text="contributors" term_id="contributor" >}} and develop extensions which are contributed to the Kubernetes community. Others develop closed-source commercial or site-specific extensions.
|
||||
-->
|
||||
|
||||
例如，平台开发人员可以使用[定制资源](/docs/concepts/api-extension/custom-resources/)或[使用汇聚层扩展 Kubernetes API](/docs/concepts/api-extension/apiserver-aggregation/) 来为其 Kubernetes 实例增加功能，特别是为其应用程序添加功能。一些平台开发人员也是 Kubrenetes {{< glossary_tooltip text="贡献者" term_id="contributor" >}}，他们会开发贡献给 Kubernetes 社区的扩展；另一些则开发封闭源代码的商业扩展或用于特定功能的扩展。
|
||||
|
||||
@@ -0,0 +1,40 @@
|
||||
---
|
||||
id: pod-disruption-budget
|
||||
title: Pod Disruption Budget
|
||||
full-link: /docs/concepts/workloads/pods/disruptions/
|
||||
date: 2019-02-12
|
||||
short_description: >
|
||||
Pod Disruption Budget 是这样一种对象：它保证在主动中断（ voluntary disruptions）时，多实例应用的 {{< glossary_tooltip text="Pod" term_id="pod" >}} 不会少于一定的数量。
|
||||
|
||||
aka:
|
||||
- PDB
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
id: pod-disruption-budget
|
||||
title: Pod Disruption Budget
|
||||
full-link: /docs/concepts/workloads/pods/disruptions/
|
||||
date: 2019-02-12
|
||||
short_description: >
|
||||
An object that limits the number of {{< glossary_tooltip text="Pods" term_id="pod" >}} of a replicated application, that are down simultaneously from voluntary disruptions.
|
||||
|
||||
aka:
|
||||
- PDB
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A [Pod Disruption Budget](/docs/concepts/workloads/pods/disruptions/) allows an application owner to create an object for a replicated application, that ensures a certain number or percentage of Pods with an assigned label will not be voluntarily evicted at any point in time. PDBs cannot prevent an involuntary disruption, but will count against the budget.
|
||||
-->
|
||||
[Pod Disruption Budget](/docs/concepts/workloads/pods/disruptions/) 使应用所有者能够为多实例应用创建一个对象，来确保一定数量的具有指定标签的 Pod 在任何时候都不会被主动驱逐。 PDB 无法防止非主动的中断，但是会计入预算（budget）。
|
||||
@@ -0,0 +1,40 @@
|
||||
<!--
|
||||
---
|
||||
title: Pod Lifecycle
|
||||
id: pod-lifecycle
|
||||
date: 2019-02-17
|
||||
full-link: /docs/concepts/workloads/pods/pod-lifecycle/
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- fundamental
|
||||
short_description: >
|
||||
A high-level summary of what phase the Pod is in within its lifecyle.
|
||||
|
||||
---
|
||||
A high-level summary of what phase the Pod is in within its lifecyle.
|
||||
|
||||
<!--more-->
|
||||
-->
|
||||
---
|
||||
title: Pod 生命周期
|
||||
id: pod-lifecycle
|
||||
date: 2019-02-17
|
||||
full-link: /docs/concepts/workloads/pods/pod-lifecycle/
|
||||
related:
|
||||
- pod
|
||||
- container
|
||||
tags:
|
||||
- fundamental
|
||||
short_description: >
|
||||
关于 Pod 在其生命周期中处于哪个阶段的更高层次概述。
|
||||
|
||||
---
|
||||
关于 Pod 在其生命周期中处于哪个阶段的更高层次概述。
|
||||
|
||||
<!--more-->
|
||||
<!--
|
||||
The [Pod Lifecycle](/docs/concepts/workloads/pods/pod-lifecycle/) is a high level summary of where a Pod is in its lifecyle. A Pod’s `status` field is a [PodStatus](/docs/reference/generated/kubernetes-api/v1.13/#podstatus-v1-core) object, which has a `phase` field that displays one of the following phases: Running, Pending, Succeeded, Failed, Unknown, Completed, or CrashLoopBackOff.
|
||||
-->
|
||||
[Pod 生命周期](/docs/concepts/workloads/pods/pod-lifecycle/) 是关于 Pod 在其生命周期中处于哪个阶段的更高层次概述。Pod 的`status` 字段是 [PodStatus](/docs/reference/generated/kubernetes-api/v1.13/#podstatus-v1-core) 对象, 该对象的 `phase` 字段包含了下面的状态: Running、Pending、Succeeded、Failed、Unknown、Completed 或 CrashLoopBackOff。
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: Pod 优先级
|
||||
id: pod-priority
|
||||
date: 2019-01-31
|
||||
full_link: /docs/concepts/configuration/pod-priority-preemption/#pod-priority
|
||||
short_description: >
|
||||
Pod 优先级表示一个 Pod 相对于其他 Pod 的重要性。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Pod Priority
|
||||
id: pod-priority
|
||||
date: 2019-01-31
|
||||
full_link: /docs/concepts/configuration/pod-priority-preemption/#pod-priority
|
||||
short_description: >
|
||||
Pod Priority indicates the importance of a Pod relative to other Pods.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Pod Priority indicates the importance of a Pod relative to other Pods.
|
||||
-->
|
||||
Pod 优先级表示一个 Pod 相对于其他 Pod 的重要性。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
[Pod Priority](/docs/concepts/configuration/pod-priority-preemption/#pod-priority) gives the ability to set scheduling priority of a Pod to be higher and lower than other Pods — an important feature for production clusters workload.
|
||||
-->
|
||||
[Pod 优先级](/docs/concepts/configuration/pod-priority-preemption/#pod-priority) 允许为一个 Pod 设置高于或低于其他 Pod 的优先级 -- 这对于生产集群工作负载而言是一个重要的特性。
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Pod 安全策略
|
||||
id: pod-security-policy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/policy/pod-security-policy/
|
||||
short_description: >
|
||||
为 Pod 的创建和更新操作启用细粒度的授权。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Pod Security Policy
|
||||
id: pod-security-policy
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/policy/pod-security-policy/
|
||||
short_description: >
|
||||
Enables fine-grained authorization of pod creation and updates.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Enables fine-grained authorization of {{< glossary_tooltip term_id="pod" >}} creation and updates.
|
||||
-->
|
||||
|
||||
为 Pod 的创建和更新操作启用细粒度的授权。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A cluster-level resource that controls security sensitive aspects of the Pod specification. The `PodSecurityPolicy` objects define a set of conditions that a Pod must run with in order to be accepted into the system, as well as defaults for the related fields. Pod Security Policy control is implemented as an optional admission controller.
|
||||
-->
|
||||
|
||||
Pod 安全策略是集群级别的资源，它控制着 Pod 规约中的安全性敏感的内容。
|
||||
`PodSecurityPolicy`对象定义了一组条件以及相关字段的默认值，Pod 运行时必须满足这些条件。Pod 安全策略控制实现上体现为一个可选的准入控制器。
|
||||
|
||||
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Pod
|
||||
id: pod
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/pods/pod-overview/
|
||||
short_description: >
|
||||
Pod 是 Kubernetes 的原子对象。Pod 表示您的集群上一组正在运行的容器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Pod
|
||||
id: pod
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/pods/pod-overview/
|
||||
short_description: >
|
||||
The smallest and simplest Kubernetes object. A Pod represents a set of running containers on your cluster.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The smallest and simplest Kubernetes object. A Pod represents a set of running {{< glossary_tooltip text="containers" term_id="container" >}} on your cluster.
|
||||
-->
|
||||
|
||||
Pod 是 Kubernetes 的原子对象。Pod 表示您的集群上一组正在运行的{{< glossary_tooltip text="容器" term_id="container" >}}。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
A Pod is typically set up to run a single primary container. It can also run optional sidecar containers that add supplementary features like logging. Pods are commonly managed by a {{< glossary_tooltip term_id="deployment" >}}.
|
||||
-->
|
||||
|
||||
通常创建 Pod 是为了运行单个主容器。Pod 还可以运行可选的挂斗（sidecar）容器，以添加诸如日志记录之类的补充特性。通常用 {{< glossary_tooltip term_id="deployment" >}} 来管理 Pod。
|
||||
+40
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: PodPreset
|
||||
id: podpreset
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
PodPreset 是一种 API 对象，在创建 Pod 时将诸如 Secret、卷挂载和环境变量之类的信息注入到该 Pod 中。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: PodPreset
|
||||
id: podpreset
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
An API object that injects information such as secrets, volume mounts, and environment variables into pods at creation time.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An API object that injects information such as secrets, volume mounts, and environment variables into pods at creation time.
|
||||
-->
|
||||
PodPreset 是一种 API 对象，在创建 Pod 时将诸如 Secret、卷挂载和环境变量之类的信息注入到该 Pod 中。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
This object chooses the pods to inject information into using standard selectors. This allows the podspec definitions to be nonspecific, decoupling the podspec from environment specific configuration.
|
||||
-->
|
||||
|
||||
此 API 对象使用标准选择器选择 Pod 并向其中注入信息。这允许 podspec 定义是非特定的，从而将 podspec 与环境特定的配置解耦。
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: 抢占
|
||||
id: preemption
|
||||
date: 2019-01-31
|
||||
full_link: /docs/concepts/configuration/pod-priority-preemption/#preemption
|
||||
short_description: >
|
||||
Kubernetes 中的抢占逻辑通过驱逐节点上的低优先级 Pod 来帮助挂起的 Pod 找到合适的节点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Preemption
|
||||
id: preemption
|
||||
date: 2019-01-31
|
||||
full_link: /docs/concepts/configuration/pod-priority-preemption/#preemption
|
||||
short_description: >
|
||||
Preemption logic in Kubernetes helps a pending Pod to find a suitable Node by evicting low priority Pods existing on that Node.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- operation
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
Preemption logic in Kubernetes helps a pending Pod to find a suitable Node by evicting low priority Pods existing on that Node.
|
||||
-->
|
||||
Kubernetes 中的抢占逻辑通过驱逐节点上的低优先级 Pod 来帮助挂起的 Pod 找到合适的节点。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
If a Pod cannot be scheduled, the scheduler tries to [preempt](/docs/concepts/configuration/pod-priority-preemption/#preemption) lower priority Pods to make scheduling of the pending Pod possible.
|
||||
-->
|
||||
如果一个 Pod 无法调度，调度器会尝试[抢占](/docs/concepts/configuration/pod-priority-preemption/#preemption)较低优先级的 Pod，以使得挂起的 Pod 可能被调度。
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: QoS 类
|
||||
id: qos-class
|
||||
date: 2019-04-15
|
||||
full_link:
|
||||
short_description: >
|
||||
QoS 类（Quality of Service Class）为 Kubernetes 提供了一种将集群中的 Pod 分为几个类并做出有关调度和驱逐决策的方法。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: QoS Class
|
||||
id: qos-class
|
||||
date: 2019-04-15
|
||||
full_link:
|
||||
short_description: >
|
||||
QoS Class (Quality of Service Class) provides a way for Kubernetes to classify pods within the cluster into several classes and make decisions about scheduling and eviction.
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- fundamental
|
||||
- architecture
|
||||
related:
|
||||
- pod
|
||||
|
||||
---
|
||||
-->
|
||||
|
||||
QoS Class（Quality of Service Class）为 Kubernetes 提供了一种将集群中的 Pod 分为几个类型并做出有关调度和驱逐决策的方法。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
QoS Class of a Pod is set at creation time based on its compute resources requests and limits settings. QoS classes are used to make decisions about Pods scheduling and eviction.
|
||||
Kubernetes can assign one of the following QoS classes to a Pod: `Guaranteed`, `Burstable` or `BestEffort`.
|
||||
-->
|
||||
Pod 的 QoS 类是基于 Pod 在创建时配置的计算资源请求和限制。QoS 类用于制定有关 Pod 调度和逐出的决策。
|
||||
Kubernetes 可以为 Pod 分配以下 QoS 类：`Guaranteed`，`Burstable` 或者 `BestEffort`。
|
||||
@@ -0,0 +1,60 @@
|
||||
---
|
||||
title: 数量
|
||||
id: quantity
|
||||
date: 2018-08-07
|
||||
full_link:
|
||||
short_description: >
|
||||
使用 SI 后缀的小数或大数的整数表示。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Quantity
|
||||
id: quantity
|
||||
date: 2018-08-07
|
||||
full_link:
|
||||
short_description: >
|
||||
A whole-number representation of small or large numbers using SI suffixes.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
|
||||
<!--more-->
|
||||
|
||||
数量是使用紧凑的整数表示法的小数或大数的表示，并带有国际计量单位制（SI）后缀。
|
||||
小数用 milli 单位表示，而大数用 kilo、mega 或 giga 单位表示。
|
||||
|
||||
例如，数字 `1.5` 表示为`1500m`，
|
||||
而数字`1000`表示为`1k`，`1000000`表示为`1M`。
|
||||
您还可以指定二进制表示法后缀; 数字 2048 可以写成`2Ki`。
|
||||
|
||||
公认的十进制（10的幂）单位是 `m`（milli）、`k`（kilo，
|
||||
有意小写）、`M`（mega），`G`（giga）、`T`（terra）、`P`（peta）、
|
||||
`E`（exa）。
|
||||
|
||||
公认的二进制（2的幂）单位是 `Ki` (kibi)、 `Mi` (mebi)、`Gi` (gibi)、
|
||||
`Ti` (tebi)、 `Pi` (pebi)、 `Ei` (exbi)。
|
||||
|
||||
<!--
|
||||
Quantities are representations of small or large numbers using a compact,
|
||||
whole-number notation with SI suffixes. Fractional numbers are represented
|
||||
using milli units, while large numbers can be represented using kilo,
|
||||
mega, or giga units.
|
||||
|
||||
For instance, the number `1.5` is represented as `1500m`, while the number `1000`
|
||||
can be represented as `1k`, and `1000000` as `1M`. You can also specify
|
||||
binary-notation suffixes; the number 2048 can be written as `2Ki`.
|
||||
|
||||
The accepted decimal (power-of-10) units are `m` (milli), `k` (kilo,
|
||||
intentionally lowercase), `M` (mega), `G` (giga), `T` (terra), `P` (peta),
|
||||
`E` (exa).
|
||||
|
||||
The accepted binary (power-of-2) units are `Ki` (kibi), `Mi` (mebi), `Gi` (gibi),
|
||||
`Ti` (tebi), `Pi` (pebi), `Ei` (exbi).
|
||||
-->
|
||||
Executable
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: RBAC（基于角色的访问控制）
|
||||
id: rbac
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/access-authn-authz/rbac/
|
||||
short_description: >
|
||||
管理授权决策，允许管理员通过 Kubernetes API 动态配置访问策略。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: RBAC (Role-Based Access Control)
|
||||
id: rbac
|
||||
date: 2018-04-12
|
||||
full_link: /docs/reference/access-authn-authz/rbac/
|
||||
short_description: >
|
||||
Manages authorization decisions, allowing admins to dynamically configure access policies through the Kubernetes API.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Manages authorization decisions, allowing admins to dynamically configure access policies through the {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}}.
|
||||
-->
|
||||
管理授权决策，允许管理员通过 {{< glossary_tooltip text="Kubernetes API" term_id="kubernetes-api" >}} 动态配置访问策略。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
RBAC utilizes *roles*, which contain permission rules, and *role bindings*, which grant the permissions defined in a role to a set of users.
|
||||
-->
|
||||
RBAC 使用 *角色* (包含权限规则)和 *角色绑定* (将角色中定义的权限授予一组用户)。
|
||||
|
||||
|
||||
+45
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: ReplicaSet
|
||||
id: replica-set
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/replicaset/
|
||||
short_description: >
|
||||
ReplicaSet 是下一代副本控制器。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: ReplicaSet
|
||||
id: replica-set
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/workloads/controllers/replicaset/
|
||||
short_description: >
|
||||
ReplicaSet is the next-generation Replication Controller.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
- workload
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
ReplicaSet is the next-generation Replication Controller.
|
||||
-->
|
||||
|
||||
ReplicaSet 是下一代副本控制器。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
ReplicaSet, like ReplicationController, ensures that a specified number of pods replicas are running at one time. ReplicaSet supports the new set-based selector requirements as described in the labels user guide, whereas a Replication Controller only supports equality-based selector requirements.
|
||||
-->
|
||||
|
||||
ReplicaSet 就像 ReplicationController 那样，确保一次运行指定数量的 Pod 副本。ReplicaSet 支持新的基于集合的选择器需求（在标签的用户指南中有相关描述），而副本控制器只支持基于等值的选择器需求。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: Replication Controller
|
||||
id: replication-controller
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Replication Controller 是 Kubernetes 的一种服务，用来确保给定个数的 Pod 一直处于运行状态。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
- core-object
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Replication Controller
|
||||
id: replication-controller
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
Kubernetes service that ensures a specific number of instances of a pod are always running.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- workload
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Kubernetes service that ensures a specific number of instances of a pod are always running.
|
||||
-->
|
||||
|
||||
Replication Controller 是 Kubernetes 的一种服务，用来确保给定个数的 Pod 一直处于运行状态。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Will automatically add or remove running instances of a pod, based on a set value for that pod. Allows the pod to return to the defined number of instances if pods are deleted or if too many are started by mistake.
|
||||
-->
|
||||
|
||||
Replication Controller 会基于设定值自动增删 Pod 的实例。如果 Pod 被误删除或者启动实例过多，Replication Controller 允许 Pod 的实例个数恢复到设定值。
|
||||
+47
@@ -0,0 +1,47 @@
|
||||
---
|
||||
title: 资源配额
|
||||
id: resource-quota
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/policy/resource-quotas/
|
||||
short_description: >
|
||||
资源配额提供了限制每个命名空间的资源消耗总和的约束。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- architecture
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Resource Quotas
|
||||
id: resource-quota
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/policy/resource-quotas/
|
||||
short_description: >
|
||||
Provides constraints that limit aggregate resource consumption per namespace.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- operation
|
||||
- architecture
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Provides constraints that limit aggregate resource consumption per {{< glossary_tooltip term_id="namespace" >}}.
|
||||
-->
|
||||
|
||||
资源配额提供了限制每个 {{< glossary_tooltip text="命名空间" term_id="namespace">}} 的资源消耗总和的约束。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Limits the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.
|
||||
-->
|
||||
|
||||
限制了命名空间中每种对象可以创建的数量，也限制了项目中可被资源对象利用的计算资源总数。
|
||||
|
||||
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: 评审者
|
||||
id: reviewer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
评审者是负责评审项目的某部分代码以便提高代码质量和正确性的人。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Reviewer
|
||||
id: reviewer
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
A person who reviews code for quality and correctness on some part of the project.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- community
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
A person who reviews code for quality and correctness on some part of the project.
|
||||
-->
|
||||
|
||||
评审者是负责评审项目的某部分代码以便提高代码质量和正确性的人。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Reviewers are knowledgeable about both the codebase and software engineering principles. Reviewer status is scoped to a part of the codebase.
|
||||
-->
|
||||
|
||||
评审者既要了解代码库又要了解软件工程规范。评审者状态是基于代码库的组成部分来设定的。
|
||||
Executable
+45
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Secret
|
||||
id: secret
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/configuration/secret/
|
||||
short_description: >
|
||||
Secret 用于存储敏感信息，如密码、OAuth 令牌和 SSH 密钥。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- security
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Secret
|
||||
id: secret
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/configuration/secret/
|
||||
short_description: >
|
||||
Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- core-object
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
|
||||
-->
|
||||
|
||||
Secret 用于存储敏感信息，如密码、OAuth 令牌和 SSH 密钥。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Allows for more control over how sensitive information is used and reduces the risk of accidental exposure, including [encryption](/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted) at rest. A {{< glossary_tooltip text="Pod" term_id="pod" >}} references the secret as a file in a volume mount or by the kubelet pulling images for a pod. Secrets are great for confidential data and [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) for non-confidential data.
|
||||
-->
|
||||
|
||||
Secret 允许用户对如何使用敏感信息进行更多的控制，并减少信息意外暴露的风险，包括静态[加密](/docs/tasks/administer-cluster/encrypt-data/#ensure-all-secrets-are-encrypted)。
|
||||
{{< glossary_tooltip text="Pod" term_id="pod" >}} 通过挂载卷中的文件的方式引用 Secret，或者通过 kubelet 为 pod 拉取镜像时引用。
|
||||
Secret 非常适合机密数据使用，而 [ConfigMaps](/docs/tasks/configure-pod-container/configure-pod-configmap/) 适用于非机密数据。
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 安全上下文（Security Context）
|
||||
id: security-context
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/security-context/
|
||||
short_description: >
|
||||
securityContext 字段定义 Pod 或容器的特权和访问控制设置，包括运行时 UID 和 GID。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Security Context
|
||||
id: security-context
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/security-context/
|
||||
short_description: >
|
||||
The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- security
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
The securityContext field defines privilege and access control settings for a Pod or Container, including the runtime UID and GID.
|
||||
-->
|
||||
securityContext 字段定义 Pod 或容器的特权和访问控制设置，包括运行时 UID 和 GID。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
The securityContext field in a {{< glossary_tooltip term_id="pod" >}} (applying to all containers) or container is used to set the user (runAsUser) and group (fsGroup), capabilities, privilege settings, and security policies (SELinux/AppArmor/Seccomp) that container processes use.
|
||||
-->
|
||||
{{< glossary_tooltip term_id="pod" >}} 或者容器中的 securityContext 字段（应用于所有容器）用于设置容器进程使用的用户（runAsUser）和组 （fsGroup）、权能字、特权设置和安全策略（SELinux/AppArmor/Seccomp）。
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 选择算符
|
||||
id: selector
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/labels/
|
||||
short_description: >
|
||||
选择算符允许用户通过标签对一组资源对象进行筛选过滤。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Selector
|
||||
id: selector
|
||||
date: 2018-04-12
|
||||
full_link: /docs/concepts/overview/working-with-objects/labels/
|
||||
short_description: >
|
||||
Allows users to filter a list of resources based on labels.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Allows users to filter a list of resources based on labels.
|
||||
-->
|
||||
|
||||
选择算符允许用户通过标签对一组资源对象进行筛选过滤。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
Selectors are applied when querying lists of resources to filter them by {{< glossary_tooltip text="Labels" term_id="label" >}}.
|
||||
-->
|
||||
|
||||
在查询资源列表时，选择算符可以通过 {{< glossary_tooltip text="标签" term_id="label" >}} 对资源进行过滤筛选。
|
||||
|
||||
+43
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 服务账户
|
||||
id: service-account
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/configure-service-account/
|
||||
short_description: >
|
||||
为在 Pod 中运行的进程提供标识。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Service Account
|
||||
id: service-account
|
||||
date: 2018-04-12
|
||||
full_link: /docs/tasks/configure-pod-container/configure-service-account/
|
||||
short_description: >
|
||||
Provides an identity for processes that run in a Pod.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- fundamental
|
||||
- core-object
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
Provides an identity for processes that run in a {{< glossary_tooltip text="Pod" term_id="pod" >}}.
|
||||
-->
|
||||
为在 {{< glossary_tooltip text="Pod" term_id="pod" >}} 中运行的进程提供标识。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
When processes inside Pods access the cluster, they are authenticated by the API server as a particular service account, for example, `default`. When you create a Pod, if you do not specify a service account, it is automatically assigned the default service account in the same namespace {{< glossary_tooltip text="Namespace" term_id="namespace" >}}.
|
||||
-->
|
||||
当 Pod 中的进程访问集群时，API 服务器将它们作为特定的服务帐户进行身份验证，例如 `default`。当您创建 Pod 时，如果您没有指定服务帐户，它将在相同的命名空间 {{< glossary_tooltip text="命名空间" term_id="namespace" >}} 中自动分配 default 服务账户。
|
||||
|
||||
|
||||
+42
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: 服务代理（Service Broker）
|
||||
id: service-broker
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
由第三方提供并维护的一组托管服务的访问端点。
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
title: Service Broker
|
||||
id: service-broker
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
An endpoint for a set of Managed Services offered and maintained by a third-party.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
-->
|
||||
|
||||
<!--
|
||||
An endpoint for a set of {{< glossary_tooltip text="Managed Service" term_id="managed-service">}} offered and maintained by a third-party.
|
||||
-->
|
||||
|
||||
由第三方提供并维护的一组{{< glossary_tooltip text="托管服务" term_id="managed-service">}} 的访问端点。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
{{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}} implement the [Open Service Broker API spec](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md) and provide a standard interface for applications to use their Managed Services. [Service Catalog](/docs/concepts/service-catalog/) provides a way to list, provision, and bind with Managed Services offered by Service Brokers.
|
||||
-->
|
||||
|
||||
{{< glossary_tooltip text="服务代理" term_id="service-broker">}}会实现
|
||||
[开放服务代理 API 规范](https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md)
|
||||
并为应用提供使用其托管服务的标准接口。
|
||||
[服务目录（Service Catalog）](/docs/concepts/service-catalog/)则提供一种方法，用来列举、供应和绑定服务代理商所提供的托管服务。
|
||||
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 服务目录
|
||||
id: service-catalog
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
服务目录是一种扩展 API，它能让 Kubernetes 集群中运行的应用易于使用外部托管的软件服务，例如云供应商提供的数据仓库服务。
|
||||
|
||||
An extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
|
||||
<!--
|
||||
---
|
||||
title: Service Catalog
|
||||
id: service-catalog
|
||||
date: 2018-04-12
|
||||
full_link:
|
||||
short_description: >
|
||||
An extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
|
||||
|
||||
aka:
|
||||
tags:
|
||||
- extension
|
||||
---
|
||||
-->
|
||||
|
||||
<!--
|
||||
An extension API that enables applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
|
||||
-->
|
||||
|
||||
服务目录（Service Catalog）是一种扩展 API，它能让 Kubernetes 集群中运行的应用易于使用外部托管的的软件服务，例如云供应商提供的数据仓库服务。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
It provides a way to list, provision, and bind with external {{< glossary_tooltip text="Managed Services" term_id="managed-service" >}} from {{< glossary_tooltip text="Service Brokers" term_id="service-broker" >}} without needing detailed knowledge about how those services are created or managed.
|
||||
-->
|
||||
|
||||
服务目录可以检索、供应、和绑定由 {{< glossary_tooltip text="服务代理人（Service Brokers）" term_id="service-broker" >}} 提供的外部 {{< glossary_tooltip text="托管服务" term_id="managed-service" >}}，而无需知道那些服务具体是怎样创建和托管的。
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user