)]}'
{
  "commit": "9ce118455933da3a4863ffb51b21542569174e56",
  "tree": "aec24655c727d53a81a15df7e132f3af42810ceb",
  "parents": [
    "7820e75e8dfa4df8ebbff697f91711971b41e8c6"
  ],
  "author": {
    "name": "Aleksei Kasatkin",
    "email": "akasatkin@mirantis.com",
    "time": "Fri Nov 23 14:27:33 2018 +0100"
  },
  "committer": {
    "name": "Aleksei Kasatkin",
    "email": "akasatkin@mirantis.com",
    "time": "Wed Dec 05 17:57:03 2018 +0100"
  },
  "message": "Add verification of Calico policy setting during upgrade\n\nIn order to perform Calico upgrade properly, it\u0027s required to\ndetermine whether Calico policy is enabled on the environment already\nand to align policy settings for Calico v3.x (that will be running\nafter upgrade) accordingly.\n\nThe following actions are performed:\n1. Check CNI config for policy settings.\n2. Check Kubernetes addons for calico_policy addon.\n3. Check whether kube-controllers pod is running.\n4. Remove v2.6.x calico_policy addon on masters to not interfere with\n   v3.x kube-controllers.\n5. Check consistency between Calico policy entities detected during\n   pp.1-3. Show a warning and do not touch policy turn on/off flag in\n   case of non-consistency.\n6. Check Calico policy setting for v3.x (that will be effective after\n   upgrade) if Calico policy was enabled for currently running\n   environment (so for Calico v2.6.x) already.\n7. Issue a warning message if Calico policy is enabled currently but\n   it is going to be disabled after upgrade.\n\nIt\u0027s safe to enable Calico policy any time, but it may be unsafe to\ndisable it. So, no need to disable Calico policy for v3.x if it\u0027s\nnot in use currently. But if Calico policy is in use already, it\nshould be enabled after upgrade as well.\n\nRelated-Prod: PROD-25161 (PROD:25161)\n\nChange-Id: I35634adef52c29037b0184440aae9cbb4872ffd5\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "980aa2f49206f4ad4260c7797ccf245cb9a9b617",
      "old_mode": 33188,
      "old_path": "k8s-upgrade-pipeline.groovy",
      "new_id": "f9a16e075d6bff662ebbe2dba2aecd187c37f683",
      "new_mode": 33188,
      "new_path": "k8s-upgrade-pipeline.groovy"
    }
  ]
}