- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 67 for tenant (0.08 sec)
-
docs/multi-tenancy/README.md
## 1. Standalone Deployment To host multiple tenants on a single machine, run one MinIO Server per tenant with a dedicated HTTPS port, configuration, and data directory. ### 1.1 Host Multiple Tenants on a Single Drive Use the following commands to host 3 tenants on a single drive: ```sh minio server --address :9001 /data/tenant1 minio server --address :9002 /data/tenant2 minio server --address :9003 /data/tenant3 ```
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 3K bytes - Viewed (0) -
docs/orchestration/README.md
MinIO is built ground up on the cloud-native premise. With features like erasure-coding, distributed and shared setup, it focuses only on storage and does it very well. While, it can be scaled by just replicating MinIO instances per tenant via an orchestration platform.
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 2.2K bytes - Viewed (0) -
SECURITY.md
tenant isolation, resource allocation, model sharing and hardware attacks. ### Tenant isolation Since any tenants or users providing models, graphs or checkpoints can execute code in context of the TensorFlow service, it is important to design isolation mechanisms that prevent unwanted access to the data from other tenants.
Registered: Tue Nov 05 12:39:12 UTC 2024 - Last Modified: Wed Oct 16 16:10:43 UTC 2024 - 9.6K bytes - Viewed (0) -
docs/orchestration/kubernetes/README.md
MinIO is a high performance distributed object storage server, designed for large-scale private cloud infrastructure. MinIO is designed in a cloud-native manner to scale sustainably in multi-tenant environments. Orchestration platforms like Kubernetes provide perfect cloud-native environment to deploy and scale MinIO. ## MinIO Deployment on Kubernetes There are multiple options to deploy MinIO on Kubernetes:
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 1.6K bytes - Viewed (0) -
docs/distributed/DECOMMISSION.md
- On Operator based MinIO deployments, you need to modify the `tenant.yaml` specification and modify the `pools:` section from two entries to a single entry. After making relevant changes, proceed to execute `kubectl apply -f tenant.yaml`. > Without a 'Complete' status any 'Active' or 'Draining' pool(s) are not allowed to be removed once configured. ## NOTE
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Jul 11 14:59:49 UTC 2022 - 8.3K bytes - Viewed (0) -
docs/distributed/README.md
Install MinIO on Kubernetes: - [MinIO Quickstart Guide for Kubernetes](https://min.io/docs/minio/kubernetes/upstream/index.html#quickstart-for-kubernetes). - [Deploy a Tenant from the MinIO Operator](https://min.io/docs/minio/kubernetes/upstream/operations/install-deploy-manage/deploy-minio-tenant.html) Install Distributed MinIO on Linux:
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jan 18 07:03:17 UTC 2024 - 8.8K bytes - Viewed (0) -
docs/minio-limits.md
# MinIO Server Limits Per Tenant For optimal production setup MinIO recommends Linux kernel version 4.x and later. ## Erasure Code (Multiple Drives / Servers) | Item | Specification | |:----------------------------------------------------------------|:--------------| | Maximum number of servers per cluster | no-limit |
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jan 18 07:03:17 UTC 2024 - 5.9K bytes - Viewed (0) -
helm/minio/README.md
| This Helm chart is community built, maintained, and supported. MinIO does not guarantee support for any given bug, feature request, or update referencing this chart. <br/><br/> MinIO publishes a separate [MinIO Kubernetes Operator and Tenant Helm Chart](https://github.com/minio/operator/tree/master/helm) that is officially maintained and supported. MinIO strongly recommends using the MinIO Kubernetes Operator for production deployments. See [Deploy Operator With Helm](https://min.io/...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jan 24 07:27:57 UTC 2024 - 10.9K bytes - Viewed (0) -
docs/config/README.md
[here](https://github.com/minio/minio/blob/master/docs/kms/IAM.md). > NOTE: if *path_prefix* is set then MinIO will not federate your buckets, namespaced IAM assets are assumed as isolated tenants, only buckets are considered globally unique but performing a lookup with a *bucket* which belongs to a different tenant will fail unlike federated setups where MinIO would port-forward and route the request to relevant cluster accordingly. This is a special feature, federated deployments should not need to...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Aug 16 08:43:49 UTC 2024 - 17.9K bytes - Viewed (0) -
docs/bigdata/README.md
MinIO object storage is via S3/SQL SELECT API. In addition to the compute nodes, MinIO containers are also managed by Kubernetes as stateful containers with local storage (JBOD/JBOF) mapped as persistent local volumes. This architecture enables multi-tenant MinIO, allowing isolation of data between customers. MinIO also supports multi-cluster, multi-site federation similar to AWS regions and tiers. Using MinIO Information Lifecycle Management (ILM), you can configure data to be tiered between...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 29 04:28:45 UTC 2022 - 14.7K bytes - Viewed (0)