-
with ref to #8650
@aspiringmind-code and @belforte had a chat today. Here's notes to guide development:
## Design in words
At very high level we decide which TW is master and which canary an…
-
### Describe the bug
I'm attempting to use Flagger on AWS EKS with the Gateway API making use of the AWS Gateway API Controller. I have followed the instructions in the tutorial at: https://docs.fl…
-
# Summary
Consider implementing a solution to automatically add the routes defined in `strategy.canary.trafficRouting.istio.virtualService.routes` to `strategy.canary.trafficRouting.managedRoutes`.…
-
- [ ] aggiornare i tags
- [ ] rimuovere Cos'è
-
-
- Deploy new code to a small percentage of traffic (
-
*Description*:
It would beneficial for users to be able to rollout proxy config change to canary service first prior to wide fleet rollout. EG could be managing multiple envoyproxy services (stable a…
-
Ability to redirect traffic from one route based on matched headers:
Envoy Config example:
```
routes:
- match:
prefix: "/service/v1"
headers:
- name: "x-canary"
value:…
-
### Description
The resource type `aws_api_gateway_deployment` has three attributes, `stage_name`, `stage_description`, and `canary_settings`, that "silently" create a new stage that is not managed…
-
Checklist:
* [ ] I've included steps to reproduce the bug.
* [x] I've included the version of argo rollouts.
**Describe the bug**
We had a issue when in the middle of the rollout we ran …