v0.12.1

What's Changed

• keep monitor list elements unique by @JiaminZhu in #150
• keep monitor list elements unique (#150) by @JiaminZhu in #151

Full Changelog: v0.12.0...v0.12.1

v0.12.0 dce-go release

kill container process when docker is not responsive

v0.11.2 DCE-Go

adding only one step metrics for healthcheck per container

v0.11.1 DCE-Go

removed the long logs which printed the fileMap

upgrade mesos-go

This release upgrades mesos-go, gorealis and thrift.

v0.8.2

Modify health check order to support docker version 20.

In docker version 20, even container exit gracefully with 0 code, docker still marks health check as unhealthy. Before docker provide the fix, DCE is going to check exit code first and followed by health status of container

0.8.1

Update launch flag before running launch cmd to avoid pod leaks when launch command got interrupted.

v0.8.0 DCE-GO

• refactor stepMetric
• store the serviceMap in memory rather than context
• refactor interface, change the first parameter from pointer of context to context
• add monitor interface, and add an plugin to monitor pod status in the backend

0.7.6 DCE-GO

Today most duration config use type of integer, to make it more readable, update all duration related config under launchtask section from integer to duration string.

A duration string is a possibly signed sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms", "1.5h" or "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h"

What we have today

launchtask:
   podmonitorinterval: 10000
   retryinterval: 10000
   timeout: 500000

Update it to

launchtask:
   podmonitorinterval: 10s
   retryinterval: 10s
   timeout: 500s

DCE-GO-0.7.5

• changing the stepMetric status from completed to error and success.
• moving from glide to go mod
• HTTP client should accept a transport