Architecture on Software Factory

ADR

Mon, 01 Jan 0001 00:00:00 +0000

You find here the detailed architecture decision record that references in the TASD .

For information part of theses decision are logged in Lewis Craftsmanship archi decisions list .

ADR001: From services to product to deploy services

Status: Accepted in September 2022

Creation of sf-package in September 2022
Recorded in [SWF organization] in April 2023

Context

Software Factory services available on TDP C2, TDP C3, RTDP.
Code for TDP C2 & TDP C3 + platform is similar (pipeline, terraform for IaaS, helm + kubectl for Kubernetes) but not in only one code base.
Need to merge our different repos.
Need to deploy a Software Factory on CASTLE.
Plan to deploy Country Eyes Only Software Factories.

Decision

New deliverable: a product.
Deploy and update CASTLE with the product (1rst deployment in March 2023).
In the mid/long term, platform TDP C2 & C3 will migrate to the product delivery.
Keep in mind that RTDP is currently directly deployed on a VM and will not be compatible with the product.

Consequences

Put in place Smart Delivery team that will manage the product.

ADR002: Deploy using Flux

Status: Accepted in January 2023

Context

Software Factory product launch.
Deploying SF on TDP C2 & TDP C3-CA with pipelines & runners.
DevOps mode.
Analysis on different deployment mode (DevOps with pipeline, GitOps with Flux / with ArgoCD) + POC.
Pipeline require credential to be external of the Kubernetes Cluster.
Flux deploy and update using one source of trust, and store internally secrets.
GitLab choose Flux.

Decision

Use Flux.

Consequences

Refactor POC to become the product.

ADR003: Add components Black Duck and Synopsys Alert

Status: Accepted in June 2024

SWaaP in EA