Merge pull request #1539 from bcreane/release-v2.6.4

v2.6.4 versions update

_data/versions.yml

@@ -1,13 +1,71 @@
 v2.6:
+- title: v2.6.4
+  note: |
+    20 December 2017
+
+    - Certain configuration changes no longer cause Felix to restart, allowing
+      upgrades to Calico v3.0.0. [felix #1631](https://github.com/projectcalico/felix/pull/1631) (@fasaxc)
+
+    - Calico now assigns the host side of veth pairs a MAC address of `ee:ee:ee:ee:ee:ee`.
+      If this fails, it uses a kernel-generated MAC address as before. For more information,
+      refer to the [Troubleshooting FAQ](https://docs.projectcalico.org/v2.6/usage/troubleshooting/). [cni-plugin #436](https://github.com/projectcalico/cni-plugin/pull/436) (@tmjd)
+
+    - The CNI plugin now offers an optional environment variable called `CNI_OLD_CONF_NAME`.
+      If set, the CNI plug-in cleans up old configuration data during an upgrade, making it
+      easier to migrate to a new `CNI_CONF_NAME` value. [cni-plugin #392](https://github.com/projectcalico/cni-plugin/pull/392)(@weikinhuang)
+
+    - `calicoctl` now includes a new environment variable called `CALICO_LIBNETWORK_VETH_MTU`
+      that allows you to configure the MTU of veth endpoints when using the Docker orchestrator.
+      [libnetwork-plugin #164](https://github.com/projectcalico/libnetwork-plugin/pull/164) (@ti-mo)
+
+  components:
+    felix:
+      version: 2.6.3
+      url: https://github.com/projectcalico/felix/releases/tag/2.6.3
+    typha:
+      version: v0.5.4
+      url: https://github.com/projectcalico/typha/releases/tag/v0.5.4
+    calicoctl:
+      version: v1.6.3
+      url: https://github.com/projectcalico/calicoctl/releases/tag/v1.6.3
+      download_url: https://github.com/projectcalico/calicoctl/releases/download/v1.6.3/calicoctl
+    calico/node:
+      version: v2.6.4
+      url: https://github.com/projectcalico/calico/releases/tag/v2.6.4
+    calico/cni:
+      version: v1.11.2
+      url: https://github.com/projectcalico/cni-plugin/releases/tag/v1.11.2
+      download_calico_url: https://github.com/projectcalico/cni-plugin/releases/download/v1.11.2/calico
+      download_calico_ipam_url: https://github.com/projectcalico/cni-plugin/releases/download/v1.11.2/calico-ipam
+    confd:
+      version: v0.12.1-calico-0.4.3
+      url: https://github.com/projectcalico/confd/releases/tag/v0.12.1-calico-0.4.3
+    libnetwork-plugin:
+      version: v1.1.2
+      url: https://github.com/projectcalico/libnetwork-plugin/releases/tag/v1.1.2
+    calico/kube-controllers:
+      version: v1.0.2
+      url: https://github.com/projectcalico/k8s-policy/releases/tag/v1.0.2
+    calico-bird:
+      version: v0.3.1
+      url: https://github.com/projectcalico/calico-bird/releases/tag/v0.3.1
+    calico-bgp-daemon:
+      version: v0.2.1
+      url: https://github.com/projectcalico/calico-bgp-daemon/releases/tag/v0.2.1
+    networking-calico:
+      version: 1.4.3
+      url: http://git.openstack.org/cgit/openstack/networking-calico/commit/?h=1.4.3
+    calico/routereflector:
+      version: v0.4.1
+      url: ""
+
 - title: v2.6.4-rc3
   note: |
     19 December 2017
 
     This is a release candidate for testing purposes only.
     v2.6.4-rc3 has a felix fix for "liveness" checking: https://github.com/projectcalico/felix/pull/1662
 
-    <div class="alert alert-danger" role="alert"><b>Important</b>: If you are using the Kubernetes datastore and upgrading from Calico v2.4.x or earlier to Calico v2.5.x or later, you must <a href="https://github.com/projectcalico/calico/blob/master/upgrade/v2.5/README.md">migrate your Calico configuration data</a> before upgrading. Otherwise, your cluster may lose connectivity after the upgrade.</div>
-
   components:
     felix:
       version: 2.6.3-rc3
@@ -153,7 +211,7 @@ v2.6:
 
     Calico v2.6.3 addresses several outstanding common vulnerabilities and exposures (CVE).
 
-    - A new node controller for Kubernetes deployments clears data associated with deleted nodes from the Calico datastore, preventing conflicts that can lead to crash loops. 
+    - A new node controller for Kubernetes deployments clears data associated with deleted nodes from the Calico datastore, preventing conflicts that can lead to crash loops.
 
     <div class="alert alert-danger" role="alert"><b>Important</b>: If you are using the Kubernetes datastore and upgrading from Calico v2.4.x or earlier to Calico v2.5.x or later, you must <a href="https://github.com/projectcalico/calico/blob/master/upgrade/v2.5/README.md">migrate your Calico configuration data</a> before upgrading. Otherwise, your cluster may lose connectivity after the upgrade.</div>