Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 39 additions & 6 deletions .github/workflows/chart-release.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,11 @@ jobs:
ca-release:
permissions:
contents: write # for helm/chart-releaser-action to push chart release and create a release
packages: write # for pushing charts to GHCR
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4.2.2
uses: actions/checkout@v6.0.0
with:
fetch-depth: 0

Expand All @@ -18,9 +19,9 @@ jobs:
git config user.email "${GITHUB_ACTOR}@users.noreply.github.com"

- name: Install Helm
uses: azure/setup-helm@v4.2.0
uses: azure/setup-helm@v4.3.1
with:
version: v3.4.0
version: v3.19.2

- env:
CR_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Expand All @@ -29,13 +30,29 @@ jobs:
uses: helm/[email protected]
with:
charts_dir: cluster-autoscaler/charts

- name: Login to GitHub Container Registry
uses: docker/[email protected]
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}

- name: Push charts to GHCR
run: |
set -e
shopt -s nullglob
for pkg in .cr-release-packages/*; do
helm push "${pkg}" "oci://ghcr.io/${GITHUB_REPOSITORY_OWNER}/charts"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that the container registry is per "owner" (ie, in our case that would be kubernetes, not kubernetes/autoscaler)

I have no idea what the permission model is around that

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to find out whether the kubernetes org allows workflows to create new packages. This is controlled by the org's "Packages" settings. If package creation is restricted, the first push would fail and we'd need an org admin to either pre-create the package or adjust the org settings.

I can add a note in the PR description about this, or we could do a test run with workflow_dispatch to verify it works before merging. What do you think?

done
vpa-release:
permissions:
contents: write # for helm/chart-releaser-action to push chart release and create a release
packages: write # for pushing charts to GHCR
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4.2.2
uses: actions/checkout@v6.0.0
with:
fetch-depth: 0

Expand All @@ -45,9 +62,9 @@ jobs:
git config user.email "${GITHUB_ACTOR}@users.noreply.github.com"

- name: Install Helm
uses: azure/setup-helm@v4.2.0
uses: azure/setup-helm@v4.3.1
with:
version: v3.4.0
version: v3.19.2

- env:
CR_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Expand All @@ -56,8 +73,24 @@ jobs:
uses: helm/[email protected]
with:
charts_dir: vertical-pod-autoscaler/charts

- name: Login to GitHub Container Registry
uses: docker/[email protected]
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}

- name: Push charts to GHCR
run: |
set -e
shopt -s nullglob
for pkg in .cr-release-packages/*; do
helm push "${pkg}" "oci://ghcr.io/${GITHUB_REPOSITORY_OWNER}/charts"
done
name: Release Charts
on:
push:
branches:
- master
workflow_dispatch:
16 changes: 16 additions & 0 deletions cluster-autoscaler/charts/cluster-autoscaler/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ Scales Kubernetes worker nodes within autoscaling groups.

## TL;DR

### Using Helm Repository

```console
$ helm repo add autoscaler https://kubernetes.github.io/autoscaler

Expand All @@ -18,6 +20,20 @@ $ helm install my-release autoscaler/cluster-autoscaler \
--set "autoscalingGroups[0].minSize=1"
```

### Using OCI Registry

```console
# Method 1 - Using Autodiscovery
$ helm install my-release oci://ghcr.io/kubernetes/charts/cluster-autoscaler \
--set 'autoDiscovery.clusterName'=<CLUSTER NAME>

# Method 2 - Specifying groups manually
$ helm install my-release oci://ghcr.io/kubernetes/charts/cluster-autoscaler \
--set "autoscalingGroups[0].name=your-asg-name" \
--set "autoscalingGroups[0].maxSize=10" \
--set "autoscalingGroups[0].minSize=1"
```

## Introduction

This chart bootstraps a cluster-autoscaler deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
Expand Down
16 changes: 16 additions & 0 deletions cluster-autoscaler/charts/cluster-autoscaler/README.md.gotmpl
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@

## TL;DR

### Using Helm Repository

```console
$ helm repo add autoscaler https://kubernetes.github.io/autoscaler

Expand All @@ -18,6 +20,20 @@ $ helm install my-release autoscaler/cluster-autoscaler \
--set "autoscalingGroups[0].minSize=1"
```

### Using OCI Registry

```console
# Method 1 - Using Autodiscovery
$ helm install my-release oci://ghcr.io/kubernetes/charts/cluster-autoscaler \
--set 'autoDiscovery.clusterName'=<CLUSTER NAME>

# Method 2 - Specifying groups manually
$ helm install my-release oci://ghcr.io/kubernetes/charts/cluster-autoscaler \
--set "autoscalingGroups[0].name=your-asg-name" \
--set "autoscalingGroups[0].maxSize=10" \
--set "autoscalingGroups[0].minSize=1"
```

## Introduction

This chart bootstraps a cluster-autoscaler deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
Expand Down
15 changes: 15 additions & 0 deletions vertical-pod-autoscaler/charts/vertical-pod-autoscaler/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,21 @@ Automatically adjust resources for your workloads
## Introduction
The Vertical Pod Autoscaler (VPA) automatically adjusts the CPU and memory resource requests of pods to match their actual resource utilization.

## Installation

### Using Helm Repository

```console
$ helm repo add autoscaler https://kubernetes.github.io/autoscaler
$ helm install my-release autoscaler/vertical-pod-autoscaler
```

### Using OCI Registry

```console
$ helm install my-release oci://ghcr.io/kubernetes/charts/vertical-pod-autoscaler
```

## Maintainers

| Name | Email | Url |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,21 @@ WARNING: This chart is currently under development and is not ready for producti
## Introduction
The Vertical Pod Autoscaler (VPA) automatically adjusts the CPU and memory resource requests of pods to match their actual resource utilization.

## Installation

### Using Helm Repository

```console
$ helm repo add autoscaler https://kubernetes.github.io/autoscaler
$ helm install my-release autoscaler/vertical-pod-autoscaler
```

### Using OCI Registry

```console
$ helm install my-release oci://ghcr.io/kubernetes/charts/vertical-pod-autoscaler
```

{{ template "chart.maintainersSection" . }}

{{ template "chart.requirementsSection" . }}
Expand Down
Loading