2.21.1

Released on 22 May 2018

Bug Fixes

  • Fixed a bug that blocked application state from updating while starting and stopping.
  • Fixed a bug that caused application Persistent Volumes to sometimes be excluded from snapshots with the Kubernetes scheduler.
  • Fixed a bug that prevented application Persistent Volumes from being restored with the Kubernetes scheduler.
  • Fixed a bug that caused the audit log to become unresponsive after restores with the Swarm scheduler.

2.21.0

Released on 15 May 2018

Changes

  • Replicated will now install Docker 17.12.1-ce as it’s default version of Docker for both the Native and Swarm schedulers.
  • The Replicated Native scheduler now supports Amazon Linux 2018.03.
  • Completed Kubernetes Jobs no longer appear in the Pods table on the Cluster page of the Admin Console.
  • Kubernetes DaemonSets and CronJobs are now removed when the application is stopped.
  • StatefulSets are are now scaled to 0 replicas when the application is stopped.
  • Added YAML for all resources to the support bundle.

Bug Fixes

  • Fixed an issue that prevented applications on Kubernetes from auto-starting after upgrade.
  • Improved functionality of the start/stop buttton in the admin console for the Kubernetes scheduler.
  • Fixed an issue that caused pods with multiple containers to report 0 ready in the pods table on the Cluster page of the Admin Console.
  • The storage_class param that configures the StorageClass for Replicated PersistentVolumeClaims is now applied to all application PersistentVolumeClaims when using the Kubernetes Scheduler.
  • Fixed the logging level in the Retraced processor and cron images to prevent excessive logging.
  • Fixed an issue that could sometimes cause the support bundle to be empty when run in a multi-node airgapped Kubernetes environment.
  • Fixed an issue that prevented support bundle commands from using the Docker API when using the Kubernetes scheduler.
  • Included Retraced logs in the Support Bundle when using the Kubernetes scheduler.
  • A file handle leak has been fixed that occured when the application was restarted.
  • Replicated Docker images have been updated to address the following CVEs: CVE-2018-7490, CVE-2018-6797, CVE-2018-6798, CVE-2018-6913

2.20.2

Released on 26 Apr 2018

Bug Fixes

  • Reduced logging by Retraced Cron and Processor containers to avoid filling up disk space.
  • Resolved an issue where Kubernetes app would not auto-start after installing a license.

2.20.1

Released on 23 Apr 2018

Changes

  • Support bundle v2 now includes Docker Journald logs and system load averages by default on all schedulers.
  • The Kubernetes scheduler uses a ClusterIP service for internal servers for online installs and a NodePort service for airgapped installs.

Bug Fixes

  • Replicated Operator now limits the size of retained application logs. This defaults to 500MB and can be configured by adding -e APP_LOG_SIZE=500MB in /etc/default/replicated-operator, with 0 being unlimited.
  • Resolved a failure to pull the replicated cmd image that may result in failures in raw preflight checks.
  • Fixed image pull errors in online multi-node airgap caused by attempting to use the local registry.

2.20.0

Released on 19 Apr 2018

New Features

Bug Fixes

  • Resolved an issue that prevented familiar formats of docker images from being used in Swarm and Kubernetes yaml.
  • Resolved an issue that may prevent metrics from showing up in the dashboard due to a panic in the remote operator container.

2.19.3

Released on 9 Apr 2018

Changes

  • This release rolls back changes in 2.19.2

2.19.2

Released on 9 Apr 2018

Bug Fixes

  • Resolved an issue where applications could fail to start due to errors pulling the registry.replicated.com/library/cmd image.

2.19.1

Released on 4 Apr 2018

Bug Fixes

  • Resolved an issue in the Kubernetes Scheduler that caused the import airgap images task to terminate before it completed.

2.19.0

Released on 2 Apr 2018

New Features

  • Replicated can now install and manage a multi-node Kubernetes appliance.
    • There is now an option to add nodes to a Kubernetes cluster from the /cluster page in the Admin Console.
    • Replicated will install and manage Rook for relocatable persistent storage.
    • When running a cluster with at least three nodes, it is possible to have Ceph/Rook clustering enabled to allow data volumes to be stored on multiple nodes.
    • Replicated continues to support installation on existing Kubernetes clusters for customers who choose to manage their own cluster.

Changes

Bug Fixes

  • Resolved an issue that caused multi-line environment variables to fail to parse, preventing the application from starting.
  • Resolved a panic during restore when Replicated snapshots are misconfigured.
  • Resolved an issue where application logs were not showing up in the Kubernetes support bundle.
  • Resolved an issue where Admin Console Audit Logs would not persist when restarting Replicated on Kubernetes.
  • Replicated Docker images have been updated to address the following CVEs:
    • CVE-2017-14062 and CVE-2018-6954 with High severity
    • CVE-2017-3738 and CVE-2018-1049 with Medium severity
    • CVE-2012-2663, CVE-2013-4392, CVE-2017-18078, CVE-2017-1000082 and CVE-2018-0733 with Negligible severity
    • CVE-2017-15422 and CVE-2018-0739 with Unknown severity

2.18.0

Released on 19 Mar 2018

New Features

  • Replicated now supports installing and managing single-node Kubernetes 1.9.3 appliances. We’ve written a guide to help you get started.
    • The Kubernetes installation will work in airgapped, proxy and online environments.
    • The installation scripts will install Docker, Kubernetes, Replicated and your application.
    • We currently install Kubernetes 1.9.3.
    • All persistence volumes (PVs) will be mounted as a hostPath.
    • For multi-node and more custom Kubernetes installations, Replicated can be installed in an existing Kubernetes cluster.
  • Support bundle v2 has been updated to allow managing support definitions independently of your application yaml.
    • By default, all installations will continue running the standard support bundle, reading the support_files and support_cmd keys from the application yaml.
    • The v2 support bundle will use support definitions from Replicated Console if any exist for your team. When using support definitions from console, files and commands specified within the application yaml are ignored.
    • The new support bundle spec documentation is documented in the Help Center.

Changes

  • Added support for anonymous LDAP binding when using the Replicated LDAP identity integration.
  • User search DN is now optional for LDAP identity integration.
  • When running on EC2, leaving the AWS_ACCESS_KEY/SECRET_ACCESS_KEY empty in the Snapshot configuration will now use IAM roles for authentication.

Bug Fixes

  • The Swarm scheduler can be used with a proxy.
  • Resolved an issue where the application would fail to start with no such image error when application images were removed from docker.
  • All known CVEs with patches have been fixed in Replicated Docker images.
  • All known CVEs with patches have been fixed in third party Javascript libraries.
  • Fixed an issue on the native scheduler that could cause an error “image not found” if a container’s when condition is toggled from false to true during application startup.
  • Resolved an issue that prevented replicatedctl params import and replicatedctl params export command from functioning properly when formatted with yaml.