Synopsis Create a LoadBalancer service with the specified name. kubectl create service loadbalancer NAME [--tcp=port:targetPort] [--dry-run=server|client|none] Examples # Create a new LoadBalancer service named my-lbs kubectl create service loadbalancer my-lbs --tcp=5678:8080 Options --allow-missing-template-keys     Default: true 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. --dry-run string[="unchanged"]     Default: "none" Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it.

mxnet.np.atleast_1d atleast_1d ( *arys ) Convert inputs to arrays with at least one dimension. Scalar inputs are conv...

Project Dependencies compile The following is a list of compile dependencies for this project. These dependencies are...

mxnet.engine Engine properties management. Functions bulk (size) Bulk execution bundles many operators to run togethe...

mxnet.runtime.feature_list feature_list ( ) [source] Check the library for compile-time features. The list of feature...

mxnet.rtc Interface to runtime cuda kernel compile module. Classes CudaKernel (handle, name, is_ndarray, dtypes) Cons...

symbol.random Random distribution generator Symbol API of MXNet. Functions uniform ([low, high, shape, dtype]) Draw r...

All of the APIs in Kubernetes that let you write persistent API resource data support at-rest encryption. For example, you can enable at-rest encryption for Secrets. This at-rest encryption is additional to any system-level encryption for the etcd cluster or for the filesystem(s) on hosts where you are running the kube-apiserver. This page shows how to switch from encryption of API data at rest, so that API data are stored unencrypted.

FEATURE STATE: Kubernetes v1.18 [stable] This page provides an overview of NodeLocal DNSCache feature in Kubernetes. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitt...