stackset-controller

stackset-controller copied to clipboard

Bump sigs.k8s.io/controller-tools from 0.6.2 to 0.9.2

1

Bumps [sigs.k8s.io/controller-tools](https://github.com/kubernetes-sigs/controller-tools) from 0.6.2 to 0.9.2. Release notes Sourced from sigs.k8s.io/controller-tools's releases. v0.9.2 changes since v0.9.1 :bug: Bug Fixes Fix crd flattening for structType marker to not create duplicate entries...

dependabot[bot]

Add the type match label

1

When using the `autoscaler` we are still letting `kube-metrics-adapter` to rely in the metric name. This commit adds the `type` label to the ZMON and SQS queue len metrics. It...

jonathanbeber

Update annotations in per-stack ingresses

4

Per-stack ingresses should be updated when the annotations in `stackset.ingress.metadata` change as well, otherwise filter/predicate changes won't be propagated. We should probably handle label changes as well, but doing this...

aermakov-zalando

We need to loop back to kubernetes to wait progressing with a rolling restart until the traffic fade-in of a pod is complete. If we don't, we create a skew...

otrosien

pre define shunt backend in case routegroups are used

3

I am not sure if it makes sense, but a user had the idea to pre define shunt backend in case routegroups are used, such that they don't need to...

szuecs

- the error cases in StackSetController.collectResources() - the normalizWeight edge cases in traffic.go via: https://github.com/zalando-incubator/stackset-controller/pull/251#issuecomment-694266780

muaazsaleem

Original issue https://github.com/kubernetes/client-go/issues/374#issuecomment-716846816 This could cause no update for 30 minutes... Recent comments suggest that we can fix it and use http2 Transport for connecting to kube-apiserver and set ReadIdleTimeout:...

szuecs

Support dark release deployment

1

An interesting feature instead of starting with canary, and directly shifting traffic to your new stack, it would be nice to first push some shadow traffic to the new stack,...

otrosien

Try out github actions

1

Try to build with github actions

mikkeloscar

Include ConfigMaps and Secrets into the spec

3

When deployments reference a ConfigMap or Secret they do get updated in place when a new blue/green rollout is triggered. This can already have unintended effects on the old deployment....

linki