stackset-controller icon indicating copy to clipboard operation
stackset-controller copied to clipboard

Opinionated StackSet resource for managing application life cycle and traffic switching in Kubernetes

Results 41 stackset-controller issues
Sort by recently updated
recently updated
newest added

Since https://github.com/zalando-incubator/stackset-controller/issues/31 is not solved, our probers still have to rely on monitoring `Failed…` events to figure out if the stackset is healthy. We currently determine if the events are...

minor

I have created a stackset called `ss-stack` with stacks `v1` and `v2`. When I switch traffic using fractional values, the resulting traffic percentage is slightly inaccurate. See the following examples:...

We see this in the logs when API servers are rolled (presumably): ``` W0304 09:48:56.883806 1 reflector.go:340] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:108: watch of *v1.StackSet ended with: an error on the server ("unable to...

#71 implemented a hacky solution to a problem where the controller scaled down stacks before the deployment even had a chance to switch traffic to those. However, this behaviour is...

It's impossible to figure out whether the controller has processed the changes and updated the resources or not. The following information needs to be exposed so it's possible to figure...

enhancement

Hi, I couldn't find a way to add annotations to a deployment. For service, ingress and even pods it's straight forward. The annotation is at Zalando to define a custom...

These logs here should be all more considered as debug logs ``` time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-82 for StackSet stack default/cluster-registry-master-82" controller=stacks namespace=default stackset=cluster-registry time="2018-09-10T07:24:35Z" level=info msg="Updating Deployment default/cluster-registry-master-79 for...

The prometheus endpoint should expose more metrics that allow to detect whether stackset controller is running well. Some possibilities: * number of errors / error rate * number of stacksets...

There is unclarity how an all-zero traffic weight is handled and interpreted. Handled (currently): * rejected by at least one client (zkubectl) * Not handled by the server (stackset controller...