Release notes for Edge-LB Service version 1.2.3

Edge-LB Service version 1.2.3 was released on November 27, 2018.

Notable Changes

• lbmgr: Enforce the timeout also during the connection phase of the healthcheck command
• apiserver: Make the following parameters of the pool tasks healthchecking configurable via new pool parameters:
  • poolHealthcheckGracePeriod - Defines the period of time after start of the pool container when failed healtchecks will be ignored (default: 180s).
  • poolHealthcheckInterval - Defines healthcheck execution interval. At most one healtcheck is going to execute at any given time (default: 12s).
  • poolHealthcheckMaxFail - Defines how many consecutive failures mark the task as failed and force Mesos to kill it (default: 5).
  • poolHealthcheckTimeout - Defines the timeout enforced by Mesos on the healthcheck execution. It includes the container startup (fetch, setup, start, etc…) as well as the time spent by the healthcheck command executing the test.

Bug Fixes

• LB task getting killed intermittently leading to outage for apps being load balanced.

Known Limitations

• Edge-LB currently does not support Strict security mode on DC/OS 1.10, but supports Strict security mode in DC/OS 1.11.
• Edge-LB currently does not support self-service configuration. All configuration must be handled centrally.

Known Issues

• The steps provided in the DC/OS 1.10 web interface to uninstall Edge-LB are incorrect. In order to correctly uninstall Edge-LB for any given DC/OS version, please follow the steps in the Edge-LB uninstall documentation.
• Edge-LB running on a CentOS/RHEL 7.2 node where /var/lib/mesos is formatted with ext4 may have connection issues.
• If a pool is configured with invalid constraints it must be removed manually since a failure in proper creation leads to a failure in proper removal.

Release Notes for Edge-LB Service version 1.2.2

Edge-LB Service version 1.2.2 was released on November 15, 2018.

Notable Changes

• lbmgr: Improved healthchecking
  • Instead of shelling out to socat, lbmgr now natively handles communication with HAProxy
  • Added more information about status on successful and failed healthcheck regarding size of the reply, time it took to write the command, fetch the result, total time
  • Made the healthcheck time out to 9 seconds. This is 1 second sooner than Mesos healthcheck. This helps identifying the timeout occurence time.
• mesos-listener: Added support for TASK_GONE_BY_OPERATOR event
• mesos-listener: Events for non-existent tasks are ignored
• mesos-listener: Made goroutines properly mark themselves as done during the termination
• mesos-listener: Mesos-failover code handling:
  • Prevent overriding of framework data in carried-over tasks
  • Prevent carry-over logic from removing frameworks that may still be in use by the tasks in the active shapshot
• mesos-listener: No longer sends inactive tasks to the clients; only those in TASK_RUNNING will be now present in the data offered to clients.
• mesos-listener: Increased tests coverage with improved integration tests
• Updated SDK used by Edge-LB from 0.42.3 to 0.54.2
  • This also updated Java JRE to 8u192 from 8u172 to address Java vulnerabilities
• Bumped HAProxy version used from 1.8.13 to 1.8.14
• Pool task container improvements:
  • Use -slim version of Debian for smaller container
  • Installed basic debugging tooling
  • Made LBWORKDIR the working directory of the container
  • Removed unnecessary tooling regarding iptables, syslogd, etc.
  • Now only necessary artifacts are copied into the container during the build (i.e., no more Dockerfile)
  • Verbose when copying files during the container start

Bug Fixes

• In DC/OS 1.11.3 EE (strict mode), non-superuser access needed to Edge-LB pool logs
• Edge-LB – default template for SNI is incorrect
• Edge-LB should ignore terminal but not ack’ed tasks from Mesos when subscribing.
• Edge-LB pool is unable to launch additional load balancer tasks
• Edge-LB pool can not deploy if app and secret are under namespace/group

Known Limitations

• Edge-LB currently does not support Strict security mode on DC/OS 1.10, but supports Strict security mode in DC/OS 1.11.
• Edge-LB currently does not support self-service configuration. All configuration must be handled centrally.

Known Issues

• The steps provided in the DC/OS 1.10 web interface to uninstall Edge-LB are incorrect. In order to correctly uninstall Edge-LB for any given DC/OS version, please follow the steps in the Edge-LB uninstall documentation.
• Edge-LB running on a CentOS/RHEL 7.2 node where /var/lib/mesos is formatted with ext4 may have connection issues.
• If a pool is configured with invalid constraints it must be removed manually since a failure on proper creation leads to a failure in proper removal.