apache / apache/camel-k

Possibility to enforce image name and image tag for dry-build

Open
#6,428 2 comments 0 reactions 0 assignees View on GitHub
kind/feature status/never-stale
Dominant language
Go
Stars
927
Forks
387
Avg merge
15h 5m
Merged PRs (30d)
36

Description

### Requirement

Currently dry build feature creates image with "arbitrary" image name / tag, that AFAIU comes from `IntegrationKit` name
e.g. `host.k3d.internal:5000/iesh/camel-k/camel-k-kit-d55aa136at9s739et9cg:10480`

It could be great to have options ( annotations, traits) so one could enforce resulting image name, e.g.

`host.k3d.internal:5000/iesh/camel-k/my-cool-integration:v1.0.0`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the dry-build flow and how the IntegrationKit name is converted into the resulting image name and tag. Check where annotations or traits could provide these options, and consider how the requested repository, image name, and version should be represented; done means a dry build can produce the explicitly requested image reference.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.