Release process enhancement #1185

didierofrivia · 2025-03-05T09:20:45Z

This PR introduces a new process for releasing the Kuadrant operator. It replaces the poorly documented manual way and the error prone automated workflow, by a new automated workflow and a well documented manual one. Both of the processes work around a new manifest named release.yaml, which is the source of truth for our kustomize configs, bundles and helm charts.

release.yaml file format.

This example of the release.yaml file uses tag v1.0.1 as reference.

# FILE: ./release.yaml
kuadrant-operator:
  version: "1.0.1"
olm:
  default-channel: "stable"
  channels:
    - "stable"
dependencies:
  authorino-operator: "0.16.0"
  console-plugin: "0.0.14"
  dns-operator: "0.12.0"
  limitador-operator: "0.12.1"
  wasm-shim: "0.8.1"

The kuadrant-operator section relates to the release version of the kuadrant operator.
While the olm section relates to fields required for building the olm catalogs.
And the dependencies section relates to the released versions of the subcomponents that will be included in a release.
There are validation steps during the make prepare-release that require the dependencies to be release before generating the release of the Kuadrant operator.

How to release Kuadrant Operator

To release a version “vX.Y.Z” of Kuadrant Operator in GitHub and Quay.io, there are two options, a manual and an automated process.
For both processes, first make sure every Kuadrant Operator dependency has been already released.

Automated Workflow

Run the GHA Automated Release
filling the following fields:
- gitRef: Select the branch/tag/commit where you want to cut a release from.
- kuadrantOperatorVersion: the Semantic Version of the desired release.
- authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)
- limitadorOperatorVersion: Limitador Operator bundle version (X.Y.Z)
- dnsOperatorVersion: DNS Operator bundle version (X.Y.Z)
- wasmShimVersion: WASM Shim version (X.Y.Z)
- consolePluginVersion: ConsolePlugin version (X.Y.Z)
- olmChannel: This will set the OLM channels and default-channel annotations
The workflow will create a Pull Request that should be peer-reviewed and approved by a member of the Kuadrant team, focusing on the changes made in Kustomize config, OLM bundles and Helm Charts.
Once the PR is merged, a release workflow will be triggered tagging and publishing the Github release
it will also build the images and packages and publish them on Quay, Helm repository.

Notes

It's not possible to cherry-pick commits, the workflow will pick a branch/tag/commit and all the history behind to the PR, any modifications should be done in the created PR.

Manual Workflow

Local steps

Create the release-vX.Y branch, if the branch does not already exist.
Push the release-vX.Y to the remote (kuadrant/kuadrant-operator)
Create the release-vX.Y.Z-rc(n) branch with release-vX.Y as the base.
Cherry-pick commits to the kudrant-vX.Y.Z-rc(n) from the relevant sources, i.e. main.
Update the applicable version in the release.yaml.
Run make prepare-release on the release-vX.Y.Z-rc(n). If you run into rate limit errors, set the env GITHUB_TOKEN with your PAT.

Remote steps

Open a PR against the release-vX.Y branch with the changes from release-vX.Y.Z-rc(n) branch.
PR verification checks will run.
Get manual review of PR with focus on changes in these areas:
- ./bundle.Dockerfile
- ./bundle
- ./config
- ./charts/
Merge PR
Run the Release Workflow on the release-vX.Y. This does the following:
- Creates the GitHub release
- Creates tags
Verify that the build release tag workflow is triggered and completes for the new tag.

TODO

Fix verifications #1197
Fix release operator workflow, removing needs directive from steps
alpha releases to check it works as expected
Fix creation of tag images for releases -> Fix image creation for tag push event #1212

Adjust the release document to suit the new release process. Signed-off-by: Jim Fitzpatrick <[email protected]>

From talks and calls, the release process has being moved to a more local process, less automated to allow for manual checks of the data before releasing. Signed-off-by: Jim Fitzpatrick <[email protected]>

- fix naming issue - refine process steps Signed-off-by: Jim Fitzpatrick <[email protected]>

The release script has being design to use a toml file for the version and is to be run locally. Signed-off-by: Jim Fitzpatrick <[email protected]>

Remove the reference to bundles from the format. It is suspected that the released version of the operator will never be different from the bundles. There is also an overlap with helm which does not have the concept of bundles. Signed-off-by: Jim Fitzpatrick <[email protected]>

