ab-testing

Describe the feature

I was testing a blue/green strategie within my Kubernetes cluster using flagger and the kubernetes provider.

In the documentation, in the blue/green usage strategie steps, we can see that the traffic should be routed to canary while the primary is promoted https://docs.flagger.app/usage/deployment-strategies#blue-green-deployments

I was assuming that using

As we are constantly upgrading Flagr server, the client SDKs may experience unexpected changes from the server side. The integration tests should better include these SDKs instead of just simple CURL tests.

Specifically, we want to cover

• https://github.com/checkr/jsflagr
• https://github.com/checkr/rbflagr
• https://github.com/checkr/pyflagr
• https://github.com/checkr/goflagr

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

Documentation is not up to date

For example, supported datastores misses PGSQL
https://maif.github.io/izanami/manual/architecture/index.html

Please documentation freshness problems in this issue

Is your feature request related to a problem? Please describe the problem.
Some experiments fail because fortio fails early. One strategy to avoiding some errors (caused by cold start) is use of the -ignore-initial-errors option in fortio. This adds a measure of resilience to the task even though it won't solve every issue.

Describe the feature/solution you'd like
A clear an