K8s profiles: Add `--image` arg to `charmcraft init`

Metadata

Project: charmcraft
Number: #1246
Type: issue
State: open
Author: sed-i
Labels: —
Created: 2023-09-06 01:28 AM UTC
Updated: 2025-08-15 03:18 PM UTC
Closed: —

Current evaluation

Feature request to add a --image argument to `charmcraft init` for Kubernetes profiles, so rendered metadata.yaml uses the provided container image instead of the 'some-container-image' placeholder. Unlabelled, no maintainer response, not yet implemented.

Suggested action: needs triage

Reason: The issue has no labels, no comments, and no maintainer acknowledgement, so it has not been triaged. The requested `--image` flag is still absent from InitCommand.fill_parser (only --name/--author/--force/--profile/--project-dir exist), and the templates still hardcode the 'some-container-image' placeholder, confirming it is unimplemented. Although the init/profiles area is still actively developed, this specific request needs a maintainer decision on scope (single vs multiple images, which files to render).

Impact: 30 Quick Win: 18.0 Staleness: 70 Complexity: 40 Confidence: 80 Support Request: 0

Issue body

### What needs to get done It would be handy if `charmcraft init` could take image name(s) when rendering a project tree. This could be done similarly to the `--resource` arg in juju: ``` charmcraft init \ --profile kubernetes \ --name charmed-app-k8s \ --image workload1=ghcr.io/x/y:z --image workload2=ghcr.io/a/b:c ``` This would render metadata.yaml etc. with the provided image(s) instead of the placeholder "some-container-image". ### Why it needs to get done When we charm up an app, we usually know which image we want to start with. Having it rendered up front would save some time and confusion, especially for beginners.

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 12:39 AM UTC	qwen/qwen3.8-27b	Impact: 30 Quick Win: 18.0 Staleness: 70 Complexity: 40 Confidence: 80 Support Request: 0	needs triage	Feature request to add a --image argument to `charmcraft init` for Kubernetes profiles, so rendered metadata.yaml uses the provided container image instead of the 'some-container-image' placeholder. Unlabelled, no maintainer response, not yet implemented.
2026-07-22 11:48 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 92 Complexity: 20 Confidence: 85 Support Request: 10	close stale	Feature request to add --image argument to charmcraft init for Kubernetes profiles. Unlabeled, zero comments, inactive for over 2.5 years, awaiting review.
2026-07-07 11:29 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 20 Confidence: 85 Support Request: 10	needs triage	Feature request to add --image argument to charmcraft init for Kubernetes profiles, allowing pre-filled container images instead of placeholders. Untriaged and inactive for over 10 months.
2026-07-05 05:10 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 20 Confidence: 80 Support Request: 5	needs triage	Feature request to add an --image argument to charmcraft init for Kubernetes profiles, allowing users to specify container images during project initialization. The issue remains untriaged with no maintainer interaction for over two years.
2026-06-16 02:16 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 20 Confidence: 70 Support Request: 10	needs triage	Proposes adding a --image flag to charmcraft init for K8s profiles to pre-populate container images in generated metadata. Open with zero comments and 304 days of inactivity, awaiting triage.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.