The release workflow has being modified to only be triggered when a pull request is merged to branches that match `release-vX.Y`. The workflow will only make the GitHub release objects. Signed-off-by: Jim Fitzpatrick <[email protected]>

Set up a make target for verifying that the prepare-release target was ran, and there is no uncommitted changes. There has also being a workflow set up to run this check when a Pull Request is made against the release branches. Signed-off-by: Jim Fitzpatrick <[email protected]>

Slight change to the form that is being used. Signed-off-by: Jim Fitzpatrick <[email protected]>

[ci] Setting OLM channel depending on prerelease input [ci] Fixing yq cmd updating release.yaml [ci] Fixing branching, prepare release scripts and dependencies [ci] Creating CR release branch on `Create Pull Request` step * Running Create Pull Request only if not triggered by ACT * In order to set the desired channel and default channel * Changed consolePlugin default to `0.0.0` * Also descriptions of inputs to semver [ci] Updated sed command to also work with `+build` tags Signed-off-by: dd di cesare <[email protected]>

Signed-off-by: dd di cesare <[email protected]>

Refactor workflows to only use the verify-prepare-release target. This removed one of the workflows which was no longer required. Signed-off-by: Jim Fitzpatrick <[email protected]>

In the release.yaml 0.0.0 can now be used to mark a version should be the latest version. Signed-off-by: Jim Fitzpatrick <[email protected]>

codecov · 2025-03-07T14:29:14Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.46%. Comparing base (2ae754e) to head (7f7e8a5).
Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1185      +/-   ##
==========================================
+ Coverage   83.38%   83.46%   +0.07%     
==========================================
  Files          82       82              
  Lines        7120     7117       -3     
==========================================
+ Hits         5937     5940       +3     
+ Misses        949      946       -3     
+ Partials      234      231       -3

Flag	Coverage Δ
bare-k8s-integration	`23.65% <ø> (+0.23%)`	⬆️
controllers-integration	`74.09% <ø> (-0.19%)`	⬇️
envoygateway-integration	`41.30% <ø> (-0.34%)`	⬇️
gatewayapi-integration	`19.79% <ø> (-0.27%)`	⬇️
istio-integration	`44.11% <ø> (+0.08%)`	⬆️
unit	`19.08% <ø> (-0.01%)`	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
api/v1beta1 (u)	`90.78% <ø> (ø)`
api/v1beta2 (u)	`∅ <ø> (∅)`
pkg/common (u)	`∅ <ø> (∅)`
pkg/istio (u)	`62.06% <ø> (ø)`
pkg/log (u)	`93.18% <ø> (ø)`
pkg/reconcilers (u)	`24.50% <100.00%> (-0.18%)`	⬇️
pkg/rlptools (u)	`∅ <ø> (∅)`
controllers (i)	`86.55% <100.00%> (+0.02%)`	⬆️

see 9 files with indirect coverage changes

🚀 New features to boost your workflow:

❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Signed-off-by: dd di cesare <[email protected]>

* If it so, exit the release process Signed-off-by: dd di cesare <[email protected]>

* Until we have some scripts in that directory Signed-off-by: dd di cesare <[email protected]>

Signed-off-by: dd di cesare <[email protected]>

* In order to avoid rate limiting and empty json Signed-off-by: dd di cesare <[email protected]>

Signed-off-by: dd di cesare <[email protected]>

The workflow steps has no field needs Signed-off-by: Jim Fitzpatrick <[email protected]>

Set the commitish-target to the prerlease branch. The branch will be the in the following format: "release-vMAJOR.MINO" Signed-off-by: Jim Fitzpatrick <[email protected]>

Signed-off-by: dd di cesare <[email protected]>

* In order to be able to trigger other workflows with push tag Signed-off-by: dd di cesare <[email protected]>

* With some modifications. verify-manfiests calls the targets verify bundle, controller-gen and helm Signed-off-by: dd di cesare <[email protected]>

Signed-off-by: dd di cesare <[email protected]>

maleck13

These changes all look good.

/lgtm

eguzki · 2025-03-19T08:42:32Z

Let's 👁️ this.

Please, wait for my review before merging it

guicassolato · 2025-03-19T09:34:39Z

release.yaml

