Skip to content

Commit

Permalink
[wip][rfc] Guide-level explanation: Current Process intro
Browse files Browse the repository at this point in the history
  • Loading branch information
didierofrivia committed Dec 5, 2023
1 parent 925aa13 commit ba3d704
Showing 1 changed file with 16 additions and 0 deletions.
16 changes: 16 additions & 0 deletions rfcs/0000-kuadrant-ci-cd.md
Original file line number Diff line number Diff line change
Expand Up @@ -299,6 +299,22 @@ exposed in the auto generated description of the PR.

</details>

## 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

Expand Down

0 comments on commit ba3d704

Please sign in to comment.