- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for top (0.14 sec)
-
docs/federation/lookup/README.md
be same across the federated deployment, i.e. all the MinIO instances within a federated deployment should use same etcd back-end. #### MINIO_DOMAIN This is the top level domain name used for the federated setup. This domain name should ideally resolve to a load-balancer running in front of all the federated MinIO instances. The domain name is used to create sub domain entries to etcd. For
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4K bytes - Viewed (0) -
manifests/charts/README.md
certificate provisioning tool, or use components that are centrally managed and running in a different cluster. This is a work in progress - building on top of the multi-cluster installer. As an extreme, the goal is to be possible to run Istio workloads in a cluster without installing any Istio component
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
docs/bucket/notifications/README.md
## Publish MinIO events via AMQP Install RabbitMQ from [here](https://www.rabbitmq.com/). ### Step 1: Add AMQP endpoint to MinIO The AMQP configuration is located under the sub-system `notify_amqp` top-level key. Create a configuration key-value pair here for your AMQP instance. The key is a name for your AMQP endpoint, and the value is a collection of key-value parameters described in the table below. ``` KEY:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
docs/bigdata/README.md
Kubernetes manages stateless Spark and Hive containers elastically on the compute nodes. Spark has native scheduler integration with Kubernetes. Hive, for legacy reasons, uses YARN scheduler on top of Kubernetes.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 14.7K bytes - Viewed (0) -
ci/official/README.md
### Brief System Overview The top-level scripts and utility scripts should be fairly well-documented. Here is a brief explanation of how they tie together: 1. `envs/*` are lists of variables made with bash syntax. A user must set a `TFCI` env param pointing to a list of `env` files. 2. `utilities/setup.sh`, initialized by all top-level scripts, reads and sets values from those `TFCI` paths.
Plain Text - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Thu Feb 01 03:21:19 GMT 2024 - 8K bytes - Viewed (0)