[installer]: Add server chargebee configuration to the installer #9717
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
One of the Webapp team's epics for Q2 is to use the Gitpod installer to deploy to Gitpod SaaS. In order to do that we will need to add additional configuration to the installer to make the output suitable for a SaaS deployment as opposed to a self-hosted deployment.
This PR makes it possible to configure the
server
component's chargebee configuration via new configuration surface in theexperimental
section of the installer config that allows specifying the name of a secret containing chargebee config. For installations on which payments should be enabled, we expect there to be a secret present in the cluster containing this configuration. For Gitpod SaaS, this is achieved via terraform as a cluster prerequisite:https://github.com/gitpod-io/ops/blob/8fb50515adbfa90a3435f2148660f7de8d70c219/terraform/modules/gitpod/main.tf#L31-L38
Related Issue(s)
Part of #9097
How to test
Create an installer config file containing this
experimental
section:Get a
versions.yaml
for use with the installer:Then invoke the installer as:
The
server
configmap will haveenablePayment
set totrue
and theserver
deployment will have an extra volume + volumemount:Release Notes
Documentation
None.