openshift-start-kubernetes-apiserver man page

openshift start kubernetes apiserver — Launch Kubernetes apiserver (kube-apiserver)


openshift start kubernetes apiserver [Options]


Start Kubernetes apiserver

This command launches an instance of the Kubernetes apiserver (kube-apiserver).



DEPRECATED: see --insecure-bind-address instead.


Ordered list of plug-ins to do admission control of resources into cluster. Comma-delimited list of: AlwaysAdmit, AlwaysDeny, AlwaysPullImages, BuildByStrategy, ClusterResourceOverride, DefaultStorageClass, DenyEscalatingExec, DenyExecOnPrivileged, ExternalIPRanger, ImagePolicyWebhook, InitialResources, LimitPodHardAntiAffinityTopology, LimitRanger, NamespaceAutoProvision, NamespaceExists, NamespaceLifecycle, OriginNamespaceLifecycle, OriginPodNodeEnvironment, OwnerReferencesPermissionEnforcement, PersistentVolumeLabel, PodNodeConstraints, PodNodeSelector, PodSecurityPolicy, ProjectRequestLimit, ResourceQuota, RunOnceDuration, SCCExecRestrictions, SecurityContextConstraint, SecurityContextDeny, ServiceAccount,,,,,,,,,


File with admission control configuration.


The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.


If true, allow privileged containers.


Enables anonymous requests to the secure port of the API server. Requests that are not rejected by another authentication method are treated as anonymous requests. Anonymous requests have a username of system:anonymous, and a group name of system:unauthenticated.


The number of apiservers running in the cluster.


The maximum number of days to retain old audit log files based on the timestamp encoded in their filename.


The maximum number of old audit log files to retain.


The maximum size in megabytes of the audit log file before it gets rotated. Defaults to 100MB.


If set, all requests coming to the apiserver will be logged to this file.


The duration to cache responses from the webhook token authenticator. Default is 2m.


File with webhook configuration for token authentication in kubeconfig format. The API server will query the remote service to determine authentication for bearer tokens.


Ordered list of plug-ins to do authorization on secure port. Comma-delimited list of: AlwaysAllow,AlwaysDeny,ABAC,Webhook,RBAC.


File with authorization policy in csv format, used with --authorization-mode=ABAC, on the secure port.


If specified, a username which avoids RBAC authorization checks and role binding privilege escalation checks, to be used with --authorization-mode=RBAC.


The duration to cache 'authorized' responses from the webhook authorizer. Default is 5m.


The duration to cache 'unauthorized' responses from the webhook authorizer. Default is 30s.


File with webhook configuration in kubeconfig format, used with --authorization-mode=Webhook. The API server will query the remote service to determine access on the API server's secure port.


If set, the file that will be used to admit requests to the secure port of the API server via http basic authentication.


