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...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

Project Dependency Management compile The following is a list of compile dependencies in the DependencyManagement of ...

Project Team A successful project requires many people to play many roles. Some members write code or documentation, ...

English ▾ English Français Português (Brasil) українська мова 简体中文 Topics ▾ Setup and Config git config help bugrepor...

This page shows you how to configure a Pod to use a PersistentVolumeClaim for storage. Here is a summary of the process: You, as cluster administrator, create a PersistentVolume backed by physical storage. You do not associate the volume with any Pod. You, now taking the role of a developer / cluster user, create a PersistentVolumeClaim that is automatically bound to a suitable PersistentVolume. You create a Pod that uses the above PersistentVolumeClaim for storage.

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.