{
  "id": 7229217,
  "title": "Migrated Up, Then Back",
  "url": "https://urgent.news/2026/09/14/migrated-up-then-back",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-14T02:20:55.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jeromefromhk/migrated-up-then-back-3j10"
  },
  "original_language": "en",
  "account": "A self-hosted services provider migrated seven of their services onto Kubernetes, including ArgoCD, supply-chain policy, and GitOps loop. However, they later moved all seven back to Docker Compose, a move that wasn't a technical failure but was due to a shift in perspective about what Kubernetes is for. The migration involved compressing a single 4-core, 24-gig machine to run compose stacks behind one reverse proxy and adding K3s to the same box without using new hardware. The services were moved in phases, with ArgoCD ensuring each service was synced and healthy on k3s. When they decided to revert back to Docker Compose, they did so in a single day, keeping only three services on k3s, which were deemed open-source software the provider didn't write. The decision to reverse the migration was based on the observation that these open-source images didn't pay back Kubernetes with software the provider authored. These third-party images didn't integrate well with the cluster's network policy, CI pipeline, internal DNS, or admission rules, making them unsuitable for integration with Kubernetes. The provider found that there was no necessary reason for these stock open-source images to integrate with their cluster, and the value proposition of Kubernetes, such as canary releases and service meshes, only existed for producers, not consumers. The provider also noted that supply-chain policy, which they had been proud of, had a notion of a clean scan, but for software they didn't write, fixing vulnerabilities meant running a fork of the upstream image, applying patches, and rebasing their changes onto every release, which was a costly and ongoing process. The provider concluded that the cost of this approach was not hypothetical, as repairs forced upon them due to the migration are documented in their incident log.",
  "summary": "Over a few weeks I moved seven self-hosted services onto Kubernetes — ArgoCD, supply-chain policy, the whole GitOps loop — and then, on one afternoon, I moved all seven back to Docker Compose. This is the part almost nobody writes about: not the triumphant migration, but the reversal, and the reasoning that justified both halves of it. The reversal wasn't a technical failure. What broke was…",
  "key_points": [
    "Migrated seven services to Kubernetes, including ArgoCD and GitOps loop.",
    "Reverted back to Docker Compose within a day, keeping only three open-source services."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}