From ba3d704e22fac887b8345f7cd5b72d494cae0340 Mon Sep 17 00:00:00 2001 From: dd di cesare Date: Tue, 5 Dec 2023 11:10:18 +0100 Subject: [PATCH] [wip][rfc] Guide-level explanation: Current Process intro --- rfcs/0000-kuadrant-ci-cd.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/rfcs/0000-kuadrant-ci-cd.md b/rfcs/0000-kuadrant-ci-cd.md index cc3237eb..c3581465 100644 --- a/rfcs/0000-kuadrant-ci-cd.md +++ b/rfcs/0000-kuadrant-ci-cd.md @@ -299,6 +299,22 @@ exposed in the auto generated description of the PR. +## New process +The new process ideally should be as simple as possible, and should be able to be triggered by any person, process and +set of events (particular commits, tags, merge, etc) that needs the artifacts. It also should be able to be repeated +in a consistent way and without the need of any human setting variables or parameters at the time of triggering it +(at least for the most common cases). + +Given our current process, we can identify some similarities and particularities between the different components: + +* All of them are built using a CI/CD tool (GitHub Actions) and published to a container registry (quay.io). +* Not all of them are built using the same build system (Cargo, Go, Operator SDK, etc.). +* 3 of them follow the Operator Pattern and are built using the Operator SDK (Authorino, Limitador and Kuadrant operators). +* 2 of them are Rust projects (Limitador and WASMShim). +* There's a dependency between the different components, Kuadrant Operator depends on Authorino and Limitador Operators, +and the WasmShim; while the before mentioned operators depend on their operands (Authorino and Limitador). + + # Reference-level explanation [reference-level-explanation]: #reference-level-explanation