Attempting to Using 'Configure additional registry credentials' Causes Installer Pod to Fail

[jimmybrancaccio]

Bug description

When using the 'Configure additional registry credentials' option within the KOTS Admin UI under Config, it will cause an error that causes the installer pod to fail.

Steps to reproduce

I have KOTS 1.88.0 installed and my Gitpod version is release-2022.10.0.16.

1. Created a new private repository on GitLab.
2. Created a Personal Access Token on GitLab.
3. Pulled node:buster and then pushed it to my private repository registry.gitlab.com/astuffedtiger/gitpod-private-repo.
4. Grabbed my Docker login credentials and stuck them into a file - docker-config.json.
5. Opened up the KOTS admin UI for gitpod.support.
6. Updated my configuration to use this .json file under the "Configure additional registry credentials" section.
7. I also created a config patch file - default-workspace-image-override.yaml with the contents:

   observability:
     logLevel: debug
   workspace:
     workspaceImage: registry.gitlab.com/astuffedtiger/gitpod-private-repo:latest

8. I used this under the Advanced Options > Gitpod config patch (YAML file).
9. I hit Save config and deployed that new sequence.
10. In looking at ConfigMap/gitpod I do not see workspace > workspaceImage as being set.
11. In looking at the diff in the KOTS admin UI I saw the addition of the workspaceImage line.

Workspace affected

No response

Expected behavior

I expect this functionality to work so that I can use workspace images from a private registry.

Example repository

No response

Anything else?

Line of code which may be related to this issue -

gitpod/install/installer/scripts/kots-install.sh

Line 166 in 3ac8f43

REGISTRY_SECRET="$(jq -s '.[0] * .[1]' /tmp/userconfig.json /tmp/currentconfig.json | base64 -w 0)"

--

Front conversations