Components in the form

Status: Implemented Issue: none Parent: GitLab components

Goal

An administrator switches the components of an instance in the Bridge form, and sees what a switch breaks before saving it. For the design, see ADR 40.

Requirements

• The Core Components section shows one switch for each of Webservice, Sidekiq, Gitaly, GitLab Shell, KAS, GitLab Exporter, Mailroom, and GitLab Pages. Each switch starts at the value the instance runs with when spec.chart.values do not override it.
• The registry, the Toolbox, and OpenBao are add-ons, each with a tab of its own and an enable switch that unlocks its settings.
• The form writes only the components that differ from their default, and leaves spec.components unset when none does.
• Clearing the switch of an add-on writes enabled: false and keeps the settings of each complete group. An add-on switched off with no complete group is left out.
• Turning off Webservice or Gitaly shows a warning of what stops working.

Out of scope

• Showing in the form that spec.chart.values override a switch.

FAQ

• Why does the form not write a switch left at its default? So the resource states only what the administrator changed, and a later chart default reaches the instance. A component set to its default by hand is dropped on the next save from the form, which changes nothing it runs.