Skip to content

Latest commit

 

History

History
251 lines (136 loc) · 10.6 KB

ReleaseNotes20.md

File metadata and controls

251 lines (136 loc) · 10.6 KB
Raw

Release Notes

New features

Docker EE 2.0 and Kubernetes

Docker Enterprise Edition (EE) 2.0 is the only platform that manages and secures applications on Kubernetes in multi-Linux, multi-OS and multi-cloud customer environments. With Docker EE 2.0, you get simplified workflows for the day-to-day management of a Kubernetes environment while still having access to native Kubernetes APIs, CLIs, and interfaces.

Note: Docker EE 2.0 installs Kubernetes version 1.8. In this release, Docker Universal Control Plane (UCP) uses its own role-based acccess control (RBAC) system which is not compatible with Kubernetes RBAC.

For more information on Docker EE 2.0, see https://blog.docker.com/2018/04/announcing-docker-enterprise-edition-2-0/ and https://www.docker.com/products/docker-enterprise.

A sample Kubernetes application has been documented in the section Kubernetes guestbook example with Redis to facilitate verification of the deployed playbooks and configuration. This example is also useful for exploring the new Kubernetes-specific features in the latest Splunk and Sysidg offerings.

Note: The verion of kubectl used to access the Kubernetes cluster needs to be 1.10 or below. The current release of kubectl is not compatible with the version of Kubernetes (1.8) shipped with Docker EE 2.0. See the section Installing kubectl.

Splunk 7.1.2 and Kubernetes

This minor update to Splunk Enterprise supports monitoring of Kubernetes logs and metrics. Kubernetes metadata is collected by a universal forwarder implemented as a Deployment (with just one replica), while logs are collected by a universal forwarder running on each Kubernetes node using a DaemonSet. The integration leverages the open-source Splunk IT Monitoring and Troubleshooting project at https://github.com/splunk/docker-itmonitoring.

This update also includes new versions of Splunk software components - see the section on installing the Splunk App for Windows Infrastructure and its dependencies here.

Sysdig and Kubernetes

Sysdig now supports the monitoring of Kubernetes clusters and the playbooks have been updated to make use of this new functionality. See the section Deploying Sysdig monitoring on Kubernetes for more information.

Prometheus and Grafana

Prometheus has been updated to version v2.3.2 while Grafana is now at version 5.2.3

Note: Prometheus and Grafana do not currently support monitoring Kubernetes worker nodes in this solution and so can only be used in conjunction with Docker swarm deployments.

Changes from previous release

Software updates

  • Docker EE changed to version 2.0 (UCP version 3.0.4, DTR version 2.5.3). The recommended RAM requirement for UCP has been increased to 16GB for production systems.
  • Splunk Enterprise version changed from 7.0.2 to 7.1.2. You must download and install version 7.1.2 of the relevant Splunk Universal Forwarder(s) as described in Splunk prerequisites.
  • RHEL 7.5
  • Prometheus v2.3.2
  • Grafana 5.2.3

Playbook updates

An overview of all the playbooks is available here. This section outlines the changes from the previous release of the playbooks.

New playbooks:

Modified playbooks:

  • playbooks/create_vms.yml
  • playbooks/install_nfs_server.yml

Renamed/Removed playbooks:

  • playbooks/monitoring.yml replaced by playbooks/splunk_uf.yml
  • playbooks/monitoring_win.yml replaced by playbooks/splunk_uf_win.yml
  • templates/monitoring folder renamed to templates/splunk

Configuration updates

New variables and configuration files have been introduced in this release.

Fixed in this release

Partition occupies all free space on boot drive

In the previous release, when a disk size of 100GB was requested for the boot drive, the drive was configured accordingly in the VM but the size of the / partition was determined by the template. The / partition is now resized to occupy all the free space of the boot drive. This fix has only been implemented for Linux VMs.

Known issues

An issue has been seen during the execution of the playbook playboooks/config_networking.yml when using RHEL 7.4. 

TASK [Change hostname with FQDN]
fatal: [<hostname>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ssh: connect to host <hostname> port 22: No route to host\r\n", "unreachable": true}

This error indicates that the configuration of the network interface of the virtual machine was not successful.

This error was seen with the VM running version 10.1.5.59732 (build-5055683) of the VMware tools and Red Hat 7.4. It was not reproduced with version 10.1.10.63510 (build-6082533) of the VMware tools plus Red Hat 7.5. As a result, we recommend that you update your Linux template to Red Hat 7.5 which will also upgrade the VMware tools if they were installed.