@@ -0,0 +1,14 @@
+kuadrant-operator:


I wonder if this file should be named something like release.yaml.tmpl or release.yaml.in in the main branch, and renamed/duplicated as release.yaml only in the release branches.

What would the advantage of doing that be?

Mainly communication, to call the file for what it is. This file should only exist in release branches. The only meaning it has in main is as a template.

Plus, we don't want people modifying and committing this file in main. Some distraction and it may end up with some of values set something other than 0.0.0, which is ugly, to say the least.

I would not say it should only exist on release branches, there are possible advantages to how the nightly pipelines could make use of the file. None of that work has being done as of yet. There is also a hope to get make local-setup to be able to consume that file, so it is not truly about releases.

guicassolato · 2025-03-19T09:43:08Z

utils/release/release.sh

+
+    log "RUNNING: $dir_name"
+
+    tasks=($(find "$script_dir/$dir_name" -mindepth 1 -maxdepth 1 -perm -001 | sort))


Should the names of the task files be prefixed with an ordering number (e.g.: 1-verify_dependencies.sh, 2-verify_release_file.sh, ...)?

This is something that can be done if there is a required order that the scripts most proceed as. For now there is no hard requirement on the ordering. While it is not requirement lets not introduce a number schema to maintain.

Why sort then? Deterministic output?

Good question. Initial the order did matter, and there was numbering prefixes. This is something could be removed, but I currently don't see the harm in having it there. The deterministic output is a nice side affect. I don't think there is a need for a change here. More of an understanding of what is happening.

eguzki · 2025-03-19T09:46:18Z

.github/workflows/test.yaml

-  verify-bundle:
-    name: Verify bundle
-    if: needs.pre-job.outputs.should_skip != 'true'
+  verify-manifests:


I think it is better to have N verify jobs. Two reasons:

the UX is better in Github. You know very quickly what failed

Each tests is run in isolation: one test cannot interfere the other test. For instance, make bundle could be changing files from helm charts and the helm charts test could be failing due to bundle test. Test isolation is always a desired property.

I am not sure I fully agree with the each test running in isolation. There is a strong interaction between the bundles and helm charts when it comes to releasing. Would see this test more of an integration test over a unit test. When the make prepare-release would resolve both issue I don't see the need to have them split.

You might know very quickly what failed, but does that tell you as quickly how to fix it. I also think the make target in the test should not be used, but instead use make verify-prepare-release.

The source of truth is in golang code and /config plus few other places like Makefile. Those are verification steps to make sure the source of truth is consistent with the shipped manifests (bundle or helm charts). So, IMO, independent and isolated tests are good to have. I can live without it as well.

In the future, the Makefile will no longer be a source of truth.. it will be replaced by release.yaml. Because now there are two ways to generate the manifests and eventually we need to merge into one.

Agreed eventually it needs to merge into one. The next step on the road I see is how the nightly test pipeline generate their builds.

guicassolato · 2025-03-19T09:51:01Z

utils/release/dependencies/dependencies-manifests.sh

+dns_version=$(mod_version $(yq '.dependencies.dns-operator' $env/release.yaml))
+limitador_version=$(mod_version $(yq '.dependencies.limitador-operator' $env/release.yaml))
+
+AUTHORINO_OPERATOR_GITREF=$authorino_version envsubst < $env/config/dependencies/authorino/kustomization.template.yaml > $env/config/dependencies/authorino/kustomization.yaml


I see env is being set at utils/release/release.sh:49. Should we add a default value for it to the project dir at the beginning of each task script file?

I'm afraid one who inadvertently tries to run one of these script files locally, individually, i.e. without the initialisation by release.sh, could accidentally target /config/….

I would not be in favor of setting a default value. However I can see your point about accidentally targetting /config/..., would a early error termination of the script solve the issue in a satisfactory manner?

would a early error termination of the script solve the issue in a satisfactory manner?

I don't think it's enough. /config was just an example. This is a problem that affects all scripts, not just this one. Imagine if it was referring to /bin.

I think we can come up with plenty of other examples where this can go wrong, even if it doesn't fail with an error.

So then I am hear that for now the best step forward is to document the use of the release.sh.

I think the best step is to set a default.

