Skip to content

[Feature flag] Cleanup kubernetes_agent_internal_api

Summary

This issue is to cleanup the kubernetes_agent_internal_api ops feature flag, after the feature flag has been enabled by default for 3 years (!41045 (merged)).

This Feature Flag is causing slowness in the GET /api/internal/kubernetes/agent_info API (#362075 (closed)). Given that this Feature Flag has been enabled for a while, it should be fine to remove this now.

We will only remove the flag and not the feature, so the internal Kubernetes agent API will be permanently available.

Owners

Stakeholders

N/A

Expectations

What might happen if this goes wrong?

This Feature Flag has been enabled by default for 3 years, so it should not cause any problems to remove the flag and make the feature permanently available. This is also a feature addition, so it would not cause any breaking changes.

Cleaning up the feature flag

  • Specify in the issue description if this feature will be removed completely or will be productized as part of the Feature Flag cleanup
  • Create a merge request to remove kubernetes_agent_internal_api feature flag. Ask for review and merge it.
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
    • 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 feature can be officially announced in a release blog post.
    • /chatops run auto_deploy status <merge-commit-of-cleanup-mr>
  • Close the feature issue to indicate the feature will be released in the current milestone.
  • If not already done, clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete <feature-flag-name> --dev --ops --pre --staging --staging-ref --production
  • Close this rollout issue.
Edited by Pam Artiaga