Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull helm chart from git repo as ArgoCD #5658

Open
1 of 2 tasks
qdrddr opened this issue Apr 14, 2024 · 2 comments
Open
1 of 2 tasks

Pull helm chart from git repo as ArgoCD #5658

qdrddr opened this issue Apr 14, 2024 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@qdrddr
Copy link

qdrddr commented Apr 14, 2024

Eschewed features

  • 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?

Often, helmcharts are located in a git repo released under a brunch or tag.

Why is this needed?

Having kustimize be able to pull from that Git Repo and kustimize will make it easier to maintain in more GitOps fashion similar to ArgoCD, making it more convenient and popular.

Consider this environment: you have ArgoCD or FluxCD tool and wish to install a helm chart like this one. All is good if the default helm chart is enough since both Cd tools can pull from the Git Repo. But what if it's not, and you need to kustomize it? It's troublesome since you have to clone the git repo to customize it manually. This makes Git Ops hard, so lifting this limitation would make Gitops a brize.

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

The current workaround is to manually pull the git repo and then kustomize, making this more complicated to maintain and support and requiring more manual effort.

What other solutions have you considered?

N/A

Anything else we should know?

No response

Feature ownership

  • I am interested in contributing to this feature myself! 🎉
@qdrddr qdrddr added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 14, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 14, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@qdrddr
Copy link
Author

qdrddr commented May 1, 2024

I hope its not going to be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants