bookingcom / shipper

Kubernetes native multi-cluster canary or blue-green rollouts using Helm
Apache License 2.0
733 stars 39 forks source link

WIP: fix moving back in strategy bug #378

Closed hihilla closed 3 years ago

hihilla commented 3 years ago

When a current release is progressing shipper will:

  1. increase capacity to current (or contender)
  2. increase traffic to current
  3. decrease traffic to previous (or incumbent)
  4. decrease capacity to previous

When a release is moving back in the strategy (not progressing), this process will cause pods dropping. So when a release in not progressing, shipper will first move capacity and traffic to the previous release and then reduce traffic and capacity from current release.