aermakov-zalando
aermakov-zalando
Use server-side apply instead of invoking `kubectl`. Should be much faster with a lot less memory usage. This is however still somewhat unusable in its current state due to the...
Currently we call `kubectl` externally when applying manifests. This allows us to reuse `apply` logic, which would be cumbersome to implement internally, but leads to excessive resource consumption and complicates...
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...
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...
#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...
If I delete a database, resources created by it (services, statefulsets, etc.) should be deleted automatically. This can be easily implemented by adding the Postgres resource as an `ownerReference` (with...
## Expected Behavior Creating a cluster definition where the pod template doesn't include either a `nodeSelector` or an `affinity` that's compatible with the priority node selector should either result in...
Right now users get a completely unhelpful `ERROR: Failed to download public key for "…" from https://even.stups.zalan.do: server returned status 503` message and we have to investigate.
If all 3 attempts to `docker pull` fail, the boot process is aborted and the instance then proceeds to do nothing. We should either retry the pull infinitely (with a...