mxnet.np.signbit signbit ( x , / , out=None , * , where=True , casting='same_kind' , order='K' , dtype=None , subok=T...

mxnet.np.multiply multiply ( x1 , x2 , out=None , **kwargs ) Multiply arguments element-wise. Parameters x2 ( x1 , ) ...

Production-Grade Container Orchestration

mxnet.np.modf modf ( x , [ out1 , out2 , ] / , [ out=(None , None) , ] * , where=True , casting='same_kind' , order='...

Production-Grade Container Orchestration

mxnet.np.correlate correlate ( a , v , mode='valid' ) Cross-correlation of two 1-dimensional sequences. This function...

mxnet.np.where where ( condition [ , x , y ] ) Return elements chosen from x or y depending on condition . Note When ...

Package v1beta1 is the v1beta1 version of the metrics API. Resource Types NodeMetrics NodeMetricsList PodMetrics PodMetricsList NodeMetrics Appears in: NodeMetricsList NodeMetrics sets resource usage metrics of a node. FieldDescription apiVersionstringmetrics.k8s.io/v1beta1 kindstringNodeMetrics metadata meta/v1.ObjectMeta Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata Refer to the Kubernetes API documentation for the fields of the metadata field. timestamp [Required] meta/v1.Time The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].

Synopsis Update existing container image(s) of resources. Possible resources include (case insensitive): pod (po), replicationcontroller (rc), deployment (deploy), daemonset (ds), statefulset (sts), cronjob (cj), replicaset (rs) kubectl set image (-f FILENAME | TYPE NAME) CONTAINER_NAME_1=CONTAINER_IMAGE_1 ... CONTAINER_NAME_N=CONTAINER_IMAGE_N Examples # Set a deployment's nginx container image to 'nginx:1.9.1', and its busybox container image to 'busybox' kubectl set image deployment/nginx busybox=busybox nginx=nginx:1.9.1 # Update all deployments' and rc's nginx container's image to 'nginx:1.

Each major Kubernetes release introduces new features that require documentation. New releases also bring updates to existing features and documentation (such as upgrading a feature from alpha to beta). Generally, the SIG responsible for a feature submits draft documentation of the feature as a pull request to the appropriate development branch of the kubernetes/website repository, and someone on the SIG Docs team provides editorial feedback or edits the draft directly.