MinIO for Red Hat OpenShift
Container Platform

Storage Classes and Tiering

The key requirement to deploy MinIO at scale on OpenShift is the ability tier across storage classes (NVMe, HDD, Public Cloud). This allows enterprises to manage both cost and performance.

MinIO supports automatic transition of aged objects from the fast NVMe tier to a more cost-efficient HDD tier and even cost-optimized cold Public Cloud storage tiers.

When tiering, MinIO presents a unified namespace across the tiers. Movement across the tiers is transparent to the application and is triggered by policies determined by the customer.

MinIO provides secure storage across an OpenShift hybrid cloud by encrypting objects right at the source - ensuring customers are always in complete control over the data. When OpenShift is deployed inside the public cloud the tiering functionality helps OpenShift efficiently manage data across persistent block storage and cheaper object storage tiers.

OpenShift | Understanding Persistent Storage - Learn more

Transition Objects from MinIO to S3 - Learn more

External Load Balancing

All of MinIO’s communication is based on HTTPs, RESTful APIs and will support any standard, Kubernetes compatible ingress controller. This includes hardware based and software defined solutions. The most popular choice is NGINX. Use the OperatorHub or the OpenShift Marketplace to install, then expose a MinIO tenant(s) using annotations.

Using the NGINX Ingress Operator - Learn more

Configure TLS/SSL for MinIO Tenants - Learn more

Encryption Key Management

There is no native OpenShift key management functionality. As a result, MinIO recommends using HashiCorp Vault to store keys outside of the object storage system. This is a best practice for cloud native applications.

For all production environments we recommend encryption to be enabled on all buckets by default. MinIO uses AES-256-GCM or ChaCha20-Poly1305 encryption to protect data integrity and confidentiality with negligible performance impact.

MinIO supports all of the three server-side encryption (SSE-KMS, SSE-S3 and SSE-C) modes. SSE-S3 and SSE-KMS integrates with the KMS on the server side, whereas SSE-C uses the client supplied keys.

MinIO will use this KMS to bootstrap its internal key encryption server (KES service) to enable high-performance, per object encryption. Each tenant runs its own KES server in an isolated namespace.

Integrating HashiCorp Vault in OpenShift 4 - Learn more

MinIO Encryption and Key Management - Learn more

Identity Management

When running MinIO on OpenShift, customers can manage single sign-on (SSO) through a third party OpenID Connect/LDAP compatible identity provider like Keycloak, Okta/Auth0, Google, Facebook, ActiveDirectory and OpenLDAP. MinIO recommends OpenID Connect compatible Keycloak IDP.

An external IDP allows administrators to centrally manage user/application identity. MinIO builds on top of the IDP, providing AWS IAM-style users, groups, roles, policies and token service API. The ability to have a unified identity and access management (IAM) layer independent of the infrastructure provides significant architectural flexibility.

OpenShift | Understanding identity provider configuration - Learn more

MinIO Identity and Access Management - Learn more

Certificate Management

All traffic from the application to MinIO, including internode traffic, is encrypted with TLS. TLS certificates are used to secure network communications and establish the identity of network-connected resources, such as a MinIO server domain.

MinIO integrates with the OpenShift certificate manager so you can use the MinIO Operator to automatically configure, provision, manage and update certificates for the MinIO tenants. The tenants are completely isolated from each other in their own Kubernetes namespace with their own certificates for improved security.

OpenShift and Let’s Encrypt - Learn more

MinIO Encryption and Key Management - Learn more

Monitoring and Alerting

MinIO recommends either Grafana, the platform monitoring components installed in the OpenShift-user-workload-monitoring project, or any other OpenShift container monitoring tool to connect to MinIO. MinIO publishes every object storage related Prometheus metric imaginable, from bucket capacity to access metrics. Those metrics can be collected and visualized in any Prometheus-compatible tool or the MinIO Console.

External monitoring solutions scrape the MinIO Prometheus endpoint at regular intervals. MinIO recommends either Grafana or the platform monitoring components installed in the openshift-user-workload-monitoring project to connect to MinIO. These same tools can also be used to establish baselines and set alert thresholds for notifications, which can then be routed to a notification platform such as PagerDuty, Freshservice or even SNMP.

OpenShift | Understanding the Monitoring Stack - Learn more

How to monitor MinIO server with Prometheus - Learn more