Expose a resource as a new Kubernetes service.

Looks up a deployment, service, replica set, replication controller or pod by name and uses the selector for that resource as the selector for a new service on the specified port. A deployment or replica set will be exposed as a service only if its selector is convertible to a selector that service supports, i.e. when the selector contains only the matchLabels component. Note that if no port is specified via –port and the exposed resource has multiple ports, all will be re-used by the new service. Also if no labels are specified, the new service will re-use the labels from the resource it exposes.

Possible resources include (case insensitive):

pod (po), service (svc), replicationcontroller (rc), deployment (deploy), replicaset (rs)


werf 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] [options]


  # Create a service for a replicated nginx, which serves on port 80 and connects to the containers on port 8000
  kubectl expose rc nginx --port=80 --target-port=8000
  # Create 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
  kubectl expose -f nginx-controller.yaml --port=80 --target-port=8000
  # Create a service for a pod valid-pod, which serves on port 444 with the name "frontend"
  kubectl expose pod valid-pod --port=444 --name=frontend
  # Create a second service based on the above service, exposing the container port 8443 as port 443 with the name "nginx-https"
  kubectl expose service nginx --port=443 --target-port=8443 --name=nginx-https
  # Create a service for a replicated streaming application on port 4100 balancing UDP traffic and named 'video-stream'.
  kubectl expose rc streamer --port=4100 --protocol=UDP --name=video-stream
  # Create a service for a replicated nginx using replica set, which serves on port 80 and connects to the containers on port 8000
  kubectl expose rs nginx --port=80 --target-port=8000
  # Create a service for an nginx deployment, which serves on port 80 and connects to the containers on port 8000
  kubectl expose deployment nginx --port=80 --target-port=8000


            If true, ignore any errors in templates when a field or map key is missing in the       
            template. Only applies to golang and jsonpath output formats.
            ClusterIP to be assigned to the service. Leave empty to auto-allocate, or set to `None` 
            to create a headless service.
            Must be "none", "server", or "client". If client strategy, only print the object that   
            would be sent, without sending it. If server strategy, submit server-side request       
            without persisting the resource.
            Additional external IP address (not managed by Kubernetes) to accept for the service.   
            If this IP is routed to a node, the service can be accessed by this IP in addition to   
            its generated service IP.
            Name of the manager used to track field ownership.
  -f, --filename=[]
            Filename, directory, or URL to files identifying the resource to expose a service
            The name of the API generator to use. There are 2 generators: `service/v1` and          
            `service/v2`. The only difference between them is that service port in v1 is named      
            `default`, while it is left unnamed in v2. Default is `service/v2`.
  -k, --kustomize=''
            Process the kustomization directory. This flag can`t be used together with -f or -R.
  -l, --labels=''
            Labels to apply to the service created by this call.
            IP to assign to the LoadBalancer. If empty, an ephemeral IP will be created and used    
            (cloud-provider specific).
            The name for the newly created object.
  -o, --output=''
            Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile
            An inline JSON override for the generated object. If this is non-empty, it is used to   
            override the generated object. Requires that the object supply a valid apiVersion field.
            The port that the service should serve on. Copied from the resource being exposed, if   
            The network protocol for the service to be created. Default is `TCP`.
  -R, --recursive=false
            Process the directory used in -f, --filename recursively. Useful when you want to       
            manage related manifests organized within the same directory.
            If true, the configuration of current object will be saved in its annotation.           
            Otherwise, the annotation will be unchanged. This flag is useful when you want to       
            perform kubectl apply on this object in the future.
            A label selector to use for this service. Only equality-based selector requirements are 
            supported. If empty (the default) infer the selector from the replication controller or 
            replica set.)
            If non-empty, set the session affinity for the service to this; legal values: `None`,   
            If true, keep the managedFields when printing objects in JSON or YAML format.
            Name or number for the port on the container that the service should direct traffic to. 
            Template string or path to template file to use when -o=go-template,                    
            -o=go-template-file. The template format is golang templates                            
            Type for this service: ClusterIP, NodePort, LoadBalancer, or ExternalName. Default is   

Options inherited from parent commands

            Username to impersonate for the operation
            Group to impersonate for the operation, this flag can be repeated to specify multiple   
            Default cache directory
            Path to a cert file for the certificate authority
            Path to a client certificate file for TLS
            Path to a client key file for TLS
            The name of the kubeconfig cluster to use
            The name of the kubeconfig context to use (default $WERF_KUBE_CONTEXT)
            Use specified dir to store werf cache files and dirs (default $WERF_HOME or ~/.werf)
            If true, the server`s certificate will not be checked for validity. This will make your 
            HTTPS connections insecure (default $WERF_SKIP_TLS_VERIFY_REGISTRY)
            Kubernetes config data as base64 string (default $WERF_KUBE_CONFIG_BASE64 or            
            Path to the kubeconfig file to use for CLI requests (default $WERF_KUBE_CONFIG, or      
            $WERF_KUBECONFIG, or $KUBECONFIG). Ignored if kubeconfig passed as base64.
            Require server version to match client version
  -n, --namespace=''
            If present, the namespace scope for this CLI request
            Password for basic authentication to the API server
            Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex)
            Name of the file to write the profile to
            The length of time to wait before giving up on a single server request. Non-zero values 
            should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don`t 
            timeout requests.
  -s, --server=''
            The address and port of the Kubernetes API server
            Server name to use for server certificate validation. If it is not provided, the        
            hostname used to contact the server is used
            Use specified dir to store tmp files and dirs (default $WERF_TMP_DIR or system tmp dir)
            Bearer token for authentication to the API server
            The name of the kubeconfig user to use
            Username for basic authentication to the API server
            Treat warnings received from the server as errors and exit with a non-zero exit code