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

Extract helm chart(s) into its own repo #11

Closed
dblock opened this issue Jul 22, 2021 · 8 comments
Closed

Extract helm chart(s) into its own repo #11

dblock opened this issue Jul 22, 2021 · 8 comments
Labels
enhancement New feature or request helm

Comments

@dblock
Copy link
Member

dblock commented Jul 22, 2021

Coming from #4 (comment), should be its own project.

@dblock dblock mentioned this issue Jul 22, 2021
1 task
@dblock
Copy link
Member Author

dblock commented Jul 22, 2021

@TheAlgo since you PR-ed #4 if you have any interest in making/extracting this into a new repo I can help move it into the org

@davidkarlsen
Copy link

It can still reside here. What would be great is to publish the charts and index to a helm repo for instance using github pages and this gh action :https://github.com/helm/chart-release-action
Which makes consumption a lot easier

@dblock
Copy link
Member Author

dblock commented Jul 22, 2021

It can still reside here. What would be great is to publish the charts and index to a helm repo for instance using github pages and this gh action :https://github.com/helm/chart-release-action
Which makes consumption a lot easier

What are the advantages to bundling all this in one repo? Feels like it's easy to make a mess. Each helm chart would have its own setup to be published every time code changes via CI that anyone can setup/contribute to as well.

That said, looking at https://github.com/helm/chart-releaser-action it seems like it wants charts to be combined and released together?

@peterzhuamazon
Copy link
Member

peterzhuamazon commented Jul 22, 2021

Instead of doing a new repo can we do something like this:
opendistro-for-elasticsearch/opendistro-build#693

This is a place for us to have multiple community projects co-exist and I would like to keep that behavior for now.

@dblock
Copy link
Member Author

dblock commented Jul 22, 2021

Instead of doing a new repo can we do something like this:
opendistro-for-elasticsearch/opendistro-build#693

Probably. My only worry is that this repo becomes a kitchen sink of all thinks devops that are unrelated to each-other. Will leave it to the people contributing to consider the pros and cons.

@dblock
Copy link
Member Author

dblock commented Jul 22, 2021

This is a place for us to have multiple community projects co-exist and I would like to keep that behavior for now.

👍

@dblock dblock changed the title Extract helm chart into its own repo Extract helm chart(s) into its own repo Jul 22, 2021
@TheAlgo
Copy link
Member

TheAlgo commented Jul 23, 2021

Instead of doing a new repo can we do something like this:
opendistro-for-elasticsearch/opendistro-build#693

This is a place for us to have multiple community projects co-exist and I would like to keep that behavior for now.

@dblock @peterzhuamazon @davidkarlsen I will agree with Peter and David , if we can have an index that will make consumption easier.

@peterzhuamazon peterzhuamazon added the enhancement New feature or request label Jul 23, 2021
@peterzhuamazon
Copy link
Member

Both #4 and #10 are now in the repo, approved and merged.
Thanks everyone for the help in the process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request helm
Projects
None yet
Development

No branches or pull requests

4 participants