Cloud Docs Home > F5 Marathon ASP Controller Index

Release Notes for Marathon ASP Controller¶

v1.1.0¶

Added Functionality¶

Reduced size of the required container to support controller.

Allow applications to set attributes per port on service.

Support ASP ephemeral datastore configuration.

Support ASP health monitoring configuration.

Support ASP custom event handlers configuration.

Bug Fixes¶

Fix issue where controller initially created an ASP instance with an invalid virtual server.

Updated incorrect documentation and missing links.

v1.0.0¶

Added Functionality¶

Configures and manages the Application Services Proxy in the Apache Mesos/Marathon environment.

Default configuration can be overridden using environment variables.

Controller’s configuration can be overridden on a per-app basis by using labels on the app.

Configures Service port from the service definition as Host port of the ASP.

To update the upgrade strategy of ASP created by the controller, use environment variables ASP_UPGRADE_MIN_HEALTH and/or ASP_UPGRADE_MAX_OVER.

Rounds down floating point values for stats flush interval and keep-alive to integer values.

Passes environment variables prefixed with ASP_ENV_PREFIX to ASP unmodified after stripping off the prefix.

Deletes orphaned proxies for apps on restart.

Updates proxy when port mappings change for an app.

Updates proxy when default proxy container image changes.

Supports configuration of ‘ca’ and ‘rejectUnauthorized’ attributes of ASP via ASP_STATS_CA and ASP_STATS_REJECT_UNAUTHORIZED environment variables.

Limitations¶

Controller starts an initial ASP with an incorrect host port, kill it, and starts a new ASP with the correct host port.

Changes to ASP_ENABLE_LABEL cause the marathon-asp-controller to start controlling a new set of apps which have the new value as a label. The controller ignores all apps with the old label. Since the controller is stateless with respect to Marathon it needs to be this way. An easy way to avoid this problem is to never change the ASP_ENABLE_LABEL of an existing marathon-asp-controller. Always destroy the controller and create a new one. This way there is no confusion or expectation of a different behavior.