-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add chart repo to Artifact Hub #3638
Comments
Hi, thanks for raising this! Thanks to a helping hand from @scottrigby there's now an initial publish of it at https://artifacthub.io/packages/helm/cluster-autoscaler/cluster-autoscaler Unfortunately, as I hadn't fully anticipated the way Artifact Hub would perform indexing I've had to go back and raise a PR to mark the intermediate chart we published |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Resolved and available on artifact hub, with the previous chart naming deprecated. /close |
@gjtempleton: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The Artifact Hub is a place discover cloud native artifact (Helm charts, operators, etc). This is a request to add the autoscaler chart repo you are running to it. Specifically, https://kubernetes.github.io/autoscaler.
Currently, when people search the Artifact Hub they will discover the cluster autoscaler as presented by banzaicloud with an out of date version. It would be great to have newer versions listed and from the official source.
There is an existing Kubernetes organization and nginx ingress is listed in it. This should likely go in that organization.
The text was updated successfully, but these errors were encountered: