<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Consul on Suzf Blog</title>
    <link>https://suzf.net/blog/tags/consul/</link>
    <description>Recent content in Consul on Suzf Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>i@suzf.net (JeffreySu)</managingEditor>
    <webMaster>i@suzf.net (JeffreySu)</webMaster>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Fri, 30 Jan 2026 16:32:53 +0800</lastBuildDate>
    <atom:link href="https://suzf.net/blog/tags/consul/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>consul server upgrade</title>
      <link>https://suzf.net/blog/posts/consul-server-upgrade/</link>
      <pubDate>Fri, 30 Jan 2026 16:32:53 +0800</pubDate><author>i@suzf.net (JeffreySu)</author>
      <guid>https://suzf.net/blog/posts/consul-server-upgrade/</guid>
      <description>&lt;p&gt;Upgrading a Consul cluster must follow the principle of &amp;ldquo;step by step, Servers before Clients, maintain compatibility&amp;rdquo;. If the version gap is too large (e.g., jumping from 1.1x directly to 1.2x), a direct upgrade may cause Raft protocol incompatibility or data corruption.&lt;/p&gt;&#xA;&lt;p&gt;Below is a detailed upgrade roadmap and procedure:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
