helm-release: Publish the helm chart as OCI artifact

[marcofranssen]

This PR will ensure whenever a new release of the chart is published it will also be published as OCI.

the chart will be published at ghcr.io/kubernetes-sigs/charts/cluster-proportional-autoscaler

Same is used for couple of years here https://github.com/spiffe/helm-charts-hardened/blob/spire-0.26.1/.github/workflows/helm-release.yaml#L53-L70

Also see kubernetes-sigs/metrics-server#1734

Note

As the original helm release isn't touched that part of the release will not be affected. Only if the http release succeeds the workflow will try to also publish this OCI release.

The risk therefore is very low.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: marcofranssen / name: Marco Franssen (62acb64)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: marcofranssen
Once this PR has been reviewed and has the lgtm label, please assign thockin for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @marcofranssen!

It looks like this is your first PR to kubernetes-sigs/cluster-proportional-autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-proportional-autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

[marcofranssen]

/remove-lifecycle stale

[marcofranssen]

/cc

[k8s-ci-robot]

@marcofranssen: GitHub didn't allow me to request PR reviews from the following users: marcofranssen.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc

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-sigs/prow repository.

[marcofranssen]

/auto-cc