in-toto Helm Charts #34
Comments
|
@in-toto/in-toto-steering-committee-itsc As a maintainer of Witness and Archivista, I'm happy to also be a maintainer of this new repo. |
|
Hey folks, any update about this issue? We have an issue related to this helm chart. |
|
Discussed in the community meeting! Created @in-toto/helm-charts team and helm-charts repository |
wcrum
added a commit
to wcrum/archivista
that referenced
this issue
Dec 16, 2024
- helm charts moved to github.com/in-toto/helm-charts - see in-toto/community#34
5 tasks
wcrum
added a commit
to wcrum/archivista
that referenced
this issue
Dec 16, 2024
- helm charts moved to github.com/in-toto/helm-charts - see in-toto/community#34 Signed-off-by: Will <[email protected]>
jkjell
pushed a commit
to wcrum/archivista
that referenced
this issue
Dec 17, 2024
- helm charts moved to github.com/in-toto/helm-charts - see in-toto/community#34 Signed-off-by: Will <[email protected]>
kairoaraujo
pushed a commit
to in-toto/archivista
that referenced
this issue
Dec 17, 2024
- helm charts moved to github.com/in-toto/helm-charts - see in-toto/community#34 Signed-off-by: Will <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi folks,
I want to propose the creation of a repository in in-toto GitHub Organization helm-charts .
Also, this project should have a branch gh-pages pointing to https://in-toto.org/helm-charts, and we could use the helm/chart-releaser-action to automatically manage release versions of the chart.
All sub-projects that provide containers and would like to use a helm chart for deployment could use it to facilitate provisioning.
So, users could easily do:
I'm asking because I would like to have the Archivista helm charts released and delivered in this way 🙂
So, Archivista users could have the helm charts in an easier way.
Reference:
I also managed this for RSTUF, providing the helm-charts that way. So, I would love to kick off it with Archivista in the in-to-helm charts.
Actions required:
Having it, I'm ready to submit the PRs to the repository and branches 😉
The text was updated successfully, but these errors were encountered: