{
	"id": "ad7e0573-1155-4737-9afc-6adc421dc4a3",
	"created_at": "2026-04-06T00:15:26.025474Z",
	"updated_at": "2026-04-10T13:12:22.25472Z",
	"deleted_at": null,
	"sha1_hash": "21c1f26d63d26e693d2109cf391d1909bf9abac9",
	"title": "Kubectl Reference Docs",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 823656,
	"plain_text": "Kubectl Reference Docs\r\nArchived: 2026-04-05 21:43:52 UTC\r\n⚠️ This page is deprecated and will be removed in a future release.\r\nUse the new kubectl reference. For a single-page view, see the printable version.\r\nGETTING STARTED\r\nThis section contains the most basic commands for getting a workload running on your cluster.\r\nrun will start running 1 or more instances of a container image on your cluster.\r\nexpose will load balance traffic across the running instances, and can create a HA proxy for accessing the\r\ncontainers from outside the cluster.\r\nOnce your workloads are running, you can use the commands in the WORKING WITH APPS section to inspect\r\nthem.\r\ncreate\r\nCreate a pod using the data in pod.json\r\nkubectl create -f ./pod.json\r\nCreate a pod based on the JSON passed into stdin\r\ncat pod.json | kubectl create -f -\r\nEdit the data in registry.yaml in JSON then create the resource using the edited data\r\nkubectl create -f registry.yaml --edit -o json\r\nCreate a resource from a file or from stdin.\r\nJSON and YAML formats are accepted.\r\nUsage\r\n$ kubectl create -f FILENAME\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 1 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nedit false Edit the API resource before creating\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nfilename f [] Filename, directory, or URL to files to use to create the resource\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nraw\r\nRaw URI to POST to the server. Uses the transport specified by\r\nthe kubeconfig file.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 2 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nwindows-line-endings\r\nfalse\r\nOnly relevant if --edit=true. Defaults to the line ending native to\r\nyour platform.\r\nclusterrole\r\nCreate a cluster role named \"pod-reader\" that allows user to perform \"get\", \"watch\" and \"list\" on pods\r\nkubectl create clusterrole pod-reader --verb=get,list,watch --resource=pods\r\nCreate a cluster role named \"pod-reader\" with ResourceName specified\r\nkubectl create clusterrole pod-reader --verb=get --resource=pods --resource-name=readablepod --resource-name=an\r\nCreate a cluster role named \"foo\" with API Group specified\r\nkubectl create clusterrole foo --verb=get,list,watch --resource=rs.apps\r\nCreate a cluster role named \"foo\" with SubResource specified\r\nkubectl create clusterrole foo --verb=get,list,watch --resource=pods,pods/status\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 3 of 150\n\nCreate a cluster role name \"foo\" with NonResourceURL specified\r\nkubectl create clusterrole \"foo\" --verb=get --non-resource-url=/logs/*\r\nCreate a cluster role name \"monitoring\" with AggregationRule specified\r\nkubectl create clusterrole monitoring --aggregation-rule=\"rbac.example.com/aggregate-to-monitoring=true\"\r\nCreate a cluster role.\r\nUsage\r\n$ kubectl create clusterrole NAME --verb=verb --resource=resource.group [--resource-name=resourcename] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\naggregation-rule\r\nAn aggregation label selector for combining ClusterRoles.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-create\r\nName of the manager used to track field ownership.\r\nnon-resource-url\r\n[] A partial url that user should have access to.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nresource [] Resource that the rule applies to\r\nresource-name\r\n[]\r\nResource in the white list that the rule applies to, repeat this flag\r\nfor multiple items\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 4 of 150\n\nName Shorthand Default Usage\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nverb [] Verb that applies to the resources contained in the rule\r\nclusterrolebinding\r\nCreate a cluster role binding for user1, user2, and group1 using the cluster-admin cluster role\r\nkubectl create clusterrolebinding cluster-admin --clusterrole=cluster-admin --user=user1 --user=user2 --group=g\r\nCreate a cluster role binding for a particular cluster role.\r\nUsage\r\n$ kubectl create clusterrolebinding NAME --clusterrole=NAME [--user=username] [--group=groupname] [--\r\nserviceaccount=namespace:serviceaccountname] [--dry-run=server|client|none]\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 5 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nclusterrole ClusterRole this ClusterRoleBinding should reference\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-create\r\nName of the manager used to track field ownership.\r\ngroup []\r\nGroups to bind to the clusterrole. The flag can be repeated to\r\nadd multiple groups.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nserviceaccount []\r\nService accounts to bind to the clusterrole, in the format\r\n\u003cnamespace\u003e:\u003cname\u003e. The flag can be repeated to add\r\nmultiple service accounts.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nuser []\r\nUsernames to bind to the clusterrole. The flag can be repeated\r\nto add multiple users.\r\nvalidate strict Must be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and\r\nfail the request if invalid. It will perform server side validation\r\nif ServerSideFieldValidation is enabled on the api-server, but\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 6 of 150\n\nName Shorthand Default Usage\r\nwill fall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled\r\non the API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nconfigmap\r\nCreate a new config map named my-config based on folder bar\r\nkubectl create configmap my-config --from-file=path/to/bar\r\nCreate a new config map named my-config with specified keys instead of file basenames on disk\r\nkubectl create configmap my-config --from-file=key1=/path/to/bar/file1.txt --from-file=key2=/path/to/bar/file2\r\nCreate a new config map named my-config with key1=config1 and key2=config2\r\nkubectl create configmap my-config --from-literal=key1=config1 --from-literal=key2=config2\r\nCreate a new config map named my-config from the key=value pairs in the file\r\nkubectl create configmap my-config --from-file=path/to/bar\r\nCreate a new config map named my-config from an env file\r\nkubectl create configmap my-config --from-env-file=path/to/foo.env --from-env-file=path/to/bar.env\r\nCreate a config map based on a file, directory, or specified literal value.\r\nA single config map may package one or more key/value pairs.\r\nWhen creating a config map based on a file, the key will default to the basename of the file, and the value will\r\ndefault to the file content. If the basename is an invalid key, you may specify an alternate key.\r\nWhen creating a config map based on a directory, each file whose basename is a valid key in the directory will be\r\npackaged into the config map. Any directory entries except regular files are ignored (e.g. subdirectories, symlinks,\r\ndevices, pipes, etc).\r\nUsage\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 7 of 150\n\n$ kubectl create configmap NAME [--from-file=[key=]source] [--from-literal=key1=value1] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath output\r\nformats.\r\nappend-hash\r\nfalse Append a hash of the configmap to its name.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nfrom-env-file\r\n[]\r\nSpecify the path to a file to read lines of key=val pairs to create a\r\nconfigmap.\r\nfrom-file []\r\nKey file can be specified using its file path, in which case file\r\nbasename will be used as configmap key, or optionally with a key\r\nand file path, in which case the given key will be used. Specifying\r\na directory will iterate each named file in the directory whose\r\nbasename is a valid configmap key.\r\nfrom-literal []\r\nSpecify a key and literal value to insert in configmap (i.e.\r\nmykey=somevalue)\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 8 of 150\n\nName Shorthand Default Usage\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will fall\r\nback to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on the\r\nAPI server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation, silently\r\ndropping any unknown or duplicate fields.\r\ncronjob\r\nCreate a cron job\r\nkubectl create cronjob my-job --image=busybox --schedule=\"*/1 * * * *\"\r\nCreate a cron job with a command\r\nkubectl create cronjob my-job --image=busybox --schedule=\"*/1 * * * *\" -- date\r\nCreate a cron job with the specified name.\r\nUsage\r\n$ kubectl create cronjob NAME --image=image --schedule='0/5 * * * ?' -- [COMMAND] [args...]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none Must be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 9 of 150\n\nName Shorthand Default Usage\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nimage Image name to run.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrestart job's restart policy. supported values: OnFailure, Never\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nschedule A schedule in the Cron format the job should be run with.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\ndeployment\r\nCreate a deployment named my-dep that runs the busybox image\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 10 of 150\n\nkubectl create deployment my-dep --image=busybox\r\nCreate a deployment with a command\r\nkubectl create deployment my-dep --image=busybox -- date\r\nCreate a deployment named my-dep that runs the nginx image with 3 replicas\r\nkubectl create deployment my-dep --image=nginx --replicas=3\r\nCreate a deployment named my-dep that runs the busybox image and expose port 5701\r\nkubectl create deployment my-dep --image=busybox --port=5701\r\nCreate a deployment with the specified name.\r\nUsage\r\n$ kubectl create deployment NAME --image=image -- [COMMAND] [args...]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nimage [] Image names to run.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nport -1 The port that this container exposes.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 11 of 150\n\nName Shorthand Default Usage\r\nreplicas r 1 Number of replicas to create. Default is 1.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\ningress\r\nCreate a single ingress called 'simple' that directs requests to foo.com/bar to svc # svc1:8080 with a tls\r\nsecret \"my-cert\"\r\nkubectl create ingress simple --rule=\"foo.com/bar=svc1:8080,tls=my-cert\"\r\nCreate a catch all ingress of \"/path\" pointing to service svc:port and Ingress Class as \"otheringress\"\r\nkubectl create ingress catch-all --class=otheringress --rule=\"/path=svc:port\"\r\nCreate an ingress with two annotations: ingress.annotation1 and ingress.annotations2\r\nkubectl create ingress annotated --class=default --rule=\"foo.com/bar=svc:port\" \\\r\n--annotation ingress.annotation1=foo \\\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 12 of 150\n\n--annotation ingress.annotation2=bla\r\nCreate an ingress with the same host and multiple paths\r\nkubectl create ingress multipath --class=default \\\r\n--rule=\"foo.com/=svc:port\" \\\r\n--rule=\"foo.com/admin/=svcadmin:portadmin\"\r\nCreate an ingress with multiple hosts and the pathType as Prefix\r\nkubectl create ingress ingress1 --class=default \\\r\n--rule=\"foo.com/path*=svc:8080\" \\\r\n--rule=\"bar.com/admin*=svc2:http\"\r\nCreate an ingress with TLS enabled using the default ingress certificate and different path types\r\nkubectl create ingress ingtls --class=default \\\r\n--rule=\"foo.com/=svc:https,tls\" \\\r\n--rule=\"foo.com/path/subpath*=othersvc:8080\"\r\nCreate an ingress with TLS enabled using a specific secret and pathType as Prefix\r\nkubectl create ingress ingsecret --class=default \\\r\n--rule=\"foo.com/*=svc:8080,tls=secret1\"\r\nCreate an ingress with a default backend\r\nkubectl create ingress ingdefault --class=default \\\r\n--default-backend=defaultsvc:http \\\r\n--rule=\"foo.com/*=svc:8080,tls=secret1\"\r\nCreate an ingress with the specified name.\r\nUsage\r\n$ kubectl create ingress NAME --rule=host/path=service:port[,tls[=secret]]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-true If true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 13 of 150\n\nName Shorthand Default Usage\r\ntemplate-keysoutput formats.\r\nannotation []\r\nAnnotation to insert in the ingress object, in the format\r\nannotation=value\r\nclass Ingress Class to be used\r\ndefault-backend\r\nDefault service for backend, in format of svcname:port\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrule []\r\nRule in format host/path=service:port[,tls=secretname]. Paths\r\ncontaining the leading character '*' are considered\r\npathType=Prefix. tls argument is optional.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict Must be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 14 of 150\n\nName Shorthand Default Usage\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\njob\r\nCreate a job\r\nkubectl create job my-job --image=busybox\r\nCreate a job with a command\r\nkubectl create job my-job --image=busybox -- date\r\nCreate a job from a cron job named \"a-cronjob\"\r\nkubectl create job test-job --from=cronjob/a-cronjob\r\nCreate a job with the specified name.\r\nUsage\r\n$ kubectl create job NAME --image=image [--from=cronjob/name] -- [COMMAND] [args...]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 15 of 150\n\nName Shorthand Default Usage\r\nfrom\r\nThe name of the resource to create a Job from (only cronjob is\r\nsupported).\r\nimage Image name to run.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nnamespace\r\nCreate a new namespace named my-namespace\r\nkubectl create namespace my-namespace\r\nCreate a namespace with the specified name.\r\nUsage\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 16 of 150\n\n$ kubectl create namespace NAME [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 17 of 150\n\npoddisruptionbudget\r\nCreate a pod disruption budget named my-pdb that will select all pods with the app=rails label # and\r\nrequire at least one of them being available at any point in time\r\nkubectl create poddisruptionbudget my-pdb --selector=app=rails --min-available=1\r\nCreate a pod disruption budget named my-pdb that will select all pods with the app=nginx label # and\r\nrequire at least half of the pods selected to be available at any point in time\r\nkubectl create pdb my-pdb --selector=app=nginx --min-available=50%\r\nCreate a pod disruption budget with the specified name, selector, and desired minimum available pods.\r\nUsage\r\n$ kubectl create poddisruptionbudget NAME --selector=SELECTOR --min-available=N [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nmax-unavailableThe maximum number or percentage of unavailable pods this\r\nbudget requires.\r\nmin-availableThe minimum number or percentage of available pods this\r\nbudget requires.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 18 of 150\n\nName Shorthand Default Usage\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nselector\r\nA label selector to use for this budget. Only equality-based\r\nselector requirements are supported.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\npriorityclass\r\nCreate a priority class named high-priority\r\nkubectl create priorityclass high-priority --value=1000 --description=\"high priority\"\r\nCreate a priority class named default-priority that is considered as the global default priority\r\nkubectl create priorityclass default-priority --value=1000 --global-default=true --description=\"default priorit\r\nCreate a priority class named high-priority that cannot preempt pods with lower priority\r\nkubectl create priorityclass high-priority --value=1000 --description=\"high priority\" --preemption-policy=\"Neve\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 19 of 150\n\nCreate a priority class with the specified name, value, globalDefault and description.\r\nUsage\r\n$ kubectl create priorityclass NAME --value=VALUE --global-default=BOOL [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field\r\nor map key is missing in the template. Only applies\r\nto golang and jsonpath output formats.\r\ndescription\r\ndescription is an arbitrary string that usually\r\nprovides guidelines on when this priority class\r\nshould be used.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client\r\nstrategy, only print the object that would be sent,\r\nwithout sending it. If server strategy, submit server-side request without persisting the resource.\r\nfield-manager\r\nkubectl-create Name of the manager used to track field ownership.\r\nglobal-default\r\nfalse\r\nglobal-default specifies whether this PriorityClass\r\nshould be considered as the default priority.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile,\r\njsonpath, jsonpath-as-json, jsonpath-file).\r\npreemption-policy\r\nPreemptLowerPriority\r\npreemption-policy is the policy for preempting pods\r\nwith lower priority.\r\nsave-config false\r\nIf true, the configuration of current object will be\r\nsaved in its annotation. Otherwise, the annotation\r\nwill be unchanged. This flag is useful when you\r\nwant to perform kubectl apply on this object in the\r\nfuture.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 20 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing\r\nobjects in JSON or YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when\r\n-o=go-template, -o=go-template-file. The template\r\nformat is golang templates\r\n[http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or\r\nfalse).\r\n\"true\" or \"strict\" will use a schema to validate the\r\ninput and fail the request if invalid. It will perform\r\nserver side validation if ServerSideFieldValidation\r\nis enabled on the api-server, but will fall back to less\r\nreliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields\r\nwithout blocking the request if server-side field\r\nvalidation is enabled on the API server, and behave\r\nas \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema\r\nvalidation, silently dropping any unknown or\r\nduplicate fields.\r\nvalue 0 the value of this priority class.\r\nquota\r\nCreate a new resource quota named my-quota\r\nkubectl create quota my-quota --hard=cpu=1,memory=1G,pods=2,services=3,replicationcontrollers=2,resourcequotas=\r\nCreate a new resource quota named best-effort\r\nkubectl create quota best-effort --hard=pods=100 --scopes=BestEffort\r\nCreate a resource quota with the specified name, hard limits, and optional scopes.\r\nUsage\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 21 of 150\n\n$ kubectl create quota NAME [--hard=key1=value1,key2=value2] [--scopes=Scope1,Scope2] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nhard\r\nA comma-delimited set of resource=quantity pairs that define a\r\nhard limit.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nscopes\r\nA comma-delimited set of quota scopes that must all match each\r\nobject tracked by the quota.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict Must be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 22 of 150\n\nName Shorthand Default Usage\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nrole\r\nCreate a role named \"pod-reader\" that allows user to perform \"get\", \"watch\" and \"list\" on pods\r\nkubectl create role pod-reader --verb=get --verb=list --verb=watch --resource=pods\r\nCreate a role named \"pod-reader\" with ResourceName specified\r\nkubectl create role pod-reader --verb=get --resource=pods --resource-name=readablepod --resource-name=anotherpo\r\nCreate a role named \"foo\" with API Group specified\r\nkubectl create role foo --verb=get,list,watch --resource=rs.apps\r\nCreate a role named \"foo\" with SubResource specified\r\nkubectl create role foo --verb=get,list,watch --resource=pods,pods/status\r\nCreate a role with single rule.\r\nUsage\r\n$ kubectl create role NAME --verb=verb --resource=resource.group/subresource [--resource-name=resourcename] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 23 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nresource [] Resource that the rule applies to\r\nresource-name\r\n[]\r\nResource in the white list that the rule applies to, repeat this flag\r\nfor multiple items\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nverb [] Verb that applies to the resources contained in the rule\r\nrolebinding\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 24 of 150\n\nCreate a role binding for user1, user2, and group1 using the admin cluster role\r\nkubectl create rolebinding admin --clusterrole=admin --user=user1 --user=user2 --group=group1\r\nCreate a role binding for a particular role or cluster role.\r\nUsage\r\n$ kubectl create rolebinding NAME --clusterrole=NAME|--role=NAME [--user=username] [--\r\ngroup=groupname] [--serviceaccount=namespace:serviceaccountname] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nclusterrole ClusterRole this RoleBinding should reference\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-create\r\nName of the manager used to track field ownership.\r\ngroup []\r\nGroups to bind to the role. The flag can be repeated to add\r\nmultiple groups.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\nrole Role this RoleBinding should reference\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nserviceaccount []\r\nService accounts to bind to the role, in the format\r\n\u003cnamespace\u003e:\u003cname\u003e. The flag can be repeated to add\r\nmultiple service accounts.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 25 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nuser []\r\nUsernames to bind to the role. The flag can be repeated to add\r\nmultiple users.\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and\r\nfail the request if invalid. It will perform server side validation\r\nif ServerSideFieldValidation is enabled on the api-server, but\r\nwill fall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled\r\non the API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nsecret\r\nCreate a secret using specified subcommand.\r\nUsage\r\n$ kubectl create secret\r\nsecret docker-registry\r\nIf you don't already have a .dockercfg file, you can create a dockercfg secret directly by using:\r\nkubectl create secret docker-registry my-secret --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER\r\nCreate a new secret named my-secret from ~/.docker/config.json\r\nkubectl create secret docker-registry my-secret --from-file=.dockerconfigjson=path/to/.docker/config.json\r\nCreate a new secret for use with Docker registries.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 26 of 150\n\nDockercfg secrets are used to authenticate against Docker registries.\r\nWhen using the Docker command line to push images, you can authenticate to a given registry by running: '$\r\ndocker login DOCKER_REGISTRY_SERVER --username=DOCKER_USER --\r\npassword=DOCKER_PASSWORD --email=DOCKER_EMAIL'.\r\nThat produces a ~/.dockercfg file that is used by subsequent 'docker push' and 'docker pull' commands to\r\nauthenticate to the registry. The email address is optional.\r\nWhen creating applications, you may have a Docker registry that requires authentication. In order for the nodes to\r\npull images on your behalf, they must have the credentials. You can provide this information by creating a\r\ndockercfg secret and attaching it to your service account.\r\nUsage\r\n$ kubectl create secret docker-registry NAME --docker-username=user --docker-password=password --\r\ndocker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field\r\nor map key is missing in the template. Only applies\r\nto golang and jsonpath output formats.\r\nappend-hash\r\nfalse Append a hash of the secret to its name.\r\ndocker-email\r\nEmail for Docker registry\r\ndocker-password\r\nPassword for Docker registry authentication\r\ndocker-server\r\nhttps://index.docker.io/v1/ Server location for Docker registry\r\ndocker-username\r\nUsername for Docker registry authentication\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client\r\nstrategy, only print the object that would be sent,\r\nwithout sending it. If server strategy, submit\r\nserver-side request without persisting the resource.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 27 of 150\n\nName Shorthand Default Usage\r\nfield-manager\r\nkubectl-create\r\nName of the manager used to track field\r\nownership.\r\nfrom-file []\r\nKey files can be specified using their file path, in\r\nwhich case a default name will be given to them,\r\nor optionally with a name and file path, in which\r\ncase the given name will be used. Specifying a\r\ndirectory will iterate each named file in the\r\ndirectory that is a valid secret key.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile,\r\njsonpath, jsonpath-as-json, jsonpath-file).\r\nsave-config\r\nfalse\r\nIf true, the configuration of current object will be\r\nsaved in its annotation. Otherwise, the annotation\r\nwill be unchanged. This flag is useful when you\r\nwant to perform kubectl apply on this object in the\r\nfuture.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing\r\nobjects in JSON or YAML format.\r\ntemplate\r\nTemplate string or path to template file to use\r\nwhen -o=go-template, -o=go-template-file. The\r\ntemplate format is golang templates\r\n[http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict Must be one of: strict (or true), warn, ignore (or\r\nfalse).\r\n\"true\" or \"strict\" will use a schema to validate the\r\ninput and fail the request if invalid. It will perform\r\nserver side validation if ServerSideFieldValidation\r\nis enabled on the api-server, but will fall back to\r\nless reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate\r\nfields without blocking the request if server-side\r\nfield validation is enabled on the API server, and\r\nbehave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 28 of 150\n\nName Shorthand Default Usage\r\nvalidation, silently dropping any unknown or\r\nduplicate fields.\r\nsecret generic\r\nCreate a new secret named my-secret with keys for each file in folder bar\r\nkubectl create secret generic my-secret --from-file=path/to/bar\r\nCreate a new secret named my-secret with specified keys instead of names on disk\r\nkubectl create secret generic my-secret --from-file=ssh-privatekey=path/to/id_rsa --from-file=ssh-publickey=pat\r\nCreate a new secret named my-secret with key1=supersecret and key2=topsecret\r\nkubectl create secret generic my-secret --from-literal=key1=supersecret --from-literal=key2=topsecret\r\nCreate a new secret named my-secret using a combination of a file and a literal\r\nkubectl create secret generic my-secret --from-file=ssh-privatekey=path/to/id_rsa --from-literal=passphrase=top\r\nCreate a new secret named my-secret from env files\r\nkubectl create secret generic my-secret --from-env-file=path/to/foo.env --from-env-file=path/to/bar.env\r\nCreate a secret based on a file, directory, or specified literal value.\r\nA single secret may package one or more key/value pairs.\r\nWhen creating a secret based on a file, the key will default to the basename of the file, and the value will default\r\nto the file content. If the basename is an invalid key or you wish to chose your own, you may specify an alternate\r\nkey.\r\nWhen creating a secret based on a directory, each file whose basename is a valid key in the directory will be\r\npackaged into the secret. Any directory entries except regular files are ignored (e.g. subdirectories, symlinks,\r\ndevices, pipes, etc).\r\nUsage\r\n$ kubectl create secret generic NAME [--type=string] [--from-file=[key=]source] [--from-literal=key1=value1] [--dry-run=server|client|none]\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 29 of 150\n\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nappend-hash\r\nfalse Append a hash of the secret to its name.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nfrom-env-file\r\n[]\r\nSpecify the path to a file to read lines of key=val pairs to create a\r\nsecret.\r\nfrom-file []\r\nKey files can be specified using their file path, in which case a\r\ndefault name will be given to them, or optionally with a name and\r\nfile path, in which case the given name will be used. Specifying a\r\ndirectory will iterate each named file in the directory that is a valid\r\nsecret key.\r\nfrom-literal []\r\nSpecify a key and literal value to insert in secret (i.e.\r\nmykey=somevalue)\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 30 of 150\n\nName Shorthand Default Usage\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntype The type of secret to create\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will fall\r\nback to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on the\r\nAPI server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation, silently\r\ndropping any unknown or duplicate fields.\r\nsecret tls\r\nCreate a new TLS secret named tls-secret with the given key pair\r\nkubectl create secret tls tls-secret --cert=path/to/tls.cert --key=path/to/tls.key\r\nCreate a TLS secret from the given public/private key pair.\r\nThe public/private key pair must exist beforehand. The public key certificate must be .PEM encoded and match\r\nthe given private key.\r\nUsage\r\n$ kubectl create secret tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 31 of 150\n\nName Shorthand Default Usage\r\nappend-hash\r\nfalse Append a hash of the secret to its name.\r\ncert Path to PEM encoded public key certificate.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nkey Path to private key associated with given certificate.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nservice\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 32 of 150\n\nCreate a service using a specified subcommand.\r\nUsage\r\n$ kubectl create service\r\nservice clusterip\r\nCreate a new ClusterIP service named my-cs\r\nkubectl create service clusterip my-cs --tcp=5678:8080\r\nCreate a new ClusterIP service named my-cs (in headless mode)\r\nkubectl create service clusterip my-cs --clusterip=\"None\"\r\nCreate a ClusterIP service with the specified name.\r\nUsage\r\n$ kubectl create service clusterip NAME [--tcp=\u003cport\u003e:\u003ctargetPort\u003e] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nclusterip\r\nAssign your own ClusterIP or set to 'None' for a 'headless' service\r\n(no loadbalancing).\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 33 of 150\n\nName Shorthand Default Usage\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntcp [] Port pairs can be specified as '\u003cport\u003e:\u003ctargetPort\u003e'.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nservice externalname\r\nCreate a new ExternalName service named my-ns\r\nkubectl create service externalname my-ns --external-name bar.com\r\nCreate an ExternalName service with the specified name.\r\nExternalName service references to an external DNS address instead of only pods, which will allow application\r\nauthors to reference services that exist off platform, on other clusters, or locally.\r\nUsage\r\n$ kubectl create service externalname NAME --external-name external.name [--dry-run=server|client|none]\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 34 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nexternal-name\r\nExternal name of service\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntcp [] Port pairs can be specified as '\u003cport\u003e:\u003ctargetPort\u003e'.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 35 of 150\n\nservice loadbalancer\r\nCreate a new LoadBalancer service named my-lbs\r\nkubectl create service loadbalancer my-lbs --tcp=5678:8080\r\nCreate a LoadBalancer service with the specified name.\r\nUsage\r\n$ kubectl create service loadbalancer NAME [--tcp=port:targetPort] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntcp [] Port pairs can be specified as '\u003cport\u003e:\u003ctargetPort\u003e'.\r\ntemplate Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 36 of 150\n\nName Shorthand Default Usage\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nservice nodeport\r\nCreate a new NodePort service named my-ns\r\nkubectl create service nodeport my-ns --tcp=5678:8080\r\nCreate a NodePort service with the specified name.\r\nUsage\r\n$ kubectl create service nodeport NAME [--tcp=port:targetPort] [--dry-run=server|client|none]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\nnode-port 0 Port used to expose the service on each node in a cluster.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 37 of 150\n\nName Shorthand Default Usage\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntcp [] Port pairs can be specified as '\u003cport\u003e:\u003ctargetPort\u003e'.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nserviceaccount\r\nCreate a new service account named my-service-account\r\nkubectl create serviceaccount my-service-account\r\nCreate a service account with the specified name.\r\nUsage\r\n$ kubectl create serviceaccount NAME [--dry-run=server|client|none]\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 38 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-create\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This flag\r\nis useful when you want to perform kubectl apply on this object in\r\nthe future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\ntoken\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 39 of 150\n\nRequest a token to authenticate to the kube-apiserver as the service account \"myapp\" in the current\r\nnamespace\r\nkubectl create token myapp\r\nRequest a token for a service account in a custom namespace\r\nkubectl create token myapp --namespace myns\r\nRequest a token with a custom expiration\r\nkubectl create token myapp --duration 10m\r\nRequest a token with a custom audience\r\nkubectl create token myapp --audience https://example.com\r\nRequest a token bound to an instance of a Secret object\r\nkubectl create token myapp --bound-object-kind Secret --bound-object-name mysecret\r\nRequest a token bound to an instance of a Secret object with a specific uid\r\nkubectl create token myapp --bound-object-kind Secret --bound-object-name mysecret --bound-object-uid 0d4691ed-Request a service account token.\r\nUsage\r\n$ kubectl create token SERVICE_ACCOUNT_NAME\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\naudience [] Audience of the requested token. If unset, defaults to requesting a\r\ntoken for use with the Kubernetes API server. May be repeated to\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 40 of 150\n\nName Shorthand Default Usage\r\nrequest a token valid for multiple audiences.\r\nbound-object-kindKind of an object to bind the token to. Supported kinds are Pod,\r\nSecret. If set, --bound-object-name must be provided.\r\nbound-object-nameName of an object to bind the token to. The token will expire\r\nwhen the object is deleted. Requires --bound-object-kind.\r\nbound-object-uid\r\nUID of an object to bind the token to. Requires --bound-object-kind and --bound-object-name. If unset, the UID of the existing\r\nobject is used.\r\nduration 0s\r\nRequested lifetime of the issued token. The server may return a\r\ntoken with a longer or shorter lifetime.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nget\r\nList all pods in ps output format\r\nkubectl get pods\r\nList all pods in ps output format with more information (such as node name)\r\nkubectl get pods -o wide\r\nList a single replication controller with specified NAME in ps output format\r\nkubectl get replicationcontroller web\r\nList deployments in JSON output format, in the \"v1\" version of the \"apps\" API group\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 41 of 150\n\nkubectl get deployments.v1.apps -o json\r\nList a single pod in JSON output format\r\nkubectl get -o json pod web-pod-13je7\r\nList a pod identified by type and name specified in \"pod.yaml\" in JSON output format\r\nkubectl get -f pod.yaml -o json\r\nList resources from a directory with kustomization.yaml - e.g. dir/kustomization.yaml\r\nkubectl get -k dir/\r\nReturn only the phase value of the specified pod\r\nkubectl get -o template pod/web-pod-13je7 --template={{.status.phase}}\r\nList resource information in custom columns\r\nkubectl get pod test-pod -o custom-columns=CONTAINER:.spec.containers[0].name,IMAGE:.spec.containers[0].image\r\nList all replication controllers and services together in ps output format\r\nkubectl get rc,services\r\nList one or more resources by their type and names\r\nkubectl get rc/web service/frontend pods/web-pod-13je7\r\nList status subresource for a single pod.\r\nkubectl get pod web-pod-13je7 --subresource status\r\nDisplay one or many resources.\r\nPrints a table of the most important information about the specified resources. You can filter the list using a label\r\nselector and the --selector flag. If the desired resource type is namespaced you will only see results in your current\r\nnamespace unless you pass --all-namespaces.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 42 of 150\n\nBy specifying the output as 'template' and providing a Go template as the value of the --template flag, you can\r\nfilter the attributes of the fetched resources.\r\nUse \"kubectl api-resources\" for a complete list of supported resources.\r\nUsage\r\n$ kubectl get [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file|custom-columns|custom-columns-file|wide] (TYPE[.VERSION][.GROUP] [NAME | -l label] | TYPE[.VERSION][.GROUP]/NAME ...) [flags]\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with --\r\nnamespace.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath output\r\nformats.\r\nchunk-size 500\r\nReturn large lists in chunks rather than all at once. Pass 0 to\r\ndisable. This flag is beta and may change in the future.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.(e.g. --\r\nfield-selector key1=value1,key2=value2). The server only supports\r\na limited number of field queries per type.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nignore-not-found\r\nfalse\r\nIf the requested object does not exist the command will return exit\r\ncode 0.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlabel-columns\r\nL []\r\nAccepts a comma separated list of labels that are going to be\r\npresented as columns. Names are case-sensitive. You can also use\r\nmultiple flag options like -L label1 -L label2...\r\nno-headers false\r\nWhen using the default or custom-column output format, don't\r\nprint headers (default print headers).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 43 of 150\n\nName Shorthand Default Usage\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file, custom-columns, custom-columns-file, wide). See\r\ncustom columns\r\n[https://kubernetes.io/docs/reference/kubectl/#custom-columns],\r\ngolang template [http://golang.org/pkg/text/template/#pkg-overview] and jsonpath template\r\n[https://kubernetes.io/docs/reference/kubectl/jsonpath/].\r\noutput-watch-events\r\nfalse\r\nOutput watch event objects when --watch or --watch-only is used.\r\nExisting objects are output as initial ADDED events.\r\nraw\r\nRaw URI to request from the server. Uses the transport specified by\r\nthe kubeconfig file.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nserver-print true\r\nIf true, have the server return the appropriate table output. Supports\r\nextension APIs and CRDs.\r\nshow-kind false If present, list the resource type for the requested object(s).\r\nshow-labels false\r\nWhen printing, show all labels as the last column (default hide\r\nlabels column)\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nsort-by\r\nIf non-empty, sort list types using this field specification. The field\r\nspecification is expressed as a JSONPath expression (e.g.\r\n'{.metadata.name}'). The field in the API resource specified by this\r\nJSONPath expression must be an integer or a string.\r\nsubresource\r\nIf specified, gets the subresource of the requested object. Must be\r\none of [status scale]. This flag is alpha and may change in the\r\nfuture.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 44 of 150\n\nName Shorthand Default Usage\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nuse-openapi-print-columns\r\nfalse\r\nIf true, use x-kubernetes-print-column metadata (if present) from\r\nthe OpenAPI schema for displaying a resource.\r\nwatch w false After listing/getting the requested object, watch for changes.\r\nwatch-only false\r\nWatch for changes to the requested object(s), without listing/getting\r\nfirst.\r\nrun\r\nStart a nginx pod\r\nkubectl run nginx --image=nginx\r\nStart a hazelcast pod and let the container expose port 5701\r\nkubectl run hazelcast --image=hazelcast/hazelcast --port=5701\r\nStart a hazelcast pod and set environment variables \"DNS_DOMAIN=cluster\" and\r\n\"POD_NAMESPACE=default\" in the container\r\nkubectl run hazelcast --image=hazelcast/hazelcast --env=\"DNS_DOMAIN=cluster\" --env=\"POD_NAMESPACE=default\"\r\nStart a hazelcast pod and set labels \"app=hazelcast\" and \"env=prod\" in the container\r\nkubectl run hazelcast --image=hazelcast/hazelcast --labels=\"app=hazelcast,env=prod\"\r\nDry run; print the corresponding API objects without creating them\r\nkubectl run nginx --image=nginx --dry-run=client\r\nStart a nginx pod, but overload the spec with a partial set of values parsed from JSON\r\nkubectl run nginx --image=nginx --overrides='{ \"apiVersion\": \"v1\", \"spec\": { ... } }'\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 45 of 150\n\nStart a busybox pod and keep it in the foreground, don't restart it if it exits\r\nkubectl run -i -t busybox --image=busybox --restart=Never\r\nStart the nginx pod using the default command, but use custom arguments (arg1 .. argN) for that\r\ncommand\r\nkubectl run nginx --image=nginx -- \u003carg1\u003e \u003carg2\u003e ... \u003cargN\u003e\r\nStart the nginx pod using a different command and custom arguments\r\nkubectl run nginx --image=nginx --command -- \u003ccmd\u003e \u003carg1\u003e ... \u003cargN\u003e\r\nCreate and run a particular image in a pod.\r\nUsage\r\n$ kubectl run NAME --image=image [--env=\"key=value\"] [--port=port] [--dry-run=server|client] [--\r\noverrides=inline-json] [--command] -- [COMMAND] [args...]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nannotations [] Annotations to apply to the pod.\r\nattach false\r\nIf true, wait for the Pod to start running, and then attach to the\r\nPod as if 'kubectl attach ...' were called. Default false, unless '-\r\ni/--stdin' is set, in which case the default is true. With '--\r\nrestart=Never' the exit code of the container process is\r\nreturned.\r\ncascade background\r\nMust be \"background\", \"orphan\", or \"foreground\". Selects the\r\ndeletion cascading strategy for the dependents (e.g. Pods\r\ncreated by a ReplicationController). Defaults to background.\r\ncommand false\r\nIf true and extra arguments are present, use them as the\r\n'command' field in the container, rather than the 'args' field\r\nwhich is the default.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 46 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nenv [] Environment variables to set in the container.\r\nexpose false\r\nIf true, create a ClusterIP service associated with the pod.\r\nRequires --port .\r\nfield-manager\r\nkubectl-run Name of the manager used to track field ownership.\r\nfilename f [] to use to replace the resource.\r\nforce false\r\nIf true, immediately remove resources from API and bypass\r\ngraceful deletion. Note that immediate deletion of some\r\nresources may result in inconsistency or data loss and requires\r\nconfirmation.\r\ngrace-period -1\r\nPeriod of time in seconds given to the resource to terminate\r\ngracefully. Ignored if negative. Set to 1 for immediate\r\nshutdown. Can only be set to 0 when --force is true (force\r\ndeletion).\r\nimage The image for the container to run.\r\nimage-pull-policy\r\nThe image pull policy for the container. If left empty, this\r\nvalue will not be specified by the client and defaulted by the\r\nserver.\r\nkustomize k\r\nProcess a kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlabels l\r\nComma separated labels to apply to the pod. Will override\r\nprevious values.\r\nleave-stdin-open\r\nfalse\r\nIf the pod is started in interactive mode or with stdin, leave\r\nstdin open after the first attach completes. By default, stdin\r\nwill be closed after the first attach completes.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 47 of 150\n\nName Shorthand Default Usage\r\noverride-type\r\nmerge\r\nThe method used to override the generated object: json, merge,\r\nor strategic.\r\noverrides\r\nAn inline JSON override for the generated object. If this is\r\nnon-empty, it is used to override the generated object.\r\nRequires that the object supply a valid apiVersion field.\r\npod-running-timeout\r\n1m0s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to\r\nwait until at least one pod is running\r\nport The port that this container exposes.\r\nprivileged false If true, run the container in privileged mode.\r\nquiet q false If true, suppress prompt messages.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record\r\nthe command. If not set, default to updating the existing\r\nannotation value only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nrestart Always\r\nThe restart policy for this Pod. Legal values [Always,\r\nOnFailure, Never].\r\nrm false\r\nIf true, delete the pod after it exits. Only valid when attaching\r\nto the container, e.g. with '--attach' or with '-i/--stdin'.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\nstdin i false\r\nKeep stdin open on the container in the pod, even if nothing is\r\nattached.\r\ntemplate Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 48 of 150\n\nName Shorthand Default Usage\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntimeout 0s\r\nThe length of time to wait before giving up on a delete, zero\r\nmeans determine a timeout from the size of the object\r\ntty t false Allocate a TTY for the container in the pod.\r\nwait false\r\nIf true, wait for resources to be gone before returning. This\r\nwaits for finalizers.\r\nexpose\r\nCreate a service for a replicated nginx, which serves on port 80 and connects to the containers on port\r\n8000\r\nkubectl expose rc nginx --port=80 --target-port=8000\r\nCreate a service for a replication controller identified by type and name specified in \"nginx-controller.yaml\", which serves on port 80 and connects to the containers on port 8000\r\nkubectl expose -f nginx-controller.yaml --port=80 --target-port=8000\r\nCreate a service for a pod valid-pod, which serves on port 444 with the name \"frontend\"\r\nkubectl expose pod valid-pod --port=444 --name=frontend\r\nCreate a second service based on the above service, exposing the container port 8443 as port 443 with\r\nthe name \"nginx-https\"\r\nkubectl expose service nginx --port=443 --target-port=8443 --name=nginx-https\r\nCreate a service for a replicated streaming application on port 4100 balancing UDP traffic and named\r\n'video-stream'.\r\nkubectl expose rc streamer --port=4100 --protocol=UDP --name=video-stream\r\nCreate a service for a replicated nginx using replica set, which serves on port 80 and connects to the\r\ncontainers on port 8000\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 49 of 150\n\nkubectl expose rs nginx --port=80 --target-port=8000\r\nCreate a service for an nginx deployment, which serves on port 80 and connects to the containers on\r\nport 8000\r\nkubectl expose deployment nginx --port=80 --target-port=8000\r\nExpose a resource as a new Kubernetes service.\r\nLooks up a deployment, service, replica set, replication controller or pod by name and uses the selector for that\r\nresource as the selector for a new service on the specified port. A deployment or replica set will be exposed as a\r\nservice only if its selector is convertible to a selector that service supports, i.e. when the selector contains only the\r\nmatchLabels component. Note that if no port is specified via --port and the exposed resource has multiple ports,\r\nall will be re-used by the new service. Also if no labels are specified, the new service will re-use the labels from\r\nthe resource it exposes.\r\nPossible resources include (case insensitive):\r\npod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs)\r\nUsage\r\n$ kubectl expose (-f FILENAME | TYPE NAME) [--port=port] [--protocol=TCP|UDP|SCTP] [--target-port=number-or-name] [--name=name] [--external-ip=external-ip-of-service] [--type=type]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncluster-ip\r\nClusterIP to be assigned to the service. Leave empty to auto-allocate, or set to 'None' to create a headless service.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nexternal-ip\r\nAdditional external IP address (not managed by Kubernetes) to\r\naccept for the service. If this IP is routed to a node, the service\r\ncan be accessed by this IP in addition to its generated service IP.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 50 of 150\n\nName Shorthand Default Usage\r\nfield-managerkubectl-expose\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nexpose a service\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlabels l Labels to apply to the service created by this call.\r\nload-balancer-ipIP to assign to the LoadBalancer. If empty, an ephemeral IP will\r\nbe created and used (cloud-provider specific).\r\nname The name for the newly created object.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noverride-type\r\nmerge\r\nThe method used to override the generated object: json, merge, or\r\nstrategic.\r\noverrides\r\nAn inline JSON override for the generated object. If this is non-empty, it is used to override the generated object. Requires that\r\nthe object supply a valid apiVersion field.\r\nport\r\nThe port that the service should serve on. Copied from the\r\nresource being exposed, if unspecified\r\nprotocol\r\nThe network protocol for the service to be created. Default is\r\n'TCP'.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 51 of 150\n\nName Shorthand Default Usage\r\nselector\r\nA label selector to use for this service. Only equality-based\r\nselector requirements are supported. If empty (the default) infer\r\nthe selector from the replication controller or replica set.)\r\nsession-affinityIf non-empty, set the session affinity for the service to this; legal\r\nvalues: 'None', 'ClientIP'\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntarget-port\r\nName or number for the port on the container that the service\r\nshould direct traffic to. Optional.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntype\r\nType for this service: ClusterIP, NodePort, LoadBalancer, or\r\nExternalName. Default is 'ClusterIP'.\r\ndelete\r\nDelete a pod using the type and name specified in pod.json\r\nkubectl delete -f ./pod.json\r\nDelete resources from a directory containing kustomization.yaml - e.g. dir/kustomization.yaml\r\nkubectl delete -k dir\r\nDelete resources from all files that end with '.json' - i.e. expand wildcard characters in file names\r\nkubectl delete -f '*.json'\r\nDelete a pod based on the type and name in the JSON passed into stdin\r\ncat pod.json | kubectl delete -f -\r\nDelete pods and services with same names \"baz\" and \"foo\"\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 52 of 150\n\nkubectl delete pod,service baz foo\r\nDelete pods and services with label name=myLabel\r\nkubectl delete pods,services -l name=myLabel\r\nDelete a pod with minimal delay\r\nkubectl delete pod foo --now\r\nForce delete a pod on a dead node\r\nkubectl delete pod foo --force\r\nDelete all pods\r\nkubectl delete pods --all\r\nDelete resources by file names, stdin, resources and names, or by resources and label selector.\r\nJSON and YAML formats are accepted. Only one type of argument may be specified: file names, resources and\r\nnames, or resources and label selector.\r\nSome resources, such as pods, support graceful deletion. These resources define a default period before they are\r\nforcibly terminated (the grace period) but you may override that value with the --grace-period flag, or pass --now\r\nto set a grace-period of 1. Because these resources often represent entities in the cluster, deletion may not be\r\nacknowledged immediately. If the node hosting a pod is down or cannot reach the API server, termination may\r\ntake significantly longer than the grace period. To force delete a resource, you must specify the --force flag. Note:\r\nonly a subset of resources support graceful deletion. In absence of the support, the --grace-period flag is ignored.\r\nIMPORTANT: Force deleting pods does not wait for confirmation that the pod's processes have been terminated,\r\nwhich can leave those processes running until the node detects the deletion and completes graceful deletion. If\r\nyour processes use shared storage or talk to a remote API and depend on the name of the pod to identify\r\nthemselves, force deleting those pods may result in multiple processes running on different machines using the\r\nsame identification which may lead to data corruption or inconsistency. Only force delete pods when you are sure\r\nthe pod is terminated, or if your application can tolerate multiple copies of the same pod running at once. Also, if\r\nyou force delete pods, the scheduler may place new pods on those nodes before the node has released those\r\nresources and causing those pods to be evicted immediately.\r\nNote that the delete command does NOT do resource version checks, so if someone submits an update to a\r\nresource right when you submit a delete, their update will be lost along with the rest of the resource.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 53 of 150\n\nAfter a CustomResourceDefinition is deleted, invalidation of discovery cache may take up to 6 hours. If you don't\r\nwant to wait, you might want to run \"kubectl api-resources\" to refresh the discovery cache.\r\nUsage\r\n$ kubectl delete ([-f FILENAME] | [-k DIRECTORY] | TYPE [(NAME | -l label | --all)])\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nDelete all resources, in the namespace of the specified resource\r\ntypes.\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with\r\n--namespace.\r\ncascade background\r\nMust be \"background\", \"orphan\", or \"foreground\". Selects the\r\ndeletion cascading strategy for the dependents (e.g. Pods\r\ncreated by a ReplicationController). Defaults to background.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.\r\n(e.g. --field-selector key1=value1,key2=value2). The server\r\nonly supports a limited number of field queries per type.\r\nfilename f [] containing the resource to delete.\r\nforce false\r\nIf true, immediately remove resources from API and bypass\r\ngraceful deletion. Note that immediate deletion of some\r\nresources may result in inconsistency or data loss and requires\r\nconfirmation.\r\ngrace-period -1\r\nPeriod of time in seconds given to the resource to terminate\r\ngracefully. Ignored if negative. Set to 1 for immediate\r\nshutdown. Can only be set to 0 when --force is true (force\r\ndeletion).\r\nignore-not-found\r\nfalse\r\nTreat \"resource not found\" as a successful delete. Defaults to\r\n\"true\" when --all is specified.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 54 of 150\n\nName Shorthand Default Usage\r\nkustomize k\r\nProcess a kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nnow false\r\nIf true, resources are signaled for immediate shutdown (same\r\nas --grace-period=1).\r\noutput o\r\nOutput mode. Use \"-o name\" for shorter output\r\n(resource/name).\r\nraw\r\nRaw URI to DELETE to the server. Uses the transport\r\nspecified by the kubeconfig file.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.\r\n(e.g. -l key1=value1,key2=value2). Matching objects must\r\nsatisfy all of the specified label constraints.\r\ntimeout 0s\r\nThe length of time to wait before giving up on a delete, zero\r\nmeans determine a timeout from the size of the object\r\nwait true\r\nIf true, wait for resources to be gone before returning. This\r\nwaits for finalizers.\r\nAPP MANAGEMENT\r\nThis section contains commands for creating, updating, deleting, and viewing your workloads in a Kubernetes\r\ncluster.\r\napply\r\nApply the configuration in pod.json to a pod\r\nkubectl apply -f ./pod.json\r\nApply resources from a directory containing kustomization.yaml - e.g. dir/kustomization.yaml\r\nkubectl apply -k dir/\r\nApply the JSON passed into stdin to a pod\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 55 of 150\n\ncat pod.json | kubectl apply -f -\r\nApply the configuration from all files that end with '.json' - i.e. expand wildcard characters in file names\r\nkubectl apply -f '*.json'\r\nNote: --prune is still in Alpha # Apply the configuration in manifest.yaml that matches label app=nginx\r\nand delete all other resources that are not in the file and match label app=nginx\r\nkubectl apply --prune -f manifest.yaml -l app=nginx\r\nApply the configuration in manifest.yaml and delete all the other config maps that are not in the file\r\nkubectl apply --prune -f manifest.yaml --all --prune-allowlist=core/v1/ConfigMap\r\nApply a configuration to a resource by file name or stdin. The resource name must be specified. This resource will\r\nbe created if it doesn't exist yet. To use 'apply', always create the resource initially with either 'apply' or 'create --\r\nsave-config'.\r\nJSON and YAML formats are accepted.\r\nAlpha Disclaimer: the --prune functionality is not yet complete. Do not use unless you are aware of what the\r\ncurrent state is. See https://issues.k8s.io/34274.\r\nUsage\r\n$ kubectl apply (-f FILENAME | -k DIRECTORY)\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources in the namespace of the specified resource\r\ntypes.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncascade background\r\nMust be \"background\", \"orphan\", or \"foreground\". Selects the\r\ndeletion cascading strategy for the dependents (e.g. Pods\r\ncreated by a ReplicationController). Defaults to background.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 56 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If\r\nserver strategy, submit server-side request without persisting\r\nthe resource.\r\nfield-manager\r\nkubectl-client-side-apply\r\nName of the manager used to track field ownership.\r\nfilename f [] The files that contain the configurations to apply.\r\nforce false\r\nIf true, immediately remove resources from API and bypass\r\ngraceful deletion. Note that immediate deletion of some\r\nresources may result in inconsistency or data loss and requires\r\nconfirmation.\r\nforce-conflicts\r\nfalse\r\nIf true, server-side apply will force the changes against\r\nconflicts.\r\ngrace-period\r\n-1\r\nPeriod of time in seconds given to the resource to terminate\r\ngracefully. Ignored if negative. Set to 1 for immediate\r\nshutdown. Can only be set to 0 when --force is true (force\r\ndeletion).\r\nkustomize k\r\nProcess a kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nopenapi-patch\r\ntrue\r\nIf true, use openapi to calculate diff when the openapi presents\r\nand the resource can be found in the openapi spec. Otherwise,\r\nfall back to use baked-in types.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\noverwrite true\r\nAutomatically resolve conflicts between the modified and live\r\nconfiguration by using values from the modified configuration\r\nprune false\r\nAutomatically delete resource objects, that do not appear in\r\nthe configs and are created by either apply or create --save-config. Should be used with either -l or --all.\r\nprune-allowlist\r\n[]\r\nOverwrite the default allowlist with \u003cgroup/version/kind\u003e for\r\n--prune\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 57 of 150\n\nName Shorthand Default Usage\r\nprune-whitelist\r\n[]\r\nOverwrite the default whitelist with \u003cgroup/version/kind\u003e for\r\n--prune\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record\r\nthe command. If not set, default to updating the existing\r\nannotation value only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.\r\n(e.g. -l key1=value1,key2=value2). Matching objects must\r\nsatisfy all of the specified label constraints.\r\nserver-side false If true, apply runs in the server instead of the client.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in\r\nJSON or YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntimeout 0s\r\nThe length of time to wait before giving up on a delete, zero\r\nmeans determine a timeout from the size of the object\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and\r\nfail the request if invalid. It will perform server side validation\r\nif ServerSideFieldValidation is enabled on the api-server, but\r\nwill fall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled\r\non the API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nwait false\r\nIf true, wait for resources to be gone before returning. This\r\nwaits for finalizers.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 58 of 150\n\nedit-last-applied\r\nEdit the last-applied-configuration annotations by type/name in YAML\r\nkubectl apply edit-last-applied deployment/nginx\r\nEdit the last-applied-configuration annotations by file in JSON\r\nkubectl apply edit-last-applied -f deploy.yaml -o json\r\nEdit the latest last-applied-configuration annotations of resources from the default editor.\r\nThe edit-last-applied command allows you to directly edit any API resource you can retrieve via the command-line tools. It will open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall\r\nback to 'vi' for Linux or 'notepad' for Windows. You can edit multiple objects, although changes are applied one at\r\na time. The command accepts file names as well as command-line arguments, although the files you point to must\r\nbe previously saved versions of resources.\r\nThe default format is YAML. To edit in JSON, specify \"-o json\".\r\nThe flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your\r\noperating system will be used.\r\nIn the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied\r\nchanges. The most common error when updating a resource is another editor changing the resource on the server.\r\nWhen this occurs, you will have to apply your changes to the newer version of the resource, or update your\r\ntemporary saved copy to include the latest resource version.\r\nUsage\r\n$ kubectl apply edit-last-applied (RESOURCE/NAME | -f FILENAME)\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfield-manager\r\nkubectl-client-side-apply\r\nName of the manager used to track field ownership.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 59 of 150\n\nName Shorthand Default Usage\r\nfilename f [] Filename, directory, or URL to files to use to edit the resource\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nwindows-line-endings\r\nfalse Defaults to the line ending native to your platform.\r\nset-last-applied\r\nSet the last-applied-configuration of a resource to match the contents of a file\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 60 of 150\n\nkubectl apply set-last-applied -f deploy.yaml\r\nExecute set-last-applied against each configuration file in a directory\r\nkubectl apply set-last-applied -f path/\r\nSet the last-applied-configuration of a resource to match the contents of a file; will create the annotation\r\nif it does not already exist\r\nkubectl apply set-last-applied -f deploy.yaml --create-annotation=true\r\nSet the latest last-applied-configuration annotations by setting it to match the contents of a file. This results in the\r\nlast-applied-configuration being updated as though 'kubectl apply -f ' was run, without updating any other parts of\r\nthe object.\r\nUsage\r\n$ kubectl apply set-last-applied -f FILENAME\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncreate-annotation\r\nfalse\r\nWill create 'last-applied-configuration' annotations if current\r\nobjects doesn't have one\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfilename f []\r\nFilename, directory, or URL to files that contains the last-applied-configuration annotations\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nshow-managed-false If true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 61 of 150\n\nName Shorthand Default Usage\r\nfields\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nview-last-applied\r\nView the last-applied-configuration annotations by type/name in YAML\r\nkubectl apply view-last-applied deployment/nginx\r\nView the last-applied-configuration annotations by file in JSON\r\nkubectl apply view-last-applied -f deploy.yaml -o json\r\nView the latest last-applied-configuration annotations by type/name or file.\r\nThe default output will be printed to stdout in YAML format. You can use the -o option to change the output\r\nformat.\r\nUsage\r\n$ kubectl apply view-last-applied (TYPE [NAME | -l label] | TYPE/NAME | -f FILENAME)\r\nFlags\r\nName Shorthand Default Usage\r\nall false Select all resources in the namespace of the specified resource types\r\nfilename f []\r\nFilename, directory, or URL to files that contains the last-applied-configuration annotations\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used together\r\nwith -f or -R.\r\noutput o yaml Output format. Must be one of (yaml, json)\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful when\r\nyou want to manage related manifests organized within the same\r\ndirectory.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 62 of 150\n\nName Shorthand Default Usage\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of the\r\nspecified label constraints.\r\nannotate\r\nUpdate pod 'foo' with the annotation 'description' and the value 'my frontend' # If the same annotation is\r\nset multiple times, only the last value will be applied\r\nkubectl annotate pods foo description='my frontend'\r\nUpdate a pod identified by type and name in \"pod.json\"\r\nkubectl annotate -f pod.json description='my frontend'\r\nUpdate pod 'foo' with the annotation 'description' and the value 'my frontend running nginx',\r\noverwriting any existing value\r\nkubectl annotate --overwrite pods foo description='my frontend running nginx'\r\nUpdate all pods in the namespace\r\nkubectl annotate pods --all description='my frontend running nginx'\r\nUpdate pod 'foo' only if the resource is unchanged from version 1\r\nkubectl annotate pods foo description='my frontend running nginx' --resource-version=1\r\nUpdate pod 'foo' by removing an annotation named 'description' if it exists # Does not require the --\r\noverwrite flag\r\nkubectl annotate pods foo description-Update the annotations on one or more resources.\r\nAll Kubernetes objects support the ability to store additional data with the object as annotations. Annotations are\r\nkey/value pairs that can be larger than labels and include arbitrary string values such as structured JSON. Tools\r\nand system extensions may use annotations to store their own data.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 63 of 150\n\nAttempting to set an annotation that already exists will fail unless --overwrite is set. If --resource-version is\r\nspecified and does not match the current resource version on the server the command will fail.\r\nUse \"kubectl api-resources\" for a complete list of supported resources.\r\nUsage\r\n$ kubectl annotate [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified resource\r\ntypes.\r\nall-namespaces\r\nA false If true, check the specified action in all namespaces.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-annotate\r\nName of the manager used to track field ownership.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.(e.g.\r\n--field-selector key1=value1,key2=value2). The server only\r\nsupports a limited number of field queries per type.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nupdate the annotation\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlist false If true, display the annotations for a given resource.\r\nlocal false If true, annotation will NOT contact api-server but run locally.\r\noutput o Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 64 of 150\n\nName Shorthand Default Usage\r\njsonpath-file).\r\noverwrite false\r\nIf true, allow annotations to be overwritten, otherwise reject\r\nannotation updates that overwrite existing annotations.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nresource-version\r\nIf non-empty, the annotation update will only succeed if this is\r\nthe current resource-version for the object. Only valid when\r\nspecifying a single resource.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nautoscale\r\nAuto scale a deployment \"foo\", with the number of pods between 2 and 10, no target CPU utilization\r\nspecified so a default autoscaling policy will be used\r\nkubectl autoscale deployment foo --min=2 --max=10\r\nAuto scale a replication controller \"foo\", with the number of pods between 1 and 5, target CPU\r\nutilization at 80%\r\nkubectl autoscale rc foo --max=5 --cpu-percent=80\r\nCreates an autoscaler that automatically chooses and sets the number of pods that run in a Kubernetes cluster.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 65 of 150\n\nLooks up a deployment, replica set, stateful set, or replication controller by name and creates an autoscaler that\r\nuses the given resource as a reference. An autoscaler can automatically increase or decrease number of pods\r\ndeployed within the system as needed.\r\nUsage\r\n$ kubectl autoscale (-f FILENAME | TYPE NAME | TYPE/NAME) [--min=MINPODS] --max=MAXPODS [--cpu-percent=CPU]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncpu-percent -1\r\nThe target average CPU utilization (represented as a percent of\r\nrequested CPU) over all the pods. If it's not specified or\r\nnegative, a default autoscaling policy will be used.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-managerkubectl-autoscale\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nautoscale.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nmax -1\r\nThe upper limit for the number of pods that can be set by the\r\nautoscaler. Required.\r\nmin -1\r\nThe lower limit for the number of pods that can be set by the\r\nautoscaler. If it's not specified or negative, the server will apply a\r\ndefault value.\r\nname\r\nThe name for the newly created object. If not specified, the name\r\nof the input resource will be used.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 66 of 150\n\nName Shorthand Default Usage\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ndebug\r\nCreate an interactive debugging session in pod mypod and immediately attach to it. # (requires the\r\nEphemeralContainers feature to be enabled in the cluster)\r\nkubectl debug mypod -it --image=busybox\r\nCreate a debug container named debugger using a custom automated debugging image. # (requires the\r\nEphemeralContainers feature to be enabled in the cluster)\r\nkubectl debug --image=myproj/debug-tools -c debugger mypod\r\nCreate a copy of mypod adding a debug container and attach to it\r\nkubectl debug mypod -it --image=busybox --copy-to=my-debugger\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 67 of 150\n\nCreate a copy of mypod changing the command of mycontainer\r\nkubectl debug mypod -it --copy-to=my-debugger --container=mycontainer -- sh\r\nCreate a copy of mypod changing all container images to busybox\r\nkubectl debug mypod --copy-to=my-debugger --set-image=*=busybox\r\nCreate a copy of mypod adding a debug container and changing container images\r\nkubectl debug mypod -it --copy-to=my-debugger --image=debian --set-image=app=app:debug,sidecar=sidecar:debug\r\nCreate an interactive debugging session on a node and immediately attach to it. # The container will run\r\nin the host namespaces and the host's filesystem will be mounted at /host\r\nkubectl debug node/mynode -it --image=busybox\r\nDebug cluster resources using interactive debugging containers.\r\n'debug' provides automation for common debugging tasks for cluster objects identified by resource and name.\r\nPods will be used by default if no resource is specified.\r\nThe action taken by 'debug' varies depending on what resource is specified. Supported actions include:\r\nWorkload: Create a copy of an existing pod with certain attributes changed, for example changing the image tag\r\nto a new version.\r\nWorkload: Add an ephemeral container to an already running pod, for example to add debugging utilities without\r\nrestarting the pod.\r\n* Node: Create a new pod that runs in the node's host namespaces and can access the node's filesystem.\r\nUsage\r\n$ kubectl debug (POD | TYPE[[.VERSION].GROUP]/NAME) [ -- COMMAND [args...] ]\r\nFlags\r\nName Shorthand Default Usage\r\narguments-only\r\nfalse\r\nIf specified, everything after -- will be passed to the new container\r\nas Args instead of Command.\r\nattach false\r\nIf true, wait for the container to start running, and then attach as if\r\n'kubectl attach ...' were called. Default false, unless '-i/--stdin' is\r\nset, in which case the default is true.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 68 of 150\n\nName Shorthand Default Usage\r\ncontainer c Container name to use for debug container.\r\ncopy-to Create a copy of the target Pod with this name.\r\nenv [] Environment variables to set in the container.\r\nimage Container image to use for debug container.\r\nimage-pull-policyThe image pull policy for the container. If left empty, this value\r\nwill not be specified by the client and defaulted by the server.\r\nprofile legacy Debugging profile.\r\nquiet q false If true, suppress informational messages.\r\nreplace false When used with '--copy-to', delete the original Pod.\r\nsame-node false\r\nWhen used with '--copy-to', schedule the copy of target Pod on the\r\nsame node.\r\nset-image []\r\nWhen used with '--copy-to', a list of name=image pairs for\r\nchanging container images, similar to how 'kubectl set image'\r\nworks.\r\nshare-processes\r\ntrue\r\nWhen used with '--copy-to', enable process namespace sharing in\r\nthe copy.\r\nstdin i false\r\nKeep stdin open on the container(s) in the pod, even if nothing is\r\nattached.\r\ntarget\r\nWhen using an ephemeral container, target processes in this\r\ncontainer name.\r\ntty t false Allocate a TTY for the debugging container.\r\ndiff\r\nDiff resources included in pod.json\r\nkubectl diff -f pod.json\r\nDiff file read from stdin\r\ncat service.yaml | kubectl diff -f -\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 69 of 150\n\nDiff configurations specified by file name or stdin between the current online configuration, and the configuration\r\nas it would be if applied.\r\nThe output is always YAML.\r\nKUBECTL_EXTERNAL_DIFF environment variable can be used to select your own diff command. Users can\r\nuse external commands with params too, example: KUBECTL_EXTERNAL_DIFF=\"colordiff -N -u\"\r\nBy default, the \"diff\" command available in your path will be run with the \"-u\" (unified diff) and \"-N\" (treat absent\r\nfiles as empty) options.\r\nExit status: 0 No differences were found. 1 Differences were found. \u003e1 Kubectl or diff failed with an error.\r\nNote: KUBECTL_EXTERNAL_DIFF, if used, is expected to follow that convention.\r\nUsage\r\n$ kubectl diff -f FILENAME\r\nFlags\r\nName Shorthand Default Usage\r\nfield-manager\r\nkubectl-client-side-apply\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files contains the configuration\r\nto diff\r\nforce-conflicts\r\nfalse\r\nIf true, server-side apply will force the changes against\r\nconflicts.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nprune false\r\nInclude resources that would be deleted by pruning. Can be\r\nused with -l and default shows all resources would be pruned\r\nprune-allowlist\r\n[]\r\nOverwrite the default whitelist with \u003cgroup/version/kind\u003e for\r\n--prune\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nselector l Selector (label query) to filter on, supports '=', '==', and '!='.\r\n(e.g. -l key1=value1,key2=value2). Matching objects must\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 70 of 150\n\nName Shorthand Default Usage\r\nsatisfy all of the specified label constraints.\r\nserver-side false If true, apply runs in the server instead of the client.\r\nshow-managed-fields\r\nfalse If true, include managed fields in the diff.\r\nedit\r\nEdit the service named 'registry'\r\nkubectl edit svc/registry\r\nUse an alternative editor\r\nKUBE_EDITOR=\"nano\" kubectl edit svc/registry\r\nEdit the job 'myjob' in JSON using the v1 API format\r\nkubectl edit job.v1.batch/myjob -o json\r\nEdit the deployment 'mydeployment' in YAML and save the modified config in its annotation\r\nkubectl edit deployment/mydeployment -o yaml --save-config\r\nEdit the deployment/mydeployment's status subresource\r\nkubectl edit deployment mydeployment --subresource='status'\r\nEdit a resource from the default editor.\r\nThe edit command allows you to directly edit any API resource you can retrieve via the command-line tools. It\r\nwill open the editor defined by your KUBE_EDITOR, or EDITOR environment variables, or fall back to 'vi' for\r\nLinux or 'notepad' for Windows. You can edit multiple objects, although changes are applied one at a time. The\r\ncommand accepts file names as well as command-line arguments, although the files you point to must be\r\npreviously saved versions of resources.\r\nEditing is done with the API version used to fetch the resource. To edit using a specific API version, fully-qualify\r\nthe resource, version, and group.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 71 of 150\n\nThe default format is YAML. To edit in JSON, specify \"-o json\".\r\nThe flag --windows-line-endings can be used to force Windows line endings, otherwise the default for your\r\noperating system will be used.\r\nIn the event an error occurs while updating, a temporary file will be created on disk that contains your unapplied\r\nchanges. The most common error when updating a resource is another editor changing the resource on the server.\r\nWhen this occurs, you will have to apply your changes to the newer version of the resource, or update your\r\ntemporary saved copy to include the latest resource version.\r\nUsage\r\n$ kubectl edit (RESOURCE/NAME | -f FILENAME)\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfield-managerkubectl-edit\r\nName of the manager used to track field ownership.\r\nfilename f [] Filename, directory, or URL to files to use to edit the resource\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noutput-patch false Output the patch if the resource is edited.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nsave-config false If true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 72 of 150\n\nName Shorthand Default Usage\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\nsubresource\r\nIf specified, edit will operate on the subresource of the requested\r\nobject. Must be one of [status]. This flag is alpha and may\r\nchange in the future.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail\r\nthe request if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nwindows-line-endings\r\nfalse Defaults to the line ending native to your platform.\r\nkustomize\r\nBuild the current working directory\r\nkubectl kustomize\r\nBuild some shared configuration directory\r\nkubectl kustomize /home/config/production\r\nBuild from github\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 73 of 150\n\nkubectl kustomize https://github.com/kubernetes-sigs/kustomize.git/examples/helloWorld?ref=v1.0.6\r\nBuild a set of KRM resources using a 'kustomization.yaml' file. The DIR argument must be a path to a directory\r\ncontaining 'kustomization.yaml', or a git repository URL with a path suffix specifying same with respect to the\r\nrepository root. If DIR is omitted, '.' is assumed.\r\nUsage\r\n$ kubectl kustomize DIR\r\nFlags\r\nName Shorthand Default Usage\r\nas-current-user\r\nfalse\r\nuse the uid and gid of the command executor\r\nto run the function in the container\r\nenable-alpha-plugins\r\nfalse enable kustomize plugins\r\nenable-helm false\r\nEnable use of the Helm chart inflator\r\ngenerator.\r\nenable-managedby-label\r\nfalse enable adding app.kubernetes.io/managed-by\r\nenv e []\r\na list of environment variables to be used by\r\nfunctions\r\nhelm-command\r\nhelm helm command (path to executable)\r\nload-restrictor\r\nLoadRestrictionsRootOnly\r\nif set to 'LoadRestrictionsNone', local\r\nkustomizations may load files from outside\r\ntheir root. This does, however, break the\r\nrelocatability of the kustomization.\r\nmount []\r\na list of storage options read from the\r\nfilesystem\r\nnetwork false\r\nenable network access for functions that\r\ndeclare it\r\nnetwork-name\r\nbridge the docker network to run the container in\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 74 of 150\n\nName Shorthand Default Usage\r\noutput o If specified, write output to this path.\r\nreorder legacy\r\nReorder the resources just before output. Use\r\n'legacy' to apply a legacy reordering\r\n(Namespaces first, Webhooks last, etc). Use\r\n'none' to suppress a final reordering.\r\nlabel\r\nUpdate pod 'foo' with the label 'unhealthy' and the value 'true'\r\nkubectl label pods foo unhealthy=true\r\nUpdate pod 'foo' with the label 'status' and the value 'unhealthy', overwriting any existing value\r\nkubectl label --overwrite pods foo status=unhealthy\r\nUpdate all pods in the namespace\r\nkubectl label pods --all status=unhealthy\r\nUpdate a pod identified by the type and name in \"pod.json\"\r\nkubectl label -f pod.json status=unhealthy\r\nUpdate pod 'foo' only if the resource is unchanged from version 1\r\nkubectl label pods foo status=unhealthy --resource-version=1\r\nUpdate pod 'foo' by removing a label named 'bar' if it exists # Does not require the --overwrite flag\r\nkubectl label pods foo bar-Update the labels on a resource.\r\nA label key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and\r\nunderscores, up to 63 characters each.\r\nOptionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.\r\nIf --overwrite is true, then existing labels can be overwritten, otherwise attempting to overwrite a label will result\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 75 of 150\n\nin an error.\r\nIf --resource-version is specified, then updates will use this resource version, otherwise the existing resource-version will be used.\r\nUsage\r\n$ kubectl label [--overwrite] (-f FILENAME | TYPE NAME) KEY_1=VAL_1 ... KEY_N=VAL_N [--resource-version=version]\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified resource\r\ntypes\r\nall-namespaces\r\nA false If true, check the specified action in all namespaces.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-label\r\nName of the manager used to track field ownership.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.(e.g.\r\n--field-selector key1=value1,key2=value2). The server only\r\nsupports a limited number of field queries per type.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nupdate the labels\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlist false If true, display the labels for a given resource.\r\nlocal false If true, label will NOT contact api-server but run locally.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 76 of 150\n\nName Shorthand Default Usage\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noverwrite false\r\nIf true, allow labels to be overwritten, otherwise reject label\r\nupdates that overwrite existing labels.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nresource-version\r\nIf non-empty, the labels update will only succeed if this is the\r\ncurrent resource-version for the object. Only valid when\r\nspecifying a single resource.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\npatch\r\nPartially update a node using a strategic merge patch, specifying the patch as JSON\r\nkubectl patch node k8s-node-1 -p '{\"spec\":{\"unschedulable\":true}}'\r\nPartially update a node using a strategic merge patch, specifying the patch as YAML\r\nkubectl patch node k8s-node-1 -p $'spec:\\n unschedulable: true'\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 77 of 150\n\nPartially update a node identified by the type and name specified in \"node.json\" using strategic merge\r\npatch\r\nkubectl patch -f node.json -p '{\"spec\":{\"unschedulable\":true}}'\r\nUpdate a container's image; spec.containers[*].name is required because it's a merge key\r\nkubectl patch pod valid-pod -p '{\"spec\":{\"containers\":[{\"name\":\"kubernetes-serve-hostname\",\"image\":\"new image\"}\r\nUpdate a container's image using a JSON patch with positional arrays\r\nkubectl patch pod valid-pod --type='json' -p='[{\"op\": \"replace\", \"path\": \"/spec/containers/0/image\", \"value\":\"n\r\nUpdate a deployment's replicas through the scale subresource using a merge patch.\r\nkubectl patch deployment nginx-deployment --subresource='scale' --type='merge' -p '{\"spec\":{\"replicas\":2}}'\r\nUpdate fields of a resource using strategic merge patch, a JSON merge patch, or a JSON patch.\r\nJSON and YAML formats are accepted.\r\nNote: Strategic merge patch is not supported for custom resources.\r\nUsage\r\n$ kubectl patch (-f FILENAME | TYPE NAME) [-p PATCH|--patch-file FILE]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfield-manager\r\nkubectl-patch\r\nName of the manager used to track field ownership.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 78 of 150\n\nName Shorthand Default Usage\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nupdate\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlocal false\r\nIf true, patch will operate on the content of the file, not the\r\nserver-side resource.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\npatch p The patch to be applied to the resource JSON file.\r\npatch-file A file containing a patch to be applied to the resource.\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If\r\nset to false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\nsubresource\r\nIf specified, patch will operate on the subresource of the\r\nrequested object. Must be one of [status scale]. This flag is alpha\r\nand may change in the future.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntype strategic The type of patch being provided; one of [json merge strategic]\r\nreplace\r\nReplace a pod using the data in pod.json\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 79 of 150\n\nkubectl replace -f ./pod.json\r\nReplace a pod based on the JSON passed into stdin\r\ncat pod.json | kubectl replace -f -\r\nUpdate a single-container pod's image version (tag) to v4\r\nkubectl get pod mypod -o yaml | sed 's/\\(image: myimage\\):.*$/\\1:v4/' | kubectl replace -f -\r\nForce replace, delete and then re-create the resource\r\nkubectl replace --force -f ./pod.json\r\nReplace a resource by file name or stdin.\r\nJSON and YAML formats are accepted. If replacing an existing resource, the complete resource spec must be\r\nprovided. This can be obtained by\r\n$ kubectl get TYPE NAME -o yaml\r\nUsage\r\n$ kubectl replace -f FILENAME\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and\r\njsonpath output formats.\r\ncascade background\r\nMust be \"background\", \"orphan\", or \"foreground\". Selects the\r\ndeletion cascading strategy for the dependents (e.g. Pods\r\ncreated by a ReplicationController). Defaults to background.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If\r\nserver strategy, submit server-side request without persisting\r\nthe resource.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 80 of 150\n\nName Shorthand Default Usage\r\nfield-managerkubectl-replace\r\nName of the manager used to track field ownership.\r\nfilename f [] The files that contain the configurations to replace.\r\nforce false\r\nIf true, immediately remove resources from API and bypass\r\ngraceful deletion. Note that immediate deletion of some\r\nresources may result in inconsistency or data loss and requires\r\nconfirmation.\r\ngrace-period -1\r\nPeriod of time in seconds given to the resource to terminate\r\ngracefully. Ignored if negative. Set to 1 for immediate\r\nshutdown. Can only be set to 0 when --force is true (force\r\ndeletion).\r\nkustomize k\r\nProcess a kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\nraw\r\nRaw URI to PUT to the server. Uses the transport specified by\r\nthe kubeconfig file.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nsave-config false\r\nIf true, the configuration of current object will be saved in its\r\nannotation. Otherwise, the annotation will be unchanged. This\r\nflag is useful when you want to perform kubectl apply on this\r\nobject in the future.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in\r\nJSON or YAML format.\r\nsubresource\r\nIf specified, replace will operate on the subresource of the\r\nrequested object. Must be one of [status scale]. This flag is\r\nalpha and may change in the future.\r\ntemplate Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 81 of 150\n\nName Shorthand Default Usage\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntimeout 0s\r\nThe length of time to wait before giving up on a delete, zero\r\nmeans determine a timeout from the size of the object\r\nvalidate strict\r\nMust be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and\r\nfail the request if invalid. It will perform server side\r\nvalidation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation\r\nif not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled\r\non the API server, and behave as \"ignore\" otherwise.\r\n\"false\" or \"ignore\" will not perform any schema validation,\r\nsilently dropping any unknown or duplicate fields.\r\nwait false\r\nIf true, wait for resources to be gone before returning. This\r\nwaits for finalizers.\r\nrollout\r\nRollback to the previous deployment\r\nkubectl rollout undo deployment/abc\r\nCheck the rollout status of a daemonset\r\nkubectl rollout status daemonset/foo\r\nRestart a deployment\r\nkubectl rollout restart deployment/abc\r\nRestart deployments with the app=nginx label\r\nkubectl rollout restart deployment --selector=app=nginx\r\nManage the rollout of one or many resources.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 82 of 150\n\nValid resource types include:\r\ndeployments\r\ndaemonsets\r\n* statefulsets\r\nUsage\r\n$ kubectl rollout SUBCOMMAND\r\nhistory\r\nView the rollout history of a deployment\r\nkubectl rollout history deployment/abc\r\nView the details of daemonset revision 3\r\nkubectl rollout history daemonset/abc --revision=3\r\nView previous rollout revisions and configurations.\r\nUsage\r\n$ kubectl rollout history (TYPE NAME | TYPE/NAME) [flags]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 83 of 150\n\nName Shorthand Default Usage\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nrevision 0 See the details, including podTemplate of the revision specified\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\npause\r\nMark the nginx deployment as paused # Any current state of the deployment will continue its function;\r\nnew updates # to the deployment will not have an effect as long as the deployment is paused\r\nkubectl rollout pause deployment/nginx\r\nMark the provided resource as paused.\r\nPaused resources will not be reconciled by a controller. Use \"kubectl rollout resume\" to resume a paused resource.\r\nCurrently only deployments support being paused.\r\nUsage\r\n$ kubectl rollout pause RESOURCE\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 84 of 150\n\nName Shorthand Default Usage\r\nfield-managerkubectl-rollout\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nget from a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nrestart\r\nRestart a deployment\r\nkubectl rollout restart deployment/nginx\r\nRestart a daemon set\r\nkubectl rollout restart daemonset/abc\r\nRestart deployments with the app=nginx label\r\nkubectl rollout restart deployment --selector=app=nginx\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 85 of 150\n\nRestart a resource.\r\nResource rollout will be restarted.\r\nUsage\r\n$ kubectl rollout restart RESOURCE\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfield-managerkubectl-rollout\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nget from a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 86 of 150\n\nresume\r\nResume an already paused deployment\r\nkubectl rollout resume deployment/nginx\r\nResume a paused resource.\r\nPaused resources will not be reconciled by a controller. By resuming a resource, we allow it to be reconciled\r\nagain. Currently only deployments support being resumed.\r\nUsage\r\n$ kubectl rollout resume RESOURCE\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfield-managerkubectl-rollout\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nget from a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 87 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nstatus\r\nWatch the rollout status of a deployment\r\nkubectl rollout status deployment/nginx\r\nShow the status of the rollout.\r\nBy default 'rollout status' will watch the status of the latest rollout until it's done. If you don't want to wait for the\r\nrollout to finish then you can use --watch=false. Note that if a new rollout starts in-between, then 'rollout status'\r\nwill continue watching the latest revision. If you want to pin to a specific revision and abort if it is rolled over by\r\nanother revision, use --revision=N where N is the revision you need to watch for.\r\nUsage\r\n$ kubectl rollout status (TYPE NAME | TYPE/NAME) [flags]\r\nFlags\r\nName Shorthand Default Usage\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used together\r\nwith -f or -R.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful when\r\nyou want to manage related manifests organized within the same\r\ndirectory.\r\nrevision 0\r\nPin to a specific revision for showing its status. Defaults to 0 (last\r\nrevision).\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 88 of 150\n\nName Shorthand Default Usage\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of the\r\nspecified label constraints.\r\ntimeout 0s\r\nThe length of time to wait before ending watch, zero means never.\r\nAny other values should contain a corresponding time unit (e.g. 1s,\r\n2m, 3h).\r\nwatch w true Watch the status of the rollout until it's done.\r\nundo\r\nRoll back to the previous deployment\r\nkubectl rollout undo deployment/abc\r\nRoll back to daemonset revision 3\r\nkubectl rollout undo daemonset/abc --to-revision=3\r\nRoll back to the previous deployment with dry-run\r\nkubectl rollout undo --dry-run=server deployment/abc\r\nRoll back to a previous rollout.\r\nUsage\r\n$ kubectl rollout undo (TYPE NAME | TYPE/NAME) [flags]\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 89 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nto-revision 0 The revision to rollback to. Default to 0 (last revision).\r\nscale\r\nScale a replica set named 'foo' to 3\r\nkubectl scale --replicas=3 rs/foo\r\nScale a resource identified by type and name specified in \"foo.yaml\" to 3\r\nkubectl scale --replicas=3 -f foo.yaml\r\nIf the deployment named mysql's current size is 2, scale mysql to 3\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 90 of 150\n\nkubectl scale --current-replicas=2 --replicas=3 deployment/mysql\r\nScale multiple replication controllers\r\nkubectl scale --replicas=5 rc/foo rc/bar rc/baz\r\nScale stateful set named 'web' to 3\r\nkubectl scale --replicas=3 statefulset/web\r\nSet a new size for a deployment, replica set, replication controller, or stateful set.\r\nScale also allows users to specify one or more preconditions for the scale action.\r\nIf --current-replicas or --resource-version is specified, it is validated before the scale is attempted, and it is\r\nguaranteed that the precondition holds true when the scale is sent to the server.\r\nUsage\r\n$ kubectl scale [--resource-version=version] [--current-replicas=count] --replicas=COUNT (-f FILENAME\r\n| TYPE NAME)\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources in the namespace of the specified resource\r\ntypes\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncurrent-replicas\r\n-1\r\nPrecondition for current size. Requires that the current size of the\r\nresource match this value in order to scale. -1 (default) for no\r\ncondition.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to set\r\na new size\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 91 of 150\n\nName Shorthand Default Usage\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nreplicas 0 The new desired number of replicas. Required.\r\nresource-versionPrecondition for resource version. Requires that the current\r\nresource version match this value in order to scale.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntimeout 0s\r\nThe length of time to wait before giving up on a scale operation,\r\nzero means don't wait. Any other values should contain a\r\ncorresponding time unit (e.g. 1s, 2m, 3h).\r\nset\r\nConfigure application resources.\r\nThese commands help you make changes to existing application resources.\r\nUsage\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 92 of 150\n\n$ kubectl set SUBCOMMAND\r\nenv\r\nUpdate deployment 'registry' with a new environment variable\r\nkubectl set env deployment/registry STORAGE_DIR=/local\r\nList the environment variables defined on a deployments 'sample-build'\r\nkubectl set env deployment/sample-build --list\r\nList the environment variables defined on all pods\r\nkubectl set env pods --all --list\r\nOutput modified deployment in YAML, and does not alter the object on the server\r\nkubectl set env deployment/sample-build STORAGE_DIR=/data -o yaml\r\nUpdate all containers in all replication controllers in the project to have ENV=prod\r\nkubectl set env rc --all ENV=prod\r\nImport environment from a secret\r\nkubectl set env --from=secret/mysecret deployment/myapp\r\nImport environment from a config map with a prefix\r\nkubectl set env --from=configmap/myconfigmap --prefix=MYSQL_ deployment/myapp\r\nImport specific keys from a config map\r\nkubectl set env --keys=my-example-key --from=configmap/myconfigmap deployment/myapp\r\nRemove the environment variable ENV from container 'c1' in all deployment configs\r\nkubectl set env deployments --all --containers=\"c1\" ENV-https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 93 of 150\n\nRemove the environment variable ENV from a deployment definition on disk and # update the\r\ndeployment config on the server\r\nkubectl set env -f deploy.json ENV-Set some of the local shell environment into a deployment config on the server\r\nenv | grep RAILS_ | kubectl set env -e - deployment/registry\r\nUpdate environment variables on a pod template.\r\nList environment variable definitions in one or more pods, pod templates. Add, update, or remove container\r\nenvironment variable definitions in one or more pod templates (within replication controllers or deployment\r\nconfigurations). View or modify the environment variable definitions on all containers in the specified pods or pod\r\ntemplates, or just those that match a wildcard.\r\nIf \"--env -\" is passed, environment variables can be read from STDIN using the standard env syntax.\r\nPossible resources include (case insensitive):\r\npod (po), replicationcontroller (rc), deployment (deploy), daemonset (ds), statefulset (sts), cronjob (cj), replicaset\r\n(rs)\r\nUsage\r\n$ kubectl set env RESOURCE/NAME KEY_1=VAL_1 ... KEY_N=VAL_N\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nIf true, select all resources in the namespace of the specified\r\nresource types\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncontainers c *\r\nThe names of containers in the selected pod templates to change -\r\nmay use wildcards\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 94 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nenv e []\r\nSpecify a key-value pair for an environment variable to set into\r\neach container.\r\nfield-managerkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files the resource to update the\r\nenv\r\nfrom\r\nThe name of a resource from which to inject environment\r\nvariables\r\nkeys [] Comma-separated list of keys to import from specified resource\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlist false\r\nIf true, display the environment and any changes in the standard\r\nformat. this flag will removed when we have kubectl view env.\r\nlocal false If true, set env will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noverwrite true\r\nIf true, allow environment to be overwritten, otherwise reject\r\nupdates that overwrite existing environment.\r\nprefix Prefix to append to variable names\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nresolve false\r\nIf true, show secret or configmap references when listing\r\nvariables\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -\r\nl key1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 95 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nimage\r\nSet a deployment's nginx container image to 'nginx:1.9.1', and its busybox container image to 'busybox'\r\nkubectl set image deployment/nginx busybox=busybox nginx=nginx:1.9.1\r\nUpdate all deployments' and rc's nginx container's image to 'nginx:1.9.1'\r\nkubectl set image deployments,rc nginx=nginx:1.9.1 --all\r\nUpdate image of all containers of daemonset abc to 'nginx:1.9.1'\r\nkubectl set image daemonset abc *=nginx:1.9.1\r\nPrint result (in yaml format) of updating nginx container image from local file, without hitting the\r\nserver\r\nkubectl set image -f path/to/file.yaml nginx=nginx:1.9.1 --local -o yaml\r\nUpdate existing container image(s) of resources.\r\nPossible resources include (case insensitive):\r\npod (po), replicationcontroller (rc), deployment (deploy), daemonset (ds), statefulset (sts), cronjob (cj), replicaset\r\n(rs)\r\nUsage\r\n$ kubectl set image (-f FILENAME | TYPE NAME) CONTAINER_NAME_1=CONTAINER_IMAGE_1 ...\r\nCONTAINER_NAME_N=CONTAINER_IMAGE_N\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 96 of 150\n\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified resource\r\ntypes\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlocal false If true, set image will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 97 of 150\n\nName Shorthand Default Usage\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nresources\r\nSet a deployments nginx container cpu limits to \"200m\" and memory to \"512Mi\"\r\nkubectl set resources deployment nginx -c=nginx --limits=cpu=200m,memory=512Mi\r\nSet the resource request and limits for all containers in nginx\r\nkubectl set resources deployment nginx --limits=cpu=200m,memory=512Mi --requests=cpu=100m,memory=256Mi\r\nRemove the resource requests for resources on containers in nginx\r\nkubectl set resources deployment nginx --limits=cpu=0,memory=0 --requests=cpu=0,memory=0\r\nPrint the result (in yaml format) of updating nginx container limits from a local, without hitting the\r\nserver\r\nkubectl set resources -f path/to/file.yaml --limits=cpu=200m,memory=512Mi --local -o yaml\r\nSpecify compute resource requirements (CPU, memory) for any resource that defines a pod template. If a pod is\r\nsuccessfully scheduled, it is guaranteed the amount of resource requested, but may burst up to its specified limits.\r\nFor each compute resource, if a limit is specified and a request is omitted, the request will default to the limit.\r\nPossible resources include (case insensitive): Use \"kubectl api-resources\" for a complete list of supported\r\nresources..\r\nUsage\r\n$ kubectl set resources (-f FILENAME | TYPE NAME) ([--limits=LIMITS \u0026 --requests=REQUESTS]\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified resource\r\ntypes\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 98 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ncontainers c *\r\nThe names of containers in the selected pod templates to change,\r\nall containers are selected by default - may use wildcards\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlimits\r\nThe resource requirement requests for this container. For example,\r\n'cpu=100m,memory=256Mi'. Note that server side components\r\nmay assign requests depending on the server configuration, such\r\nas limit ranges.\r\nlocal false If true, set resources will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nrequests\r\nThe resource requirement requests for this container. For example,\r\n'cpu=100m,memory=256Mi'. Note that server side components\r\nmay assign requests depending on the server configuration, such\r\nas limit ranges.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 99 of 150\n\nName Shorthand Default Usage\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nselector\r\nSet the labels and selector before creating a deployment/service pair\r\nkubectl create service clusterip my-svc --clusterip=\"None\" -o yaml --dry-run=client | kubectl set selector --lo\r\nkubectl create deployment my-dep -o yaml --dry-run=client | kubectl label --local -f - environment=qa -o yaml |\r\nSet the selector on a resource. Note that the new selector will overwrite the old selector if the resource had one\r\nprior to the invocation of 'set selector'.\r\nA selector must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores,\r\nup to 63 characters. If --resource-version is specified, then updates will use this resource version, otherwise the\r\nexisting resource-version will be used. Note: currently selectors can only be set on Service objects.\r\nUsage\r\n$ kubectl set selector (-f FILENAME | TYPE NAME) EXPRESSIONS [--resource-version=version]\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources in the namespace of the specified resource\r\ntypes\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 100 of 150\n\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f [] identifying the resource.\r\nlocal false If true, annotation will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false\r\nRecord current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R true\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nresource-version\r\nIf non-empty, the selectors update will only succeed if this is the\r\ncurrent resource-version for the object. Only valid when\r\nspecifying a single resource.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nserviceaccount\r\nSet deployment nginx-deployment's service account to serviceaccount1\r\nkubectl set serviceaccount deployment nginx-deployment serviceaccount1\r\nPrint the result (in YAML format) of updated nginx deployment with the service account from local file,\r\nwithout hitting the API server\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 101 of 150\n\nkubectl set sa -f nginx-deployment.yaml serviceaccount1 --local --dry-run=client -o yaml\r\nUpdate the service account of pod template resources.\r\nPossible resources (case insensitive) can be:\r\nreplicationcontroller (rc), deployment (deploy), daemonset (ds), job, replicaset (rs), statefulset\r\nUsage\r\n$ kubectl set serviceaccount (-f FILENAME | TYPE NAME) SERVICE_ACCOUNT\r\nFlags\r\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified resource\r\ntypes\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to get\r\nfrom a server.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlocal false\r\nIf true, set serviceaccount will NOT contact api-server but run\r\nlocally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecord false Record current kubectl command in the resource annotation. If set\r\nto false, do not record the command. If set to true, record the\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 102 of 150\n\nName Shorthand Default Usage\r\ncommand. If not set, default to updating the existing annotation\r\nvalue only if one already exists.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nsubject\r\nUpdate a cluster role binding for serviceaccount1\r\nkubectl set subject clusterrolebinding admin --serviceaccount=namespace:serviceaccount1\r\nUpdate a role binding for user1, user2, and group1\r\nkubectl set subject rolebinding admin --user=user1 --user=user2 --group=group1\r\nPrint the result (in YAML format) of updating rolebinding subjects from a local, without hitting the\r\nserver\r\nkubectl create rolebinding admin --role=admin --user=admin -o yaml --dry-run=client | kubectl set subject --loc\r\nUpdate the user, group, or service account in a role binding or cluster role binding.\r\nUsage\r\n$ kubectl set subject (-f FILENAME | TYPE NAME) [--user=username] [--group=groupname] [--\r\nserviceaccount=namespace:serviceaccountname] [--dry-run=server|client|none]\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 103 of 150\n\nName Shorthand Default Usage\r\nall false\r\nSelect all resources, in the namespace of the specified\r\nresource types\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key\r\nis missing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If\r\nserver strategy, submit server-side request without persisting\r\nthe resource.\r\nfield-manager\r\nkubectl-set\r\nName of the manager used to track field ownership.\r\nfilename f []\r\nFilename, directory, or URL to files the resource to update the\r\nsubjects\r\ngroup [] Groups to bind to the role\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nlocal false If true, set subject will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within\r\nthe same directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.\r\n(e.g. -l key1=value1,key2=value2). Matching objects must\r\nsatisfy all of the specified label constraints.\r\nserviceaccount [] Service accounts to bind to the role\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in\r\nJSON or YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 104 of 150\n\nName Shorthand Default Usage\r\nuser [] Usernames to bind to the role\r\nwait\r\nWait for the pod \"busybox1\" to contain the status condition of type \"Ready\"\r\nkubectl wait --for=condition=Ready pod/busybox1\r\nThe default value of status condition is true; you can wait for other targets after an equal delimiter\r\n(compared after Unicode simple case folding, which is a more general form of case-insensitivity):\r\nkubectl wait --for=condition=Ready=false pod/busybox1\r\nWait for the pod \"busybox1\" to contain the status phase to be \"Running\".\r\nkubectl wait --for=jsonpath='{.status.phase}'=Running pod/busybox1\r\nWait for the pod \"busybox1\" to be deleted, with a timeout of 60s, after having issued the \"delete\"\r\ncommand\r\nkubectl delete pod/busybox1\r\nkubectl wait --for=delete pod/busybox1 --timeout=60s\r\nExperimental: Wait for a specific condition on one or many resources.\r\nThe command takes multiple resources and waits until the specified condition is seen in the Status field of every\r\ngiven resource.\r\nAlternatively, the command can wait for the given set of resources to be deleted by providing the \"delete\"\r\nkeyword as the value to the --for flag.\r\nA successful message will be printed to stdout indicating when the specified condition has been met. You can use -\r\no option to change to output destination.\r\nUsage\r\n$ kubectl wait ([-f FILENAME] | resource.group/resource.name | resource.group [(-l label | --all)])\r\n[--for=delete|--for condition=available|--for=jsonpath='{}'=value]\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 105 of 150\n\nName Shorthand Default Usage\r\nall false\r\nSelect all resources in the namespace of the specified resource\r\ntypes\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with --\r\nnamespace.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.(e.g. --\r\nfield-selector key1=value1,key2=value2). The server only\r\nsupports a limited number of field queries per type.\r\nfilename f [] identifying the resource.\r\nfor\r\nThe condition to wait on: [delete|condition=condition-name[=condition-value]|jsonpath='{JSONPath\r\nexpression}'=JSONPath Condition]. The default condition-value\r\nis true. Condition values are compared after Unicode simple case\r\nfolding, which is a more general form of case-insensitivity.\r\nlocal false If true, annotation will NOT contact api-server but run locally.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R true\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2)\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 106 of 150\n\nName Shorthand Default Usage\r\ntimeout 30s\r\nThe length of time to wait before giving up. Zero means check\r\nonce and don't wait, negative means wait for a week.\r\nWORKING WITH APPS\r\nThis section contains commands for inspecting and debugging your applications.\r\nlogs will print the logs from the specified pod + container.\r\nexec can be used to get an interactive shell on a pod + container.\r\ndescribe will print debug information about the given resource.\r\nattach\r\nGet output from running pod mypod; use the 'kubectl.kubernetes.io/default-container' annotation # for\r\nselecting the container to be attached or the first container in the pod will be chosen\r\nkubectl attach mypod\r\nGet output from ruby-container from pod mypod\r\nkubectl attach mypod -c ruby-container\r\nSwitch to raw terminal mode; sends stdin to 'bash' in ruby-container from pod mypod # and sends\r\nstdout/stderr from 'bash' back to the client\r\nkubectl attach mypod -c ruby-container -i -t\r\nGet output from the first pod of a replica set named nginx\r\nkubectl attach rs/nginx\r\nAttach to a process that is already running inside an existing container.\r\nUsage\r\n$ kubectl attach (POD | TYPE/NAME) -c CONTAINER\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 107 of 150\n\nName Shorthand Default Usage\r\ncontainer c\r\nContainer name. If omitted, use the kubectl.kubernetes.io/default-container annotation for selecting the container to be attached or\r\nthe first container in the pod will be chosen\r\npod-running-timeout\r\n1m0s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to wait\r\nuntil at least one pod is running\r\nquiet q false Only print output from the remote session\r\nstdin i false Pass stdin to the container\r\ntty t false Stdin is a TTY\r\nauth\r\nInspect authorization\r\nUsage\r\n$ kubectl auth\r\ncan-i\r\nCheck to see if I can create pods in any namespace\r\nkubectl auth can-i create pods --all-namespaces\r\nCheck to see if I can list deployments in my current namespace\r\nkubectl auth can-i list deployments.apps\r\nCheck to see if I can do everything in my current namespace (\"*\" means all)\r\nkubectl auth can-i '*' '*'\r\nCheck to see if I can get the job named \"bar\" in namespace \"foo\"\r\nkubectl auth can-i list jobs.batch/bar -n foo\r\nCheck to see if I can read pod logs\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 108 of 150\n\nkubectl auth can-i get pods --subresource=log\r\nCheck to see if I can access the URL /logs/\r\nkubectl auth can-i get /logs/\r\nList all allowed actions in namespace \"foo\"\r\nkubectl auth can-i --list --namespace=foo\r\nCheck whether an action is allowed.\r\nVERB is a logical Kubernetes API verb like 'get', 'list', 'watch', 'delete', etc. TYPE is a Kubernetes resource.\r\nShortcuts and groups will be resolved. NONRESOURCEURL is a partial URL that starts with \"/\". NAME is the\r\nname of a particular Kubernetes resource. This command pairs nicely with impersonation. See --as global flag.\r\nUsage\r\n$ kubectl auth can-i VERB [TYPE | TYPE/NAME | NONRESOURCEURL]\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces A false If true, check the specified action in all namespaces.\r\nlist false If true, prints all allowed actions.\r\nno-headers false If true, prints allowed actions without headers\r\nquiet q false If true, suppress output and just return the exit code.\r\nsubresource SubResource such as pod/log or deployment/scale\r\nreconcile\r\nReconcile RBAC resources from a file\r\nkubectl auth reconcile -f my-rbac-rules.yaml\r\nReconciles rules for RBAC role, role binding, cluster role, and cluster role binding objects.\r\nMissing objects are created, and the containing namespace is created for namespaced objects, if required.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 109 of 150\n\nExisting roles are updated to include the permissions in the input objects, and remove extra permissions if --\r\nremove-extra-permissions is specified.\r\nExisting bindings are updated to include the subjects in the input objects, and remove extra subjects if --remove-extra-subjects is specified.\r\nThis is preferred to 'apply' for RBAC resources so that semantically-aware merging of rules and subjects is done.\r\nUsage\r\n$ kubectl auth reconcile -f FILENAME\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nreconcile.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nremove-extra-permissions\r\nfalse If true, removes extra permissions added to roles\r\nremove-extra-subjects\r\nfalse If true, removes extra subjects added to rolebindings\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 110 of 150\n\nName Shorthand Default Usage\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ncp\r\n!!!Important Note!!! # Requires that the 'tar' binary is present in your container # image. If 'tar' is not\r\npresent, 'kubectl cp' will fail. # # For advanced use cases, such as symlinks, wildcard expansion or # file\r\nmode preservation, consider using 'kubectl exec'. # Copy /tmp/foo local file to /tmp/bar in a remote pod\r\nin namespace\r\ntar cf - /tmp/foo | kubectl exec -i -n \u003csome-namespace\u003e \u003csome-pod\u003e -- tar xf - -C /tmp/bar\r\nCopy /tmp/foo from a remote pod to /tmp/bar locally\r\nkubectl exec -n \u003csome-namespace\u003e \u003csome-pod\u003e -- tar cf - /tmp/foo | tar xf - -C /tmp/bar\r\nCopy /tmp/foo_dir local directory to /tmp/bar_dir in a remote pod in the default namespace\r\nkubectl cp /tmp/foo_dir \u003csome-pod\u003e:/tmp/bar_dir\r\nCopy /tmp/foo local file to /tmp/bar in a remote pod in a specific container\r\nkubectl cp /tmp/foo \u003csome-pod\u003e:/tmp/bar -c \u003cspecific-container\u003e\r\nCopy /tmp/foo local file to /tmp/bar in a remote pod in namespace\r\nkubectl cp /tmp/foo \u003csome-namespace\u003e/\u003csome-pod\u003e:/tmp/bar\r\nCopy /tmp/foo from a remote pod to /tmp/bar locally\r\nkubectl cp \u003csome-namespace\u003e/\u003csome-pod\u003e:/tmp/foo /tmp/bar\r\nCopy files and directories to and from containers.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 111 of 150\n\nUsage\r\n$ kubectl cp \u003cfile-spec-src\u003e \u003cfile-spec-dest\u003e\r\nFlags\r\nName Shorthand Default Usage\r\ncontainer c\r\nContainer name. If omitted, use the kubectl.kubernetes.io/default-container annotation for selecting the container to be attached or the\r\nfirst container in the pod will be chosen\r\nno-preserve\r\nfalse\r\nThe copied file/directory's ownership and permissions will not be\r\npreserved in the container\r\nretries 0\r\nSet number of retries to complete a copy operation from a container.\r\nSpecify 0 to disable or any negative value for infinite retrying. The\r\ndefault is 0 (no retry).\r\ndescribe\r\nDescribe a node\r\nkubectl describe nodes kubernetes-node-emt8.c.myproject.internal\r\nDescribe a pod\r\nkubectl describe pods/nginx\r\nDescribe a pod identified by type and name in \"pod.json\"\r\nkubectl describe -f pod.json\r\nDescribe all pods\r\nkubectl describe pods\r\nDescribe pods by label name=myLabel\r\nkubectl describe po -l name=myLabel\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 112 of 150\n\nDescribe all pods managed by the 'frontend' replication controller # (rc-created pods get the name of the\r\nrc as a prefix in the pod name)\r\nkubectl describe pods frontend\r\nShow details of a specific resource or group of resources.\r\nPrint a detailed description of the selected resources, including related resources such as events or controllers. You\r\nmay select a single object by name, all objects of that type, provide a name prefix, or label selector. For example:\r\n$ kubectl describe TYPE NAME_PREFIX\r\nwill first check for an exact match on TYPE and NAME_PREFIX. If no such resource exists, it will output details\r\nfor every resource that has a name prefixed with NAME_PREFIX.\r\nUse \"kubectl api-resources\" for a complete list of supported resources.\r\nUsage\r\n$ kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | -l label] | TYPE/NAME)\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with --\r\nnamespace.\r\nchunk-size 500\r\nReturn large lists in chunks rather than all at once. Pass 0 to\r\ndisable. This flag is beta and may change in the future.\r\nfilename f []\r\nFilename, directory, or URL to files containing the resource to\r\ndescribe\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-events true If true, display events related to the described object.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 113 of 150\n\nevents\r\nList recent events in the default namespace.\r\nkubectl events\r\nList recent events in all namespaces.\r\nkubectl events --all-namespaces\r\nList recent events for the specified pod, then wait for more events and list them as they arrive.\r\nkubectl events --for pod/web-pod-13je7 --watch\r\nList recent events in given format. Supported ones, apart from default, are json and yaml.\r\nkubectl events -oyaml\r\nList recent only events in given event types\r\nkubectl events --types=Warning,Normal\r\nDisplay events\r\nPrints a table of the most important information about events. You can request events for a namespace, for all\r\nnamespace, or filtered to only those pertaining to a specified resource.\r\nUsage\r\n$ kubectl events [(-o|--output=)json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file] [--for TYPE/NAME] [--watch] [--\r\nevent=Normal,Warning]\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with --\r\nnamespace.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 114 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nchunk-size 500\r\nReturn large lists in chunks rather than all at once. Pass 0 to\r\ndisable. This flag is beta and may change in the future.\r\nfor Filter events to only those pertaining to the specified resource.\r\nno-headers false When using the default output format, don't print headers.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ntypes [] Output only events of given types.\r\nwatch w false After listing the requested events, watch for more events.\r\nexec\r\nGet output from running the 'date' command from pod mypod, using the first container by default\r\nkubectl exec mypod -- date\r\nGet output from running the 'date' command in ruby-container from pod mypod\r\nkubectl exec mypod -c ruby-container -- date\r\nSwitch to raw terminal mode; sends stdin to 'bash' in ruby-container from pod mypod # and sends\r\nstdout/stderr from 'bash' back to the client\r\nkubectl exec mypod -c ruby-container -i -t -- bash -il\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 115 of 150\n\nList contents of /usr from the first container of pod mypod and sort by modification time # If the\r\ncommand you want to execute in the pod has any flags in common (e.g. -i), # you must use two dashes\r\n(--) to separate your command's flags/arguments # Also note, do not surround your command and its\r\nflags/arguments with quotes # unless that is how you would execute it normally (i.e., do ls -t /usr, not\r\n\"ls -t /usr\")\r\nkubectl exec mypod -i -t -- ls -t /usr\r\nGet output from running 'date' command from the first pod of the deployment mydeployment, using the\r\nfirst container by default\r\nkubectl exec deploy/mydeployment -- date\r\nGet output from running 'date' command from the first pod of the service myservice, using the first\r\ncontainer by default\r\nkubectl exec svc/myservice -- date\r\nExecute a command in a container.\r\nUsage\r\n$ kubectl exec (POD | TYPE/NAME) [-c CONTAINER] [flags] -- COMMAND [args...]\r\nFlags\r\nName Shorthand Default Usage\r\ncontainer c\r\nContainer name. If omitted, use the kubectl.kubernetes.io/default-container annotation for selecting the container to be attached or\r\nthe first container in the pod will be chosen\r\nfilename f [] to use to exec into the resource\r\npod-running-timeout\r\n1m0s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to wait\r\nuntil at least one pod is running\r\nquiet q false Only print output from the remote session\r\nstdin i false Pass stdin to the container\r\ntty t false Stdin is a TTY\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 116 of 150\n\nlogs\r\nReturn snapshot logs from pod nginx with only one container\r\nkubectl logs nginx\r\nReturn snapshot logs from pod nginx with multi containers\r\nkubectl logs nginx --all-containers=true\r\nReturn snapshot logs from all containers in pods defined by label app=nginx\r\nkubectl logs -l app=nginx --all-containers=true\r\nReturn snapshot of previous terminated ruby container logs from pod web-1\r\nkubectl logs -p -c ruby web-1\r\nBegin streaming the logs of the ruby container in pod web-1\r\nkubectl logs -f -c ruby web-1\r\nBegin streaming the logs from all containers in pods defined by label app=nginx\r\nkubectl logs -f -l app=nginx --all-containers=true\r\nDisplay only the most recent 20 lines of output in pod nginx\r\nkubectl logs --tail=20 nginx\r\nShow all logs from pod nginx written in the last hour\r\nkubectl logs --since=1h nginx\r\nShow logs from a kubelet with an expired serving certificate\r\nkubectl logs --insecure-skip-tls-verify-backend nginx\r\nReturn snapshot logs from first container of a job named hello\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 117 of 150\n\nkubectl logs job/hello\r\nReturn snapshot logs from container nginx-1 of a deployment named nginx\r\nkubectl logs deployment/nginx -c nginx-1\r\nPrint the logs for a container in a pod or specified resource. If the pod has only one container, the container name\r\nis optional.\r\nUsage\r\n$ kubectl logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]\r\nFlags\r\nName Shorthand Default Usage\r\nall-containers false Get all containers' logs in the pod(s).\r\ncontainer c Print the logs of this container\r\nfollow f false Specify if the logs should be streamed.\r\nignore-errors false\r\nIf watching / following pod logs, allow for any errors that occur\r\nto be non-fatal\r\ninsecure-skip-tls-verify-backend\r\nfalse\r\nSkip verifying the identity of the kubelet that logs are requested\r\nfrom. In theory, an attacker could provide invalid log content\r\nback. You might want to use this if your kubelet serving\r\ncertificates have expired.\r\nlimit-bytes 0 Maximum bytes of logs to return. Defaults to no limit.\r\nmax-log-requests\r\n5\r\nSpecify maximum number of concurrent logs to follow when\r\nusing by a selector. Defaults to 5.\r\npod-running-timeout\r\n20s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to wait\r\nuntil at least one pod is running\r\nprefix false\r\nPrefix each log line with the log source (pod name and container\r\nname)\r\nprevious p false\r\nIf true, print the logs for the previous instance of the container\r\nin a pod if it exists.\r\nselector l Selector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 118 of 150\n\nName Shorthand Default Usage\r\nof the specified label constraints.\r\nsince 0s\r\nOnly return logs newer than a relative duration like 5s, 2m, or\r\n3h. Defaults to all logs. Only one of since-time / since may be\r\nused.\r\nsince-time\r\nOnly return logs after a specific date (RFC3339). Defaults to all\r\nlogs. Only one of since-time / since may be used.\r\ntail -1\r\nLines of recent log file to display. Defaults to -1 with no\r\nselector, showing all log lines otherwise 10, if a selector is\r\nprovided.\r\ntimestamps false Include timestamps on each line in the log output\r\nport-forward\r\nListen on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod\r\nkubectl port-forward pod/mypod 5000 6000\r\nListen on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in a pod selected\r\nby the deployment\r\nkubectl port-forward deployment/mydeployment 5000 6000\r\nListen on port 8443 locally, forwarding to the targetPort of the service's port named \"https\" in a pod\r\nselected by the service\r\nkubectl port-forward service/myservice 8443:https\r\nListen on port 8888 locally, forwarding to 5000 in the pod\r\nkubectl port-forward pod/mypod 8888:5000\r\nListen on port 8888 on all addresses, forwarding to 5000 in the pod\r\nkubectl port-forward --address 0.0.0.0 pod/mypod 8888:5000\r\nListen on port 8888 on localhost and selected IP, forwarding to 5000 in the pod\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 119 of 150\n\nkubectl port-forward --address localhost,10.19.21.23 pod/mypod 8888:5000\r\nListen on a random port locally, forwarding to 5000 in the pod\r\nkubectl port-forward pod/mypod :5000\r\nForward one or more local ports to a pod.\r\nUse resource type/name such as deployment/mydeployment to select a pod. Resource type defaults to 'pod' if\r\nomitted.\r\nIf there are multiple pods matching the criteria, a pod will be selected automatically. The forwarding session ends\r\nwhen the selected pod terminates, and a rerun of the command is needed to resume forwarding.\r\nUsage\r\n$ kubectl port-forward TYPE/NAME [options] [LOCAL_PORT:]REMOTE_PORT [...\r\n[LOCAL_PORT_N:]REMOTE_PORT_N]\r\nFlags\r\nName Shorthand Default Usage\r\naddress [localhost]\r\nAddresses to listen on (comma separated). Only accepts IP\r\naddresses or localhost as a value. When localhost is supplied,\r\nkubectl will try to bind on both 127.0.0.1 and ::1 and will fail if\r\nneither of these addresses are available to bind.\r\npod-running-timeout\r\n1m0s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to wait\r\nuntil at least one pod is running\r\nproxy\r\nTo proxy all of the Kubernetes API and nothing else\r\nkubectl proxy --api-prefix=/\r\nTo proxy only part of the Kubernetes API and also some static files # You can get pods info with 'curl\r\nlocalhost:8001/api/v1/pods'\r\nkubectl proxy --www=/my/files --www-prefix=/static/ --api-prefix=/api/\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 120 of 150\n\nTo proxy the entire Kubernetes API at a different root # You can get pods info with 'curl\r\nlocalhost:8001/custom/api/v1/pods'\r\nkubectl proxy --api-prefix=/custom/\r\nRun a proxy to the Kubernetes API server on port 8011, serving static content from ./local/www/\r\nkubectl proxy --port=8011 --www=./local/www/\r\nRun a proxy to the Kubernetes API server on an arbitrary local port # The chosen port for the server\r\nwill be output to stdout\r\nkubectl proxy --port=0\r\nRun a proxy to the Kubernetes API server, changing the API prefix to k8s-api # This makes e.g. the\r\npods API available at localhost:8001/k8s-api/v1/pods/\r\nkubectl proxy --api-prefix=/k8s-api\r\nCreates a proxy server or application-level gateway between localhost and the Kubernetes API server. It also\r\nallows serving static content over specified HTTP path. All incoming data enters through one port and gets\r\nforwarded to the remote Kubernetes API server port, except for the path matching the static content path.\r\nUsage\r\n$ kubectl proxy [--port=PORT] [--www=static-dir] [--www-prefix=prefix] [--api-prefix=prefix]\r\nFlags\r\nName Shorthand Default Usage\r\naccept-hosts\r\n^localhost$,^127.0.0.1$,^[::1]$\r\nRegular expression for hosts that the\r\nproxy should accept.\r\naccept-paths\r\n^.*\r\nRegular expression for paths that the\r\nproxy should accept.\r\naddress 127.0.0.1 The IP address on which to serve on.\r\napi-prefix / Prefix to serve the proxied API under.\r\nappend-server-path\r\nfalse\r\nIf true, enables automatic path\r\nappending of the kube context server\r\npath to each request.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 121 of 150\n\nName Shorthand Default Usage\r\ndisable-filter\r\nfalse\r\nIf true, disable request filtering in the\r\nproxy. This is dangerous, and can leave\r\nyou vulnerable to XSRF attacks, when\r\nused with an accessible port.\r\nkeepalive 0s\r\nkeepalive specifies the keep-alive\r\nperiod for an active network\r\nconnection. Set to 0 to disable\r\nkeepalive.\r\nport p 8001\r\nThe port on which to run the proxy. Set\r\nto 0 to pick a random port.\r\nreject-methods\r\n^$\r\nRegular expression for HTTP methods\r\nthat the proxy should reject (example -\r\n-reject-methods='POST,PUT,PATCH').\r\nreject-paths\r\n^/api/./pods/./exec,^/api/./pods/./attach\r\nRegular expression for paths that the\r\nproxy should reject. Paths specified\r\nhere will be rejected even accepted by\r\n--accept-paths.\r\nunix-socket\r\nu Unix socket on which to run the proxy.\r\nwww w\r\nAlso serve static files from the given\r\ndirectory under the specified prefix.\r\nwww-prefix\r\nP /static/\r\nPrefix to serve static files under, if\r\nstatic file directory is specified.\r\ntop\r\nDisplay Resource (CPU/Memory) usage.\r\nThe top command allows you to see the resource consumption for nodes or pods.\r\nThis command requires Metrics Server to be correctly configured and working on the server.\r\nUsage\r\n$ kubectl top\r\nnode\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 122 of 150\n\nShow metrics for all nodes\r\nkubectl top node\r\nShow metrics for a given node\r\nkubectl top node NODE_NAME\r\nDisplay resource (CPU/memory) usage of nodes.\r\nThe top-node command allows you to see the resource consumption of nodes.\r\nUsage\r\n$ kubectl top node [NAME | -l label]\r\nFlags\r\nName Shorthand Default Usage\r\nno-headers false If present, print output without headers\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-capacity\r\nfalse\r\nPrint node resources based on Capacity instead of\r\nAllocatable(default) of the nodes.\r\nsort-by\r\nIf non-empty, sort nodes list using specified field. The field can be\r\neither 'cpu' or 'memory'.\r\nuse-protocol-buffers\r\ntrue Enables using protocol-buffers to access Metrics API.\r\npod\r\nShow metrics for all pods in the default namespace\r\nkubectl top pod\r\nShow metrics for all pods in the given namespace\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 123 of 150\n\nkubectl top pod --namespace=NAMESPACE\r\nShow metrics for a given pod and its containers\r\nkubectl top pod POD_NAME --containers\r\nShow metrics for the pods defined by label name=myLabel\r\nkubectl top pod -l name=myLabel\r\nDisplay resource (CPU/memory) usage of pods.\r\nThe 'top pod' command allows you to see the resource consumption of pods.\r\nDue to the metrics pipeline delay, they may be unavailable for a few minutes since pod creation.\r\nUsage\r\n$ kubectl top pod [NAME | -l label]\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces\r\nA false\r\nIf present, list the requested object(s) across all namespaces.\r\nNamespace in current context is ignored even if specified with --\r\nnamespace.\r\ncontainers false If present, print usage of containers within a pod.\r\nfield-selector\r\nSelector (field query) to filter on, supports '=', '==', and '!='.(e.g. --\r\nfield-selector key1=value1,key2=value2). The server only\r\nsupports a limited number of field queries per type.\r\nno-headers false If present, print output without headers.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -\r\nl key1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nsort-by\r\nIf non-empty, sort pods list using specified field. The field can be\r\neither 'cpu' or 'memory'.\r\nsum false Print the sum of the resource usage\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 124 of 150\n\nName Shorthand Default Usage\r\nuse-protocol-buffers\r\ntrue Enables using protocol-buffers to access Metrics API.\r\nCLUSTER MANAGEMENT\r\napi-versions\r\nPrint the supported API versions\r\nkubectl api-versions\r\nPrint the supported API versions on the server, in the form of \"group/version\".\r\nUsage\r\n$ kubectl api-versions\r\napi-resources\r\nPrint the supported API resources\r\nkubectl api-resources\r\nPrint the supported API resources with more information\r\nkubectl api-resources -o wide\r\nPrint the supported API resources sorted by a column\r\nkubectl api-resources --sort-by=name\r\nPrint the supported namespaced resources\r\nkubectl api-resources --namespaced=true\r\nPrint the supported non-namespaced resources\r\nkubectl api-resources --namespaced=false\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 125 of 150\n\nPrint the supported API resources with a specific APIGroup\r\nkubectl api-resources --api-group=rbac.authorization.k8s.io\r\nPrint the supported API resources on the server.\r\nUsage\r\n$ kubectl api-resources\r\nFlags\r\nName Shorthand Default Usage\r\napi-group Limit to resources in the specified API group.\r\ncached false Use the cached list of resources if available.\r\ncategories [] Limit to resources that belong the the specified categories.\r\nnamespaced true\r\nIf false, non-namespaced resources will be returned, otherwise\r\nreturning namespaced resources by default.\r\nno-headers false\r\nWhen using the default or custom-column output format, don't print\r\nheaders (default print headers).\r\noutput o Output format. One of: (wide, name).\r\nsort-by\r\nIf non-empty, sort list of resources using specified field. The field\r\ncan be either 'name' or 'kind'.\r\nverbs [] Limit to resources that support the specified verbs.\r\ncertificate\r\nModify certificate resources.\r\nUsage\r\n$ kubectl certificate SUBCOMMAND\r\napprove\r\nApprove CSR 'csr-sqgzp'\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 126 of 150\n\nkubectl certificate approve csr-sqgzp\r\nApprove a certificate signing request.\r\nkubectl certificate approve allows a cluster admin to approve a certificate signing request (CSR). This action tells\r\na certificate signing controller to issue a certificate to the requestor with the attributes requested in the CSR.\r\nSECURITY NOTICE: Depending on the requested attributes, the issued certificate can potentially grant a\r\nrequester access to cluster resources or to authenticate as a requested identity. Before approving a CSR, ensure\r\nyou understand what the signed certificate can do.\r\nUsage\r\n$ kubectl certificate approve (-f FILENAME | NAME)\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nupdate\r\nforce false Update the CSR even if it is already approved.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 127 of 150\n\nName Shorthand Default Usage\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ndeny\r\nDeny CSR 'csr-sqgzp'\r\nkubectl certificate deny csr-sqgzp\r\nDeny a certificate signing request.\r\nkubectl certificate deny allows a cluster admin to deny a certificate signing request (CSR). This action tells a\r\ncertificate signing controller to not to issue a certificate to the requestor.\r\nUsage\r\n$ kubectl certificate deny (-f FILENAME | NAME)\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nfilename f []\r\nFilename, directory, or URL to files identifying the resource to\r\nupdate\r\nforce false Update the CSR even if it is already denied.\r\nkustomize k\r\nProcess the kustomization directory. This flag can't be used\r\ntogether with -f or -R.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nrecursive R false\r\nProcess the directory used in -f, --filename recursively. Useful\r\nwhen you want to manage related manifests organized within the\r\nsame directory.\r\nshow-managed-false If true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 128 of 150\n\nName Shorthand Default Usage\r\nfields\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ncluster-info\r\nPrint the address of the control plane and cluster services\r\nkubectl cluster-info\r\nDisplay addresses of the control plane and services with label kubernetes.io/cluster-service=true. To further debug\r\nand diagnose cluster problems, use 'kubectl cluster-info dump'.\r\nUsage\r\n$ kubectl cluster-info\r\ndump\r\nDump current cluster state to stdout\r\nkubectl cluster-info dump\r\nDump current cluster state to /path/to/cluster-state\r\nkubectl cluster-info dump --output-directory=/path/to/cluster-state\r\nDump all namespaces to stdout\r\nkubectl cluster-info dump --all-namespaces\r\nDump a set of namespaces to /path/to/cluster-state\r\nkubectl cluster-info dump --namespaces default,kube-system --output-directory=/path/to/cluster-state\r\nDump cluster information out suitable for debugging and diagnosing cluster problems. By default, dumps\r\neverything to stdout. You can optionally specify a directory with --output-directory. If you specify a directory,\r\nKubernetes will build a set of files in that directory. By default, only dumps things in the current namespace and\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 129 of 150\n\n'kube-system' namespace, but you can switch to a different namespace with the --namespaces flag, or specify --all-namespaces to dump all namespaces.\r\nThe command also dumps the logs of all of the pods in the cluster; these logs are dumped into different directories\r\nbased on namespace and pod name.\r\nUsage\r\n$ kubectl cluster-info dump\r\nFlags\r\nName Shorthand Default Usage\r\nall-namespaces\r\nA false If true, dump all namespaces. If true, --namespaces is ignored.\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nnamespaces [] A comma separated list of namespaces to dump.\r\noutput o json\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noutput-directoryWhere to output the files. If empty or '-' uses stdout, otherwise\r\ncreates a directory hierarchy in that directory\r\npod-running-timeout\r\n20s\r\nThe length of time (like 5s, 2m, or 3h, higher than zero) to wait\r\nuntil at least one pod is running\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON\r\nor YAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\ncordon\r\nMark node \"foo\" as unschedulable\r\nkubectl cordon foo\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 130 of 150\n\nMark node as unschedulable.\r\nUsage\r\n$ kubectl cordon NODE\r\nFlags\r\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print the\r\nobject that would be sent, without sending it. If server strategy, submit\r\nserver-side request without persisting the resource.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of the\r\nspecified label constraints.\r\ndrain\r\nDrain node \"foo\", even if there are pods not managed by a replication controller, replica set, job,\r\ndaemon set or stateful set on it\r\nkubectl drain foo --force\r\nAs above, but abort if there are pods not managed by a replication controller, replica set, job, daemon\r\nset or stateful set, and use a grace period of 15 minutes\r\nkubectl drain foo --grace-period=900\r\nDrain node in preparation for maintenance.\r\nThe given node will be marked unschedulable to prevent new pods from arriving. 'drain' evicts the pods if the API\r\nserver supports https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ eviction\r\nhttps://kubernetes.io/docs/concepts/workloads/pods/disruptions/ . Otherwise, it will use normal DELETE to delete\r\nthe pods. The 'drain' evicts or deletes all pods except mirror pods (which cannot be deleted through the API\r\nserver). If there are daemon set-managed pods, drain will not proceed without --ignore-daemonsets, and regardless\r\nit will not delete any daemon set-managed pods, because those pods would be immediately replaced by the\r\ndaemon set controller, which ignores unschedulable markings. If there are any pods that are neither mirror pods\r\nnor managed by a replication controller, replica set, daemon set, stateful set, or job, then drain will not delete any\r\npods unless you use --force. --force will also allow deletion to proceed if the managing resource of one or more\r\npods is missing.\r\n'drain' waits for graceful termination. You should not operate on the machine until the command completes.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 131 of 150\n\nWhen you are ready to put the node back into service, use kubectl uncordon, which will make the node\r\nschedulable again.\r\nhttps://kubernetes.io/images/docs/kubectl_drain.svg Workflowhttps://kubernetes.io/images/docs/kubectl_drain.svg\r\nUsage\r\n$ kubectl drain NODE\r\nFlags\r\nName Shorthand Default Usage\r\nchunk-size 500\r\nReturn large lists in chunks rather than all at once. Pass 0 to\r\ndisable. This flag is beta and may change in the future.\r\ndelete-emptydir-data\r\nfalse\r\nContinue even if there are pods using emptyDir (local data that\r\nwill be deleted when the node is drained).\r\ndelete-local-data\r\nfalse\r\nContinue even if there are pods using emptyDir (local data that\r\nwill be deleted when the node is drained).\r\ndisable-eviction\r\nfalse\r\nForce drain to use delete, even if eviction is supported. This will\r\nbypass checking PodDisruptionBudgets, use with caution.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only\r\nprint the object that would be sent, without sending it. If server\r\nstrategy, submit server-side request without persisting the\r\nresource.\r\nforce false Continue even if there are pods that do not declare a controller.\r\ngrace-period -1\r\nPeriod of time in seconds given to each pod to terminate\r\ngracefully. If negative, the default value specified in the pod will\r\nbe used.\r\nignore-daemonsets\r\nfalse Ignore DaemonSet-managed pods.\r\npod-selector Label selector to filter pods on the node\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g.\r\n-l key1=value1,key2=value2). Matching objects must satisfy all\r\nof the specified label constraints.\r\nskip-wait-for-delete-timeout\r\n0\r\nIf pod DeletionTimestamp older than N seconds, skip waiting\r\nfor the pod. Seconds must be greater than 0 to skip.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 132 of 150\n\nName Shorthand Default Usage\r\ntimeout 0s The length of time to wait before giving up, zero means infinite\r\ntaint\r\nUpdate node 'foo' with a taint with key 'dedicated' and value 'special-user' and effect 'NoSchedule' # If a\r\ntaint with that key and effect already exists, its value is replaced as specified\r\nkubectl taint nodes foo dedicated=special-user:NoSchedule\r\nRemove from node 'foo' the taint with key 'dedicated' and effect 'NoSchedule' if one exists\r\nkubectl taint nodes foo dedicated:NoSchedule-Remove from node 'foo' all the taints with key 'dedicated'\r\nkubectl taint nodes foo dedicated-Add a taint with key 'dedicated' on nodes having label mylabel=X\r\nkubectl taint node -l myLabel=X dedicated=foo:PreferNoSchedule\r\nAdd to node 'foo' a taint with key 'bar' and no value\r\nkubectl taint nodes foo bar:NoSchedule\r\nUpdate the taints on one or more nodes.\r\nA taint consists of a key, value, and effect. As an argument here, it is expressed as key=value:effect.\r\nThe key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up\r\nto 253 characters.\r\nOptionally, the key can begin with a DNS subdomain prefix and a single '/', like example.com/my-app.\r\nThe value is optional. If given, it must begin with a letter or number, and may contain letters, numbers, hyphens,\r\ndots, and underscores, up to 63 characters.\r\nThe effect must be NoSchedule, PreferNoSchedule or NoExecute.\r\nCurrently taint can only apply to node.\r\nUsage\r\n$ kubectl taint NODE NAME KEY_1=VAL_1:TAINT_EFFECT_1 ... KEY_N=VAL_N:TAINT_EFFECT_N\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 133 of 150\n\nFlags\r\nName Shorthand Default Usage\r\nall false Select all nodes in the cluster\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print\r\nthe object that would be sent, without sending it. If server strategy,\r\nsubmit server-side request without persisting the resource.\r\nfield-managerkubectl-taint\r\nName of the manager used to track field ownership.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\noverwrite false\r\nIf true, allow taints to be overwritten, otherwise reject taint updates\r\nthat overwrite existing taints.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of\r\nthe specified label constraints.\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nvalidate strict Must be one of: strict (or true), warn, ignore (or false).\r\n\"true\" or \"strict\" will use a schema to validate the input and fail the\r\nrequest if invalid. It will perform server side validation if\r\nServerSideFieldValidation is enabled on the api-server, but will\r\nfall back to less reliable client-side validation if not.\r\n\"warn\" will warn about unknown or duplicate fields without\r\nblocking the request if server-side field validation is enabled on\r\nthe API server, and behave as \"ignore\" otherwise.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 134 of 150\n\nName Shorthand Default Usage\r\n\"false\" or \"ignore\" will not perform any schema validation, silently\r\ndropping any unknown or duplicate fields.\r\nuncordon\r\nMark node \"foo\" as schedulable\r\nkubectl uncordon foo\r\nMark node as schedulable.\r\nUsage\r\n$ kubectl uncordon NODE\r\nFlags\r\nName Shorthand Default Usage\r\ndry-run none\r\nMust be \"none\", \"server\", or \"client\". If client strategy, only print the\r\nobject that would be sent, without sending it. If server strategy, submit\r\nserver-side request without persisting the resource.\r\nselector l\r\nSelector (label query) to filter on, supports '=', '==', and '!='.(e.g. -l\r\nkey1=value1,key2=value2). Matching objects must satisfy all of the\r\nspecified label constraints.\r\nKUBECTL SETTINGS AND USAGE\r\nalpha\r\nThese commands correspond to alpha features that are not enabled in Kubernetes clusters by default.\r\nUsage\r\n$ kubectl alpha\r\nauth\r\nInspect authorization\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 135 of 150\n\nUsage\r\n$ kubectl alpha auth\r\nauth whoami\r\nGet your subject attributes.\r\nkubectl alpha auth whoami\r\nGet your subject attributes in JSON format.\r\nkubectl alpha auth whoami -o json\r\nExperimental: Check who you are and your attributes (groups, extra).\r\nThis command is helpful to get yourself aware of the current user attributes, especially when dynamic\r\nauthentication, e.g., token webhook, auth proxy, or OIDC provider, is enabled in the Kubernetes cluster.\r\nUsage\r\n$ kubectl alpha auth whoami\r\nFlags\r\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\noutput o\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 136 of 150\n\ncompletion\r\nInstalling bash completion on macOS using homebrew ## If running Bash 3.2 included with macOS\r\nbrew install bash-completion\r\nor, if running Bash 4.1+\r\nbrew install bash-completion@2\r\nIf kubectl is installed via homebrew, this should start working immediately ## If you've installed via\r\nother means, you may need add the completion to your completion directory\r\nkubectl completion bash \u003e $(brew --prefix)/etc/bash_completion.d/kubectl\r\nInstalling bash completion on Linux ## If bash-completion is not installed on Linux, install the 'bash-completion' package ## via your distribution's package manager. ## Load the kubectl completion code\r\nfor bash into the current shell\r\nsource \u003c(kubectl completion bash)\r\nWrite bash completion code to a file and source it from .bash_profile\r\nkubectl completion bash \u003e ~/.kube/completion.bash.inc\r\nprintf \"\r\nKubectl shell completion\r\nsource '$HOME/.kube/completion.bash.inc'\r\n\" \u003e\u003e $HOME/.bash_profile\r\nsource $HOME/.bash_profile\r\nLoad the kubectl completion code for zsh[1] into the current shell\r\nsource \u003c(kubectl completion zsh)\r\nSet the kubectl completion code for zsh[1] to autoload on startup\r\nkubectl completion zsh \u003e \"${fpath[1]}/_kubectl\"\r\nLoad the kubectl completion code for fish[2] into the current shell\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 137 of 150\n\nkubectl completion fish | source\r\nTo load completions for each session, execute once:\r\nkubectl completion fish \u003e ~/.config/fish/completions/kubectl.fish\r\nLoad the kubectl completion code for powershell into the current shell\r\nkubectl completion powershell | Out-String | Invoke-Expression\r\nSet kubectl completion code for powershell to run on startup ## Save completion code to a script and\r\nexecute in the profile\r\nkubectl completion powershell \u003e $HOME\\.kube\\completion.ps1\r\nAdd-Content $PROFILE \"$HOME\\.kube\\completion.ps1\"\r\nExecute completion code in the profile\r\nAdd-Content $PROFILE \"if (Get-Command kubectl -ErrorAction SilentlyContinue) {\r\nkubectl completion powershell | Out-String | Invoke-Expression\r\n}\"\r\nAdd completion code directly to the $PROFILE script\r\nkubectl completion powershell \u003e\u003e $PROFILE\r\nUsage\r\n$ kubectl completion SHELL\r\nconfig\r\nModify kubeconfig files using subcommands like \"kubectl config set current-context my-context\"\r\nThe loading order follows these rules:\r\n1. If the --kubeconfig flag is set, then only that file is loaded. The flag may only be set once and no merging takes\r\nplace.\r\n2. If $KUBECONFIG environment variable is set, then it is used as a list of paths (normal path delimiting rules\r\nfor your system). These paths are merged. When a value is modified, it is modified in the file that defines the\r\nstanza. When a value is created, it is created in the first file that exists. If no files in the chain exist, then it creates\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 138 of 150\n\nthe last file in the list.\r\n3. Otherwise, ${HOME}/.kube/config is used and no merging takes place.\r\nUsage\r\n$ kubectl config SUBCOMMAND\r\nFlags\r\nName Shorthand Default Usage\r\nkubeconfig use a particular kubeconfig file\r\ncurrent-context\r\nDisplay the current-context\r\nkubectl config current-context\r\nDisplay the current-context.\r\nUsage\r\n$ kubectl config current-context\r\ndelete-cluster\r\nDelete the minikube cluster\r\nkubectl config delete-cluster minikube\r\nDelete the specified cluster from the kubeconfig.\r\nUsage\r\n$ kubectl config delete-cluster NAME\r\ndelete-context\r\nDelete the context for the minikube cluster\r\nkubectl config delete-context minikube\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 139 of 150\n\nDelete the specified context from the kubeconfig.\r\nUsage\r\n$ kubectl config delete-context NAME\r\ndelete-user\r\nDelete the minikube user\r\nkubectl config delete-user minikube\r\nDelete the specified user from the kubeconfig.\r\nUsage\r\n$ kubectl config delete-user NAME\r\nget-clusters\r\nList the clusters that kubectl knows about\r\nkubectl config get-clusters\r\nDisplay clusters defined in the kubeconfig.\r\nUsage\r\n$ kubectl config get-clusters\r\nget-contexts\r\nList all the contexts in your kubeconfig file\r\nkubectl config get-contexts\r\nDescribe one context in your kubeconfig file\r\nkubectl config get-contexts my-context\r\nDisplay one or many contexts from the kubeconfig file.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 140 of 150\n\nUsage\r\n$ kubectl config get-contexts [(-o|--output=)name)]\r\nFlags\r\nName Shorthand Default Usage\r\nno-headers\r\nfalse\r\nWhen using the default or custom-column output format, don't print\r\nheaders (default print headers).\r\noutput o Output format. One of: (name).\r\nget-users\r\nList the users that kubectl knows about\r\nkubectl config get-users\r\nDisplay users defined in the kubeconfig.\r\nUsage\r\n$ kubectl config get-users\r\nrename-context\r\nRename the context 'old-name' to 'new-name' in your kubeconfig file\r\nkubectl config rename-context old-name new-name\r\nRenames a context from the kubeconfig file.\r\nCONTEXT_NAME is the context name that you want to change.\r\nNEW_NAME is the new name you want to set.\r\nNote: If the context being renamed is the 'current-context', this field will also be updated.\r\nUsage\r\n$ kubectl config rename-context CONTEXT_NAME NEW_NAME\r\nset\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 141 of 150\n\nSet the server field on the my-cluster cluster to https://1.2.3.4\r\nkubectl config set clusters.my-cluster.server https://1.2.3.4\r\nSet the certificate-authority-data field on the my-cluster cluster\r\nkubectl config set clusters.my-cluster.certificate-authority-data $(echo \"cert_data_here\" | base64 -i -)\r\nSet the cluster field in the my-context context to my-cluster\r\nkubectl config set contexts.my-context.cluster my-cluster\r\nSet the client-key-data field in the cluster-admin user using --set-raw-bytes option\r\nkubectl config set users.cluster-admin.client-key-data cert_data_here --set-raw-bytes=true\r\nSet an individual value in a kubeconfig file.\r\nPROPERTY_NAME is a dot delimited name where each token represents either an attribute name or a map key.\r\nMap keys may not contain dots.\r\nPROPERTY_VALUE is the new value you want to set. Binary fields such as 'certificate-authority-data' expect a\r\nbase64 encoded string unless the --set-raw-bytes flag is used.\r\nSpecifying an attribute name that already exists will merge new fields on top of existing values.\r\nUsage\r\n$ kubectl config set PROPERTY_NAME PROPERTY_VALUE\r\nFlags\r\nName Shorthand Default Usage\r\nset-raw-bytes\r\nfalse\r\nWhen writing a []byte PROPERTY_VALUE, write the given string\r\ndirectly without base64 decoding.\r\nset-cluster\r\nSet only the server field on the e2e cluster entry without touching other values\r\nkubectl config set-cluster e2e --server=https://1.2.3.4\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 142 of 150\n\nEmbed certificate authority data for the e2e cluster entry\r\nkubectl config set-cluster e2e --embed-certs --certificate-authority=~/.kube/e2e/kubernetes.ca.crt\r\nDisable cert checking for the e2e cluster entry\r\nkubectl config set-cluster e2e --insecure-skip-tls-verify=true\r\nSet custom TLS server name to use for validation for the e2e cluster entry\r\nkubectl config set-cluster e2e --tls-server-name=my-cluster-name\r\nSet proxy url for the e2e cluster entry\r\nkubectl config set-cluster e2e --proxy-url=https://1.2.3.4\r\nSet a cluster entry in kubeconfig.\r\nSpecifying a name that already exists will merge new fields on top of existing values for those fields.\r\nUsage\r\n$ kubectl config set-cluster NAME [--server=server] [--certificate-authority=path/to/certificate/authority] [--insecure-skip-tls-verify=true] [--tls-server-name=example.com]\r\nFlags\r\nName Shorthand Default Usage\r\ncertificate-authority\r\nPath to certificate-authority file for the cluster entry in\r\nkubeconfig\r\nembed-certs false embed-certs for the cluster entry in kubeconfig\r\ninsecure-skip-tls-verify\r\nfalse insecure-skip-tls-verify for the cluster entry in kubeconfig\r\nproxy-url proxy-url for the cluster entry in kubeconfig\r\nserver server for the cluster entry in kubeconfig\r\ntls-server-name tls-server-name for the cluster entry in kubeconfig\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 143 of 150\n\nset-context\r\nSet the user field on the gce context entry without touching other values\r\nkubectl config set-context gce --user=cluster-admin\r\nSet a context entry in kubeconfig.\r\nSpecifying a name that already exists will merge new fields on top of existing values for those fields.\r\nUsage\r\n$ kubectl config set-context [NAME | --current] [--cluster=cluster_nickname] [--user=user_nickname]\r\n[--namespace=namespace]\r\nFlags\r\nName Shorthand Default Usage\r\ncluster cluster for the context entry in kubeconfig\r\ncurrent false Modify the current context\r\nnamespace namespace for the context entry in kubeconfig\r\nuser user for the context entry in kubeconfig\r\nset-credentials\r\nSet only the \"client-key\" field on the \"cluster-admin\" # entry, without touching other values\r\nkubectl config set-credentials cluster-admin --client-key=~/.kube/admin.key\r\nSet basic auth for the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --username=admin --password=uXFGweU9l35qcif\r\nEmbed client certificate data in the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --client-certificate=~/.kube/admin.crt --embed-certs=true\r\nEnable the Google Compute Platform auth provider for the \"cluster-admin\" entry\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 144 of 150\n\nkubectl config set-credentials cluster-admin --auth-provider=gcp\r\nEnable the OpenID Connect auth provider for the \"cluster-admin\" entry with additional args\r\nkubectl config set-credentials cluster-admin --auth-provider=oidc --auth-provider-arg=client-id=foo --auth-prov\r\nRemove the \"client-secret\" config value for the OpenID Connect auth provider for the \"cluster-admin\"\r\nentry\r\nkubectl config set-credentials cluster-admin --auth-provider=oidc --auth-provider-arg=client-secret-Enable new exec auth plugin for the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --exec-command=/path/to/the/executable --exec-api-version=client.a\r\nDefine new exec auth plugin args for the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --exec-arg=arg1 --exec-arg=arg2\r\nCreate or update exec auth plugin environment variables for the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --exec-env=key1=val1 --exec-env=key2=val2\r\nRemove exec auth plugin environment variables for the \"cluster-admin\" entry\r\nkubectl config set-credentials cluster-admin --exec-env=var-to-remove-Set a user entry in kubeconfig.\r\nSpecifying a name that already exists will merge new fields on top of existing values.\r\nClient-certificate flags: --client-certificate=certfile --client-key=keyfile\r\nBearer token flags: --token=bearer_token\r\nBasic auth flags: --username=basic_user --password=basic_password\r\nBearer token and basic auth are mutually exclusive.\r\nUsage\r\n$ kubectl config set-credentials NAME [--client-certificate=path/to/certfile] [--client-key=path/to/keyfile] [--token=bearer_token] [--username=basic_user] [--password=basic_password] [--\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 145 of 150\n\nauth-provider=provider_name] [--auth-provider-arg=key=value] [--exec-command=exec_command] [--exec-api-version=exec_api_version] [--exec-arg=arg] [--exec-env=key=value]\r\nFlags\r\nName Shorthand Default Usage\r\nauth-provider Auth provider for the user entry in kubeconfig\r\nauth-provider-arg\r\n[] 'key=value' arguments for the auth provider\r\nclient-certificate\r\nPath to client-certificate file for the user entry in kubeconfig\r\nclient-key Path to client-key file for the user entry in kubeconfig\r\nembed-certs false Embed client cert/key for the user entry in kubeconfig\r\nexec-api-versionAPI version of the exec credential plugin for the user entry in\r\nkubeconfig\r\nexec-arg []\r\nNew arguments for the exec credential plugin command for the\r\nuser entry in kubeconfig\r\nexec-commandCommand for the exec credential plugin for the user entry in\r\nkubeconfig\r\nexec-env [] 'key=value' environment values for the exec credential plugin\r\npassword password for the user entry in kubeconfig\r\ntoken token for the user entry in kubeconfig\r\nusername username for the user entry in kubeconfig\r\nunset\r\nUnset the current-context\r\nkubectl config unset current-context\r\nUnset namespace in foo context\r\nkubectl config unset contexts.foo.namespace\r\nUnset an individual value in a kubeconfig file.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 146 of 150\n\nPROPERTY_NAME is a dot delimited name where each token represents either an attribute name or a map key.\r\nMap keys may not contain dots.\r\nUsage\r\n$ kubectl config unset PROPERTY_NAME\r\nuse-context\r\nUse the context for the minikube cluster\r\nkubectl config use-context minikube\r\nSet the current-context in a kubeconfig file.\r\nUsage\r\n$ kubectl config use-context CONTEXT_NAME\r\nview\r\nShow merged kubeconfig settings\r\nkubectl config view\r\nShow merged kubeconfig settings and raw certificate data and exposed secrets\r\nkubectl config view --raw\r\nGet the password for the e2e user\r\nkubectl config view -o jsonpath='{.users[?(@.name == \"e2e\")].user.password}'\r\nDisplay merged kubeconfig settings or a specified kubeconfig file.\r\nYou can use --output jsonpath={...} to extract specific values using a jsonpath expression.\r\nUsage\r\n$ kubectl config view\r\nFlags\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 147 of 150\n\nName Shorthand Default Usage\r\nallow-missing-template-keys\r\ntrue\r\nIf true, ignore any errors in templates when a field or map key is\r\nmissing in the template. Only applies to golang and jsonpath\r\noutput formats.\r\nflatten false\r\nFlatten the resulting kubeconfig file into self-contained output\r\n(useful for creating portable kubeconfig files)\r\nmerge true Merge the full hierarchy of kubeconfig files\r\nminify false\r\nRemove all information not used by current-context from the\r\noutput\r\noutput o yaml\r\nOutput format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json,\r\njsonpath-file).\r\nraw false Display raw byte data and sensitive data\r\nshow-managed-fields\r\nfalse\r\nIf true, keep the managedFields when printing objects in JSON or\r\nYAML format.\r\ntemplate\r\nTemplate string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang\r\ntemplates [http://golang.org/pkg/text/template/#pkg-overview].\r\nexplain\r\nGet the documentation of the resource and its fields\r\nkubectl explain pods\r\nGet the documentation of a specific field of a resource\r\nkubectl explain pods.spec.containers\r\nList the fields for supported resources.\r\nThis command describes the fields associated with each supported API resource. Fields are identified via a simple\r\nJSONPath identifier:\r\n\u003ctype\u003e.\u003cfieldName\u003e[.\u003cfieldName\u003e]\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 148 of 150\n\nAdd the --recursive flag to display all of the fields at once without descriptions. Information about each field is\r\nretrieved from the server in OpenAPI format.\r\nUse \"kubectl api-resources\" for a complete list of supported resources.\r\nUsage\r\n$ kubectl explain RESOURCE\r\nFlags\r\nName Shorthand Default Usage\r\napi-versionGet different explanations for particular API version (API\r\ngroup/version)\r\nrecursive false Print the fields of fields (Currently only 1 level deep)\r\noptions\r\nPrint flags inherited by all commands\r\nkubectl options\r\nPrint the list of flags inherited by all commands\r\nUsage\r\n$ kubectl options\r\nplugin\r\nUsage\r\n$ kubectl plugin [flags]\r\nlist\r\nList all available plugins\r\nkubectl plugin list\r\nList all available plugin files on a user's PATH.\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 149 of 150\n\nAvailable plugin files are those that are: - executable - anywhere on the user's PATH - begin with \"kubectl-\"\r\nUsage\r\n$ kubectl plugin list\r\nFlags\r\nName Shorthand Default Usage\r\nname-only\r\nfalse\r\nIf true, display only the binary name of each plugin, rather than its\r\nfull path\r\nversion\r\nPrint the client and server versions for the current context\r\nkubectl version\r\nPrint the client and server version information for the current context.\r\nUsage\r\n$ kubectl version\r\nFlags\r\nName Shorthand Default Usage\r\nclient false If true, shows client version only (no server required).\r\noutput o One of 'yaml' or 'json'.\r\nshort false If true, print just the version number.\r\nSource: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nhttps://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info\r\nPage 150 of 150",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"origins": [
		"web"
	],
	"references": [
		"https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#cluster-info"
	],
	"report_names": [
		"kubectl-commands#cluster-info"
	],
	"threat_actors": [
		{
			"id": "eb3f4e4d-2573-494d-9739-1be5141cf7b2",
			"created_at": "2022-10-25T16:07:24.471018Z",
			"updated_at": "2026-04-10T02:00:05.002374Z",
			"deleted_at": null,
			"main_name": "Cron",
			"aliases": [],
			"source_name": "ETDA:Cron",
			"tools": [
				"Catelites",
				"Catelites Bot",
				"CronBot",
				"TinyZBot"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "2864e40a-f233-4618-ac61-b03760a41cbb",
			"created_at": "2023-12-01T02:02:34.272108Z",
			"updated_at": "2026-04-10T02:00:04.97558Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "ETDA:WildCard",
			"tools": [
				"RustDown",
				"SysJoker"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "256a6a2d-e8a2-4497-b399-628a7fad4b3e",
			"created_at": "2023-11-30T02:00:07.299845Z",
			"updated_at": "2026-04-10T02:00:03.484788Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "MISPGALAXY:WildCard",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		}
	],
	"ts_created_at": 1775434526,
	"ts_updated_at": 1775826742,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/21c1f26d63d26e693d2109cf391d1909bf9abac9.pdf",
		"text": "https://archive.orkl.eu/21c1f26d63d26e693d2109cf391d1909bf9abac9.txt",
		"img": "https://archive.orkl.eu/21c1f26d63d26e693d2109cf391d1909bf9abac9.jpg"
	}
}