-
### Describe the bug
I've been working on an MR for issue https://github.com/fluxcd/flagger/issues/1646 and ran into this following bug when testing Flagger in my personal kubernetes cluster. I've …
-
### Describe the bug
We are currently using `canaries` with `autoscalerRef` and HPA enabled as described in the docs.
```
apiVersion: flagger.app/v1beta1
kind: Canary
...
spec:
autoscale…
-
### Describe the bug
Following the [flagger docs for keda integration](https://docs.flagger.app/tutorials/keda-scaledobject), I updated the canary to point to the KEDA scaled object instead of the …
-
### Describe the bug
We've created Canary with manual gates approval. Everything is going according to the plan, all stages passed. New version of the app was promoted to the primary deployment. Ro…
-
Setup serverless deployment to use gradual canary roll-out (at least for production) so Travis can be allowed to deploy automatically
-
We would like to have the development branch running with the chime config for a while before actually deploying it. There are two ideas (not mine) on how to do this:
1. Keep a number of dedicated …
-
**Describe the bug**
I tried to set the values for loki-canarys resource requests and limits. Unfortunately they are not applied to the relevant pods of the canary daemonset.
**To Reproduce**
…
-
So this is a fun one :D
* have a rollout that has been just fine for ~24 hours
* the rollout was in a completed state (can see this based on notifications)
* suddenly Rollouts starts sending …
-
Use the example from https://github.com/QCDIS/NaaVRE-dev-environment/tree/main/services/canary-example to update the charts
-
### Describe the bug
We had an incident last Sunday. A team rolled out a new release using the canary strategy provided by Argo Rollouts.
The canary finished successfully and eventually transit…