Andreas Sommer
Andreas Sommer
## Summary With `scaleDownDelaySeconds: 0` on a blue-green rollout, and clicking Promote-Full in Argo CD UI for faster deployment, the operator kept the old ReplicaSet running without scaling it down...
Originally posted this issue [here](https://github.com/wycats/handlebars.js/issues/742). In the attached minimal project (using grunt and browserify-handlebars), two instances of handlebars are created 1) from 'node_modules\handlebars\Lib\index.js' 2) from 'node_modules\handlebars\Dist\Cjs\handlebars.js' I think the reason...
The README says to pin to a specific version found at https://rust-lang.github.io/rustup-components-history/ – however, that site only shows the last 7 days. It currently (at time of writing: 2022-01-10) does...
False-positive "Container has the same readiness and liveness probe" if `failureThreshold` differs
**Which version of kube-score are you using?** kube-score version: 1.10.0, commit: 95faa2ad082e05d8b7637d0bd5e1ae00d1550260, built: 2020-11-07T14:17:50Z **What did you do?** ``` readinessProbe: tcpSocket: port: http initialDelaySeconds: 5 periodSeconds: 5 failureThreshold: 3 livenessProbe:...
``` RELNOTE: Accept if readiness/liveness probes are the same but differ in threshold ``` Fixes https://github.com/zegl/kube-score/issues/339
**Describe the bug** The [blog post](https://twitter.com/grafana/status/1552406394330128385?s=20&t=itrs3vT4l5hnkI7aiE9iSw) and [API docs](https://grafana.com/docs/loki/latest/api/) give the example: ``` curl -g -X POST '[...]/loki/api/v1/delete?query={foo="bar"}&[...]' ``` That would defeat the purpose: for example when removing critical data...
### Feature Description Only these TLS-related fields are available right now: ``` // Response is a representation of an HTTP response type Response struct { // ... Timings ResponseTimings `json:"timings"`...
Current situtation: if the chart is malformed, but the Helm release was already installed earlier, `terraform apply` will not display any error. I have a case where no `resource "helm_release"...
**Describe the bug** `required-annotation-email` needs an annotation, `required-label-owner` needs a label. Also, both names are non-standardized. I suggest to make this consistent and probably use the ideas from [Annotating Kubernetes...
See separate commits. These were the learnings when I first worked with this repo ("works for me" now 😉). The developer instructions resemble what is used in CI.