Martin Linkhorst
Martin Linkhorst
it would be nice to show additional node labels to easily see e.g. kubernetes version of the node.
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....
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...
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...
currently I can set traffic on a version that doesn't exist. It will correctly reduce the desired traffic to the existing versions but will not add the new version to...
The `status` section of StackSets contains useful information about the readiness of the StackSet. However, there's more information that could be exposed there so that tools probing for its readiness...
`StackSet` and `Stack` resources are inspired by the relationship between `ReplicaSet` and `Pods` (and also `Deployment` and `ReplicaSet` I would say). When I modify a `Deployment` object (an in-place update)...
When updating the `cassandraImage` in a CDC spec it doesn't update the corresponding StatefulSets. The operator correctly gets an event and starts reconciling the CDC but somewhere in the code...