[kots]: apply customization file to Installer #10911
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
Adds the config section to the KOTS dashboard for the customization file
NB this must be applied to a cluster which does not have Gitpod installed. If you have it installed, you must run
helm un -n gitpod gitpod
beforehand if you intend to change any labels with your customization file. This is because Kubernetes cannot change the labels of a deployment/daemonset/statefulset. As this is for a specific set of enterprise customers who have engaged us for support, this should be an acceptable compromise for the time being.This may be fixed in a future PR.
This is not an issue if changing annotations
Related Issue(s)
Fixes #10910
How to test
Deploy via KOTS to a cluster, using this YAML as your customization file
When you next run it,
kubectl get pods -n gitpod -l component=server -o jsonpath="{.items[0].metadata.annotations}"
should have the annotationhello=word
Release Notes
Documentation
Werft options: