ab-testing

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca

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.
At times, we merge code to main only to have the build-and-push workflow fail because of a problem with docker build

Describe the feature/solution you'd like
Include a test of the docker build of image in the build-and-test workflow

**Will this feature/solution bring new benefits for Iter8 developers