use github pages to host official helm chart repository

kubernetes-sigs / cloud-provider-azure

Cloud provider for Azure

https://cloud-provider-azure.sigs.k8s.io/

Apache License 2.0

258 stars 270 forks source link

use github pages to host official helm chart repository #1418

Open jackfrancis opened 2 years ago

jackfrancis commented 2 years ago

What would you like to be added:

This is a proposal to consider using the github pages feature to host the helm chart repo, rather than hosting it in a static directory in the repo. It looks like there is a gh-pages branch that hasn't been updated in over a year, so maybe we can use it for this?

I've had success in other projects using this github action to accomplish this goal:

https://github.com/helm/chart-releaser-action

Why is this needed:

Not 100% required, but would make helm chart downloads easier for users. Compare:

helm install --repo https://kubernetes-sigs.github.io/cloud-provider-azure/

helm install --repo https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/helm/repo

The former (which is what a gh-pages-backed repo would look like) is cleaner IMO.

jaanhio commented 2 years ago

hello @jackfrancis , i am happy to work on this if it isn't taken yet.

but one clarification i have is, is the intention to remove the existing hugo pages and replace it with hosting of helm chart repo or have both the hugo pages and helm chart repo hosted together?

jackfrancis commented 2 years ago

I don't believe you can get both (the chart-releaser-action takes over the entire hugo implementation as far as I can tell).

cc @lzhecheng @feiskyer for permissions to overwrite the existing github pages content

bridgetkromhout commented 2 years ago

@jackfrancis This repo's ghpages branch is in use with some current updates now: https://github.com/kubernetes-sigs/cloud-provider-azure/tree/gh-pages

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Sajiyah-Salat commented 1 year ago

is this pr still valid?

feiskyer commented 1 year ago

yes, better to host with github pages, but we need to check how to host both charts and website together.

/remove-lifecycle stale