2.30.2

Changes

  • Config item default properties are again set as the value of the config item when saved on the settings screen of the Replicated admin console. This was the behavior prior to 2.30.0.

Bug Fixes

  • Fixed test proc validation for config items with a default set but no value.

2.30.1

Bug Fixes

  • Fixed an issue that would cause Replicated to crash when uploading a license tied to an application that made use of the data_cmd property in the config section.

2.30.0

New Features

Changes

  • Replicated will now include PersistentVolumeClaims from ReplicaSets, Pods, and StatefulSets in snapshots when using the Kubernetes scheduler. Previously only PersistentVolumeClaims used in Deployments could be snapshotted.
  • Config item default properties are no longer set as the value of the config item when saved on the settings screen of the Replicated admin console.
  • The Replicated install scripts will no longer add hard brackets to some IPv4 addresses as arguments to the Replicated Daemon.
  • Replicated will now use the image name or container name when available for dashboard messaging in addition to the Container ID.
  • Replicated Systemd service will now be installed as WantedBy=docker.service. This will cause Replicated to start on Docker service start. Previously Replicated would start on system boot.

Bug Fixes

  • Snapshots and restores with the Kubernetes scheduler now include audit log events.
  • Changed the StatsD Deployment strategy to “Recreate” to fix a bug that caused the StatsD Pod to be stuck in the ContainerCreating state after upgrades with the Kubernetes scheduler.
  • Fixed an issue where Kubernetes Config Maps and Secrets could get applied before Pods, resulting in the new pod having the previous values prior to the update.
  • Fixed an issue that could result in Replicated failing to initialize after an upgrade, prompting the user with an error message indicating network issues.
  • Fixed a possible crash when generating a support bundle.
  • Fixed an issue that would cause the support bundle to hang until the timeout was reached when on a Journald enabled system.
  • Fixed an issue that caused Replicated services not to start after a Docker upgrade on distributions with the Systemd service manager.
  • Fixed an issue where Docker 1.13.1 on RHEL is not able to validate the on-prem registry certificate.
  • Replicated install scripts will now re-configure the Docker proxy settings on subsequent runs when changed. Previously these values were ignored.
  • Fixed an issue that could cause Replicated to fail to install Docker on Debian 9 when the Replicated install scripts are invoked from a startup script on machine boot.
  • Fixed a confusing error message when a command fails while updating the application that stated there was “invalid yaml”.
  • Fixed an issue which could prevent registry.replicated.com images hosted in the library organization from pulling due to authentication failures.
  • All known CVEs with fixes have been patched in all images distributed by Replicated at the time of the release. For more information see this article.

2.29.0

New Features

  • The command replicatedctl app apply-config has been added, which will apply config changes to the running application. When using the native scheduler this command will perform a restart. When using the Kubernetes and Swarm scheduler, it is equivalent to kubectl apply and stack deploy respectively.
  • The AWS Auth Test Procedure will now use instance profiles when the first and second argument (AWS access key and secret) are left blank. The AWS Auth Test Procedure now supports an AWS region as its 5th argument. This will default to us-east-1.
  • The property stop_timeout has been added to the Native scheduler container definition to specify the number of seconds to wait after stopping an application container before killing it.

Changes

  • A link has been added on Console Settings page of the Admin Console to change admin password.
  • Additional messaging is now present when running replicatedctl console-auth command for follow up steps.
  • The Debian image included in the Replicated airgap package is no longer used and has now been omitted from the package.
  • Error messages from the replicatedctl support-bundle command have been improved. Users will now be instructed on how to collect a CLI support bundle when replicatedctl is unsupported.
  • Install scripts now support the usage of additional-no-proxy, http-proxy, private-address, and public-address flags during airgapped installations.

Bug Fixes

  • Fixed an issue that could cause the Replicated Operator service to fail on a Replicated update when using the Swarm scheduler.
  • Fixed an issue that caused the CLI to crash when using the --attach flag.
  • Fixed an issue that prevented raw commands from running Pods for programmable preflight checks on Kubernetes.
  • Fixed an issue that prevented V1 Support Bundles from including journald logs.
  • Fixed an issue that prevented Kubernetes apps from being restored from a snapshot.
  • Fixed an issue that could prevent snapshot list from being loaded during the restore process and when browsing snapshots.
  • Fixed a race condition when waiting for Rook to start that occasionally required manually restarting kubelet when using the Kubernetes scheduler
  • Reverted Kubernetes 1.9.3 installs to use iptables mode for kube-proxy to fix a networking issue.
  • Fixed an issue that prevented pulling 3rd party private images when running Docker 1.7.1.
  • Fixed an issue that prevented Replicated from appending the correct Docker bridge network gateway address to the list of NO_PROXY addresses when configured to be anything other than the default 172.17.0.1.

2.28.1

Bug Fixes

2.28.0

New Features

  • The LDAP Provisioning API can now be configured with an optional filter string as a parameter to filter entities that are synced back to your integration.

Changes

