Spike: Distro for radix

[emirgens]

Create a workflow for distribution of radix, include Radix-operator for the first iteration

DoD
Implement sample
Provide a workflow drawing (simple)

[Richard87]

Goals:

1. Good dev-experience
2. Easy to know versions being installed
3. Easy to manage across clusters
4. All versions should be SemVer with v prefix

Radix Helm Distribution

Main Chart starting point (example):

apiVersion: v2
name: app-distro
version: v1.0.0
dependencies:
  - name: radix-operator
    version: v1.0.0
  - name: radix-api
    version: v1.0.0
  - name: radix-web-console
    version: v1.0.0
  - name: radix-github-webhook
    version: v1.0.0

After Radix-API is updated with new tag v1.0.1

(Question, should we always update a patch/minor version when promoting from dev to QA, or should we use master/latest-timestamp?)

apiVersion: v2
name: app-distro
version: v1.0.1-rc.1 # prepare a new release candidate, could/should this be done by release-please?
dependencies:
  - name: radix-operator
    version: v1.0.0
  - name: radix-api
    version: v1.0.1 # bump radix-api
  - name: radix-web-console
    version: v1.0.0
  - name: radix-github-webhook
    version: v1.0.0

When QA is confirmed to be stable, relase a new version of Distro:

apiVersion: v2
name: app-distro
version: v1.1.0
dependencies:
  - name: radix-operator
    version: v1.0.0
  - name: radix-api
    version: v1.1.0
  - name: radix-web-console
    version: v1.0.0
  - name: radix-github-webhook
    version: v1.0.0

https://excalidraw.com/#json=JLJIC7H3CYmGk4X8vwqmu,92DfYDznO0UjwmIUo8mKNA

[emirgens]

Start with one component - radix-cicd-canary

• start using conventional commits
• in the future implement release please

New repo: radix-stack
Create Helm charts for applicable components