manifest download 404

[nmnellis]

What happened:

Install instructions returns a 404 https://github.com/kubernetes-sigs/metrics-server/releases/download/metrics-server-helm-chart-3.5.0/components.yaml

  kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

What you expected to happen:
download components.yaml

/kind bug

[serathius]

Looks like #670 broke README on master :(

[serathius]

Updated README to target v0.5.0 release.
@stevehipwell is there any option to avoid conflicting MS and chart releases for latest?

[nmnellis]

This isnt a great solution because lots of people like myself use the old url in our demo installs and such. its been that way for a long time.

https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

[stevehipwell]

@serathius I don't think so, this is a GH issue which catches backport release out too. I think you might be able to manually edit the release description of the release you want to be latest to make it so.

[serathius]

QQ, do we need for chart pipeling to push release GH at all, could tag be enough?

[stevehipwell]

@serathius it needs to be a release as it's a fundamental part of how the action works and manages the chart repo artifacts. Have you tried manually modifying the release you want to be latest to see if that's possible? If it is then maybe the chart release workflow could modify the last release to automate this.

[serathius]

If my modifying you mean adding any string to description then I tried that, also didn't find any other alternative ideas by Googling.

[stevehipwell]

@serathius I don't think there is an easy way to achieve this.

[serathius]

Could we just delete release after action works?

[stevehipwell]

@serathius no, that's where the chart artifact is hosted that the users download.

[stevehipwell]

@serathius we could add the artifacts to the chart release so they're still available.

[serathius]

that's hacky but should work.

[stevehipwell]

@serathius if you added the required artifacts to the current chart release manually I could take a look at automating them the next time?

[serathius]

Sure, uploaded components.yaml to chart release. @nmnellis please take a look if it works for you