For now this is a low risk issue. We can iterate on the problem. The scope of the PR has already blow out of scale. The issue #1219 is the follow up issue for this. I think that is where we should describe the change what wanted to be seen in an iteration.

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

Makefile: Release section

eguzki

Looking good

eguzki · 2025-03-19T11:19:01Z

RELEASE.md

+   filling the following fields:
+   - gitRef: Select the branch/tag/commit where you want to cut a release from.
+   - kuadrantOperatorVersion: the [Semantic Version](https://semver.org/) of the desired release.
+   - authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)


Suggested change

- authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)

- authorinoOperatorVersion: Authorino Operator version (X.Y.Z)

eguzki · 2025-03-19T11:19:14Z

RELEASE.md

+   - gitRef: Select the branch/tag/commit where you want to cut a release from.
+   - kuadrantOperatorVersion: the [Semantic Version](https://semver.org/) of the desired release.
+   - authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)
+   - limitadorOperatorVersion: Limitador Operator bundle version (X.Y.Z)


Suggested change

- limitadorOperatorVersion: Limitador Operator bundle version (X.Y.Z)

- limitadorOperatorVersion: Limitador Operator version (X.Y.Z)

eguzki · 2025-03-19T11:19:22Z

RELEASE.md

+   - kuadrantOperatorVersion: the [Semantic Version](https://semver.org/) of the desired release.
+   - authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)
+   - limitadorOperatorVersion: Limitador Operator bundle version (X.Y.Z)
+   - dnsOperatorVersion: DNS Operator bundle version (X.Y.Z)


Suggested change

- dnsOperatorVersion: DNS Operator bundle version (X.Y.Z)

- dnsOperatorVersion: DNS Operator version (X.Y.Z)

eguzki · 2025-03-19T11:21:31Z

RELEASE.md

+   - dnsOperatorVersion: DNS Operator bundle version (X.Y.Z)
+   - wasmShimVersion: WASM Shim version (X.Y.Z)
+   - consolePluginVersion: ConsolePlugin version (X.Y.Z)
+   - olmChannel: This will set the OLM `channels` and `default-channel` annotations


good enough for now.

While channel is mandatory setting for a bundle, default channel is not. The default values if not set on the workflow form should be:

channel: stable (or whatever is in the workspace)

default-channel: not set.

Good thing is that we can modify that on the actual PR, so there's nothing committed

averevki · 2025-03-19T16:50:34Z

utils/release/load_github_envvar.sh

+
+releaseBody="**This release enables installations of Authorino Operator v$authorinoOperatorVersion, Limitador Operator v$limitadorOperatorVersion, DNS Operator v$dnsOperatorVersion, WASM Shim v$wasmShimVersion and ConsolePlugin $consolePluginURL**"
+
+kuadratantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"


Suggested change

kuadratantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"

kuadrantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"

averevki · 2025-03-19T18:20:21Z

RELEASE.md

