lizhencheng
lizhencheng
/assign
After developing the e2e test cases, it would be a good idea to write an e2e test runner guide document？ This could help other team members independently run the e2e...
* [ ] Application * [ ] Fleet Plugin * [x] Fleet Cluster #594
You can use version 1.36.1 of Flagger to see if it solves this problem.
For example, if a deployment/podinfo that changed the image version passed the canary analysis, then according to the normal release process, Flagger would assign podinfo-canary to podinfo-primary, and gradually/fully migrate...
After my verification, it meets my usage scenario. Thank you for your hard work. @aryan9600
Could you provide the flagger logs? Was there a log like this when the flagger installation succeeded: `{"level":"info","ts":"2024-01-26T07:44:04.473Z","caller":"flagger/main.go:206","msg":"Connected to metrics server http://prometheus:9090"}`
Based on my current understanding of flagger, it does not currently support multi-cluster deployment functionality. This is because resource creation across multiple clusters requires providing the `KUBECONFIG` of each cluster,...
In the current version of Flagger, specifying multiple ports can only be achieved through PortDiscovery. For more options, please refer to [multiple-ports](https://docs.flagger.app/v/main/faq#multiple-ports)
Are you trying to publish using multiple ports? Perhaps you can refer to this [document](https://docs.flagger.app/faq#multiple-ports)