Image reference becomes repo:tag:tag when the repository field already includes a tag

Which component(s) is affected?

Kubero CLI

Describe the bug

The KuberoApp Helm chart templates (helm-charts/kuberoapp/templates/deployment-web.yaml and deployment-worker.yaml) build the image reference by blind concatenation:

image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default "latest" }}"

There's no check for whether .Values.image.repository already contains a tag. If a user enters an image reference including a tag (e.g. myrepo/myimage:latest) into the "repository" field in the Kubero UI — a natural thing to do, since most people are used to typing full image refs that way — and the separate tag field defaults to latest, the rendered image becomes myrepo/myimage:latest:latest, which is not a valid image reference.

Steps to reproduce

1. In the Kubero UI, set an app's image repository field to a value that includes a tag, e.g. nginx:latest
2. Leave the tag field at its default
3. Deploy and inspect the generated Deployment's image: field

Expected behavior

Expected behavior: Kubero should either strip any tag already present in the repository field, or clearly document/enforce that the field must not include a tag.

Actual behavior: The rendered image reference is ::, causing the image pull to fail.

Suggested fix: Split any existing :tag off the repository field before concatenating, or validate/reject repository values containing a colon in the UI.

Screenshots

No response

Additional information

No response

Debug information

No response

Start by inspecting helm-charts/kuberoapp/templates/deployment-web.yaml and deployment-worker.yaml, then render a chart using a repository value such as nginx:latest and the default tag. Done means the generated Deployment has a valid image reference without a duplicated tag, with the repository-field behavior clearly documented or enforced.