Releases: projectcalico/calicoctl
Version v0.8.0 New libnetwork plugin integration
This release updates calico-docker to utilize the latest libnetwork-plugin that uses the latest libnetwork and IPAM APIs that are part of the current Docker 1.9 development. The latest libnetwork plug-in image is reduced to just containing the libnetwork plugin, and no longer wrpas up the plug in with the calico-node (felix, bird and confd).
calicoctl node --libnetwork now spins up both the calico/node and calico/libnetwork-node containers together.
If you plan on using Calico with libnetwork, an development Docker build is required to make use of the new libnetwork architecture.
The changes in the Project Calico fork of python-etcd have now been upstreamed to the core etcd repo. This release now uses the upstream version of etcd (>=v4.2)
Notable Merges:
- #494: Upgrade calico-kubernetes to
[email protected] - #469: Rework confd templates to reduce confd churn
- #508: Adding auto_assigning IP logic to calicoctl container
- #510: Add new calicoctl ipam commands
- #516: calicoctl node starts/stops libnetwork plugin as separate container
- #526: Use upstream etcd
- #528: Add route aggregation based on IPAM
Project Calico module updates:
Version v0.7.0 New IPAM and `rkt` Plugin Integration
This release brings the calico-docker repo up to date with the new IPAM changes introduced in [email protected].
calicoctl node --kubernetes now takes advantage of our IPAM improvements to calico-kubernetes.
Improvements to felix bring increased performance.
The libnetwork plugin has been updated to handle API changes. If you plan on using Calico with libnetwork, an experimental Docker build is required to make use of the libnetwork features.
Notable Merges:
- #482:
calico-rktplugin integration incalicoctl - #494: Upgrade calico-kubernetes to
[email protected]
Project Calico module updates:
Version v0.6.0 Use Felix 1.0 and add new calicoctl config command
The calico/node Docker image now uses the released version of Calico Felix 1.0.
Calico libnetwork plugin has been refactored into its own repository: projectcalico/libnetwork-plugin. To run calico with libnetwork, run the calicoctl node command with the --libnetwork flag or specify --node-image=calico/node-libnetwork.
BIRD binaries are now being created and stored in projectcalico/calico-bird.
New calicoctl config command allows specifying loglevels of logs for Felix, bgp, and per-node bgp.
Bug Fix:
- #462: Fix issue with
calicoctl nodecommand autodetecting docker bridge IP as the host's IP address.
Version v0.5.5 Kubernetes Plugin Independence
This release decouples projectcalico/calico-kubernetes from the projectcalico/calico-docker repo.
calicoctl node --kubernetes will now load the new v0.1.0 release of the calico_kubernetes binary, enabling Calico policy in Kubernetes deployments.
If you plan on using Calico with libnetwork, an experimental Docker build is required to make use of the libnetwork features. For more information on how this affects your deployment see our previous release.
Version v0.5.4 Felix Update + calicoctl version command
The felix process has been updated to version 0.28.
calicoctl version command will print the version of calicoctl being used.
As with previous releases, an experimental Docker build is required to make use of the libnetwork features. In particular, a build from at least July 18th is required. We recommend installing the latest version of experimental docker on your machine by running the command for experimental builds found here.
Since the docker builds are brand new and released daily, there is potential for a build to not work correctly. For this case, we've included a docker build from moby/moby@38e5764 that has been tested and functions correctly on Ubuntu 14.04 64-bit. Download this docker binary, make the binary executable, then copy it to the current location of docker. You will have to restart the docker process in order for this to take effect.
Version 0.5.3
- Several fixes for Kubernetes support including the new
calicoctl node --kubernetesflag which will install the Kubernetes binary on the host - Adjusted logging level which was slowing down calico at scale
As with previous releases, an experimental Docker build is required to make use of the libnetwork features. In particular, a build from at least July 18th is required. At the current time, Docker haven't updated their experimental repos with a recent enough release, so a build from moby/moby@3ee15ac on the official docker master branch is attached below.
Download this docker binary, make the binary executable, then copy it to the current location of docker. You will have to restart the docker process in order for this to take effect.
Version 0.4.9 Hotfix for alternative Unix socket
Fixes #363 - [Powerstrip] calicoctl node fails if alternate unix socket in use
Version v0.5.2 libnetwork Plugin Rewrite
Various improvements and bug fixes
New command calicoctl pool range add <START_IP> <END_IP> allows specifying a range of IP addresses for calico to use when assigning addresses to newly created containers.
As with previous releases, an experimental Docker build is required to make use of the libnetwork features. In particular, a build from at least July 18th is required. At the current time, Docker haven't updated their experimental repos with a recent enough release, so a build from moby/moby@3ee15ac on the official docker master branch is attached below.
Download this docker binary, make the binary executable, then copy it to the current location of docker. You will have to restart the docker process in order for this to take effect.
Version 0.5.1
- New
--kubernetesflag added tocalicoctl nodewhich will install the calico-kubernetes plugin on the host - Improved documentation on Calico with libnetwork
- Numerous bugfixes
Version 0.5.0 Docker libnetwork integration
Added support for Experimental Docker's libnetwork network driver. This version of Calico should be used in conjunction with Experimental Docker version 1.8, which is included as a release binary.
Calico's usage of the Powerstrip networking plugin is now deprecated.
The calicoctl command help text has been updated and improved for clarity and simplicity. Different commands within calicoctl now have their own descriptions.