Clean up PREVENT_LOAD_BALANCER_RETRIES_IN_TRANSACTION

Summary

This issue is to cleanup the PREVENT_LOAD_BALANCER_RETRIES_IN_TRANSACTION environment variable, after it has been rolled out for an appropriate amount of time in production.

The environment variable was used for incremental rollout of the fix for #220242 (closed).

Owners

• Team: groupdatabase
• Most appropriate slack channel to reach out to: #g_database
• Best individual to reach out to: @krasio
• PM: @rogerwoo

Stakeholders

Expectations

What might happen if this goes wrong?

Cleaning up the environment variable

• Create a merge request to remove PREVENT_LOAD_BALANCER_RETRIES_IN_TRANSACTION environment variable. Ask for review and merge it.
  • Remove all references to PREVENT_LOAD_BALANCER_RETRIES_IN_TRANSACTION from the codebase.
  • Remove all code branche and tests that are no longer needed.
  • Create a changelog entry.
• Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the fix can be officially announced in a release blog post.
  • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
• Create a MR for https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com to clean up the environment variable from all environments.ture-flag-name>`
• Close this clean up issue.