What's new in Version 2.1.0.2

Get a quick overview of what's added, changed, improved, or deprecated in this release.

IBM® Cloud Private Version 2.1.0.2 introduces the following new features or enhancements:

New features

Kubernetes

IBM Cloud Private Version 2.1.0.2 is now upgraded to use Kubernetes Version 1.9.1. For more information about the features that are introduced in Kubernetes 1.9.1, see https://github.com/kubernetes/sig-release/blob/master/releases/release-1.9/release-notes-draft.md External link icon.

Docker

IBM Cloud Private now supplies Docker packages for most of the supported operating systems and platforms. These Docker packages are available for manual installation on boot nodes and automatic installation on cluster nodes. See Using the supplied IBM Cloud Private Docker packages.

Cluster management

Cluster management from the IBM Cloud Private management console

You can now perform the following functions from the IBM Cloud Private management console:

Cluster management from the IBM Cloud Private CLI

If you installed the IBM Cloud Private CLI, you can now perform the following functions:

Helm CLI

TLS certificates are now needed to use the Helm CLI. See, Setting up the Helm CLI.

Role-based access control of resources

For IBM Cloud Private Version 2.1.0.2, the role-based access control of some resources such as Helm repository and charts are revised. Only the cluster administrator can add, remove, or synchronize Helm charts. See, Role-based access control.

Managing external cluster access

The cluster_access_ip and proxy_access_ip parameter values that were used in earlier versions of IBM Cloud Private are deprecated. Use the cluster_lb_address and proxy_lb_address parameters instead. You can set IP addresses, fully-qualified domain names, or OpenStack floating IP addresses as the values of these parameters. See Customizing the cluster with the config.yaml file.

Cluster access URL

You can now customize the URL that you use to log in to the IBM® Cloud Private cluster management console. For more information, see Customizing the cluster access URL.

Cluster administrator

The super administrator is now called the cluster administrator.

Vulnerability Advisor is now GA

Use the Vulnerability Advisor to get security status for containers and images that are running in your IBM Cloud Private Cloud Native and IBM Cloud Private Enterprise edition clusters. See Vulnerability advisor.

Security

LDAP integration

Metering

You can now gather information about core, memory, and processor usage for subsets of your environment. These metrics can now be tracked by strategic namespace usage or deployment metadata management. Information that is collected can be used to manage billing for the cluster users, a practice that is commonly known as "chargeback." See Using the metering service to manage chargebacks.

More detailed reporting is also available with this release, as metrics are now collected at the container level and not the pod level.

New packages

The following new packages are available from the catalog:

Technology previews

The following features are available as technology previews:

Fixes and improvements

With the introduction of IBM Cloud Private Version 2.1.0.2, the following improvements and enhancements were made:

IBM Cloud Private Cloud Foundry changes

For the details of changes to IBM Cloud Private Cloud Foundry, see What's new in IBM Cloud Private Cloud Foundry Version 2.1.0.2.

Kibana Helm chart removed from the public repository

Beginning March 8, 2019, the ibmcom/ibm-icplogging-kibana was removed from the public repository in the IBM Cloud Private Catalog. The Kibana instance is installed automatically, and can be enabled. See Kibana for more information.

Moved Helm charts

What changed

With the introduction of IBM Cloud Private Version 2.1.0.2, the following package versions changed: