Autoscaler: cluster-autoscaler-chart chart 1.0.5 and 1.1.0 releases are missing

Created on 12 Oct 2020  路  10Comments  路  Source: kubernetes/autoscaler

Ref:
wget https://kubernetes.github.io/autoscaler/index.yaml

Most helpful comment

For future reference, I'm currently the best person to tag on any issues with the CA's Chart as per the Chart directory's OWNERS file.

I've just raised the PR to add these as #3617 - due to the branch protection enforced on this repo the automated push to the gh-pages branch method used by the Helm chart releaser action fails when attempting the second part of the action. This is a known issue, and at the moment means that we have to follow up releases with manual pull requests as here meaning that the versions accessible to helm may lag behind the published artifacts - I'll raise a PR to make this clearer in the chart docs going forward.

All 10 comments

@bskiba could you please take a look?

same for me

same here

@tghartland @displague @Ladicle could you please help?

@mwielgus or @maciekpytel maybe you?

https://github.com/kubernetes/autoscaler/runs/1253906372?check_suite_focus=true

+ git push ***github.com/kubernetes/autoscaler gh-pages remote: error: GH006: Protected branch update failed for refs/heads/gh-pages. remote: error: 2 of 2 required status checks are expected. To https://github.com/kubernetes/autoscaler ! [remote rejected] gh-pages -> gh-pages (protected branch hook declined) error: failed to push some refs to 'https://github.com/kubernetes/autoscaler'

For future reference, I'm currently the best person to tag on any issues with the CA's Chart as per the Chart directory's OWNERS file.

I've just raised the PR to add these as #3617 - due to the branch protection enforced on this repo the automated push to the gh-pages branch method used by the Helm chart releaser action fails when attempting the second part of the action. This is a known issue, and at the moment means that we have to follow up releases with manual pull requests as here meaning that the versions accessible to helm may lag behind the published artifacts - I'll raise a PR to make this clearer in the chart docs going forward.

Closing as #3617 has been merged and validated fetching both 1.0.5 and 1.1.0 locally.

/close

@gjtempleton: Closing this issue.

In response to this:

Closing as #3617 has been merged and validated fetching both 1.0.5 and 1.1.0 locally.

/close

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.

Thank you!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mboersma picture mboersma  路  6Comments

benmoss picture benmoss  路  4Comments

bpinske picture bpinske  路  5Comments

losipiuk picture losipiuk  路  7Comments

hprotzek picture hprotzek  路  5Comments