Locking down MinIO Operator Permissions

AJ AJ on Kubernetes |
Locking down MinIO Operator Permissions

In this post, we’ll show you how to configure the MinIO Operator with the most restrictive namespace permissions – all the while being able to fully utilize the power and flexibility of the MinIO Operator for day-to-day operations.

Read more

Debugging MinIO Installs

AJ AJ on DevOps |
Debugging MinIO Installs

In this blog post, we’ll show you how to debug a MinIO install running in Kubernetes and also some of the common issues you might encounter when doing bare metal installation and how to rectify them.

Read more

Renewing KES certificate

AJ AJ on Security |
Renewing KES certificate

In this post we'll show you some of the common errors you can run into when the certs in KES expire. We'll show you what errors you can expect and how to renew and update the certs in a quick fashion.

Read more

How do I know replication is up to date?

AJ AJ on DevOps |
How do I know replication is up to date?

In this post, we’ll take a look at the various states an object can be in during the replication process and how to get back up and running as quickly as possible among other tidbits so you have a pleasant experience Day 2 of replication.

Read more

Add Pools and expand capacity

AJ AJ on DevOps |
Add Pools and expand capacity

Server pools help you expand the capacity of your existing MinIO cluster quickly and easily. This blog post focuses on increasing the capacity of one cluster, which is different from adding another cluster and replicating the same data across multiple clusters.

Read more

MinIO Batch Framework Adds Support for Expiry

MinIO Batch Framework Adds Support for Expiry

You can now perform S3 Delete operations using the MinIO Batch Framework to remove multitudes of objects with a single API request. The MinIO Batch Framework lets you quickly and easily perform repetitive or bulk actions like Batch Replication and Batch Key-Rotate across your MinIO deployment. The MinIO Batch Framework handles all the manual work, including managing retries and reporting

Read more

The Blog Year in Review: Top 10 for 2023

Sasha Wodtke Sasha Wodtke on |
The Blog Year in Review: Top 10 for 2023

With only a few days left in 2023 (who else can’t believe it?), we have been taking some time to look back on what an amazing year it’s been. There have been so many highlights. Whether it’s been the many awards, conferences, or meeting so many of you, we are eternally grateful!  The biggest part of MinIO

Read more

Distributed Training and Experiment Tracking with Ray Train, MLflow, and MinIO

Distributed Training and Experiment Tracking with Ray Train, MLflow, and MinIO

Over the past few months, I have written about a number of different technologies (Ray Data, Ray Train, and MLflow). I thought it would make sense to pull them all together and deliver an easy-to-understand recipe for distributed data preprocessing and distributed training using a production-ready MLOPs tool for tracking and model serving. This post integrates the code I presented

Read more

Recent Launch of Amazon S3 Express One Zone Validates That Object Storage is Primary Storage for AI

Matt Sarrel Matt Sarrel Matt Sarrel @msarrel on |
Recent Launch of Amazon S3 Express One Zone Validates That Object Storage is Primary Storage for AI

We have made the case for several years that in modern data stacks object storage is primary storage. This is even more true in the age of AI where enterprises focus almost exclusively on object storage. The modern data stack relies on disaggregated compute and storage alongside cloud-native microservices running in containers on Kubernetes. As more enterprises shift to this

Read more

Distributed Training with Ray Train and MinIO

Distributed Training with Ray Train and MinIO

Most machine learning projects start off as a single-threaded proof of concept where each task is completed before the next task can begin. The single-threaded ML pipeline depicted below is an example. However, at some point, you will outgrow the pipeline shown above. This may be caused by datasets that no longer fit into the memory of a single process.

Read more