Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add images for Tenant architecture, Console dashboard #438

Merged
merged 2 commits into from
Jan 27, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,12 @@ MinIO is a Kubernetes-native high performance object store with an S3-compatible
MinIO Kubernetes Operator supports deploying MinIO Tenants onto private and public
cloud infrastructures ("Hybrid" Cloud).

*IMPORTANT*: This documentation reflects the *latest bleeding-edge release* of the MinIO Operator. The API and syntax may differ from
previous releases. For documentation on previous releases, please visit the documentation in context of that release tag:

- [v0.3.29](https://github.com/minio/operator/blob/v3.0.29/README.md)
- [v0.3.28](https://github.com/minio/operator/blob/v3.0.28/README.md)

## Table of Contents

* [Architecture](#architecture)
Expand All @@ -26,7 +32,7 @@ Each MinIO Tenant represents an independent MinIO Object Store within
the Kubernetes cluster. The following diagram describes the architecture of a
MinIO Tenant deployed into Kubernetes:

IMAGE
![Tenant Architecture](docs/images/architecture.png)

MinIO provides multiple methods for accessing and managing the MinIO Tenant:

Expand All @@ -35,7 +41,7 @@ MinIO provides multiple methods for accessing and managing the MinIO Tenant:
The MinIO Console provides a graphical user interface (GUI) for interacting with
MinIO Tenants.

IMAGE
![Console Dashboard](docs/images/console-dashboard.png)

Administrators of MinIO Tenants can perform a variety of tasks through the Console,
including user creation, policy configuration, and bucket replication. The
Expand Down Expand Up @@ -107,7 +113,7 @@ volumes, and a total capacity of 16Ti. This configuration requires
--volumes 16 \
--capacity 16Ti \
--namespace minio-tenant-1 \
--storageClassName local-storage \
--storage-class local-storage \
```

- The `minio-tenant-1` argument specifies the name of the MinIO Tenant. The MinIO
Expand Down Expand Up @@ -136,7 +142,7 @@ volumes, and a total capacity of 16Ti. This configuration requires

MinIO supports *one* MinIO Tenant per namespace.

- The `--storageClassName` field indicates which
- The `--storage-class` field indicates which
[`StorageClass`](https://kubernetes.io/docs/concepts/storage/storage-classes/) to use
when generating each `PVC`.

Expand Down Expand Up @@ -257,7 +263,7 @@ provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer
```

To specify the storage class, include the `--storageClassName` option to
To specify the storage class, include the `--storage-class` option to
`kubectl minio tenant create`.


Expand Down
Binary file added docs/images/architecture.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/console-dashboard.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.