1.0.3

What's New

The CloudStack Container Service is now open sourced under the Apache License Version 2. In addition to changing all license collateral to the new license, the package repositories have been moved to allow public access. The latest 1.0.3 version will work with Apache CloudStack 4.11.1.0+ and brings support for the latest Kubernetes v1.11.4 and CoreOS (stable) 1855.5.0. In the new version, the API server runs by default on port 6443 to allow port 443 to be used by any user application.

Upgrading to 1.0.3

Since the package repositories have moved, existing users must add the new package repository and upgrade the shapeblue-ccs package. Ensure you're running Apache CloudStack 4.11.1.0 or above.

RHEL/CentOS 6 & 7

1. Define the yum repository by creating /etc/yum.repos.d/ccs.repo with the following
   content:

   [ccs-1. 0]
   name=ccs
   baseurl=http://packages.shapeblue.com/ccs/centosenabled=1
   gpgcheck=1
   gpgkey=http://packages.shapeblue.com/release.asc
   

2. Import the ShapeBlue Release GPG Key (Key ID: 584DF93F; Key fingerprint: 7203 0CA1 18C1 A275 68B1 37C4 BDF0 E176 584D F93F) with the following commands:

   # wget http://packages.shapeblue.com/release.asc
   # sudo rpm --import release.asc
   

3. Upgrade CCS to 1.0.3 by executing the yum update shapeblue-ccs command

Debian/Ubuntu

1. Define the apt repository by creating /etc/apt/sources.list.d/ccs.list with the following
   content:

   deb http://packages.shapeblue.com/ccs/debian/
   

2. Import the ShapeBlue Release GPG Key (Key ID: 584DF93F; Key fingerprint: 7203 0CA1
   18C1 A275 68B1 37C4 BDF0 E176 584D F93F) with the following commands:

   # wget -qO- http://packages.shapeblue.com/release.asc | sudo apt-key add -
   

3. Upgrade CCS to 1.0.3 by executing the apt-get upgrade; apt-get upgrade shapeblue-ccs command

Known Issues and Limitations

The following are the known issues and limitations in the CCS 1.0.3 release:

• Each node should have at least 2GB RAM per Kubernetes docs.
• Recovery of the Kubernetes cluster master is not supported. If a cluster master node fails, the
  cluster must be rebuilt. (Issue #30)
• Recovery of a Kubernetes node VM is not supported. If a VM underlying a Kubernetes node fails, the
  cluster must be rebuilt to bring the cluster back to full capacity. (Issue #31)
• Kubernetes availability master node deployment is not supported. (Issue #32)
• Docker is the only supported container runtime (Issue #33)
• The etcd store for each Kubernetes cluster is deployed on the cluster master and not configured for
  high-availability or replication (Issue #34)
• An existing CloudStack defect causes numerous warnings to be logged about the an unknown parameter, listAll, for the listContainerCluster API. This warning is spurious and is not an indication that management server is malfunctioning. (Issue #37)
• Kubernetes deployment is managed using kubeadm which creates and uses its own CA PKI because of which CA certificates import in browser will not fix the security warnings. A user can ignore and proceed to use the dashboard by logging in using the credentials manually. (Issue #59)
• Dashboard not available for unauthenticated users, kubectl proxy use is advised. (Issue #63)
• UI Issue: Safari on Mac OS X treats the embedded Kubernetes Dashboard as a phishing site. Therefore, when accessing it will cause Safari to display a phishing warning. (Issue #35)
• UI Issue: In Container Cluster Details view, if the user issues Destroy Cluster command and stays on the same page until the command is finished, they might encounter an error message "Unable to find account by id: ...". The container cluster will be deleted as expected and a page refresh will display the correct information. (Issue #36)
• UI Issue: Kubernetes Dashboard embedding does not work in the Internet Explorer and Edge browsers. ShapeBlue recommends using either Mozilla Firefox or Google Chrome when administering CCS from Windows. (Issue #37)

1.0.1

What's New

The CloudStack Container Service is now open sourced under the Apache License Version 2. In addition to changing all license collateral to the new license, the package repositories have been moved to allow public access.

Upgrading from 1.0.0 to 1.0.1

Since the package repositories have moved, existing users must add the new package repository and upgrade the shapeblue-ccs package.

RHEL/CentOS 6 & 7

1. Define the yum repository by creating /etc/yum.repos.d/ccs.repo with the following
   content:

   [ccs-1. 0]
   name=ccs
   baseurl=http://packages.shapeblue.com/ccs/centosenabled=1
   gpgcheck=1
   gpgkey=http://packages.shapeblue.com/release.asc
   

2. Import the ShapeBlue Release GPG Key (Key ID: 584DF93F; Key fingerprint: 7203 0CA1 18C1 A275 68B1 37C4 BDF0 E176 584D F93F) with the following commands:

   # wget http://packages.shapeblue.com/release.asc
   # sudo rpm --import release.asc
   

3. Upgrade CCS to 1.0.1 by executing the yum update shapeblue-ccs command

Debian/Ubuntu

1. Define the apt repository by creating /etc/apt/sources.list.d/ccs.list with the following
   content:

   deb http://packages.shapeblue.com/ccs/debian/
   

2. Import the ShapeBlue Release GPG Key (Key ID: 584DF93F; Key fingerprint: 7203 0CA1
   18C1 A275 68B1 37C4 BDF0 E176 584D F93F) with the following commands:

   # wget -qO- http://packages.shapeblue.com/release.asc | sudo apt-key add -
   

3. Upgrade CCS to 1.0.1 by executing the apt-get upgrade; apt-get upgrade shapeblue-ccs command

Known Issues

The following are the known issues in the CCS 1.0.1 release:

• Recovery of the Kubernetes cluster master is not supported. If a cluster master node fails, the
  cluster must be rebuilt. (Issue #30)
• Recovery of a Kubernetes node VM is not supported. If a VM underlying a Kubernetes node fails, the
  cluster must be rebuilt to bring the cluster back to full capacity. (Issue #31)
• Kubernetes availability master node deployment is not supported. (Issue #32)
• Docker is the only supported container runtime (Issue #33)
• The etcd store for each Kubernetes cluster is deployed on the cluster master and not configured for
  high-availability or replication (Issue #34)
• An existing CloudStack defect causes numerous warnings to be logged about the an unknown parameter, listAll, for the listContainerCluster API. This warning is spurious and is not an indication that management server is malfunctioning. (Issue #37)
• UI Issue: Safari on Mac OS X treats the embedded Kubernetes Dashboard as a phishing site. Therefore, when accessing it will cause Safari to display a phishing warning. (Issue #35)
• UI Issue: In Container Cluster Details view, if the user issues Destroy Cluster command and stays on the same page until the command is finished, they might encounter an error message "Unable to find account by id: ...". The container cluster will be deleted as expected and a page refresh will display the correct information. (Issue #36)
• UI Issue: Kubernetes Dashboard embedding does not work in the Internet Explorer and Edge browsers. ShapeBlue recommends using either Mozilla Firefox or Google Chrome when administering CCS from Windows. (Issue #37)

CCS 1.0.0-rc3

Merge pull request #19 from shapeblue/rename-pkg-jar

ccs: fix package name and jar name

CCS 1.0.0-rc2

Merge pull request #18 from shapeblue/jsb/licensing

Add license collateral and headers to plain-text artifacts

CCS 1.0.0-rc1

CCS 1.0.0 RC1