- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 48 for notes (0.14 sec)
-
helm/minio/templates/NOTES.txt
MinIO can be accessed via port {{ .Values.service.port }} on an external IP address. Get the service external IP address by: kubectl get svc --namespace {{ .Release.Namespace }} -l app={{ template "minio.fullname" . }} Note that the public IP may take a couple of minutes to be available. You can now access MinIO server on http://<External-IP>:9000. Follow the below steps to connect to MinIO server with mc client:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 2.7K bytes - Viewed (0) -
docs/bucket/lifecycle/DESIGN.md
### Additional notes Tiering and lifecycle transition are applicable only to erasure/distributed MinIO. ## Explore Further
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 4.3K bytes - Viewed (0) -
helm/minio/README.md
```bash helm install --set tls.enabled=true,tls.certSecret=tls-ssl-minio minio/minio ``` ### Installing certificates from third party CAs
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Jan 24 07:27:57 GMT 2024 - 10.9K bytes - Viewed (0) -
docs/kms/README.md
```sh export MINIO_ROOT_USER=minio export MINIO_ROOT_PASSWORD=minio123 minio server ~/export ``` > The KES instance at `https://play.min.io:7373` is meant to experiment and provides a way to get started quickly. > Note that anyone can access or delete master keys at `https://play.min.io:7373`. You should run your own KES > instance in production. ## Configuration Guides A typical MinIO deployment that uses a KMS for SSE-S3 looks like this:
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) -
docs/docker/README.md
## Prerequisites Docker installed on your machine. Download the relevant installer from [here](https://www.docker.com/community-edition#/download). ## Run Standalone MinIO on Docker *Note*: Standalone MinIO is intended for early development and evaluation. For production clusters, deploy a [Distributed](https://min.io/docs/minio/container/operations/install-deploy-manage/deploy-minio-single-node-multi-drive.html) MinIO deployment.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 29 04:28:45 GMT 2022 - 8.2K bytes - Viewed (0) -
docs/config/README.md
``` #### Etcd MinIO supports storing encrypted IAM assets in etcd, if KMS is configured. Please refer to how to encrypt your config and IAM credentials [here](https://github.com/minio/minio/blob/master/docs/kms/IAM.md).
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
internal/grid/README.md
} ``` The wrapper will handle all serialization and de-seralization of the request and response, and furthermore provides reuse of the structs used for the request and response. Note that Responses sent for serialization are automatically reused for similar requests. If the response contains shared data it will cause issues, since each unique response is reused.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 9.4K bytes - Viewed (0) -
docs/tls/kubernetes/README.md
items: - key: public.crt path: public.crt - key: private.key path: private.key - key: public.crt path: CAs/public.crt ``` Note that the `secretName` should be same as the secret name created in previous step. Then add the below section under `spec.containers[].volumeMounts[]` ```yaml volumeMounts: - name: secret-volume
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) -
docs/metrics/prometheus/README.md
Optionally you can also collect per node metrics. This needs to be done on a per server instance. The scrape configurations should use all the servers under `targets` so that graphing systems like grafana can visualize them for all the nodes ```yaml scrape_configs: - job_name: minio-job metrics_path: /minio/v2/metrics/node scheme: http static_configs: - targets: ['server1:9000','server2:9000','server3:9000','server4:9000'] ```
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) -
docs/sts/web-identity.md
Either `MINIO_IDENTITY_OPENID_ROLE_POLICY` (recommended) or `MINIO_IDENTITY_OPENID_CLAIM_NAME` must be specified but not both. See the section Access Control Policies to understand the differences between the two. **NOTE**: When configuring multiple OpenID based authentication providers on a MinIO cluster, any number of Role Policy based providers may be configured, and at most one JWT Claim based provider may be configured.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 19.2K bytes - Viewed (1)