Skip to content

Remove GOUI from GOB

This issue tracks removing GOUI from GOB as per the change of direction that happened in https://gitlab.com/gitlab-org/opstrace/general/-/issues/115.

Steps that need to be made, in order:

  • remove support for GOUI token authentication
    • Identify who uses GOUI tokens
      • add temporary logging to Gatekeeper MR
      • parse logs after 2 weeks
      • remove code with temporary logging MR
    • migrate existing users to GL Access Tokens
      • add support to GLAT to KAS MR
      • KAS team migration: issue, issue
      • Tanuki App MR
    • remove code in Gatekeeper that enables authentication via GOUI token MR
  • migrate users from GOUI
    • Identify users that use GOUI web interface
    • investigate use-cases of the users, see if they can use Jaeger UI or find an alternative
  • "soft" removal of GOUI - make GOUI accessible only if using direct link
    • move support of GL Tokens from observability_group_tab FF to gitlab_error_tracking FF issue
    • disable observability_group_tab feature flag globally for whole gitlab
    • make provisioning page for new tenants display jaeger ui by default instead of GOUI MR
  • "hard-block" of GOUI - block access to GOUI by redirecting to catch-all page with an info about deprecation, wait few days to verify that nobody complains
  • code removal:
    • a: dashboard controllers, CRD
    • b: datasource controllers, CRD
    • c: remove Postgresql provisioning from Gitlab namespace operator, and terraform GKE modules
    • d: GOUI-related code in gatekeeper - provisioning and auth(N|Z) related
    • e: GOUI stateful set removal from tenant operator (depends on: a, b, c, d, f)
    • f: entry in the Cluster CRD that allows for specifying the image tag for GOUI
    • g: remove GOUI provisioning/overrides from devvm (depends on: f)
  • remove GOUI embedding code from Gitlab and the observability_group_tab feature flag #2365 (closed)
Edited by Pawel Rozlach