Skip to content

v1.5.13
Compare
Choose a tag to compare
@zen-dog zen-dog released this 10 Apr 11:16
· 1103 commits to master since this release
v1.5.13
07a35d6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Marathon 1.4 Compatible /v2/tasks

Marathon 1.5 had a major overhaul of networking which resulted in an unintended change to the porting of ports in /v2/tasks. In text/plain form, this information is used to configure load-balancers and routers. When the container is in host mode the reported port is the running host port. When the container is in bridge mode, the reported port is the dynamically created host port that will bridge to the internal container port. For Marathon 1.4, in USER mode, it reported the container port. Regardless of correctness, this feature was used by some customers and needs to be forward ported. Marathon 1.5.13 now provides that ability by using the compatibilityMode query parameter to the /v2/tasks end point. If compatibilityMode is not specified the 1.5 version is rendered. If /v2/tasks?compatibilityMode=1.4 is used it will provide the previous Marathon 1.4 rendering.

Apps names restrictions (breaking change)

From now on, apps which use ids which ends with "restart", "tasks", "versions" won't be valid anymore. Such apps already had broken behavior (for example it wasn't possible to use a GET /v2/apps endpoint with them), so we made that constraint more explicit. Existing apps with such names will continue working, however, all operations on them (except deletion) will result in an error. Please take care of renaming them before upgrading Marathon.

Fixed Issues

  • MARATHON-8493 Fixed precision bug associated with summing pod resources.
  • MARATHON-8498 Fixed secrets validator when changing secret env.
  • MARATHON-8466 Prohibit the use of reserved words in app and pod ids
  • COPS-4483 Provide a backward compatible way to produce container ports for text/plain GET requests against /v2/tasks when using USER networking consistent with Marathon 1.4.
  • MARATHON-8566 - We fixed a race condition causing v2/deployments not containing a confirmed deployment after HTTP 200/201 response was returned.
Assets 2