--- title: vip-manager v5 is out: what you need to know | daily.dev description: vip-manager v5 introduces two major breaking changes that require attention before upgrading in production. First, deprecated configuration parameters have... canonical: https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: vip-manager v5 is out: what you need to know | daily.dev og:description: vip-manager v5 introduces two major breaking changes that require attention before upgrading in production. First, deprecated configuration parameters have... og:url: https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh og:image: https://api.daily.dev/og/posts/0Npe2XiHh.png og:image:alt: vip-manager v5 is out: what you need to know og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # vip-manager v5 is out: what you need to know **[Planet PostgreSQL](https://daily.dev/sources/planet-postgresql)** · 6 min read · 2 upvotes · 0 comments ## Summary vip-manager v5 introduces two major breaking changes that require attention before upgrading in production. First, deprecated configuration parameters have been removed, meaning old vip-manager.yml files may cause startup failures. Second, and more significantly, the VIP is now automatically removed when the DCS (etcd, Consul, ZooKeeper, etc.) becomes unreachable — a deliberate shift toward consistency over availability to prevent split-brain scenarios. Previously, the VIP was kept on the current node during DCS outages. Additionally, a bug causing stale VIP state after canceled etcd watches has been fixed. The recommended upgrade path includes testing in a non-production environment with simulated DCS outages, updating monitoring and runbooks to treat VIP removal during DCS outages as expected behavior, cleaning up configuration files, and revising failover procedures to check DCS health first when a VIP disappears. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What happens to the VIP in vip-manager v5 when the DCS becomes unreachable? vip-manager v5 automatically removes the VIP when the DCS (etcd, Consul, ZooKeeper, or patroni) becomes unreachable, instead of keeping it as older versions did. This change prevents split-brain scenarios where two nodes could both think they are primary and serve writes, but it means temporary DCS outages now cause VIP loss and short application downtime even if PostgreSQL itself stays healthy. _Teams tuning HA failover behavior can track breaking changes like this one on daily.dev before rolling out an upgrade._ ### Will my vip-manager.yml config still work after upgrading to vip-manager v5? Not necessarily, because vip-manager v5 refactored configuration handling and removed deprecated parameters entirely. Any old or deprecated keys still present in vip-manager.yml can cause vip-manager to fail to start or behave unexpectedly, so configs must be reviewed, deprecated keys removed, and renamed keys updated to their current names before upgrading. _Ops engineers planning a config migration can follow breaking-change writeups like this via daily.dev before touching production._ ### How does vip-manager v5 fix stale VIP state after an etcd watch is canceled? vip-manager v5 properly re-synchronizes its view of leadership after an etcd watch cancellation, updating VIP state to match the real leadership state in etcd. Previously, a canceled etcd watch could leave vip-manager with a stale VIP attached to the wrong node or not updated after a leadership change, sometimes called a phantom primary. _Anyone debugging phantom-primary incidents can follow HA fixes like this through daily.dev to stay ahead of outages._ ## Similar posts on daily.dev - [How We Eliminated Configuration-Related Outages and Scaled Consul Management at Agoda](https://daily.dev/posts/how-we-eliminated-configuration-related-outages-and-scaled-consul-management-at-agoda-xmk7lnclj) · agoda · 0 upvotes · 0 comments - [From Minutes to Seconds: Uber Boosts MySQL Cluster Uptime with Consensus Architecture](https://daily.dev/posts/from-minutes-to-seconds-uber-boosts-mysql-cluster-uptime-with-consensus-architecture-1uhaxiyym) · InfoQ · 0 upvotes · 0 comments --- Tags: [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"vip-manager v5 is out: what you need to know","url":"https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh"},"datePublished":"2026-07-30T14:46:12.577Z","dateModified":"2026-09-14T08:18:32.167Z","description":"vip-manager v5 introduces two major breaking changes that require attention before upgrading in production. First, deprecated configuration parameters have...","image":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","thumbnailUrl":"https://media.daily.dev/image/upload/s--P4t4XyoV--/f_auto/v1722860399/public/Placeholder%2001","isAccessibleForFree":true,"articleSection":"Planet PostgreSQL","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet PostgreSQL","logo":"https://media.daily.dev/image/upload/logos/placeholder.jpg","url":"https://daily.dev/sources/planet-postgresql"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"postgresql","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet PostgreSQL","item":"https://daily.dev/sources/planet-postgresql"},{"@type":"ListItem","position":3,"name":"vip-manager v5 is out: what you need to know"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/vip-manager-v5-is-out-what-you-need-to-know-0npe2xihh#faq","mainEntity":[{"@type":"Question","name":"What happens to the VIP in vip-manager v5 when the DCS becomes unreachable?","acceptedAnswer":{"@type":"Answer","text":"vip-manager v5 automatically removes the VIP when the DCS (etcd, Consul, ZooKeeper, or patroni) becomes unreachable, instead of keeping it as older versions did. This change prevents split-brain scenarios where two nodes could both think they are primary and serve writes, but it means temporary DCS outages now cause VIP loss and short application downtime even if PostgreSQL itself stays healthy. Teams tuning HA failover behavior can track breaking changes like this one on daily.dev before rolling out an upgrade."}},{"@type":"Question","name":"Will my vip-manager.yml config still work after upgrading to vip-manager v5?","acceptedAnswer":{"@type":"Answer","text":"Not necessarily, because vip-manager v5 refactored configuration handling and removed deprecated parameters entirely. Any old or deprecated keys still present in vip-manager.yml can cause vip-manager to fail to start or behave unexpectedly, so configs must be reviewed, deprecated keys removed, and renamed keys updated to their current names before upgrading. Ops engineers planning a config migration can follow breaking-change writeups like this via daily.dev before touching production."}},{"@type":"Question","name":"How does vip-manager v5 fix stale VIP state after an etcd watch is canceled?","acceptedAnswer":{"@type":"Answer","text":"vip-manager v5 properly re-synchronizes its view of leadership after an etcd watch cancellation, updating VIP state to match the real leadership state in etcd. Previously, a canceled etcd watch could leave vip-manager with a stale VIP attached to the wrong node or not updated after a leadership change, sometimes called a phantom primary. Anyone debugging phantom-primary incidents can follow HA fixes like this through daily.dev to stay ahead of outages."}}]} ```