Allow using Helm charts as bases and values.yaml file patching in overlays

pentago commented 5 months ago

Eschewed features

[X] This issue is not requesting templating, unstuctured edits, build-time side-effects from args or env vars, or any other eschewed feature.

What would you like to have added?

I'd like to have ability to use Helm charts as regular base and allow patching of that base with different values.yaml as patches in overlays, like this:

.
├── base
│   ├── Chart.yaml
│   ├── kustomization.yaml
│   └── values.yaml
└── environments
    ├── dev
    │   ├── kustomization.yaml
    │   └── prod-values.yaml
    ├── prod
    │   ├── kustomization.yaml
    │   └── prod-values.yaml
    └── stage
        ├── kustomization.yaml
        └── stage-values.yaml

Why is this needed?

Something like this would make Helm charts first-class citizens in Kustomize projects and allow for uniform patching to standard Kubernetes YAML manifests.

Can you accomplish the motivating task without this feature, and if so, how?

Only by using a lot of duplication like using full values.yaml for each overlay.

What other solutions have you considered?

Not aware of anything else doing this and would love to get this thing done with only Kustomize.

Anything else we should know?

No response

Feature ownership

[ ] I am interested in contributing this feature myself! 🎉

k8s-ci-robot commented 5 months ago

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

pentago commented 2 months ago

/remove-lifecycle stale

kubernetes-sigs / kustomize