Repo URL gets cut off about keel

[rusenask]

Hey Jeff, Thank you for your query. The example shows that you are incorrectly using keel config. That repository shouldn't be your actual image repository, it is a reference to that value in your values.yaml file. Could you please have a look at example config here https://keel.sh/user-guide/providers/#helm-configuration-example. The idea here is that you only specify actual image name in one place and just let keel find it based on that reference. I hope you find this helpful. If you have any questions don't hesitate to contact again.

…

On Mon, Sep 25, 2017, 7:51 PM Jeff Richie ***@***.***> wrote: I have my keel: settings in values.yaml.: keel: policy: all trigger: poll pollSchedule: ***@***.*** 5m" images: - repository: "quay.io/repo/app" tag: image.dockerTag In the keel pod logs I see: kube-system keel-keel-3958146990-5zn02 keel 2017/09/25 18:47:06 warning: destination for settings is a table. Ignoring non-table value <nil> kube-system keel-keel-3958146990-5zn02 keel time="2017-09-25T18:47:06Z" level=error msg="provider.helm: failed to parse image" error="io/repo/app is not a value" repository_name=quay.io/repo/app repository_tag=image.dockerTag — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#102>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIqNKcYrMRXr9DJbRg_57O0MuApnBb9wks5sl_YxgaJpZM4PjLZx> .

[jeffrichie]

We do our values.yaml files a bit differently - we have a global section that has the repo info (ie. global.registry.host = quay.io/repo) and then we use appName.service.name to name each app, and then in the charts we concatenate the two values to get the image repo.

So I can't just send in a string that is the repo URL?