KCM v0.2.0

Source build

$ tar -xvzf kubernetes-comms-mvp-0.2.0.tar.gz
$ cd kubernetes-comms-mvp-0.2.0
$ make

Release notes

• KCM init takes into account the isolcpus kernel parameter when constructing
  the pool configuration directory. For more information on how to configure
  this kernel option for use with KCM, see the CLI documentation for KCM init.
• KCM nodereport includes a new field called "topology" to describe the
  the relation of logical CPUs to physical cores and sockets. CPUs in this
  structure are designated as "isolated" or not (per isolcpus.)
• KCM init no longer exits abnormally if the configuration directory
  already exists.
• KCM discover properly updates the existing node taints. This allows
  the command to succeed when run on an already-tainted node.
• Default KCM image pull policy in pod templates and cluster-init is now
  IfNotPresent (was Never.)
• KCM waits for Kubernetes thirdparty resource to exist before creating
  instances. This previously caused spurious initial restarts of the
  reconcile-nodereport pod.
• Various test and doc improvements.
• Various minor fixes in documentation and pod template files.

v0.2.0-rc2

KCM v0.2.0-rc2

v0.2.0-rc1

KCM v0.2.0-rc1

KCM v0.1.1

Source build

$ tar -xvzf kubernetes-comms-mvp-0.1.1.tar.gz
$ cd kubernetes-comms-mvp-0.1.1
$ make

Using prebuilt docker container

$ gunzip kcm-v0.1.1-docker.tar.gz
$ docker load --input kcm-v0.1.1-docker.tar

v0.1.1-rc3

KCM v0.1.1-rc3

v0.1.1-rc2

KCM v0.1.1-rc2

v0.1.1-rc1

KCM v0.1.1-rc1

KCM v0.1.0

Loading the pre-built Docker image:

$ gunzip kcm-v0.1.0-docker.tar.gz
$ docker load --input kcm-v0.1.0-docker.tar

v0.1.0-rc4

KCM v0.1.0-rc4

v0.1.0-rc3

KCM v0.1.0-rc3