# MinIO Published articles for MinIO. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO DevFeed: [Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-11T05:00:00Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [PostgreSQL](), [Disaster Recovery](), [Kubernetes](), [MinIO](), [nginx](), [TLS (Transport Layer Security)](), [Amazon S3](), [Availability]() Tags: [availability](), [backup](), [data-recovery](), [disaster-recovery](), [failover](), [high-availability](), [how-to](), [kubernetes](), [minio](), [nginx](), [postgresql](), [recovery](), [s3](), [tls](), [tutorials]() ### AI overview A tutorial on using Crunchy PostgreSQL Operator on Kubernetes to implement multi-region PostgreSQL disaster recovery and failback. It covers secure MinIO-backed WAL storage through an NGINX TLS reverse proxy, regional failover, and reversing roles without timeline conflicts or archive poisoning. ### Source excerpt This blog talks about multiregion PostgreSQL disaster recovery using Crunchy PGO. It has some detailed steps to understand better. The post Multi-Region PostgreSQL Disaster Recovery and Failback with Crunchy PGO appeared first on CYBERTEC PostgreSQL | Services & Support. ## Kubeflow Community Distribution 26.03.1 Release Announcement DevFeed: [Kubeflow Community Distribution 26.03.1 Release Announcement]() Original publisher: [Read original article]() Author: Kubeflow 26.03 Release Team Published: 2026-04-11T05:00:00Z Content type: release Language: en Sources: [Kubeflow]() Topics: [releases](), [Kubernetes](), [MinIO](), [istio](), [OpenID connect (OIDC)](), [kubectl]() Tags: [announcement](), [authentication](), [authorization](), [catalog](), [ci](), [istio](), [kubectl](), [kubernetes](), [minio](), [network](), [oidc](), [parallel](), [release](), [storage](), [ui](), [updates](), [versioning]() ### AI overview The Kubeflow Community Distribution 26.03.1 release introduces calendar-based versioning and updates components including Kubernetes, Kubeflow Pipelines, KServe, Trainer, notebooks, the dashboard, Istio, and related dependencies. It also adds native OIDC support, conditional and parallel Local Runner control flows, SeaweedFS storage support, and completes MinIO deprecation. ### Source excerpt The release versioning is now calendar-based (Year.Month.Patch). Around two base releases are planned per year with optional patch releases. The best-effort only community support is roughly 6 months and there is commercial support available from multiple vendors. Please update regularly as explained in our upgrading and extending section to benefit also from security and performance improvements. Release details: 26.03 and 26.03.1. ## Fork yeah: We're adding ten new open source projects to EmeritOSS DevFeed: [Fork yeah: We're adding ten new open source projects to EmeritOSS]() Original publisher: [Read original article]() Published: 2026-01-15T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [Prometheus](), [Apache Cassandra](), [Amazon S3](), [observability](), [Grafana](), [data-processing]() Tags: [amazon-s3](), [cassandra](), [chainguard-containers](), [chainguard-emeritoss](), [chainguard-images](), [chainguard-open-source](), [dashboards](), [maintenance](), [minio](), [observability](), [open-source](), [open-source-chainguard-images](), [pgcat](), [prometheus](), [security](), [source]() ### AI overview Chainguard announces ten additional open source projects joining EmeritOSS, a program intended to provide long-term maintenance and stability for mature projects. The supplied text highlights MinIO, Prometheus-related exporters, and integrations involving Apache Cassandra and RabbitMQ, covering object storage, monitoring, metrics, and observability. ### Source excerpt We added 10 open source projects to EmeritOSS--including MinIO, Prometheus exporters, and PgCat--to provide long-term, stability-focused maintenance and security. ## Secure and Free MinIO Chainguard Containers DevFeed: [Secure and Free MinIO Chainguard Containers]() Original publisher: [Read original article]() Published: 2025-10-27T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [Docker Image](), [Security](), [vulnerability](), [Amazon S3](), [Open Source](), [CI/CD]() Tags: [chainguard-containers](), [ci-cd](), [container](), [containers](), [docker-image](), [minio](), [minio-containers](), [minio-docker-containers](), [object-storage](), [open-source](), [s3](), [security](), [vulnerability](), [zero-cve-minio-containers]() ### AI overview The article explains that MinIO stopped publishing free community container images and describes the resulting maintenance and security concerns for developers. It presents Chainguard's free MinIO and MinIO Client container images as an alternative. ### Source excerpt MinIO pulled its free images--but Chainguard has you covered. Get zero-CVE, continuously built MinIO and MinIO Client containers, free and secure from Chainguard. ## Blog: Falco Talon v0.3.0 DevFeed: [Blog: Falco Talon v0.3.0]() Original publisher: [Read original article]() Published: 2025-02-11T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Amazon S3](), [MinIO](), [Command-line interface](), [Kubernetes]() Tags: [aws](), [aws-s3](), [cli](), [falco](), [kubernetes](), [minio](), [release](), [talon](), [version]() ### AI overview Falco Talon 0.3.0 adds a kubernetes:sysdig action that captures syscalls when suspicious events occur in a pod and exports the resulting artifact to AWS S3 or MinIO. The release also describes configuring capture duration and buffer size, and exploring captures with the sysdig CLI or Stratoshark. ### Source excerpt Today, we announce the release of Falco Talon 0.3.0 🦅! Three updates in a row, after Falco and Falcosidekick, it's time for Falco Talon to know a new version. What's new? The key feature this release brings is the new actionner kubernetes:sysdig. For those who are not familiar with sysdig, it's a CLI tool that allows to capture and record the syscalls, like tcpdump does for the network packets. Old brother of Falco, they share the same libs and filters. With this new integration, when a suspicious event occurs in a pod, Talon triggers a capture and then exports the created artifact to AWS S3 or Minio. You can configure the duration and the amount of bytes captured for each syscall. Check out the docs to discover more settings. See this example rule: - action: Capture the syscalls actionner: kubernetes:sysdig parameters: buffer_size: 2048 duration: 20 output: target: minio:s3 parameters: bucket: falco-talon prefix: /sysdig/ After the action has been completed, you'll find the capture in Minio: And you can run the CLI tool sysdig to explore it: ❯ sysdig -r 2025-01-23T13-26-41Z_default_cncf-597d69dbd4-h9fcb_sysdig.scap.gz evt.type=execve and evt.dir=">" 18563 14:26:38.376178286 0 bash (616444.616444) > execve filename=/usr/bin/apt 19163 14:26:38.394972623 0 apt (616445.616445) > execve filename=/usr/bin/dpkg 19599 14:26:38.399546432 0 apt (616446.616446) > execve filename=/usr/lib/apt/methods/http 20319 14:26:38.408846350 0 apt (616447.616447) > execve filename=/usr/lib/apt/methods/http 21775 14:26:38.453363037 0 apt (616448.616448) > execve filename=/usr/lib/apt/methods/gpgv 22335 14:26:38.461330752 0 apt (616449.616449) > execve filename=/usr/lib/apt/methods/gpgv 29434 14:26:38.481292691 0 gpgv (616451.616451) > execve filename=/usr/bin/apt-key 29604 14:26:38.486522901 0 apt-key (616453.616453) > execve filename=/usr/bin/apt-config 30183 14:26:38.494442117 0 apt-config (616454.616454) > execve filename=/usr/bin/dpkg 30422 14:26:38.497278722 0 apt-key (616455.616455) ## Get Running with Apache Flink on Kubernetes, part 2 of 2 DevFeed: [Get Running with Apache Flink on Kubernetes, part 2 of 2]() Original publisher: [Read original article]() Published: 2025-01-28T00:00:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [apache-flink](), [Kubernetes](), [Availability](), [observability](), [Deployment](), [container](), [MinIO](), [Amazon S3](), [rocksdb](), [GitHub]() Tags: [apache-flink](), [availability](), [container-images](), [deployment](), [flink](), [github](), [kubernetes](), [minio](), [observability](), [rocksdb](), [s3](), [ui]() ### AI overview Part two of a tutorial series on running Apache Flink jobs on Kubernetes. It explains checkpointing, job manager high availability, savepoints, external object storage, incremental RocksDB checkpoints, observability, and related job-management practices. ### Source excerpt Table of Contents Fault Tolerance and High Availability Manually Triggering Savepoints Observability Bonus: Managing Flink Jobs With the Heimdall UI Summary and Discussion This post originally appeared on the Decodable blog. All rights reserved. Welcome back to this two-part blog post series about running Apache Flink on Kubernetes, using the Flink Kubernetes operator. In part one, we discussed installation and setup of the operator, different deployment types, how to deploy Flink jobs using custom Kubernetes resources, and how to create container images for your own Flink jobs. In this part, we'll focus on aspects such as fault tolerance and high availability of your Flink jobs running on Kubernetes, savepoint management, observability, and more. You can find the complete source code for all the examples shown in this series in the Decodable examples repository on GitHub: on GitHub. ## Trino on ice IV: Deep dive into Iceberg internals DevFeed: [Trino on ice IV: Deep dive into Iceberg internals]() Original publisher: [Read original article]() Author: Brian Olsen Published: 2021-08-12T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Apache Iceberg](), [Instrumentation](), [AWS Glue](), [data]() Tags: [aws-glue](), [blog](), [blog-post](), [data](), [deep-dive](), [instrumentation](), [minio]() ### AI overview This deep-dive article explains Iceberg internals in the context of the Trino query engine. It examines metadata and files produced by Trino operations, using tools such as Avro tools, the MinIO client, and Iceberg's core library, with emphasis on understanding, troubleshooting, and querying Iceberg tables. ### Source excerpt Welcome to the Trino on ice series, covering the details around how the Iceberg table format works with the Trino query engine. The examples build on each previous post, so it's recommended to read the posts sequentially and reference them as needed later. Here are links to the posts in this series: Trino on ice I: A gentle introduction to Iceberg Trino on ice II: In-place table evolution and cloud compatibility with Iceberg Trino on ice III: Iceberg concurrency model, snapshots, and the Iceberg spec Trino on ice IV: Deep dive into Iceberg internals So far, this series has covered some very interesting user level concepts of the Iceberg model, and how you can take advantage of them using the Trino query engine. This blog post dives into some implementation details of Iceberg by dissecting some files that result from various operations carried out using Trino. To dissect you must use some surgical instrumentation, namely Trino, Avro tools, the MinIO client tool and Iceberg's core library. It's useful to dissect how these files work, not only to help understand how Iceberg works, but also to aid in troubleshooting issues, should you have any issues during ingestion or querying of your Iceberg table. I like to think of this type of debugging much like a fun game of operation, and you're looking to see what causes the red errors to fly by on your screen. ## Upgrading ElasticSearch 2 to 5: S3 snapshot/restore strategy DevFeed: [Upgrading ElasticSearch 2 to 5: S3 snapshot/restore strategy]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [elasticsearch](), [migration](), [Amazon S3](), [Docker Compose](), [version](), [Testing](), [MinIO]() Tags: [docker-compose](), [elasticsearch](), [migration](), [minio](), [restore](), [s3](), [snapshot](), [testing](), [version]() ### AI overview This tutorial explains a strategy for migrating an ElasticSearch cluster from version 2 to version 5 by creating test environments, snapshotting the ES2 cluster, and restoring the snapshot on ES5 using S3. It also describes using Docker Compose and MinIO for safe testing before production migration. ### Source excerpt Migrating an ElasticSearch cluster from version 2 to 5 can be challenging, even more if it is a big cluster.