From 67a570cd0b0cc84bcd5fabed4bd5cd65f3c0c77c Mon Sep 17 00:00:00 2001
From: Michael
Объекты этой страницы ссылаются на сторонние продукты или проекты, реализующие функциональность, которая требуется Kubernetes. Авторы Kubernetes не несут ответственность за эти сторонние продукты или проекты. Подробнее читайте в инструкциях по сайту CNCF.
Перед тем, как предлагать изменения, которые добавят новую стороннюю ссылку, необходимо прочитать руководство по контенту.
""" + +[ui_search_placeholder] +other = "Поиск" [version_check_mustbe] other = "Ваш сервер Kubernetes должен быть версии " @@ -45,157 +267,11 @@ other = "Ваш сервер Kubernetes должен быть версии ил [version_check_tocheck] other = "Чтобы проверить версию, введите " -[caution] -other = "Внимание:" - -[note] -other = "Заметка:" +[version_menu] +other = "Версии" [warning] other = "Предупреждение:" -[main_read_about] -other = "Прочитать о" - -[main_read_more] -other = "Прочитать больше" - -[main_github_invite] -other = "Хотите взломать ядро кодовой базы Kubernetes?" - -[main_github_view_on] -other = "Посмотреть на GitHub" - -[main_github_create_an_issue] -other = "Сообщить о проблеме" - -[main_community_explore] -other = "Познакомиться с сообществом" - -[main_kubernetes_features] -other = "Возможности Kubernetes" - -[main_cncf_project] -other = """Мы являемся проектом CNCF""" - -[main_kubeweekly_baseline] -other = "Интересуетесь последними новостями Kubernetes? Зарегистрируйтесь в KubeWeekly." - -[main_kubernetes_past_link] -other = "Посмотреть последние новости" - -[main_kubeweekly_signup] -other = "Подписаться" - -[main_contribute] -other = "Помочь проекту" - -[main_edit_this_page] -other = "Редактировать эту страницу" - -[main_page_history] -other ="История страницы" - -[main_page_last_modified_on] -other = "Последний раз страница редактировалась" - -[main_by] -other = "by" - -[main_documentation_license] -other = """Авторы Kubernetes | Документация распространяется под лицензией CC BY 4.0""" - -[main_copyright_notice] -other = """The Linux Foundation ®. Все права защищены. The Linux Foundation является зарегистрированной торговой маркой. Список торговых марок The Linux Foundation приведен на странице использования торговых марок""" - -# Labels for the docs portal home page. -[docs_label_browse] -other = "Просмотр документации" - -[docs_label_contributors] -other = "Участники сообщества" - -[docs_label_users] -other = "Пользователи" - -[docs_label_i_am] -other = "Я ..." - -# layouts > blog > pager - -[layouts_blog_pager_prev] -other = "<< Назад" - -[layouts_blog_pager_next] -other = "Вперёд >>" - -# layouts > blog > list - -[layouts_case_studies_list_tell] -other = "Расскажите свою историю" - -# layouts > docs > glossary - -[layouts_docs_glossary_description] -other = "Данный глоссарий должен стать исчерпывающим стандартизированным списком терминологии в Kubernetes. Он включает технические термины, специфичные для K8s, а также более общие термины, которые полезно знать." - -[layouts_docs_glossary_filter] -other = "Фильтрация терминов по тегам" - -[layouts_docs_glossary_select_all] -other = "Выделить всё" - -[layouts_docs_glossary_deselect_all] -other = "Отменить выбор всех тегов" - -[layouts_docs_glossary_aka] -other = "Также известный как" - -[layouts_docs_glossary_click_details_before] -other = "Нажмите на значок" - -[layouts_docs_glossary_click_details_after] -other = "для получения более подробное объяснения по интересующему термину." - -# layouts > docs > search - -[layouts_docs_search_fetching] -other = "Получение результатов.." - -# layouts > partial > feedback - -[layouts_docs_partials_feedback_thanks] -other = "Спасибо за отзыв! Если у вас есть конкретный вопрос об использовании Kubernetes, спрашивайте" - -[layouts_docs_partials_feedback_issue] -other = "Сообщите о проблеме в репозитории GitHub, если вы хотите " - -[layouts_docs_partials_feedback_problem] -other = "сообщить о проблеме" - -[layouts_docs_partials_feedback_or] -other = "или" - -[layouts_docs_partials_feedback_improvement] -other = "предложить улучшение" - -# Community links -[community_twitter_name] -other = "Twitter" -[community_github_name] -other = "GitHub" -[community_slack_name] -other = "Slack" -[community_stack_overflow_name] -other = "Stack Overflow" -[community_forum_name] -other = "Форум" -[community_events_calendar] -other = "Календарь событий" - -# UI elements -[ui_search_placeholder] -other = "Поиск" - -[input_placeholder_email_address] -other = "адрес электронной почты" \ No newline at end of file +[whatsnext_heading] +other = "Что дальше" From 1db59c85d7d81146179ba82d1fd463723f6ec5d9 Mon Sep 17 00:00:00 2001 From: "donatohorn@gmail.com"--allow-experimental-upgrades | +|
Exibe as versões instáveis do Kubernetes como uma alternativa de atualização e permite a atualização para versões candidatas alfa/beta/release do Kubernetes. |
+|
--allow-release-candidate-upgrades | +|
Exibe as versões candidatas a lançamento do Kubernetes como uma alternativa de atualização e permite a atualização para versões candidatas a lançamento do Kubernetes. |
+|
--certificate-renewal Padrão: true | +|
Executa a renovação dos certificados usados pelo componente alterado durante as atualizações. |
+|
--config string | +|
Caminho para um arquivo de configuração do kubeadm. |
+|
--dry-run | +|
Não aplica as modificações; apenas exibe as alterações que seriam efetuadas. |
+|
--etcd-upgrade Padrão: true | +|
Atualiza o etcd. |
+|
--feature-gates string | +|
Um conjunto de pares chave=valor que descreve feature gates para várias funcionalidades. As opções são: |
+|
-f, --force | +|
Força a atualização, embora alguns requisitos possam não ser atendidos. Isso também implica o modo não interativo. |
+|
-h, --help | +|
ajuda para apply |
+|
--ignore-preflight-errors strings | +|
Uma lista de verificações para as quais erros serão exibidos como avisos. Exemplos: 'IsPrivilegedUser,Swap'. O valor 'all' ignora erros de todas as verificações. |
+|
--kubeconfig string Padrão: "/etc/kubernetes/admin.conf" | +|
O arquivo kubeconfig a ser usado para se comunicar com o cluster. Se a flag não estiver definida, um conjunto de locais predefinidos pode ser pesquisado por um arquivo kubeconfig existente. |
+|
--patches string | +|
Caminho para um diretório que contém os arquivos chamados "target[suffix][+patchtype].extension". Por exemplo, "kube-apiserver0+merge.yaml" ou apenas "etcd.json". "target" pode ser um dos "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration". "patchtype" pode ser um dos "strategic", "merge" ou "json" e eles correspondem aos formatos de patch suportados pelo kubectl. O padrão "patchtype" é "strategic". "extension" deve ser "json" ou "yaml". "suffix" é uma string opcional que pode ser usada para determinar quais patches alpha-numerically serão aplicados primeiro. |
+|
--print-config | +|
Especifica se o arquivo de configuração que será usado na atualização deve ser exibido ou não. |
+|
-y, --yes | +|
Executa a atualização e não solicita um prompt de confirmação (modo não interativo). |
+
--rootfs string | +|
[EXPERIMENTAL] O caminho para o sistema de arquivos raiz 'real' do host. |
+
--api-server-manifest string Padrão: "/etc/kubernetes/manifests/kube-apiserver.yaml" | +|
Caminho para o manifesto do servidor API |
+|
--config string | +|
Caminho para um arquivo de configuração do kubeadm. |
+|
-c, --context-lines int Padrão: 3 | +|
Quantidade de linhas de contexto do diff |
+|
--controller-manager-manifest string Padrão: "/etc/kubernetes/manifests/kube-controller-manager.yaml" | +|
Caminho para o manifesto do gerenciador |
+|
-h, --help | +|
Ajuda para o diff |
+|
--kubeconfig string Padrão: "/etc/kubernetes/admin.conf" | +|
O arquivo kubeconfig a ser usado para se comunicar com o cluster. Se a flag não estiver definida, um conjunto de locais predefinidos pode ser pesquisado por um arquivo kubeconfig existente. |
+|
--scheduler-manifest string Padrão: "/etc/kubernetes/manifests/kube-scheduler.yaml" | +|
Caminho para o manifesto do scheduler |
+
--rootfs string | +|
[EXPERIMENTAL] O caminho para o sistema de arquivos raiz 'real' do host. |
+
--certificate-renewal Padrão: true | +|
Executa a renovação dos certificados usados pelo componente alterado durante as atualizações. |
+|
--dry-run | +|
Não aplica as modificações; apenas exibe as alterações que seriam efetuadas. |
+|
--etcd-upgrade Padrão: true | +|
Atualiza o etcd. |
+|
-h, --help | +|
ajuda para node |
+|
--ignore-preflight-errors strings | +|
Uma lista de verificações para as quais erros serão exibidos como avisos. Exemplos: 'IsPrivilegedUser,Swap'. O valor 'all' ignora erros de todas as verificações. |
+|
--kubeconfig string Padrão: "/etc/kubernetes/admin.conf" | +|
O arquivo kubeconfig a ser usado para se comunicar com o cluster. Se a flag não estiver definida, um conjunto de locais predefinidos pode ser pesquisado por um arquivo kubeconfig existente. |
+|
--patches string | +|
Caminho para um diretório que contém os arquivos chamados "target[suffix][+patchtype].extension". Por exemplo, "kube-apiserver0+merge.yaml" ou apenas "etcd.json". "target" pode ser um dos "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration". "patchtype" pode ser um dos "strategic", "merge" ou "json" e eles correspondem aos formatos de patch suportados pelo kubectl. O padrão "patchtype" é "strategic". "extension" deve ser "json" ou "yaml". "suffix" é uma string opcional que pode ser usada para determinar quais patches alpha-numerically serão aplicados primeiro. |
+|
--skip-phases strings | +|
Exibe as fases a serem ignoradas |
+
--rootfs string | +|
[EXPERIMENTAL] O caminho para o sistema de arquivos raiz 'real' do host. |
+
--allow-experimental-upgrades | +|
Exibe as versões instáveis do Kubernetes como uma alternativa de atualização e permite a atualização para versões candidatas alfa/beta/release do Kubernetes. |
+|
--allow-release-candidate-upgrades | +|
Exibe as versões candidatas a lançamento do Kubernetes como uma alternativa de atualização e permite a atualização para versões candidatas a lançamento do Kubernetes. |
+|
--config string | +|
Caminho para um arquivo de configuração kubeadm. |
+|
--feature-gates string | +|
Um conjunto de pares chave=valor que descreve feature gates para várias funcionalidades. As opções são: |
+|
-h, --help | +|
ajuda para plan |
+|
--ignore-preflight-errors strings | +|
Uma lista de verificações para as quais erros serão exibidos como avisos. Exemplos: 'IsPrivilegedUser,Swap'. O valor 'all' ignora erros de todas as verificações. |
+|
--kubeconfig string Padrão: "/etc/kubernetes/admin.conf" | +|
O arquivo kubeconfig a ser usado para se comunicar com o cluster. Se a flag não estiver definida, um conjunto de locais predefinidos pode ser pesquisado por um arquivo kubeconfig existente. |
+|
-o, --output string Padrão: "text" | +|
EXPERIMENTAL: Formato de saída. Um dos: text|json|yaml. |
+|
--print-config | +|
Especifica se o arquivo de configuração que será usado na atualização deve ser exibido ou não. |
+|
--show-managed-fields | +|
Se verdadeiro, mentém os managedFields ao exibir os objetos no formato JSON ou YAML. |
+
--rootfs string | +|
[EXPERIMENTAL] O caminho para o sistema de arquivos raiz 'real' do host. |
+
*
). Use these at your own risk. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)AlwaysAllow
--config
flag. See kubelet-config-file for more information.)''
--config
flag. See kubelet-config-file for more information.)CommonName
of the client certificate. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)CommonName
of the client certificate. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)--container-runtime=remote
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)--container-runtime=remote
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)--config
flag. See kubelet-config-file for more information.)pods
none
, pods
, system-reserved
, and kube-reserved
. If the latter two options are specified, --system-reserved-cgroup
and --kube-reserved-cgroup
must also be set, respectively. If none
is specified, no additional options should be set. See here for more details. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)none
, pods
, system-reserved
, and kube-reserved
. If the latter two options are specified, --system-reserved-cgroup
and --kube-reserved-cgroup
must also be set, respectively. If none
is specified, no additional options should be set. See here for more details. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)imagefs.available<15%,memory.available<100Mi,nodefs.available<10%
imagefs.available<15%,memory.available<100Mi,nodefs.available<10%
memory.available<1Gi
) that if met would trigger a pod eviction. On a Linux node, the default value also includes nodefs.inodesFree<5%
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)imagefs.available=2Gi
) that describes the minimum amount of resource the kubelet will reclaim when performing a pod eviction if that resource is under pressure. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)memory.available<1.5Gi
) that if met over a corresponding grace period would trigger a pod eviction. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)memory.available=1m30s
) that correspond to how long a soft eviction threshold must hold before triggering a pod eviction. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)true
, hard eviction thresholds will be ignored while calculating node allocatable. See here for more details. (DEPRECATED: will be removed in 1.24 or later)--config
flag. See kubelet-config-file for more information.)mount
--config
flag. See kubelet-config-file for more information.)
@@ -623,7 +609,7 @@ WindowsHostProcessContainers=true|false (BETA - default=true)<resource name>=<resource quantity>
(e.g. cpu=200m,memory=500Mi,ephemeral-storage=1Gi,pid='100'
) pairs that describe resources reserved for kubernetes system components. Currently cpu
, memory
and local ephemeral-storage
for root file system are supported. See here for more detail. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)--config
flag. See kubelet-config-file for more information.)true
--config
flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.)":0"
:
, emit a stack trace. (DEPRECATED: will be removed in a future release, see here.)5s
'0'
--config
flag. See kubelet-config-file for more information.)LoggingAlphaOptions
feature gate to use this. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)--config
flag. See kubelet-config-file for more information.)LoggingAlphaOptions
feature gate to use this. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)text
text
, json
.--add-dir-header
, --alsologtostderr
, --log-backtrace-at
, --log-dir
, --log-file
, --log-file-max-size
, --logtostderr
, --skip_headers
, --skip_log_headers
, --stderrthreshold
, --log-flush-frequency
.--config
flag. See kubelet-config-file for more information.)true
text
, json
(gated by LoggingBetaOptions
). (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)key=value pairs
separated by ','
. Labels in the 'kubernetes.io'
namespace must begin with an allowed prefix ('kubelet.kubernetes.io'
, 'node.kubernetes.io'
) or be in the specifically allowed set ('beta.kubernetes.io/arch'
, 'beta.kubernetes.io/instance-type'
, 'beta.kubernetes.io/os'
, 'failure-domain.beta.kubernetes.io/region'
, 'failure-domain.beta.kubernetes.io/zone'
, 'kubernetes.io/arch'
, 'kubernetes.io/hostname'
, 'kubernetes.io/os'
, 'node.kubernetes.io/instance-type'
, 'topology.kubernetes.io/region'
, 'topology.kubernetes.io/zone'
)nodeMonitorGracePeriod
in Node controller. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)registry.k8s.io/pause:3.6
registry.k8s.io/pause:3.9
docker
, all containers in each pod will use the network/IPC namespaces from this image. Other CRI implementations have their own configuration to set this image.--config
flag. See kubelet-config-file for more information.)--config
flag. See kubelet-config-file for more information.)<resource name>=<percentage>
(e.g. memory=50%
) pairs that describe how pod resource requests are reserved at the QoS level. Currently only memory
is supported. Requires the QOSReserved
feature gate to be enabled. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)true
--kubeconfig
is not provided, this flag is irrelevant, as the Kubelet won't have an API server to register with. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)--kubeconfig
is not provided, this flag is irrelevant, as the Kubelet won't have an API server to register with. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)<key>=<value>:<effect>
). No-op if --register-node
is false
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)<key>=<value>:<effect>
). No-op if --register-node
is false
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)kube-apiserver
when the certificate expiration approaches. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)kube-apiserver
when the certificate expiration approaches. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)kube-apiserver
when the certificate expiration approaches. Requires the RotateKubeletServerCertificate
feature gate to be enabled, and approval of the submitted CertificateSigningRequest
objects. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)kube-apiserver
when the certificate expiration approaches. Requires the RotateKubeletServerCertificate
feature gate to be enabled, and approval of the submitted CertificateSigningRequest
objects. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)true
, exit after spawning pods from local manifests or remote urls. Exclusive with --enable-server
(DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)true
, exit after spawning pods from local manifests or remote urls. Exclusive with --enable-server
(DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)RuntimeDefault
as the default seccomp profile for all workloads. The SeccompDefault
feature gate must be enabled to allow this flag, which is disabled by default.RuntimeDefault
as the default seccomp profile for all workloads. The SeccompDefault
feature gate must be enabled to allow this flag.aufs
storage backend. Issue #10959 has more details. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)true
, avoid header prefixes in the log messages. (DEPRECATED: will be removed in a future release, see here.)true
, avoid headers when opening log files. (DEPRECATED: will be removed in a future release, see here.)4h0m0s
<resource name>=<resource quantity>
(e.g. cpu=200m,memory=500Mi,ephemeral-storage=1Gi,pid='100'
) pairs that describe resources reserved for non-kubernetes components. Currently only cpu
and memory
are supported. See here for more detail. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)TLS_AES_128_GCM_SHA256
, TLS_AES_256_GCM_SHA384
, TLS_CHACHA20_POLY1305_SHA256
, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
, TLS_RSA_WITH_AES_128_CBC_SHA
, TLS_RSA_WITH_AES_128_GCM_SHA256
, TLS_RSA_WITH_AES_256_CBC_SHA
, TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
, TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
, TLS_ECDHE_RSA_WITH_RC4_128_SHA
, TLS_RSA_WITH_3DES_EDE_CBC_SHA
, TLS_RSA_WITH_AES_128_CBC_SHA256
, TLS_RSA_WITH_RC4_128_SHA
.--config
flag. See kubelet-config-file for more information.)
'none'
, 'best-effort'
, 'restricted'
, 'single-numa-node'
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)--config
flag. See kubelet-config-file for more information.)container
'container'
, 'pod'
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config flag. See kubelet-config-file for more information.)'container'
, 'pod'
. (DEPRECATED: This parameter should be set via the config file specified by the Kubelet's --config
flag. See kubelet-config-file for more information.)Create a new secret for use with Docker registries.
Dockercfg secrets are used to authenticate against Docker registries.
When using the Docker command line to push images, you can authenticate to a given registry by running: - '$ docker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --password=DOCKER_PASSWORD --email=DOCKER_EMAIL'.
+ '$ docker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --password=DOCKER_PASSWORD --email=DOCKER_EMAIL'.That produces a ~/.dockercfg file that is used by subsequent 'docker push' and 'docker pull' commands to authenticate to the registry. The email address is optional.
When creating applications, you may have a Docker registry that requires authentication. In order for the nodes to pull images on your behalf, they must have the credentials. You can provide this information by creating a dockercfg secret and attaching it to your service account.
$ kubectl create docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]
$ kubectl create secret docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]
If true, wait for the Pod to start running, and then attach to the Pod as if 'kubectl attach ...' were called. Default false, unless '-i/--stdin' is set, in which case the default is true. With '--restart=Never' the exit code of the container process is returned. | |||
cascade | ++ | background | +Must be "background", "orphan", or "foreground". Selects the deletion cascading strategy for the dependents (e.g. Pods created by a ReplicationController). Defaults to background. | +
command | false | @@ -2656,6 +2674,24 @@ inspect them.Name of the manager used to track field ownership. | |
filename | +f | +[] | +to use to replace the resource. | +
force | ++ | false | +If true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation. | +
grace-period | ++ | -1 | +Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion). | +
image | @@ -2668,6 +2704,12 @@ inspect them. | The image pull policy for the container. If left empty, this value will not be specified by the client and defaulted by the server. | |
kustomize | +k | ++ | Process a kustomization directory. This flag can't be used together with -f or -R. | +
labels | l | @@ -2728,6 +2770,12 @@ inspect them. | Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists. |
recursive | +R | +false | +Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory. | +
restart | Always | @@ -2764,11 +2812,23 @@ inspect them.Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. | |
timeout | ++ | 0s | +The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object | +
tty | t | false | Allocate a TTY for the container in the pod. |
wait | ++ | false | +If true, wait for resources to be gone before returning. This waits for finalizers. | +
-Apply the configuration in manifest.yaml and delete all the other config maps that are not in the file
kubectl apply --prune -f manifest.yaml --all --prune-whitelist=core/v1/ConfigMap
+kubectl apply --prune -f manifest.yaml --all --prune-allowlist=core/v1/ConfigMap
Apply a configuration to a resource by file name or stdin. The resource name must be specified. This resource will be created if it doesn't exist yet. To use 'apply', always create the resource initially with either 'apply' or 'create --save-config'.
JSON and YAML formats are accepted.
Alpha Disclaimer: the --prune functionality is not yet complete. Do not use unless you are aware of what the current state is. See https://issues.k8s.io/34274.
Usage
@@ -3267,6 +3327,12 @@ viewing your workloads in a Kubernetes cluster.
Automatically delete resource objects, that do not appear in the configs and are created by either apply or create --save-config. Should be used with either -l or --all.
+prune-allowlist
+
+[]
+Overwrite the default allowlist with <group/version/kind> for --prune
+
+
prune-whitelist
[]
@@ -3934,6 +4000,12 @@ viewing your workloads in a Kubernetes cluster.
The image pull policy for the container. If left empty, this value will not be specified by the client and defaulted by the server.
+profile
+
+legacy
+Debugging profile.
+
+
quiet
q
false
@@ -4335,7 +4407,7 @@ viewing your workloads in a Kubernetes cluster.
kubectl label pods foo bar-
-Update the labels on a resource.
A label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters each.
Optionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.
If --overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result in an error.
If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.
+Update the labels on a resource.
A label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters each.
Optionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.
If --overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result in an error.
If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.
Usage
$ kubectl label [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]
Flags
@@ -4491,7 +4563,7 @@ viewing your workloads in a Kubernetes cluster.
kubectl patch deployment nginx-deployment --subresource='scale' --type='merge' -p '{"spec":{"replicas":2}}'
-Update fields of a resource using strategic merge patch, a JSON merge patch, or a JSON patch.
JSON and YAML formats are accepted.
+Update fields of a resource using strategic merge patch, a JSON merge patch, or a JSON patch.
JSON and YAML formats are accepted.
Note: Strategic merge patch is not supported for custom resources.
Usage
$ kubectl patch (-f FILENAME | TYPE NAME) [-p PATCH|--patch-file FILE]
Flags
@@ -4946,7 +5018,7 @@ viewing your workloads in a Kubernetes cluster.
kubectl rollout restart deployment --selector=app=nginx
Restart a resource.
- Resource rollout will be restarted.
+ Resource rollout will be restarted.
Usage
$ kubectl rollout restart RESOURCE
Flags
@@ -5851,7 +5923,7 @@ viewing your workloads in a Kubernetes cluster.
kubectl create deployment my-dep -o yaml --dry-run=client | kubectl label --local -f - environment=qa -o yaml | kubectl create -f -
Set the selector on a resource. Note that the new selector will overwrite the old selector if the resource had one prior to the invocation of 'set selector'.
- A selector must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters. If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used. Note: currently selectors can only be set on Service objects.
+ A selector must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters. If --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used. Note: currently selectors can only be set on Service objects.
Usage
$ kubectl set selector (-f FILENAME | TYPE NAME) EXPRESSIONS [--resource-version=version]
Flags
@@ -6156,6 +6228,12 @@ kubectl create deployment my-dep -o yaml --dry-run<
Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
+
+user
+
+[]
+Usernames to bind to the role
+
++List recent events in the default namespace.
+
kubectl events
+
+++List recent events in all namespaces.
+
kubectl events --all-namespaces
+
+++List recent events for the specified pod, then wait for more events and list them as they arrive.
+
kubectl events --for pod/web-pod-13je7 --watch
+
+++List recent events in given format. Supported ones, apart from default, are json and yaml.
+
kubectl events -oyaml
+
+++List recent only events in given event types
+
kubectl events --types=Warning,Normal
+
+Display events
Prints a table of the most important information about events. You can request events for a namespace, for all namespace, or filtered to only those pertaining to a specified resource.
$ kubectl events [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file] [--for TYPE/NAME] [--watch] [--event=Normal,Warning]
Name | +Shorthand | +Default | +Usage | +
---|---|---|---|
all-namespaces | +A | +false | +If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. | +
allow-missing-template-keys | ++ | true | +If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. | +
chunk-size | ++ | 500 | +Return large lists in chunks rather than all at once. Pass 0 to disable. This flag is beta and may change in the future. | +
for | ++ | + | Filter events to only those pertaining to the specified resource. | +
no-headers | ++ | false | +When using the default output format, don't print headers. | +
output | +o | ++ | Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file). | +
show-managed-fields | ++ | false | +If true, keep the managedFields when printing objects in JSON or YAML format. | +
template | ++ | + | Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. | +
types | ++ | [] | +Output only events of given types. | +
watch | +w | +false | +After listing the requested events, watch for more events. | +
Get output from running the 'date' command from pod mypod, using the first container by default
@@ -7285,6 +7466,102 @@ applications.Usage
$ kubectl api-versions
+api-resources
+++Print the supported API resources
++
kubectl api-resources +
++Print the supported API resources with more information
++
kubectl api-resources -o wide +
++Print the supported API resources sorted by a column
++
kubectl api-resources --sort-by=name +
++Print the supported namespaced resources
++
kubectl api-resources --namespaced=true +
++Print the supported non-namespaced resources
++
kubectl api-resources --namespaced=false +
++Print the supported API resources with a specific APIGroup
++
kubectl api-resources --api-group=rbac.authorization.k8s.io +
Print the supported API resources on the server.
+Usage
++
$ kubectl api-resources
Flags
++ +
++ + + +Name +Shorthand +Default +Usage ++ +api-group ++ + Limit to resources in the specified API group. ++ +cached ++ false +Use the cached list of resources if available. ++ +categories ++ [] +Limit to resources that belong the the specified categories. ++ +namespaced ++ true +If false, non-namespaced resources will be returned, otherwise returning namespaced resources by default. ++ +no-headers ++ false +When using the default or custom-column output format, don't print headers (default print headers). ++ +output +o ++ Output format. One of: (wide, name). ++ +sort-by ++ + If non-empty, sort list of resources using specified field. The field can be either 'name' or 'kind'. ++ + +verbs ++ [] +Limit to resources that support the specified verbs. +
certificate
Modify certificate resources.
Usage
@@ -7578,7 +7855,7 @@ applications.
kubectl drain foo --grace-period=900
-Drain node in preparation for maintenance.
The given node will be marked unschedulable to prevent new pods from arriving. 'drain' evicts the pods if the API server supports https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ . Otherwise, it will use normal DELETE to delete the pods. The 'drain' evicts or deletes all pods except mirror pods (which cannot be deleted through the API server). If there are daemon set-managed pods, drain will not proceed without --ignore-daemonsets, and regardless it will not delete any daemon set-managed pods, because those pods would be immediately replaced by the daemon set controller, which ignores unschedulable markings. If there are any pods that are neither mirror pods nor managed by a replication controller, replica set, daemon set, stateful set, or job, then drain will not delete any pods unless you use --force. --force will also allow deletion to proceed if the managing resource of one or more pods is missing.
'drain' waits for graceful termination. You should not operate on the machine until the command completes.
When you are ready to put the node back into service, use kubectl uncordon, which will make the node schedulable again.
https://kubernetes.io/images/docs/kubectl_drain.svg
Drain node in preparation for maintenance.
The given node will be marked unschedulable to prevent new pods from arriving. 'drain' evicts the pods if the API server supports https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ eviction https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ . Otherwise, it will use normal DELETE to delete the pods. The 'drain' evicts or deletes all pods except mirror pods (which cannot be deleted through the API server). If there are daemon set-managed pods, drain will not proceed without --ignore-daemonsets, and regardless it will not delete any daemon set-managed pods, because those pods would be immediately replaced by the daemon set controller, which ignores unschedulable markings. If there are any pods that are neither mirror pods nor managed by a replication controller, replica set, daemon set, stateful set, or job, then drain will not delete any pods unless you use --force. --force will also allow deletion to proceed if the managing resource of one or more pods is missing.
'drain' waits for graceful termination. You should not operate on the machine until the command completes.
When you are ready to put the node back into service, use kubectl uncordon, which will make the node schedulable again.
https://kubernetes.io/images/docs/kubectl_drain.svg Workflowhttps://kubernetes.io/images/docs/kubectl_drain.svg
$ kubectl drain NODE
kubectl taint nodes foo bar:NoSchedule
-Update the taints on one or more nodes.
A taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect.
The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 253 characters.
Optionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.
The value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters.
The effect must be NoSchedule, PreferNoSchedule or NoExecute.
Currently taint can only apply to node.
Update the taints on one or more nodes.
A taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect.
The key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 253 characters.
Optionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.
The value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters.
The effect must be NoSchedule, PreferNoSchedule or NoExecute.
Currently taint can only apply to node.
$ kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N
$ kubectl alpha
--List recent events in the default namespace.
-
kubectl alpha events
-
---List recent events in all namespaces.
-
kubectl alpha events --all-namespaces
-
---List recent events for the specified pod, then wait for more events and list them as they arrive.
-
kubectl alpha events --for pod/web-pod-13je7 --watch
-
---List recent events in given format. Supported ones, apart from default, are json and yaml.
-
kubectl alpha events -oyaml
-
---List recent only events in given event types
-
kubectl alpha events --types=Warning,Normal
-
-Experimental: Display events
-Prints a table of the most important information about events. You can request events for a namespace, for all namespace, or filtered to only those pertaining to a specified resource.
+Inspect authorization
$ kubectl alpha events [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file] [--for TYPE/NAME] [--watch] [--event=Normal,Warning]
$ kubectl alpha auth
++Get your subject attributes.
+
kubectl alpha auth whoami
+
+++Get your subject attributes in JSON format.
+
kubectl alpha auth whoami -o json
+
+Experimental: Check who you are and your attributes (groups, extra).
+This command is helpful to get yourself aware of the current user attributes, + especially when dynamic authentication, e.g., token webhook, auth proxy, or OIDC provider, + is enabled in the Kubernetes cluster.
+$ kubectl alpha auth whoami
all-namespaces | -A | -false | -If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even if specified with --namespace. | -|
allow-missing-template-keys | true | If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. | ||
chunk-size | -- | 500 | -Return large lists in chunks rather than all at once. Pass 0 to disable. This flag is beta and may change in the future. | -|
for | -- | - | Filter events to only those pertaining to the specified resource. | -|
no-headers | -- | false | -When using the default output format, don't print headers. | -|
output | o | @@ -7900,108 +8145,6 @@ applications. | Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]. | |
types | -- | [] | -Output only events of given types. | -|
watch | -w | -false | -After listing the requested events, watch for more events. | -
--Print the supported API resources
-
kubectl api-resources
-
---Print the supported API resources with more information
-
kubectl api-resources -o wide
-
---Print the supported API resources sorted by a column
-
kubectl api-resources --sort-by=name
-
---Print the supported namespaced resources
-
kubectl api-resources --namespaced=true
-
---Print the supported non-namespaced resources
-
kubectl api-resources --namespaced=false
-
---Print the supported API resources with a specific APIGroup
-
kubectl api-resources --api-group=rbac.authorization.k8s.io
-
-Print the supported API resources on the server.
-$ kubectl api-resources
Name | -Shorthand | -Default | -Usage | -
---|---|---|---|
api-group | -- | - | Limit to resources in the specified API group. | -
cached | -- | false | -Use the cached list of resources if available. | -
namespaced | -- | true | -If false, non-namespaced resources will be returned, otherwise returning namespaced resources by default. | -
no-headers | -- | false | -When using the default or custom-column output format, don't print headers (default print headers). | -
output | -o | -- | Output format. One of: (wide, name). | -
sort-by | -- | - | If non-empty, sort list of resources using specified field. The field can be either 'name' or 'kind'. | -
verbs | -- | [] | -Limit to resources that support the specified verbs. | -
Modify kubeconfig files using subcommands like "kubectl config set current-context my-context"
The loading order follows these rules:
1. If the --kubeconfig flag is set, then only that file is loaded. The flag may only be set once and no merging takes place.
2. If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimiting rules for your system). These paths are merged. When a value is modified, it is modified in the file that defines the stanza. When a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates the last file in the list.
3. Otherwise, ${HOME}/.kube/config is used and no merging takes place.
$ kubectl config SUBCOMMAND
Name | +Shorthand | +Default | +Usage | +
---|---|---|---|
kubeconfig | ++ | + | use a particular kubeconfig file | +
@@ -8293,17 +8455,41 @@ kubectl completion powershell | Out-String | Invoke-Ex
kubectl config view
-Show merged kubeconfig settings and raw certificate data
+Show merged kubeconfig settings and raw certificate data and exposed secrets
kubectl config view --raw
@@ -8546,7 +8780,7 @@ kubectl completion powershell | Out-String | Invoke-Ex
$ kubectl options
Provides utilities for interacting with plugins.
Plugins provide extended functionality that is not part of the major command-line distribution. Please refer to the documentation and examples for more information about how write your own plugins.
The easiest way to discover and install plugins is via the kubernetes sub-project krew. To install krew, visit https://krew.sigs.k8s.io/docs/user-guide/setup/install/
Provides utilities for interacting with plugins.
Plugins provide extended functionality that is not part of the major command-line distribution. Please refer to the documentation and examples for more information about how write your own plugins.
The easiest way to discover and install plugins is via the kubernetes sub-project krew. To install krew, visit https://krew.sigs.k8s.io/docs/user-guide/setup/install/ krew.sigs.k8s.io https://krew.sigs.k8s.io/docs/user-guide/setup/install/
$ kubectl plugin [flags]
J)(lYyQ1kItoa2CREud1?qW}t
zM4Dkg^u(WZ_eR(ZM4m(7XDhLZ?W2K;DP&7Sv38K>`~~8??IrDMDYinNha}2FiOrT>
z8fWDINp)=E?=H;RV^ycIj%P?dzqq-zv{ikudG9{VMbCj6I~)g<*PUTb3Et$Cl1&4S
zF!BbzQPAALhcANgend4zG<$b1djlMPRjCH?SE
zxUM|3v~V+buR}bV$`%F9=jpee08vsxGU&dmkL&kwU4VNL*{Lh%c=D|fAS$aUt*cYf
zJIK_e$vkau$TD*fK(;%`P5gN0I(hyYc}(r@5Cc>|cyDY4;B0o{eVYFY)!cJI9_Igu
z&R`fve7qW#2C#(wl0FFfV0VS&Dttg#;D3c}$nKsPE^(zGf~r6_qAm{(f~Z@U3!ib2
zOUw>Y`U`plwG}KfF6|@k?)e$nakeX>#?-}twJtAejD-@~@U(Tkpxhp^dDFTGX-