v1.19.15-dd.1

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.

v1.19.15-alpha.0-dd.1

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.

v1.14.11-beta.1-dd.11

v1.14.11-beta.1-dd.11

v1.14.11-testing.3-dd

Tweak github action to deal with no space error

The github build action is erorring out with a `no space left on
device error` when trying to download the docker image
`k8s.gcr.io/kube-cross:v1.12.12-1` to run the build. That image
is 1.87GB big, and the `easimon/maximize-build-space` action was
leaving only 512MB free on the root filesystem.

We are completely removing that action to see if the default 14GB
of disk space allocated by github actions are enough for the build

Additionally, we are removing the `actions/setup-go` as well,
since it should not be needed in this pipeline.

v1.14.11-testing.2-dd

Tweak github action to deal with no space error

The github build action is erorring out with a `no space left on
device error` when trying to download the docker image
`k8s.gcr.io/kube-cross:v1.12.12-1` to run the build. That image
is 1.87GB big, and the `easimon/maximize-build-space` action was
leaving only 512MB free on the root filesystem.

We are completely removing that action to see if the default 14GB
of disk space allocated by github actions are enough for the build

Additionally, we are removing the `actions/setup-go` as well,
since it should not be needed in this pipeline.

v1.14.11-testing.1-dd

Add pagination to describeInstances in aws

For large clusters and AWS projects, the describeInstances api call
returns a 500 http error because the response exceed the limit in
the AWS api.

This means that, for example, for a classic loadbalancer, no new nodes
get added to it, which could lead to service disruption over time
due to node attrition.

This commit attempts to solve that by changing the call to use the
pagination method from the aws sdk

v1.20.9-dd.1

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.

v1.20.6-dd.2

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.

v1.20.6-dd.1

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.

v1.19.10-dd.1

[sidecars] Missing non-sidecar status must not allow progress

When non-sidecar container statuses are missing from the pod struct,
we must assume they are waiting in order to prevent computePodActions()
from starting non-sidecars before sidecars are ready.