carvel-dev / carvel-dev/kapp-controller

Kapp-controller value schema for packages should show required configuration

Open
#474 3 comments 0 reactions 0 assignees View on GitHub
awaiting-input carvel-accepted discussion enhancement
Dominant language
Go
Stars
323
Forks
127
Avg merge
2d 10h
Merged PRs (30d)
6

Description

As part of kctrl (kapp-controller CLI) command - kctrl package available list", there is requirement to show whether there is a required configuration that should be provided (e.g. external-dns does not work without providing the required data-values).

1. Can we derive this information from value schema in kapp-controller package?
2. Will adding certain meta-data help derive this information?

---
Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

Contributor guide

Open the contributing guide

Research direction

Start with the kctrl package available list command and the kapp-controller package value schema; determine what schema information is available and whether metadata is needed. Done means the command can clearly indicate when required configuration exists, with behavior agreed for the schema and metadata cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.