[kots] Add --use-experimental-config to installer render call #10441
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/werft run 👍 started the job as gitpod-build-clu-kots-experimental.1 |
roboquat
added
release-note-none
and removed
do-not-merge/release-note-label-needed
labels
mrsimonemms
approved these changes
Jun 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Currently, in the KOTS installer job, the Gitpod Installer render call is without
--use-experimental-config. This limits what we can do with the Gitpod config patch file. This pull requests add this flag.Use case: We want to try if some configs that currently exist as experimental only will solve customer issues. If yes, we will move these configs out of experimental. To be able to test these configs first, the experimental flag is needed.
Release Notes
werft
/werft no-preview
/werft publish-to-kots