From dc44c1b7167cd5d3ca288d69b84e0e65b6b77157 Mon Sep 17 00:00:00 2001 From: r3drun3 Date: Fri, 16 Feb 2024 13:32:18 +0100 Subject: [PATCH] chore: bump version Signed-off-by: r3drun3 --- README.md | 19 ++++++++++++++----- SECURITY.md | 4 ++-- charts/khaos/values.yaml | 2 +- config/manager/kustomization.yaml | 2 +- 4 files changed, 18 insertions(+), 9 deletions(-) diff --git a/README.md b/README.md index 4b610ed..e722f35 100644 --- a/README.md +++ b/README.md @@ -839,10 +839,12 @@ Warning FailedScheduling 63s default-scheduler 0/4 nodes are available: 1 n ## Operator Installation + +### Via Makefile This repo contains a [github action](https://github.com/stackzoo/khaos/blob/main/.github/workflows/release.yaml) to publish the operator *oci image* to *github registry* when new release tags are pushed to the main branch. In order to install the operator as a pod in the cluster you can leverage one of the *make* targets: ```console -make deploy IMG=ghcr.io/stackzoo/khaos:0.0.27 +make deploy IMG=ghcr.io/stackzoo/khaos:0.0.28 ``` This command will install all the required *CRDs* and *RBAC manifests* and then start the operator as a pod: @@ -856,12 +858,19 @@ khaos-controller-manager-8887957bf-5b8g9 2/2 Running 0 > [!NOTE] > If you encounter RBAC errors, you may need to grant yourself cluster-admin privileges or be logged in as admin. +### Via Helm The *Makefile* also contains a target to build the operator's *Helm chart* with [*helmify*](https://github.com/arttor/helmify). -You can build the helm chart with the following command (once you are inside the project's root): +You can build the helm chart locally with the following command (once you are inside the project's root): ```console make helm ``` -As of right now, the charts are put inside the `charts` folder and not published to a registry or a repo. +This will put the charts inside the `charts/khaos` folder. +The release action also push the charts on the github registry. +You can install the operator via helm with the following single command: +```console +helm upgrade --install khaos oci://ghcr.io/stackzoo/khaos/helm-charts/khaos --version v0.0.28 +``` + @@ -869,12 +878,12 @@ As of right now, the charts are put inside the `charts` folder and not published The `realease` pipeline sign the operator's *OCI image* with [cosign](https://docs.sigstore.dev/signing/quickstart/). In order to verify the signature, use the following command: ```console -cosign verify --key cosign/cosign.pub ghcr.io/stackzoo/khaos:0.0.27 +cosign verify --key cosign/cosign.pub ghcr.io/stackzoo/khaos:0.0.28 ``` Verification output: ```console -Verification for ghcr.io/stackzoo/khaos:0.0.27 -- +Verification for ghcr.io/stackzoo/khaos:0.0.28 -- The following checks were performed on each of these signatures: - The cosign claims were validated - Existence of the claims in the transparency log was verified offline diff --git a/SECURITY.md b/SECURITY.md index 5284f10..b24d086 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -6,8 +6,8 @@ The following versions are currently being supported with security updates. | Version | Supported | | ------- | ------------------ | -| 0.0.27 | :white_check_mark: | -| < 0.0.27 | :x: | +| 0.0.28 | :white_check_mark: | +| < 0.0.28 | :x: | ## Reporting a Vulnerability diff --git a/charts/khaos/values.yaml b/charts/khaos/values.yaml index ee06741..1cd0cd8 100644 --- a/charts/khaos/values.yaml +++ b/charts/khaos/values.yaml @@ -32,7 +32,7 @@ controllerManager: - ALL image: repository: ghcr.io/stackzoo/khaos - tag: 0.0.27 + tag: 0.0.28 resources: limits: cpu: 500m diff --git a/config/manager/kustomization.yaml b/config/manager/kustomization.yaml index 268307a..78be94c 100644 --- a/config/manager/kustomization.yaml +++ b/config/manager/kustomization.yaml @@ -5,4 +5,4 @@ kind: Kustomization images: - name: controller newName: ghcr.io/stackzoo/khaos - newTag: 0.0.27 + newTag: 0.0.28