+1. Create the `release-vX.Y` branch, if the branch does not already exist. 
+2. Push the `release-vX.Y` to the remote (kuadrant/kuadrant-operator)
+3. Create the `release-vX.Y.Z-rc(n)` branch with `release-vX.Y` as the base.
+4. Cherry-pick commits to the `kudrant-vX.Y.Z-rc(n)` from the relevant sources, i.e. `main`.
+5. Update the applicable version in the [release.yaml](https://github.com/Kuadrant/kuadrant-operator/blob/main/RELEASE.md#release-file-format).


Why merge -rc branches into release-vX.Y ones instead of just building directly from release-vX.Y.Z named branches? Patch releases checkpoints will be saved inside x.y.z branches, and you won't need to do some extra steps and checks during this release process.
But I guess you'll need to sync minor release branch after each patch release instead. Or if you don't care at all about saving patch releases? This flow makes more sense to me though

eguzki

Image building is broken.

The image building system is implemented in .github/workflows/build-images-for-tag-release.yaml. This workflow still assumes the existence of release.mk file, which no longer exists. So Image build fails. One example run failing: https://github.com/Kuadrant/kuadrant-operator/actions/runs/13954148232/job/39060935703

I (tried to) fix it partially in #1223. But the catalog and bundle build is very likely to fail as well.

I can open another PR with the fix for the bundle and catalog builds or leave someone else to do this.

Add note on release note generation failure. Signed-off-by: Jim Fitzpatrick <[email protected]>

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

prepare-release: make default-channel optional

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

workflows/build-images-for-tag-release.yaml: fix operator image build

Boomatang and others added 14 commits March 3, 2025 15:56

UPDATE: Release Document

dfd3b7e

Adjust the release document to suit the new release process. Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: Release Process

8357a84

From talks and calls, the release process has being moved to a more local process, less automated to allow for manual checks of the data before releasing. Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: Release doc

985d410

- fix naming issue - refine process steps Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: RELEASE SCRIPT

5e0750b

The release script has being design to use a toml file for the version and is to be run locally. Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: release workflow

6c739a2

The release workflow has being modified to only be triggered when a pull request is merged to branches that match `release-vX.Y`. The workflow will only make the GitHub release objects. Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: Format release.toml

b0a573a

Slight change to the form that is being used. Signed-off-by: Jim Fitzpatrick <[email protected]>

[docs] Updating RELEASE.md including automated release

e35af00

Signed-off-by: dd di cesare <[email protected]>

[ci] Setting upstream origin for new release base branch

f15705f

Signed-off-by: dd di cesare <[email protected]>

[ci] Changed GH token

87afd8f

Signed-off-by: dd di cesare <[email protected]>

UPDATE: GitHub workflows

05147ad

Refactor workflows to only use the verify-prepare-release target. This removed one of the workflows which was no longer required. Signed-off-by: Jim Fitzpatrick <[email protected]>

UPDATE: Latest tag

7f7e8a5

In the release.yaml 0.0.0 can now be used to mark a version should be the latest version. Signed-off-by: Jim Fitzpatrick <[email protected]>

didierofrivia and others added 15 commits March 10, 2025 17:19

[refactor] DRYing release script

fc73c9b

Signed-off-by: dd di cesare <[email protected]>

[script] Checking if operator tag is already released

24f3786

* If it so, exit the release process Signed-off-by: dd di cesare <[email protected]>

[script] post-validation phase removed from main execution

9c7a3c8

* Until we have some scripts in that directory Signed-off-by: dd di cesare <[email protected]>

[refactor] Renaming verify tag script

04a4a4a

Signed-off-by: dd di cesare <[email protected]>

[refactor] Using authenticated request and json verification

6d806cd

* In order to avoid rate limiting and empty json Signed-off-by: dd di cesare <[email protected]>

[ci] Verifying if dependencies have been already released

e6a11f6

Signed-off-by: dd di cesare <[email protected]>

[ci] Calling make prepare-release with a GITHUB_TOKEN

2ae0a67

Signed-off-by: dd di cesare <[email protected]>

[docs] Updated release docs mentioning rate limiting and GITHUB_TOKEN

facf451

Signed-off-by: dd di cesare <[email protected]>

[script] Conditionally adding auth header

44c15f3

Signed-off-by: dd di cesare <[email protected]>

[script] Adding semver validation and 0.0.0 check

763f29b

Signed-off-by: dd di cesare <[email protected]>

[ci] Fix create release by creating tag before

9241456

Signed-off-by: dd di cesare <[email protected]>

FIX: Workflow steps

ca5ffa6

The workflow steps has no field needs Signed-off-by: Jim Fitzpatrick <[email protected]>

FIX: commitish-taraget

d985f86

Set the commitish-target to the prerlease branch. The branch will be the in the following format: "release-vMAJOR.MINO" Signed-off-by: Jim Fitzpatrick <[email protected]>

[ci] Adding workflow_dispatch event trigger

423518a

Signed-off-by: dd di cesare <[email protected]>

[ci] Checkout code with kuadrant PAT

acdce88

* In order to be able to trigger other workflows with push tag Signed-off-by: dd di cesare <[email protected]>

didierofrivia added 2 commits March 18, 2025 14:19

[make] Restore original verification targets

140b5ce

* With some modifications. verify-manfiests calls the targets verify bundle, controller-gen and helm Signed-off-by: dd di cesare <[email protected]>

[ci] Conditionally triggering verification of release manifests

9ce6e67

Signed-off-by: dd di cesare <[email protected]>

didierofrivia marked this pull request as ready for review March 18, 2025 14:20

didierofrivia requested a review from a team as a code owner March 18, 2025 14:20

didierofrivia added the kind/enhancement New feature or request label Mar 18, 2025

didierofrivia requested a review from a team March 18, 2025 14:33

didierofrivia assigned didierofrivia and Boomatang Mar 18, 2025

maleck13 previously approved these changes Mar 19, 2025

View reviewed changes

guicassolato reviewed Mar 19, 2025

View reviewed changes

eguzki reviewed Mar 19, 2025

View reviewed changes

guicassolato reviewed Mar 19, 2025

View reviewed changes

eguzki added 2 commits March 19, 2025 10:55

Makefile: Release section

84f35fc

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

Merge pull request #1216 from Kuadrant/improve-makefile

ad59558

Makefile: Release section

eguzki dismissed maleck13’s stale review via ad59558 March 19, 2025 10:58

eguzki reviewed Mar 19, 2025

View reviewed changes

averevki reviewed Mar 19, 2025

View reviewed changes

eguzki requested changes Mar 19, 2025

View reviewed changes

Boomatang and others added 6 commits March 20, 2025 10:29

UPDATE: Release Doc

04e933f

Add note on release note generation failure. Signed-off-by: Jim Fitzpatrick <[email protected]>

prepare-release: make default-channel optional

e44d899

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

release: post-validation of the OLM default channel

9067fca

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

Merge pull request #1217 from Kuadrant/make-default-channel-optional

f514fec

prepare-release: make default-channel optional

workflows/build-images-for-tag-release.yaml: fix operator image build

2c633ac

Signed-off-by: Eguzki Astiz Lezaun <[email protected]>

Merge pull request #1223 from Kuadrant/fix-build-images-workflow

521e80e

workflows/build-images-for-tag-release.yaml: fix operator image build

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Release process enhancement #1185

Release process enhancement #1185

didierofrivia commented Mar 5, 2025 •

edited

Loading

codecov bot commented Mar 7, 2025 •

edited

Loading

maleck13 left a comment

eguzki commented Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

eguzki Mar 19, 2025

Boomatang Mar 19, 2025

eguzki Mar 19, 2025

eguzki Mar 19, 2025

Boomatang Mar 21, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 19, 2025

Boomatang Mar 19, 2025

guicassolato Mar 19, 2025

Boomatang Mar 21, 2025

eguzki left a comment

eguzki Mar 19, 2025

eguzki Mar 19, 2025

eguzki Mar 19, 2025

eguzki Mar 19, 2025

didierofrivia Mar 19, 2025

averevki Mar 19, 2025

averevki Mar 19, 2025

eguzki left a comment


		log "RUNNING: $dir_name"

		tasks=($(find "$script_dir/$dir_name" -mindepth 1 -maxdepth 1 -perm -001 \| sort))

	- authorinoOperatorVersion: Authorino Operator bundle version (X.Y.Z)
	- authorinoOperatorVersion: Authorino Operator version (X.Y.Z)

	- limitadorOperatorVersion: Limitador Operator bundle version (X.Y.Z)
	- limitadorOperatorVersion: Limitador Operator version (X.Y.Z)

	- dnsOperatorVersion: DNS Operator bundle version (X.Y.Z)
	- dnsOperatorVersion: DNS Operator version (X.Y.Z)


		releaseBody="This release enables installations of Authorino Operator v$authorinoOperatorVersion, Limitador Operator v$limitadorOperatorVersion, DNS Operator v$dnsOperatorVersion, WASM Shim v$wasmShimVersion and ConsolePlugin $consolePluginURL"

		kuadratantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"

	kuadratantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"
	kuadrantOperatorTag="v$(yq '.kuadrant-operator.version' $ROOT/release.yaml)"

Release process enhancement #1185

Are you sure you want to change the base?

Release process enhancement #1185

Conversation

didierofrivia commented Mar 5, 2025 • edited Loading

release.yaml file format.

How to release Kuadrant Operator

Automated Workflow

Notes

Manual Workflow

Local steps

Remote steps

TODO

codecov bot commented Mar 7, 2025 • edited Loading

Codecov Report

maleck13 left a comment

Choose a reason for hiding this comment

eguzki commented Mar 19, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

eguzki left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

eguzki left a comment

Choose a reason for hiding this comment

didierofrivia commented Mar 5, 2025 •

edited

Loading

codecov bot commented Mar 7, 2025 •

edited

Loading