<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenCost on 黄文卓 | DevOps Engineer</title>
    <link>https://socake.github.io/tags/opencost/</link>
    <description>Recent content in OpenCost 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>Sun, 12 Apr 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/opencost/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>OpenCost 实战：Kubernetes 成本可见性与多团队费用分摊</title>
      <link>https://socake.github.io/posts/opencost-kubernetes-cost-visibility/</link>
      <pubDate>Sun, 12 Apr 2026 14:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/opencost-kubernetes-cost-visibility/</guid>
      <description>Kubernetes 成本不透明是 FinOps 落地的最大障碍。本文通过 OpenCost 构建完整的成本可见性体系，涵盖部署集成、云厂商价格接入、按团队分摊、Grafana 看板、超预算告警和自动周报推送，提供可直接复用的配置。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/opencost-kubernetes-cost-visibility/featured.jpg" />
    </item>
    
    <item>
      <title>FinOps 实践：Kubernetes 成本治理体系建设</title>
      <link>https://socake.github.io/posts/finops-kubernetes-cost-governance/</link>
      <pubDate>Sun, 12 Apr 2026 10:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/finops-kubernetes-cost-governance/</guid>
      <description>一套完整的 Kubernetes FinOps 落地路径：如何识别僵尸资源、配置成本分摊模型、利用 Karpenter 降低节点成本，以及如何将月账单从 $50k 压到 $30k。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/finops-kubernetes-cost-governance/featured.jpg" />
    </item>
    
  </channel>
</rss>