Bug Fixes

  • Replicated services will now restart when Docker is restarted on distributions where Docker is installed as a SysVinit service including Amazon Linux.
  • Fixed an issue where a running container could appear as “missing” on the Cluster page of the Admin Console.
  • Fixed a deceptive error message “no docker compose yaml found” when an upgrade is attempted and the airgap bundle is not found.

2.27.0

New Features

  • Added the ability to specify terms to display to the end-user in the Admin Console prior to installing a license.
  • It is now possible to specify minimum space requirements for the Docker root directory (commonly /var/lib/docker) using custom preflight checks. The minimum required space will default to 1GB when not specified.
  • As an alternative to the Rook storage provisioner, Replicated now provides an optional host path provisioner ideal for single node Kubernetes installations.
  • It is now possible to opt out of a Kubernetes storage provisioner provided by Replicated and bring your own.
  • Added resources and logs to the Kubernetes support bundle from the kube-system, heptio-contour, rook-ceph and rook-ceph-system namespaces.
  • Custom branding will now be applied prior to installation of the license when using the Kubernetes scheduler and installing via the release channel installation scripts.
  • Added a force-reset flag to the Kubernetes uninstaller that, when present, will suppress all prompts and warning messages before uninstalling Kubernetes and Replicated.

Changes

  • The language on the Open Source License page of the Admin Console has been clarified to indicate that it is Replicated that uses or distributes software under licenses listed on that page and not the vendor application.

Bug Fixes

  • Fixed an issue that would prevent the status tile on the Admin Console dashboard from updating in some scenarios.
  • Fixed a race condition after a restore that would cause the certificate in the Docker store not to match the one used by the Replicated on-prem registry API, resulting in image pull errors when starting the application.
  • Fixed an issue where in some cases the application would automatically update when when unpinning the application release sequence.
  • Fixed an issue where Replicated Operator would produce excessive logs and files when using a logging driver that does not support docker logs.
  • Fixed an issue that would produce an error when running replicatedctl without any arguments.
  • Fixed an issue that resulted in a crash in Replicated when generating a V1 Support Bundle using the Kubernetes scheduler.
  • Fixed an issue where the local snapshot file destination would fail to render in the Admin Console when using the Multi-Strategy Backups feature.

2.26.0

New Features

  • Kubernetes 1.11.1 is now the default version when installing Replicated with Kubernetes.
  • The Kubernetes support bundle now includes the following additional resources: certificatesigningrequests, clusterrolebindings, clusterroles, controllerrevisions, cronjobs, mutatingwebhookconfigurations, poddisruptionbudgets, rolebindings, roles, validatingwebhookconfigurations, volumeattachments
  • replicatedctl cluster node-join-script command has been added to retrieve a script to join a new node to the cluster.
  • replicatedctl app status command has been added to retrieve detailed information on the application’s status.
  • replicatedctl system status command has been added to retrieve the Replicated system status.

Changes

  • replicatedctl app status inspect has been deprecated in favor of the replicatedctl app status command.
  • Kubernetes clusters are now created with Rook 0.8.1 and Weave 2.4.0.
  • The Kubernetes installer is now compatible with RHEL 7.5 and CentOS 7.5.
  • The Kubernetes installer configures a 100GB Persistent Volume Claim for new airgap installs.
  • The Kubernetes installer will prompt the user to disable firewalld when enabled.
  • The Kubernetes installer will run kube-proxy in ipvs mode.

Bug Fixes

  • The order in which the custom_metrics YAML property elements are listed is now maintained when rendered to the storage-schemas.conf and storage-aggregations.conf files in the replicated-statsd container.
  • Airgapped installations will now respect license update policies set to “automatic”.
  • Fixed an issue that could result in the V2 Support Bundle not honoring excluded environment variables when using the is_excluded_from_support parameter.
  • Fixed an issue that could prevent the replicated-operator global service from updating on remote worker nodes when upgrading an airgapped installation of Replicated.
  • Fixed an issue that could prevent Swarm and Kubernetes from pulling images from the local Replicated registry due to a missing certificate in /etc/docker/certs.d.
  • Fixed an issue that allowed LDAP anonymous binds when logging into the Admin Console or when performing an Identity API login operation.
  • Improved error messaging for failures in replicatedctl script prior to running the specified sub-command.
  • Fixed an issue that occasionally prevented the Replicated snapshot controller pod from starting on airgapped installations with Kubernetes.
  • Replicated will now fetch the latest V2 Support Bundle specs rather than using the specs embedded in the license when the airgap flag is passed to the Replicated installation script and an online install is attempted.
  • Online native installations that passed the airgap flag to the Replicated install script will not use the local registry unless a remote operator is detected.
  • Fixed a crash due to an invalid LDAP query used in the Advanced Search user or group option.
  • Fixed possible snapshot DB corruption and a crash caused by this corruption.
  • Fixed an issue where stopped containers would not be included in the V2 Support Bundle.

2.25.2

Bug Fixes

  • Fixed a bug that caused the custom cert to not be installed in Docker configuration during the initial setup.

2.25.1

Bug Fixes

  • Fixed a bug that prevented docker from pulling images on additional nodes, preventing the application from starting, when custom certificates that did not contain IP SANS were uploaded on initial setup.