azure/brigade-charts

Helm Charts for the Brigade project

Brigade Charts

Helm charts for the Brigade project have been moved to brigadecore/charts.

During the transitional phase, we will continue to serve an index file in this repo pointing to the new chart URL. However, future chart releases will not be added to this repo.

All subsequent chart releases will be served at the new URL: https://brigadecore.github.io/charts

Please update your local Helm repo:

helm repo remove brigade
helm repo add brigade https://brigadecore.github.io/charts

This Azure/brigade-charts repo will be deleted after the transition is complete.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

brigade-charts's Issues

CI/brigade.js: create publish/release event(s)

The initial brigade.js just introduced test runs for PRs.

We may want:

• a publish event handler to watch for pushes to master and run make build index and merge the corresponding git commit to update the chart artifacts/index.yaml (and thereby update the helm repository) (or perhaps we just instruct contributors to do so as part of PR?)
• a release event handler to watch for tag pushes, if we plan on tagging all charts together (perhaps not?)

Add resource requests and limits where needed

It seems like some charts are missing the resource requests and limits on pods. We should add those and making them configurable.

Include Kashti in Brigade chart

As mentioned in the Brigade 1.0.0 Meta ticket:

• [ ] Include Kashti resources in main Brigade chart

• [ ] Delete separate Kashti chart?

• Include Kashti as a sub-chart in the Brigade chart; enable by default - #13

• Update Kashti docs accordingly - brigadecore/kashti#239

(edited by vdice, 12/20)

CI: Build, index and serve charts via gh-pages branch

Update CI to build, index and serve latest charts from a gh-pages branch, thereby eliminating the need (and unadvised practice) of updating charts directly on commits to master.

Ref: brigade chart: global image.{repository,tag} values?

Wondering if it'd be worth refactoring charts/brigade to use a top-level/global image config, primarily for setting image.repository and image.tag to be used by all deployments. (Currently, each component's image config needs changing when non-defaults are desired.)

Missing brigade-project with appVersion v0.20.0 in chart repo

Latest versions in brigade charts are:

• brigade 0.20.0 -> v.0.20
• brigade-project 0.19.3 -> v0.19.0

So i'm missing a new version of brigade-project for appVersion v0.20.0.

Use chart-testing to test prs

Use https://github.com/helm/chart-testing to test prs and updates to charts.

This is a very simple tool that can automatically test charts when they are updated via a pr.

This includes checking for valid authors, requiring version bumps for all changes (like the official helm repo) and linting the charts.

CI steps for packaging charts and generating index.yaml

I took a quick look at the brigade.js and did not see any steps for it to package up the charts, creating the index.yaml and pushing the updates to the repo. We probably should automate that to prevent any manual issues.

Feat(ci): add 'helm install --dry-run --debug' test for chart(s)

We currently lint charts via test, but it would be great to also helm install --dry-run --debug $(CHART) for each/all charts.

Add ingress templates

Some of the endpoints that are intended to be exposed (such as gateways) lack an ingress resource.

This issue tracks the addition of ingress templates for all gateways.

cc @dgkanatsios for the generic gateway.