What's new in Version 220.127.116.11
Get a quick overview of what's added, changed, improved, or deprecated in this release.
IBM® Cloud Private Version 18.104.22.168 introduces the following new features or enhancements:
IBM Cloud Private Version 22.214.171.124 is now upgraded to use Kubernetes Version 1.10.0. For more information about the features that are introduced in Kubernetes 1.10.0, see https://github.com/kubernetes/sig-release/blob/master/releases/release-1.10/release-notes-draft.md .
- MongoDB replaces IBM Cloudant as the backend Database for IBM Cloud Private. See IBM Cloud Private components.
- You can now configure a vSphere Cloud Provider after you install IBM Cloud Private. See Configuring a vSphere Cloud Provider in your IBM Cloud Private cluster.
- Container Storage Interface (CSI) is now available as Beta. See Using Container Storage Interface (CSI).
- Rook is an open source orchestrator for distributed storage systems that run in cloud native environments. You can now configure Rook by installing the Helm chart. See Rook Ceph cluster .
- You can now configure GlusterFS by installing the Helm chart. See GlusterFS Storage cluster .
Helm resources can now be added to a team. Helm resources include the internal Helm repository and the Helm charts that are in the Helm repository. If a Helm repository is added to a team’s resources, the team has access to all the charts within the repository.
If a chart within the Helm repository is added to the team, then the user sees the Helm repository on the Helm repositories page. The Catalog displays the selected charts available to the team only.
When a team is created, if Helm repositories or charts are not added to the team, the Catalog page for the team is empty.
For more information about adding resource to a team, see Add resources to a team.
The internal Helm repository named
local-charts can now be added to the Helm CLI as an external repository.
local-charts can be used as a source to install charts into the cluster from Helm CLI. For more information, see
Adding the internal Helm repository to Helm CLI.
You can now view release notes information for most Helm charts in the Catalog. This release notes contains information about each Helm chart, such as the version, what's new, and any fixes, or enhancements added.
Some IBM Helm charts might not have a release note. Release notes are not available for third party Helm charts that are added to the Catalog.
Also filtering from the Catalog is now enhanced to cover more options. See Managing charts and apps.
You can now collect data from and report on resource consumption of IBM products that are running outside of your IBM Cloud Private environment. This environment can be bare metal, a VM, or another cloud platform. See Tracking usage of IBM products that are running outside of your IBM Cloud Private cluster.
Docker images that you build can include labels that identify the product identifier, name and version for the offering. These labels can be discovered by the metering daemon and used to associate metered runtime metrics with the instance of the offering that is running. For more information, see Labeling images for the IBM® Cloud Private metering service.
IBM Cloud Private CLI
You can add or remove a proxy node to your cluster by using the IBM Cloud Private CLI. See the Adding or removing a proxy node by using a cloud provider section in Adding or removing a cluster node by using a cloud provider for more information.
You can manage Secret passwords with the IBM Cloud Private CLI. You can enforce password requirements, change passwords, and restart the required pods and containers by using the IBM Cloud Private CLI. See Managing Secret passwords with the IBM Cloud Private CLI for more information.
You can manage service IDs, API keys, and policies for access to specific services that are needed by an application. See IBM Cloud Private CLI service API key commands and Creating a service ID by using IBM Cloud Private CLI for more information.
Authentication and authorization audit logs are now available in IBM Cloud Private. See Authentication and authorization audit logs.
You can enable end-to-end TLS encryption for the IBM Cloud Private Elasticsearch, Logstash, and Kibana (ELK) stack. When enabled, it not only secures all communication between every product in the stack, it does so with PKI-based mutual authentication.
Note: TLS encryption for the Elasticsearch product is currently supported only on
amd64-based platforms. Filebeat can still be deployed onto any platform for secure log streaming.
You can now configure an etcd node in your IBM Cloud Private cluster to improve the etcd performance. See Architecture.
You can now enable the Vulnerability Advisor feature after you install your IBM Cloud Private cluster. See Enabling and disabling IBM Cloud Private management services.
Vulnerability Advisor can now be managed by using APIs. See Vulnerability Advisor API.
The following new Helm charts are available from the Catalog:
General Data Protection Regulation (GDPR)
General Data Protection Regulation (GDPR) has been adopted by the European Union ("EU") and applies from May 25, 2018. See IBM Cloud Private platform considerations for GDPR readiness for information about features of IBM Cloud Private platform that you can configure, and aspects of the product’s use, that you should consider to help your organization with GDPR readiness.
The following features are available as technology previews:
- Cluster federation - In multiple cluster environments, you can use a federation to deploy and manage common services across multiple Kubernetes clusters. See Working with multiple clusters (federation).
- Running kube-proxy in IP Virtual Server (IPVS) mode. See Manage kube-proxy by using IPVS.
- Manage and secure microservices with Istio. See Working with Istio.
- Pod auto scaling by using custom metrics. See Horizontal pod auto scaling by using custom metrics.
- Using containerd as a runtime for cluster nodes. See Installing IBM Cloud Private by using containerd.
Fixes and improvements
With the introduction of IBM Cloud Private Version 126.96.36.199, the following improvements and enhancements were made:
- A Launch link is now available on the Workloads > Deployments page. You can use this link to access application for the associated deployment.
- You can now run proxy nodes on IBM® Z systems. See Supported node types by platform.
- Image names are now consistent across platform architectures. You no longer require a separate command to run the Linux® 64-bit and Linux® on Power® (ppc64le) installer images.
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 188.8.131.52.
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
ibmcom/ibm-icploggingchart was moved from the public repository to the
ibmcom/ibm-icpmonitoringchart was moved from the public repository to the
With the introduction of IBM Cloud Private Version 184.108.40.206, the following package versions changed:
- Calico is upgraded from Version 2.6.6 to Version 3.0.4.
- Calicoctl is upgraded from Version 1.6.3 to Version 2.0.2.
- Calico/cni is upgraded from Version 1.11.2 to Version 2.0.3.
- Calico/kube-policy-controller is upgraded from Version 1.0.3 to Version 2.0.2.
- Kubernetes is upgraded from Version 1.9.1 to Version 1.10.0.
- NGINX Ingress controller is upgraded from Version 0.9.0 to Version 0.12.0