- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for Sluiter (0.15 sec)
-
docs/metrics/prometheus/grafana/README.md
CLuster level Replication metrics can be viewed in the Grafana dashboard using [json file here](https://raw.githubusercontent.com/minio/minio/master/docs/metrics/prometheus/grafana/replication/minio-replication-cluster.json) ![Grafana](https://raw.githubusercontent.com/minio/minio/master/docs/metrics/prometheus/grafana/replication/grafana-replication-cluster.png)
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 28 17:15:39 GMT 2024 - 2.4K bytes - Viewed (0) -
docs/bucket/lifecycle/README.md
transition feature. This will allow transitioning of older objects to a different cluster or the public cloud by setting up transition rules in the bucket lifecycle configuration. This feature enables applications to optimize storage costs by moving less frequently accessed data to a cheaper storage without compromising accessibility of data. To transition objects in a bucket to a destination bucket on a different cluster, applications need to specify a transition tier defined on MinIO instead...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Aug 26 07:33:25 GMT 2023 - 9K bytes - Viewed (1) -
docs/federation/lookup/README.md
points to the public IP address where each cluster might be accessible, this is unique for each cluster. NOTE: `mybucket` only exists on one cluster either `cluster1` or `cluster2` this is random and is decided by how `domain.com` gets resolved, if there is a round-robin DNS on `domain.com` then it is randomized which cluster might provision the bucket. ### 3. Test your setup
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) -
docs/throttle/README.md
Example: Limit a MinIO cluster to accept at max 1600 simultaneous S3 API requests across all nodes of the cluster. ```sh export MINIO_API_REQUESTS_MAX=1600 export MINIO_ROOT_USER=your-access-key
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sat Feb 12 00:51:25 GMT 2022 - 2.4K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
The command will generate the `scrape_configs` section of the prometheus.yml as follows: ##### Cluster ```yaml scrape_configs: - job_name: minio-job bearer_token: <secret> metrics_path: /minio/v2/metrics/cluster scheme: http static_configs:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
README.md
and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes. Istio is composed of these components: - **Envoy** - Sidecar proxies per microservice to handle ingress/egress traffic between services in the cluster and from a service to external services. The proxies form a _secure microservice mesh_ providing a rich
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jan 26 15:28:59 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
## 1. Prerequisites - Familiarity with [MinIO deployment process on Kubernetes](https://min.io/docs/minio/kubernetes/upstream/operations/installation.html). - Kubernetes cluster with `kubectl` configured. - Acquire TLS certificates, either from a CA or [create self-signed certificates](https://min.io/docs/minio/kubernetes/upstream/operations/network-encryption.html).
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 3K bytes - Viewed (0) -
manifests/charts/gateway/README.md
When configuring the chart, you should not include this. That is, `--set some.field=true` should be passed, not `--set defaults.some.field=true`. ### OpenShift When deploying the gateway in an OpenShift cluster, use the `openshift` profile to override the default values, for example: ```console helm install istio-ingressgateway istio/gateway --set profile=openshift ``` ### `image: auto` Information
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/kms/README.md
``` In a given setup, there are `n` MinIO instances talking to `m` KES servers but only `1` central KMS. The most simple setup consists of `1` MinIO server or cluster talking to `1` KMS via `1` KES server. The main difference between various MinIO-KMS deployments is the KMS implementation. The following table helps you select the right option for your use case:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K 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 in that cluster. Currently, the minimum we require is the security provider (node agent or citadel). ### Install Istio CRDs
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)