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

NAME

9       kubectl create service nodeport - Create a NodePort service
10
11
12

SYNOPSIS

14       kubectl create service nodeport [OPTIONS]
15
16
17

DESCRIPTION

19       Create a NodePort service 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       --node-port=0       Port  used  to expose the service on each node in a
40       cluster.
41
42
43       -o, --output=""      Output format. One of: (json, yaml, name,  go-tem‐
44       plate, go-template-file, template, templatefile, jsonpath, jsonpath-as-
45       json, jsonpath-file).
46
47
48       --save-config=false      If true, the configuration of  current  object
49       will  be saved in its annotation. Otherwise, the annotation will be un‐
50       changed. This flag is useful when you want to perform kubectl apply  on
51       this object in the future.
52
53
54       --show-managed-fields=false       If  true, keep the managedFields when
55       printing objects in JSON or YAML format.
56
57
58       --tcp=[]      Port pairs can be specified as ':'.
59
60
61       --template=""      Template string or path to template file to use when
62       -o=go-template, -o=go-template-file. The template format is golang tem‐
63       plates [http://golang.org/pkg/text/template/#pkg-overview].
64
65
66       --validate="strict"      Must be one of: strict (or true), warn, ignore
67       (or false).            "true" or "strict" will use a schema to validate
68       the input and fail the request if invalid. It will perform server  side
69       validation  if  ServerSideFieldValidation is enabled on the api-server,
70       but will fall back to less  reliable  client-side  validation  if  not.
71                 "warn"  will  warn  about unknown or duplicate fields without
72       blocking the request if server-side field validation is enabled on  the
73       API  server,  and  behave  as "ignore" otherwise.            "false" or
74       "ignore" will not perform any schema validation, silently dropping  any
75       unknown or duplicate fields.
76
77
78

OPTIONS INHERITED FROM PARENT COMMANDS

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

EXAMPLE

178                # Create a new NodePort service named my-ns
179                kubectl create service nodeport my-ns --tcp=5678:8080
180
181
182
183

SEE ALSO

185       kubectl-create-service(1),
186
187
188

HISTORY

190       January  2015,  Originally compiled by Eric Paris (eparis at redhat dot
191       com) based on the kubernetes source material, but hopefully  they  have
192       been automatically generated since!
193
194
195
196Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum