You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The apiVersion: "v1" in a customization YAML gets rendered the Installer config correctly, but this is not picked up in the internals - it's omitted entirely when it's pushed through to the config map
When looking at the config file (kubectl get configmaps -n gitpod gitpod -o jsonpath='{.data.config\.yaml}'), this is rendered as (note the missing apiVersion):
I can't recreate this, but weirdly I could when I initially raised this ticket. I've tried it against the current version in main and also the June release without success.
I'll add this as a specific unit test, but I think that's the best I can do in this
Bug description
The
apiVersion: "v1"
in a customization YAML gets rendered the Installer config correctly, but this is not picked up in the internals - it's omitted entirely when it's pushed through to the config mapapiVersion: "*"
still works thoughSteps to reproduce
When applying the customization file:
When looking at the config file (
kubectl get configmaps -n gitpod gitpod -o jsonpath='{.data.config\.yaml}'
), this is rendered as (note the missingapiVersion
):Workspace affected
No response
Expected behavior
The
apiVersion
should be implemented asv1
Example repository
No response
Anything else?
Internal discussion
The text was updated successfully, but these errors were encountered: