Start shifting traffic from VTEX I/O to EKS

[salesfelipe]

What problem is this solving?

• We will start sending/using all the traffic for 3 queries: topSearches, AutocompleteSuggestions ad SearchSuggestions. We will keep calling the I/O in case of errors.

• We will star testing the traffic to the correction query as well, 10% of it but still relying on the. I/O response.

How should this be manually tested?

Workspace

Checklist/Reminders

• Updated README.md.
• Updated CHANGELOG.md.
• Linked this PR to a Clubhouse story (if applicable).
• Updated/created tests (important for bug fixes).
• Deleted the workspace after merging this PR (if applicable).

Screenshots or example usage

Type of changes

✔️	Type of Change
_	Bug fix
_	New feature
_	Breaking change
_	Technical improvements

Notes

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.80.0 → 1.81.0

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