{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2022-12-17T09:47:09.849Z",
  "attributedTo":"https://k.matthias.org/actors/relistan",
  "inReplyTo":"https://k.matthias.org/objects/t6BayfiTEGo",
  "to":["https://k.matthias.org/actors/relistan","https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://k.matthias.org/actors/relistan/followers"],
  "content":"<p>One major win is that we always maintained our own deployment config format in a centralized repo. That has made it really light weight to build tooling to deploy to either <a href=\"https://k.matthias.org/tags/Mesos\" class=\"hashtag\" rel=\"tag\">#Mesos</a> or to <a href=\"https://k.matthias.org/tags/Kubernetes\" class=\"hashtag\" rel=\"tag\">#Kubernetes</a> during the migration.&nbsp;</p><p>We also have service discovery that spans both clusters, with instances of the same app available from either cluster. We can roll back and forth between Mesos or Kubernetes without any changes to configs. That really lowers the risk of the migration.</p><p>There are about 125 services to move. Most of them will be a simple redeploy.&nbsp;</p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#Mesos","href":"https://k.matthias.org/tags/Mesos"},
      {"type":"Hashtag","name":"#Kubernetes","href":"https://k.matthias.org/tags/Kubernetes"}
  ],
  "type":"Note",
  "id":"https://k.matthias.org/objects/KaEn_h-N4W4"
}