The IP address on which to listen for the --secure-port port. The associated interface(s) must be reachable by the rest of the cluster, and by CLI/web clients. If blank, all interfaces will be used (


The directory where the TLS certs are located (by default /var/run/kubernetes). If --tls-cert-file and --tls-private-key-file are provided, this flag will be ignored.


If set, any request presenting a client certificate signed by one of the authorities in the client-ca-file is authenticated with an identity corresponding to the CommonName of the client certificate.


The path to the cloud provider configuration file. Empty string for no configuration file.


The provider for cloud services. Empty string for no provider.


Enable contention profiling. Requires --profiling to be set to work.


List of allowed origins for CORS, comma separated.  An allowed origin can be a regular expression to support subdomain matching. If this list is empty CORS will not be enabled.


Number of workers spawned for DeleteCollection call. These are used to speed up namespace cleanup.


Number of deserialized json objects to cache in memory.


Enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-controller-manager.


Enables swagger ui on the apiserver at /swagger-ui


SSL Certificate Authority file used to secure etcd communication.


SSL certification file used to secure etcd communication.


SSL key file used to secure etcd communication.


The prefix for all resource paths in etcd.


If true, enable quorum read.


List of etcd servers to connect with (scheme://ip:port), comma separated.


Per-resource etcd servers overrides, comma separated. The individual override format: group/resource#servers, where servers are  ⟨http://ip:port⟩, semicolon separated.


Amount of time to retain events. Default is 1h.


If set, the Keystone server's certificate will be verified by one of the authorities in the experimental-keystone-ca-file, otherwise the host's root CA set will be used.


If passed, activates the keystone authentication plugin.


The hostname to use when generating externalized URLs for this master (e.g. Swagger API Docs).


A set of key=value pairs that describe feature gates for alpha/experimental features. Options are: AllAlpha=true|false (ALPHA - default=false) AllowExtTrafficLocalEndpoints=true|false (BETA - default=true) AppArmor=true|false (BETA - default=true) DynamicKubeletConfig=true|false (ALPHA - default=false) DynamicVolumeProvisioning=true|false (ALPHA - default=true) ExperimentalHostUserNamespaceDefaulting=true|false (ALPHA - default=false) StreamingProxyRedirects=true|false (ALPHA - default=false)


If set, your server will be INSECURE.  Any token will be allowed and user information will be parsed from the token as username/group1,group2


The IP address on which to serve the --insecure-port (set to for all interfaces). Defaults to localhost.


The port on which to serve unsecured, unauthenticated access. Default 8080. It is assumed that firewall rules are set up such that this port is not reachable from outside of the cluster and that port 443 on the cluster's public address is proxied to this port. This is performed by nginx in the default setup.


Path to a cert file for the certificate authority.


Path to a client cert file for TLS.


Path to a client key file for TLS.


Use https for kubelet connections.


DEPRECATED: kubelet port.


List of the preferred NodeAddressTypes to use for kubelet connections.


Timeout for kubelet operations.


If non-zero, the Kubernetes master service (which apiserver creates/maintains) will be of type NodePort, using this as the value of the port. If zero, the Kubernetes master service will be of type ClusterIP.


A regular expression matching long running requests which should be excluded from maximum inflight request handling.


DEPRECATED: the namespace from which the kubernetes master services should be injected into pods.


If non-zero, throttle each user connection to this number of bytes/sec. Currently only applies to long-running requests.


The maximum number of requests in flight at a given time. When the server exceeds this, it rejects requests. Zero for no limit.


An optional field indicating the minimum number of seconds a handler must keep a request open before timing it out. Currently only honored by the watch request handler, which picks a randomized value above this number as the connection timeout, to spread out load.


If set, the OpenID server's certificate will be verified by one of the authorities in the oidc-ca-file, otherwise the host's root CA set will be used.


The client ID for the OpenID Connect client, must be set if oidc-issuer-url is set.


If provided, the name of a custom OpenID Connect claim for specifying user groups. The claim value is expected to be a string or array of strings. This flag is experimental, please see the authentication documentation for further details.


The URL of the OpenID issuer, only HTTPS scheme will be accepted. If set, it will be used to verify the OIDC JSON Web Token (JWT).


The OpenID claim to use as the user name. Note that claims other than the default ('sub') is not guaranteed to be unique and immutable. This flag is experimental, please see the authentication documentation for further details.


DEPRECATED: see --insecure-port instead.


DEPRECATED: see --service-cluster-ip-range instead.


Enable profiling via web interface host:port/debug/pprof/


DEPRECATED: see --bind-address instead.


If true, server will do its best to fix the update request to pass the validation, e.g., setting empty UID in update request to its existing value. This flag can be turned off after we fix all the clients that send malformed updates.


List of client certificate common names to allow to provide usernames in headers specified by --requestheader-username-headers. If empty, any client certificate validated by the authorities in --requestheader-client-ca-file is allowed.


Root certificate bundle to use to verify client certificates on incoming requests before trusting usernames in headers specified by --requestheader-username-headers


List of request headers to inspect for usernames. X-Remote-User is common.


A set of key=value pairs that describe runtime configuration that may be passed to apiserver. apis/<groupVersion> key can be used to turn on/off specific api versions. apis/<groupVersion>/<resource> can be used to turn on/off specific resources. api/all and api/legacy are special keys to control all and legacy api versions respectively.


The port on which to serve HTTPS with authentication and authorization. If 0, don't serve HTTPS at all.


File containing PEM-encoded x509 RSA or ECDSA private or public keys, used to verify ServiceAccount tokens. If unspecified, --tls-private-key-file is used. The specified file can contain multiple keys, and the flag can be specified multiple times with different files.


If true, validate ServiceAccount tokens exist in etcd as part of authentication.


A CIDR notation IP range from which to assign service cluster IPs. This must not overlap with any IP ranges assigned to nodes for pods.


A port range to reserve for services with NodePort visibility. Example: '30000-32767'. Inclusive at both ends of the range.


DEPRECATED: see --service-node-port-range instead


If non-empty, use secure SSH proxy to the nodes, using this user keyfile


If non-empty, use secure SSH proxy to the nodes, using this user name


The storage backend for persistence. Options: 'etcd2' (default), 'etcd3'.


The media type to use to store objects in storage. Defaults to application/json. Some resources may only support a specific media type and will ignore this setting.


DEPRECATED: the version to store the legacy v1 resources with. Defaults to server preferred.


The per-group version to store resources in. Specified in the format "group1/version1,group2/version2,...". In the case where objects are moved from one group to the other, you may specify the format "group1=group2/v1beta1,group3/v1beta1,...". You only need to pass the groups you wish to change from the defaults. It defaults to a list of preferred versions of all registered groups, which is derived from the KUBE_API_VERSIONS environment variable.


Memory limit for apiserver in MB (used to configure sizes of caches, etc.)


If set, this certificate authority will used for secure access from Admission Controllers. This must be a valid PEM-encoded CA bundle.


File containing the default x509 Certificate for HTTPS. (CA cert, if any, concatenated after server cert). If HTTPS serving is enabled, and --tls-cert-file and --tls-private-key-file are not provided, a self-signed certificate and key are generated for the public address and saved to /var/run/kubernetes.


File containing the default x509 private key matching --tls-cert-file.


A pair of x509 certificate and private key file paths, optionally suffixed with a list of domain patterns which are fully qualified domain names, possibly with prefixed wildcard segments. If no domain patterns are provided, the names of the certificate are extracted. Non-wildcard matches trump over wildcard matches, explicit domain patterns trump over extracted names. For multiple key/certificate pairs, use the --tls-sni-cert-key multiple times. Examples: "example.key,example.crt" or "*,,foo.crt".


If set, the file that will be used to secure the secure port of the API server via token authentication.


Enable watch caching in the apiserver


List of watch cache sizes for every resource (pods, nodes, etc.), comma separated. The individual override format: resource#size, where size is a number. It takes effect when watch-cache is enabled.

Options Inherited from Parent Commands


Path to the file container Azure container registry configuration information.


The Google Cloud Platform Service Account JSON Key to use for authentication.


Maximum number of seconds between log flushes

See Also



June 2016, Ported from the Kubernetes man-doc generator

Referenced By


Openshift CLI User Manuals June 2016