Add a FAQ

[dholbach]

It'd be good to add a FAQ for the project. Initially it can probably still live on the main page, later on we might want to move it into its own file.

@crw had a couple questions we could add to seed the section:

Can we do integration testing?

• Yes, Flagger supports webhooks to do integration testing.

What if I only want to target beta testers?

• Feature in Flagger, not in App Mesh. On the App Mesh roadmap.

Can I do A/B testing?

• Feature in Flagger, not a feature in App Mesh (yet).

[dholbach]

https://weave-community.slack.com/archives/CGLQLLH9Q/p1554219991026500?thread_ts=1554140783.021000&cid=CGLQLLH9Q

[crw]

The community Slack does not store history and is thus it is not a good idea to link to it if you actually want the data. Here is the thread:

Hi All, I've been racking my brain about this one for a few days now and can't seem to come up with a solution.
Basically What I've boiled it down to is during a canary deployment of our nodejs app, the version that is being served <50% traffic reports mime type mismatch errors in the browser (js as "text/html")
When the deployment Passes/ Fails (doesn't really matter) the version that stays alive works as expected. If anyone has any tips or direction I would greatly appreciate it. Even if its as simple as I'm looking in the wrong place. Thanks in advance!
----
For anyone looking here later.
The issue was that we were not maintaining session affinity while serving files for our frontend. Which resulted in any redirects or refreshes occasionally returning a mismatched app.*.js file (generated from vue)
The solution is to use A/B testing instead of a Canary roll-out to make sure that each version remains separated and doesn't mix routes.

Details can be found here: https://docs.flagger.app/usage/ab-testing