Feature 157 (#51)

* Argo CD confirmed as replacing Spinnaker eligible tool fo CD

* Lettuce core version patching for cause of detected vulnerability about < 6.5.1 release

demonstrators-line/demonstrator-v0/pom.xml

@@ -2,7 +2,7 @@
 	<modelVersion>4.0.0</modelVersion>
 	<groupId>org.cybnity</groupId>
 	<artifactId>techstack</artifactId>
-	<version>0.38.0</version>
+	<version>0.39.0</version>
 	<packaging>pom</packaging>
 	<name>CYBNITY Official Standard Techstack</name>
 
@@ -234,7 +234,7 @@
 			<dependency>
 				<groupId>io.lettuce</groupId>
 				<artifactId>lettuce-core</artifactId>
-				<version>[6.2.0.RELEASE,)</version>
+				<version>[6.5.1.RELEASE,)</version>
 			</dependency>
 			<dependency>
 				<groupId>com.fasterxml.jackson</groupId>

demonstrators-line/demonstrator-v0/sample-project-pom.xml

@@ -3,7 +3,7 @@
 	<parent>
 		<groupId>org.cybnity</groupId>
 		<artifactId>techstack</artifactId>
-		<version>0.38.0</version>
+		<version>0.39.0</version>
 	</parent>
 
 	<groupId>org.cybnity.techstack.quality</groupId>

demonstrators-line/demonstrator-v0/technologies-stack-analysis.md

@@ -178,7 +178,7 @@ The current status of technology already in the analysis stream give a general v
 | BUILD TOOL | Component Features Specification & Automated Testing | [Concordion](https://concordion.org/tutorial/java/markdown/) | `WIN` | | | Creation of living documentation (documenting, instrumenting, coding) regarding software features via a Behavior-Driven Design approach (specification of features and behavior scenario via markdown in files, instrumentation/automation of test case via Java fixture codes, and tests execution under JUnit via gradlew and/or IDE) allowing features development/maintenance through Test-Driven Design practices for system components features (e.g processes, feature unit test, integration test) |
 | BUILD TOOL | UI Features Automated Testing | [Cypress](https://www.cypress.io/features) | `WIN` | | | All-in-one testing framework, assertion library, with mocking and stubbing, all without Selenium installation. End-to-end testing of web UI features |
 | BUILD TOOL | Components Builder | [Maven](https://maven.apache.org/) | `WIN` | `WIN` | `WIN` | Build binaries (e.g application components) from VCS, install into local repository, and deploy to Artifacts Repository |
-| BUILD TOOL | Infrastructure-As-Code (IaC) | [Terraform](https://www.terraform.io/) | `WIN` | `WIN` | `X` | Provisioning management of networking, load balancer, database, users, permissions... and Kubernetes cluster (orchestration management); integration via providers (e.g OVH Cloud), with Docker (server templating) and Helm (configuration management as repeatable application installer), with Spinnaker (assembly and installation management) |
+| BUILD TOOL | Infrastructure-As-Code (IaC) | [Terraform](https://www.terraform.io/) | `WIN` | `WIN` | `X` | Provisioning management of networking, load balancer, database, users, permissions... and Kubernetes cluster (orchestration management); integration via providers (e.g OVH Cloud), with Docker (server templating) and Helm (configuration management as repeatable application installer), with Argo CD (assembly and installation management) |
 | BUILD TOOL | Components Builder | [Node.js & NPM](https://nodejs.org/en/) | `WIN` | `WIN` | `WIN` | JavaScript runtime built on Chrome's V8 JS engine for development/test of ReactJS application (e.g frontend web server components) |
 | BUILD TOOL | System Docker Images Builder | [Docker](https://www.docker.com/) | `WIN` | | | Build immutable containerized systems (e.g docker image template of packaged system ready for run), push and tag images into System Images Repository |
 | BUILD TOOL | Version Control System (VCS) | [GitHub](https://github.com/) Repository | `WIN` | | | Source codes repository with versioning management (e.g branches, tags, code reviews) |
@@ -196,7 +196,8 @@ The current status of technology already in the analysis stream give a general v
 | DELIVERY TOOL | System Images Repository | [GitHub Container](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry) Registry | `WIN` | | | Hosting and management of Docker images and tagged versions |
 | DELIVERY TOOL | System Images Repository | [DockerHub](https://hub.docker.com/) Registry | `ALT` | | | Hosting and management of Docker images and tagged versions |
 | DELIVERY TOOL | Infrastructure & Resources Configuration | [Helm](https://helm.sh/) | `WIN` | | | Configuration of systems' resources, logs, forwarding ports of Docker image, Kubernetes objects (e.g baseline/live replica cluster allowing pre-prod dress rehearsal, canary cluster for code changed and rollout with automated recovery, production/live cluster) supporting environments/infrastructures deployment |
-| DELIVERY TOOL | Continuous Delivery Orchestrator | [Spinnaker](https://spinnaker.io/) | `WIN` | | | Deploy systems versions via deployment pipeline (e.g staging environment, Canary strategy to Live/Production), and release platform changed versions to infrastructures (e.g environments templates defined by Helm chart manifests, red/black rollout strategy); [Spinnaker in Kubernetes Cluster](https://www.weave.works/blog/a-guide-on-the-installation-of-spinnaker-in-kubernetes-clusters) |
+| DELIVERY TOOL | Continuous Delivery Orchestrator | [Spinnaker](https://spinnaker.io/) | `ALT` | | | [Spinnaker in Kubernetes Cluster](https://www.weave.works/blog/a-guide-on-the-installation-of-spinnaker-in-kubernetes-clusters) |
+| DELIVERY TOOL | Continuous Delivery Orchestrator | [Argo CD](https://argoproj.github.io/cd/) | `WIN` | | | Deploy systems versions via deployment pipeline (e.g staging environment, Canary strategy to Live/Production), and release platform changed versions to infrastructures (e.g environments templates defined by Helm chart manifests, red/black rollout strategy) |
 | DELIVERY TOOL | Continuous Delivery Orchestrator | [HashiCorp Waypoint](https://www.waypointproject.io/) | `X` | | | Build, deploy, release and publish Dockerized systems images on Kubernetes infrastructure |
 | OPERATING INFRASTRUCTURE | Infra-As-Code Execution | [Kubernetes](https://kubernetes.io/) | `WIN` | | | Automated deployment, scaling and management of containerized systems and applications; [Firewall for application in Kubernetes](https://itnext.io/firewall-for-applications-in-kubernetes-af0acbe337da); [best practices for Kubernetes security](https://www.aquasec.com/cloud-native-academy/kubernetes-in-production/kubernetes-security-best-practices-10-steps-to-securing-k8s/) |
 | OPERATING INFRASTRUCTURE | Infra-As-Code Execution | [MicroK8s](https://microk8s.io/) | `WIN` | | | Pure-upstream Kubernetes for developer workstation to production |
@@ -339,6 +340,7 @@ The acceptance level per differentiation criteria is evaluated as:
 | Terraform | | | | | | | |
 | MicroK8s | | | | | | | |
 | Kubernetes | | | | | | | |
+| Spinnaker |KO| | | | | |Partial installation with success, but lot of blocking points for integration with storage system (S3 MinIO) and no access to final operational status in K8S (RKE 2)|
 
 ## STEP 3 - Arbitration of the retained technologies set
 During this step, the final selection of the solutions set is performed between the accepted ideal or alternative eligible technologies.

demonstrators-line/demonstrator-v0/v0-technologies-stack.md

@@ -68,8 +68,8 @@ Should allow definition and test of basic software factory implementation allowi
 None supervision requirements required regarding the step of the CYBNITY Foundation project.
 
 # CURRENT MPP OFFICIAL VERSION
-- Version: 0.38.0
-- Released at: August, 29, 2024
+- Version: 0.39.0
+- Released at: December, 26, 2024
 - Status: `RELEASED`
 - Documentation: [technologies-stack-analysis](technologies-stack-analysis.md)
 - Deliverables:
@@ -80,7 +80,7 @@ None supervision requirements required regarding the step of the CYBNITY Foundat
     <parent>
       <groupId>org.cybnity</groupId>
       <artifactId>techstack</artifactId>
-      <version>0.38.0</version>
+      <version>0.39.0</version>
     </parent>
 
     <repositories>