[installer] Make ws-manager-bridge
configurable
#9760
Merged
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 allows the
ws-manager-bridge
component to control whether or not it should register itself as a workspace cluster. For self hosted installations it should do so but for SaaS, where we run separate workspace clusters, it should not.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
ws-manager-bridge
config will contain the following whenskipSelf
isfalse
:and the
staticBridges
key will be[]
whenskipSelf
istrue
.Likewise the
WSMAN_CFG_MANAGERS
env var in theserver
component will change according to the value ofskipSelf
(but the json is bas64 encoded).Release Notes
Documentation
None.