Epic: Migrate to Installer

[geropl]

Summary

WebApp is the last team that relies on the helm chart for deployments, we should get rid of it.

General approach

Go through components one by one and decide for each config to either:

• work with a default
• find a way to place variance in the installer

Tasks

• Setup a diff tool between chart and installer to identify config diff https://github.com/gitpod-io/ops/pull/1558
  • open-vsx
    • [installer] open-vsx: configure redis #9215
  • server
    • Add maximumBackupCount and blobQuota configuration surface to the installer #9227
    • Add experimental config values for the Server component #9297
    • Make server githubApp.certSecretName configurable #9305
    • remove logLevel from config, and take it from LOG_LEVEL env var
    • make defaultBaseImageRegistryWhitelist configurable (or is this an imageBuilder concern?)
    • make definitelyGpDisabled configurable
    • make disableDynamicAuthProviderLogin configurable
    • make enableLocalApp configurable
    • runDbDeleter: = !dbSync.enabled
    • builtinAuthProvidersConfigured: [server] Remove superfluous config field builtinAuthProvidersConfigured #9612
    • payment
      • add chargebee config to outer wrapper chart (cmp. old chart) already done by terraform
      • add option to specify a secret to config.experimental.server.chargebeeConfig, and configure server to find it
      • set server.config.EnablePayment when that secret is configured
    • analytics: configure GITPOD_ANALYTICS_WRITER and GITPOD_ANALYTICS_SEGMENT_KEY
    • license secret: set GITPOD_LICENSE_TYPE in wrapper chart as expected
    • mount github-app-cert (just like payment-endpoint)
    • blockedRepositories
    • workspaceGarbageCollection: defaults to true
  • ws-manager-bridge
    • add option skipSelf and use it [here](https://github.com/gitpod-io/gitpod
      /blob/21263bd4e7acdffd1fb81c0056cc9f935159679c/install/installer/pkg/components/ws-manager-bridge/objects.go#L21) done based on "installation method"
    • add option experimental.webapp.wsManagerBridge.skipSelf (default: false, set to true for SaaS)
  • proxy
    • proxy-ingress svc (wrapper chart)
    • static IP
    • serviceAnnotations (proxy, openVsxProxy & ideProxy)
  • db-sync (wrapper chart)
  • db
    • disableMigration (default: false): disable jobs dbinit-session and migrations & db-init configMap
    • validate gcloud-sql-token shape
  • messagebus (well-tested in preview envs)
    • validate config shape (incl. user/password)
  • payment-endpoint (wrapper chart)
  • setup wrapper-chart:
    • https://github.com/gitpod-io/ops/pull/1977
    • auth-providers
  • cross-cutting:
    • installationShortname: [installer] (optionally) surface "metadata.shortname" #9218
    • After meeting with self-hosted team:
      • Move PodConfig section under a new Common field, to make it clearer that these values are cross-cutting and applicable to all teams.
      • Rename Affinity method in common package to NodeAffinity ([installer] Rename common.Affinity to NodeAffinity #9400)
      • Make replicas default to 1 and use the configuration method in common everywhere.
      • Configure tracing sampling parameters
• rollout to staging
• rollout to devstaging: remove the special bash post-processing here from preview envs Make "with-payment" flag work on harvester preview envs #9855
• rollout to prod
• cleanup
  • get rid of kedge #9487
  • Remove the dev/installer-diff program (only needed for figuring out the diff of the installer vs helm chart).
• aftermath
  • find a way to configure repositoryPasslist not required, deprecated anyway

Collaboration

For collaboration and questions on the remaining tasks: Notion sync doc.

Context

Historically we all deployed with the helm chart but decided to go with the installer instead.

Value

The value lies in alignment and getting rid of technical debt.

Acceptance Criteria

We can deploy using the installer in all deployment modes, and delete to helm chart.

Measurement

Does not apply

Growth Area

No response

Persona(s)

No response

Hypothesis

No response

In scope

No response

Out of scope

No response

Complexities

No response

Press release

No response