Rollout cluster_applications_artifact flag

What

cluster_applications_artifact was introduced in ~13.1. In ~13.2 ~"devops::configure" introduced features (UI and metrics) dependent on this cluster_applications_artifact, some of these features will not be working as expected due to default value of this feature flag (false).

As @tkuah mentioned:

I think though it's ok to1. Rollout the FF
1. Enable cluster_applications_artifact for all apps (it's currently restricted to only prometheus.

Owners

  • Team: ~"devops::configure"
  • Most appropriate slack channel to reach out to: #s_configure
  • Best individual to reach out to: @tkuah

Expectations

### What are we expecting to happen?

Custer application DB state will be updated when CI job for management project succeed.

What might happen if this goes wrong?

Cluster applications will show incorrect state

What can we monitor to detect problems with this?

Cluster applications page

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

  • gitlab-org/gitlab project
  • gitlab-org/gitlab-com groups
  • ...

Roll Out Steps

  • Enable on staging
  • Test on staging
  • Ensure that documentation has been updated
  • Enable on GitLab.com for individual groups/projects listed above and verify behaviour
  • Coordinate a time to enable the flag with #production and #g_delivery on slack.
  • Announce on the issue an estimated time this will be enabled on GitLab.com
  • Enable on GitLab.com by running chatops command in #production
  • Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
  • Announce on the issue that the flag has been enabled
  • Remove feature flag and add changelog entry
  • After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel