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

Fix chart versioning based on tag events and release YAML assets #36

Open
5 tasks
chomatdam opened this issue Oct 15, 2024 · 0 comments
Open
5 tasks

Fix chart versioning based on tag events and release YAML assets #36

chomatdam opened this issue Oct 15, 2024 · 0 comments
Assignees

Comments

@chomatdam
Copy link
Contributor

chomatdam commented Oct 15, 2024

Current

  • Chart version (template) and app versions (nidhogg) are maintained manually
  • Kustomize is using newTag and gets Renovate PRs to update that value as well
  • Versioning/Releasing is challenging because of the cyclic dependency between 3rd parties and nidhogg

Desired

  • Set Chart.yaml version to a placeholder version 0.0.0 (with comment) so that we can still helm install/package locally
  • Defer responsibility of tagging the Chart.yaml version to the CI workflow when releasing a new version
  • Publish YAML artifact asset based of helm template when releasing a new version that can be consumed by 3rd parties
  • kustomize folder is removed and replaced by an example of custom config in the documentation directly
  • README.md is streamlined and indicating where to find the latest chart release in GitHub packages
@chomatdam chomatdam added the Github label Oct 15, 2024 — with Linear
@chomatdam chomatdam added Github and removed Github labels Oct 15, 2024
@scoquelin scoquelin changed the title Fix chart and kustomize versioning based on tag events Fix chart versioning based on tag events and release YAML assets Oct 16, 2024
@chomatdam chomatdam removed the Github label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants