minio.md

MinIO

Overview

MinIO is an open source high performance, Kubernetes-native object storage suite is built for the demands of the hybrid cloud.

The package is offered up as three individual packages that make up the MinIO ecosystem.

Big Bang's implementation uses the MinIO operator to provide custom resources and manage the different tenents of MinIO. The official package for MinIO Operator can be found here

The MinIO tenants are created using the MinIO package. This package is used to set up individual MinIO instances for applications to use (e.g. Gitlab).

The final package is the MinIO console. This is a graphical user interface that allows management of an individual tenant. The official package can be found here.

Tenant Architecture

Note: The Minio Operator needs to be able to reach out to the minio instances. This is to ensure that on an upgrade all existing pools are shut down before starting new ones. If you run into issues with upgrades ensure that networkPolicies allow ingress to the minio pods in your namespace on port 9000.

Big Bang Touchpoints

UI

The MinIO Console UI is the primary way of interacting with a MinIO tenant. The UI is accessible via a web browser. The UI provides access to all of a tenants features. This includes access to features very similar to what you would see in AWS S3, setting up buckets, controlling access, etc.

Logging

MinIO supports configuring audit logs through both the MinIO Console UI and the MinIO mc command line tool. For Kubernetes environments, the MinIO Operator automatically configures the Console with a LogSearch integration for visual inspection of collected audit logs.

By default logs are also shipped to Elastic via Fluentbit for advanced searching/indexing. The filter kubernetes.namespace_name set to your MinIO tenant namespace can provide easy viewing of MinIO only logs.

Monitoring

Monitoring is provided via a Prometheus capable endpoint. MinIO also provides a Grafana dashboard for use in viewing metrics. Monitoring in the Big Bang config can be enabled using the following format.

monitoring:
  enabled: false
  namespace: monitoring

Health Checks

MinIO server exposes three un-authenticated, healthcheck endpoints liveness probe and a cluster probe at /minio/health/live and /minio/health/cluster respectively.