<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>存储 on 黄文卓 | DevOps Engineer</title><link>https://socake.github.io/categories/%E5%AD%98%E5%82%A8/</link><description>Recent content in 存储 on 黄文卓 | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor><webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster><copyright>© 2026 Wenzhuo Huang</copyright><lastBuildDate>Fri, 13 Dec 2024 11:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/categories/%E5%AD%98%E5%82%A8/index.xml" rel="self" type="application/rss+xml"/><item><title>Rook-Ceph on Kubernetes 运维实战：从部署到故障恢复</title><link>https://socake.github.io/posts/ceph-rook-kubernetes/</link><pubDate>Fri, 13 Dec 2024 11:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/ceph-rook-kubernetes/</guid><description>当你需要在 Kubernetes 上提供 block、file、object 三种存储时，Rook-Ceph 是几乎没有替代品的方案。但它的复杂度也是所有 K8s 存储方案里最高的。这篇文章是我在一套裸金属 Rook-Ceph 生产集群上两年运维经验的整理，包括几次把集群从悬崖边拉回来的复盘。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/ceph-rook-kubernetes/featured.jpg"/></item><item><title>MinIO 分布式对象存储生产实践：从 Erasure Code 到多租户</title><link>https://socake.github.io/posts/minio-distributed-storage/</link><pubDate>Mon, 02 Dec 2024 10:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/minio-distributed-storage/</guid><description>自建对象存储曾经是件麻烦事，直到 MinIO 把 S3 API + Erasure Code + 简单部署这件事做到了极致。这篇文章是我在三套生产 MinIO 集群上的运维笔记，覆盖从硬件选型到故障救火的全链路。同时会聊一下 2024 年 MinIO 商业化策略调整后，社区版用户应该怎么办。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/minio-distributed-storage/featured.jpg"/></item></channel></rss>