kubectl-create-namespace(1)

1KUBERNETES(1)(kubernetes)                            KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7

NAME

9       kubectl create namespace - Create a namespace with the specified name
10
11
12

SYNOPSIS

14       kubectl create namespace [OPTIONS]
15
16
17

DESCRIPTION

19       Create a namespace with the specified name.
20
21
22

OPTIONS

24       --allow-missing-template-keys=true       If  true, ignore any errors in
25       templates when a field or map key is missing in the template. Only  ap‐
26       plies to golang and jsonpath output formats.
27
28
29       --dry-run="none"       Must be "none", "server", or "client". If client
30       strategy, only print the object that would be sent, without sending it.
31       If  server  strategy, submit server-side request without persisting the
32       resource.
33
34
35       --field-manager="kubectl-create"      Name of the manager used to track
36       field ownership.
37
38
39       -o,  --output=""      Output format. One of: (json, yaml, name, go-tem‐
40       plate, go-template-file, template, templatefile, jsonpath, jsonpath-as-
41       json, jsonpath-file).
42
43
44       --save-config=false       If  true, the configuration of current object
45       will be saved in its annotation. Otherwise, the annotation will be  un‐
46       changed.  This flag is useful when you want to perform kubectl apply on
47       this object in the future.
48
49
50       --show-managed-fields=false      If true, keep the  managedFields  when
51       printing objects in JSON or YAML format.
52
53
54       --template=""      Template string or path to template file to use when
55       -o=go-template, -o=go-template-file. The template format is golang tem‐
56       plates [http://golang.org/pkg/text/template/#pkg-overview].
57
58
59       --validate="strict"      Must be one of: strict (or true), warn, ignore
60       (or false).            "true" or "strict" will use a schema to validate
61       the  input and fail the request if invalid. It will perform server side
62       validation if ServerSideFieldValidation is enabled on  the  api-server,
63       but  will  fall  back  to  less reliable client-side validation if not.
64                 "warn" will warn about unknown or  duplicate  fields  without
65       blocking  the request if server-side field validation is enabled on the
66       API server, and behave as  "ignore"  otherwise.             "false"  or
67       "ignore"  will not perform any schema validation, silently dropping any
68       unknown or duplicate fields.
69
70
71

OPTIONS INHERITED FROM PARENT COMMANDS

73       --as=""      Username to impersonate for the operation. User could be a
74       regular user or a service account in a namespace.
75
76
77       --as-group=[]       Group  to  impersonate for the operation, this flag
78       can be repeated to specify multiple groups.
79
80
81       --as-uid=""      UID to impersonate for the operation.
82
83
84       --azure-container-registry-config=""      Path to the  file  containing
85       Azure container registry configuration information.
86
87
88       --cache-dir="/builddir/.kube/cache"      Default cache directory
89
90
91       --certificate-authority=""      Path to a cert file for the certificate
92       authority
93
94
95       --client-certificate=""      Path to a client certificate file for TLS
96
97
98       --client-key=""      Path to a client key file for TLS
99
100
101       --cluster=""      The name of the kubeconfig cluster to use
102
103
104       --context=""      The name of the kubeconfig context to use
105
106
107       --insecure-skip-tls-verify=false      If true, the server's certificate
108       will not be checked for validity. This will make your HTTPS connections
109       insecure
110
111
112       --kubeconfig=""      Path to the kubeconfig file to  use  for  CLI  re‐
113       quests.
114
115
116       --match-server-version=false        Require  server  version  to  match
117       client version
118
119
120       -n, --namespace=""      If present, the namespace scope  for  this  CLI
121       request
122
123
124       --password=""      Password for basic authentication to the API server
125
126
127       --profile="none"         Name   of   profile   to   capture.   One   of
128       (none|cpu|heap|goroutine|threadcreate|block|mutex)
129
130
131       --profile-output="profile.pprof"      Name of the  file  to  write  the
132       profile to
133
134
135       --request-timeout="0"       The length of time to wait before giving up
136       on a single server request. Non-zero values  should  contain  a  corre‐
137       sponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't time‐
138       out requests.
139
140
141       -s, --server=""      The address and port of the Kubernetes API server
142
143
144       --tls-server-name=""      Server name to  use  for  server  certificate
145       validation.  If  it  is  not provided, the hostname used to contact the
146       server is used
147
148
149       --token=""      Bearer token for authentication to the API server
150
151
152       --user=""      The name of the kubeconfig user to use
153
154
155       --username=""      Username for basic authentication to the API server
156
157
158       --version=false      Print version information and quit
159
160
161       --warnings-as-errors=false      Treat warnings received from the server
162       as errors and exit with a non-zero exit code
163
164
165

EXAMPLE

167                # Create a new namespace named my-namespace
168                kubectl create namespace my-namespace
169
170
171
172

HISTORY

179       January  2015,  Originally compiled by Eric Paris (eparis at redhat dot
180       com) based on the kubernetes source material, but hopefully  they  have
181       been automatically generated since!
182
183
184
185Manuals                              User            KUBERNETES(1)(kubernetes)