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

[stable/several] Transition from stable to bitnami #20969

Closed
carrodher opened this issue Feb 24, 2020 · 2 comments
Closed

[stable/several] Transition from stable to bitnami #20969

carrodher opened this issue Feb 24, 2020 · 2 comments

Comments

@carrodher
Copy link
Collaborator

@carrodher carrodher commented Feb 24, 2020

Context
With the Helm 3 release, there are some changes affecting the charts repository. Some changes are due to technical reasons, while others are to facilitate the maintenance of the charts.

About the second item, in the next months stable/incubator are going to be de-listed from Hubs (in fact, they are already not included by default in Helm 3). Here you can find more information about the distributed approach to maintain charts.
That means each chart maintainer should move the charts to their own repository, and of course, maintain them, provide support, include them in Kubeapps Hub, etc

Given the stable deprecation timeline, from Bitnami we are going to start moving the charts maintained by us to https://github.com/bitnami/charts.

This repository is already included in the Hubs and we will provide the same cadence of updates, support, etc that we've been keeping here these years. Installation instructions are very similar, just adding the bitnami repo and using it during the installation (bitnami/<chart> instead of stable/<chart>)

$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install my-release bitnami/<chart>           # Helm 3
$ helm install --name my-release bitnami/<chart>    # Helm 2

After the migration takes place, issues/PRs related to the charts itself will be redirected to bitnami/charts, we'll be happy to answer questions related to this migration in this Issue, k8s Slack, etc.

Action plan

  • Deprecate the charts from stable repo.
  • Add a note in each chart README pointing to the new location.
  • Update this issue so users can have a commonplace to see the reason, process, feel comfortable with the move, (comment if they feel like it), etc.

Affected charts

This was referenced Mar 10, 2020
@stale

This comment has been minimized.

Copy link

@stale stale bot commented Mar 26, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Mar 26, 2020
@scottrigby scottrigby mentioned this issue Mar 26, 2020
8 of 12 tasks complete
@stale stale bot removed the lifecycle/stale label Mar 26, 2020
@scottrigby

This comment has been minimized.

Copy link
Member

@scottrigby scottrigby commented Mar 26, 2020

This is complete, and users appear to have transitioned without trouble. Thanks @carrodher for all your work on this! 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.