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

📖 docs: add helm chart repository adr #426

Merged

Conversation

salasberryfin
Copy link
Contributor

What this PR does / why we need it:

This ADR puts together details of the two main options for serving Helm charts:

The idea is that we go over the pros/cons as a team and try to decide which is the best option and define an action plan, if necessary.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@salasberryfin salasberryfin added the kind/documentation Improvements or additions to documentation label Mar 11, 2024
@salasberryfin salasberryfin requested a review from a team as a code owner March 11, 2024 14:35
@salasberryfin salasberryfin force-pushed the adr-publish-chart-to-rancher branch 3 times, most recently from 4971324 to 51a029c Compare March 11, 2024 15:01
@salasberryfin salasberryfin changed the title docs: add helm chart repository adr 📖 docs: add helm chart repository adr Mar 11, 2024
Copy link
Contributor

@Danil-Grigorev Danil-Grigorev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Option 2 seems more appealing to me, I would also suggest renaming this ADR to chart publishing process

docs/adr/0009-publish-chart-to-rancher-charts.md Outdated Show resolved Hide resolved
@salasberryfin salasberryfin force-pushed the adr-publish-chart-to-rancher branch from 51a029c to ca0ef5f Compare March 13, 2024 15:34
@salasberryfin
Copy link
Contributor Author

I updated the ADR with the final decision. Also expanded on some topics that were not as clear as expected, as reported by @Danil-Grigorev.

richardcase
richardcase previously approved these changes Mar 13, 2024
Copy link
Contributor

@richardcase richardcase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree based on the "cons" for rancher/charts i think we go with the separate chart repo initially. We can re-evaluate in the future if needed.

docs/adr/0009-publish-chart-to-rancher-charts.md Outdated Show resolved Hide resolved
@Danil-Grigorev Danil-Grigorev added kind/proposal Issues or PRs related to proposals and removed kind/proposal Issues or PRs related to proposals labels Mar 13, 2024
@salasberryfin salasberryfin force-pushed the adr-publish-chart-to-rancher branch from ca0ef5f to fdb53c2 Compare March 14, 2024 07:44
Copy link
Contributor

@furkatgofurov7 furkatgofurov7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on using custom chart repo, as it would drag us out of the unneccessary complications&mess that rancher/charts would bring (based on hosted provider experience). However, I would suggest to expand a bit how Kubewarden does it without using it, because by just reading, it was not clear to me.

docs/adr/0009-publish-chart-to-rancher-charts.md Outdated Show resolved Hide resolved
@furkatgofurov7
Copy link
Contributor

@salasberryfin please fix the CI failure, otherwise this LGTM

@salasberryfin salasberryfin force-pushed the adr-publish-chart-to-rancher branch from b15f5bc to 209344a Compare March 18, 2024 15:53
@salasberryfin salasberryfin force-pushed the adr-publish-chart-to-rancher branch from 209344a to 27d2f7a Compare March 18, 2024 15:59
@salasberryfin
Copy link
Contributor Author

CI is now fixed and the ADR is ready for a final review.

@salasberryfin salasberryfin merged commit 61db65a into rancher:main Mar 26, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants