Use ArgoCD to quickly bootstrap kubernetes cluster from scratch.

Acceptance criteria:

• EDP user can use pre-defined structure in edp-install as a baseline for cluster deployment;
• For each engagement user can use this structure as baseline for new cluster provisioning;
• ArgoCD is used to deploy all tools on the cluster;
• Deploy new cluster and apply addons approach to ensure cluster has all the required capabilities and EDP as well

• Add new kind: Infrastructure with:
• • build-tool: terraform
• • lang: terraform
• • framework: infraspace
• Added support for Clone, Create, Import strategy
• Do not push deployment and Sonar Templates
• Create templates for "create" application (see details below)
• For CI pipelines:
• • CodeReview: run helm lint, helm docs, helm fmt
• • BuildPipeline: run helm lint, helm docs, helm fmt
• Add UI part

Currently EDP provide template for keycloak-operator - https://github.com/epam/edp-keycloak-operator/issues/new/choose

Lets add templates for all repositories this simplifies the creation of typical requests to the GitHub repositories

Acceptance Criteria:

• each EDP repositories contain GitHub open-source templates;

In the new release, I would like to see the following key features:

• New Headlamp UI Application onboarding dialog;
• Enable Autotest as Quality Gate for CD pipeline;
• Add helm application type support to deploy and manage dependencies, add support infrastructure codebase type to manage infrastructure, Vue, Angular and Express frameworks for JavaScript and Gin framework for Go;
• Add Java Multi-Module Support for Tekton;
• Enable autodeploy feature for Tekton deploy scenario;
• Feature to manually trigger codereview pipeline;

Enable logic to provide autodeploy approach in Argo CD deploy scenario.

Each time when Build pipeline update CodebaseImageStream Custom Resource - define latest artifact tag and upgrade this service on each environment, where this service deployed.

In Headlamp UI in CD pipeline create dialog enable functional to create env with auto deploy approach.

EDP currently uses alpine version 3.16.4 as the base image for its components, since there is already a more up-to-date version with many fixes, let's update to it - 3.18.0.

Acceptance Criteria:

• each EDP component use alpine:3.18.0 as base image;

Could you please describe main approach how EDP team recommends index rotation for opensearch.

Acceptance Criteria:

EDP documentation contain article of how EDP team recommends index rotation for opensearch;

Acceptance Criteria:

• user can disable default SonarQube and integrate with third-party SonarQube;
• user can create custom secret for integration EDP with SonarQube;
• EDP supports integration with custom SonarQube, a valid link in the EDP component, in Headlamp, Tekton pipelines are adapted to work with custom SonarQube;
• provide mk-docs (https://epam.github.io/edp-install/) tutorial of automate integration;

Acceptance Criteria:

• User can provide credentials of private registry into any CD namespace.

Keycloak operator provides capabilities to automate integration with AWS EKS. Let’s redesign approach to integrate AWS EKS with Keycloak as identity provider.

Enable flag to integrate Keycloak with AWS EKS.

Automate:

• keycloak client;
• keycloak scope;
• mappers;
• groups
• assign to groups;
• • align Headlamp integration as well;
• align documentation

It would be nice to be able to onboard the next js framework for JavaScript as part of the EDP platform - https://nextjs.org/

Acceptance Criteria:

• Update Headlamp UI to add oppotrunity to set nextjs framework for JavaScript;
• Enable 'create' strategy for this application type;
• Align Tekton Pipelines;
• Update mkdocs documentation - https://epam.github.io/edp-install/;

• Create and send newsletter
• Update Releases.md file
• Update SolutionsHub
• Update Medium

Acceptance Criteria:

• EDP use OKD 4.12 to verify platform capabilities;
• update mkdocs page - https://epam.github.io/edp-install/supported-versions/?h=suppo

The current functionality of the platform does not allow a simple way to restart the pipeline review if necessary.
Add functionality that allows you to provoke the launch of a pipeline review with a specific comment in a merge request review

Acceptance Criteria:

• EDP user can trigger code review pipeline in manually mode;
• comment '/recheck' in PR is the way that user can run code-review pipeline;

Provide the ability to deploy additional services with the main applications as dependencies.
Provide base CI for helm charts, thus allowing user to select a service in the CD pipeline.

Acceptance Criteria:

• user can add codebases type helm via Headlamp;
• language: helm framework: helm and build tool: helm;
• create repo for create strategy;
• Tekton CI/CD (add review and build pipelines) pipelines available for helm charts;
• check deploy functional (user can add services and deploy as dependency for application);
• check EDP and default versioning approaches;
• publish helm chart with appropriate version to registry;
• add repos with tests sources to github and gitlab for import strategy;
• describe usage in documentation (https://epam.github.io/edp-install/);

As a test template, use the PostgreSQL DB or any other.

Acceptance Criteria:

• EDP user can use proxy to hide Tekton dashboard on OKD cluster;

Migrated to configuration section https://epam.github.io/edp-install/operator-guide/install-defectdojo/?h=defe#configuration

Acceptance Criteria:

• mkdocs contain valid information how to integrate EDP with DefectDojo (secret provisioning);

Acceptance Criteria:

• EDP 3.4.1 released and available for deployment;
• installation documentation is aligned according to LTS version;
• all subcomponents are also released;
• RELEASES.md aligned;
• changelog updated;

Acceptance Criteria:

• user can integrate EDP with different clusters;
• mkdocs contain article of how to use this feature;
• user can deploy each CD pipeline stage to different clusters;
• add 'clusters' section in Headlamp UI;
• provide opportunity to add new cluster;
• each EDP tenant must be deployed with Argo CD;
• align with current RBAC model;
• Argo CD mandatory parameter by default;
• git servers must be automatically integrated with Argo CD; (codeabsae-operator logic)
• user can be add new cluster via Argo CD or Headlamp UI;
• align mkdocs;
• ** align autotest run;
• ** align custom CG run;
• ** align custom logic run on CD part;

Acceptance Criteria:

• deploy Vault as EDP subcomponent;
• use SSO approach for Vault;
• use Vault for EDP microservices only;
• describe how to manage other secrets;

Do not install perf operator within EDP as well as remove dependency on perf CRDs

Acceptance criteria:

• edp-install do not contain dependency for perf-operator deployment;
• EDP can be deployed on empty cluster without perf-operator;

Main information available: https://gin-gonic.com/

Language: Go
Framework: Gin
Buildtool: Go

Acceptance Criteria:

• user can onboard Gin Go framework on EDP platform;
• documentation updated;
• Tekton pipelines implemented;
• Headlamp UI updated;
• base CI/CD way implemented out of the box;

Acceptance Criteria:

• mkdocs contain article of how to install upgrade for EDP to 3.2.1 version (use example https://epam.github.io/edp-install/operator-guide/upgrade-edp-3.1/);
• verify documentation and all manual actions during upgrade procedure;

Acceptance Criteria:

• mkdocs contain page of how integrate EDP solution with shared Sonar (manage secret, EDP Portal UI);

Acceptance Criteria:

• DD can be integrated with Keycloak by keycloak-operator;
• upstream addons repo contain templates to enable integration;

Please align use-case according new Headlamp UI.

Acceptance Criteria:

• use-case aligned with latest Headlamp UI functional;
• Video aligned and uploaded to YouTube;
• use GitHub as VCS;

EDP provide External Secret operator capabilities usage.

During EDP deployment user can provisioning EDP secrets by External Secret operator but in EDP documentation not present any examples of EDP secret structure.

Acceptance Criteria:

• mkdocs (https://epam.github.io/edp-install/) contain example of Parameter Store EDP secret creation;

Please collect the info for the Use Cases block in the SolutionsHub page.

Useful:

• Use cases sample from another product - https://solutionshub.epam.com/solution/deps
• our EDP page - https://solutionshub.epam.com/solution/epam-delivery-platform
• our use cases - https://epam.github.io/edp-install/use-cases/
• email thread - RE: [EPMD-EDP][SolutionsHub] Add Use Cases Section
• update features block
• update technical req
• update INTEGRATES with

benefits:

• opensource;
• mkdocs framework (perfect docs)
• maybe active community

In the current deployment scenario, the deployment of the ArgoCD component is used to provide functionality for the deployment of services, with this approach, a centralized ArgoCD with cluster admin permissions is used, this may not be available for part of the deployment scenarios and project requirements, it would be nice to be able to deploy ArgoCD as a subcomponent of the platform with the appropriate RBAC.

In addition, it would be nice to automate some of the integrations, such as integration with Keycloak for SSO access and integration with git servers out of the box.

Acceptance Criteria:

• edp-install contain ArgoCD as dependency;
• Argo CD deployed in namespace wide mode;
• automate EDP+ArgoCD integration;
• ArgoCD must be deployed with Keycloak integration;
• ArgoCD values must be production ready (investigate HA mode..);
• check CD pipeline works;
• Define ArgoCD project view;
• add EDP component with ArgoCD link;
• Upgrade mkdocs to new approach:
  https://epam.github.io/edp-install/operator-guide/install-argocd/?h=
  https://epam.github.io/edp-install/operator-guide/argocd-integration/

Use Upstream helm chart deploy Nexus as a shared component

• Use the Upstream Nexus helm chart;
• Use the Latest LTS version;
• Use Add-ons approach (put the result in add-ons repo);
• Integrate EDP instances with External Nexus;
• Ensure EDP can be deployed without Nexus-Operator;

Acceptance Criteria:

• EDP 3.4.0 released and available for deployment;
• installation documentation is aligned according to LTS version;
• all subcomponents are also released;
• RELEASES.md aligned;
• changelog updated;

Add article to describe how user can delete EDP with all integrations and related resources (clean Keycloak, remove finalizers....).

Provide script to automate this process.

Acceptance Criteria:

• mkdocs (https://epam.github.io/edp-install/) contains article of how to delete (redeploy) EDP;
• provide script to remove finalizers in case if Namespace stuck in terminating state;
• describe how remove finalizers in manually mode;

Acceptance Criteria:

• EDP can be integrated with Harbor;
• mkdocs describes steps to deploy and integrate EDP with Harbor;
• EDP use Harbor to push and pull images (as base platform image registry);
• integrate with OIDC;
• check deploy and integration on OKD cluster;

Acceptance Criteria:

• helm-helm library contain structure - https://github.com/argoproj/argo-helm/tree/main
• Tekton pipelines available and support this structure;
• base linters functionals are enabled;
• EDP user can develop charts with EDP approach;

Could you please describe main approach how EDP team recommends to optimize Nexus storage usage.

Acceptance Criteria:

• EDP documentation contain article of how EDP team recommends to optimize Nexus storage usage;

EDP Headlamp has new section - Marketplace.

Please create initial page in mkdocs to describe main capabilities of Marketplace page.

Acceptance Criteria:

• mkdocs contain article with main capabilities of Marketplace page;

Acceptance Criteria:

• mkdocs contain article of how to use auto deploy in most cases;
• describe in business case (not only technical side);

Type: Application
Framework: Antora
BuildTool: asciidoc

Add CI/CD pipelines for GitHub/GitLab/Gerrit

• We can use Npm react as a baseline
• Use dockerfile:

FROM nginxinc/nginx-unprivileged:1.23-alpine
COPY build/site/ /usr/share/nginx/html
CMD ["nginx", "-g", "daemon off;"]

As an EDP user, I would like to be able to use SAST scanning out of the box for tekton pipelines.

Acceptance Criteria:

• SAST scan available out of the box for Tekton pipelines;
• Enable only for build pipelines;

Keycloak operator created KeycloakClientScope groups when ArgoCD was enabled. However, this scope is also
necessary for Nexus so we made it obligatory even if ArgoCD is disabled.

https://github.com/epam/edp-install/blob/v3.2.1/deploy-templates/templates/argocd/keycloakclientscope.yaml#L1

Use Upstream helm chart deploy sonar as a shared component

• Use the Upstream Sonar helm chart;
• Use the Latest LTS version;
• Use Add-ons approach (put the result in add-ons repo);
• Integrate EDP instances with External Sonar;
• Ensure EDP can be deployed without Sonar-Operator;

https://epam.github.io/edp-install/operator-guide/jira-integration/?h=jira

Currently, we need to provide detailed information on how to use Jira integration from a business and technical perspective.

Now use can use commit message validate even if Jira integration is disabled.
The Tekton jira integration step is optional, and we need to describe this in the documentation and explain how to enable this function.

Acceptance Criteria:

• mkdocs Jira article updated;
• use Headlamp UI instead of Admin Console;
• User can use the commit-validate Tekton step and know hot to enable this step;
• Documentation up-to-date of the latest Jira integration functional;
• The description style is not only technical but also business, to understand why this approach

Acceptance Criteria:

• edp-install automatically create EDP component with valid link and icon in case if argocd integration enabled;

Acceptance Criteria:

• customer can deploy EDP in multi AZ mode;
• pipelines can run in parallel;
• customer can scale cache size;

Possible approach:
https://github.com/actions/cache
https://aws.amazon.com/blogs/containers/using-amazon-ebs-snapshots-for-persistent-storage-with-your-amazon-eks-cluster-by-leveraging-add-ons/
https://aws.amazon.com/blogs/containers/using-ebs-snapshots-for-persistent-storage-with-your-eks-cluster/

Technical side:

We need to have flag to support other then aws deployment
Use aws ebs snapshoter https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/examples/kubernetes/snapshot/README.md

Acceptance Criteria:

• mkdocs contain article of how to install upgrade for EDP to 3.3.0 version (use example https://epam.github.io/edp-install/operator-guide/upgrade-edp-3.1/);
• verify documentation and all manual actions during upgrade procedure;

This would greatly improve the user experience if, in addition to the artifact passing table, there would be a graphical display of the status of each autotest in the CD pipelines part. Something similar to the screenshot.

Acceptance Criteria:

• User can add codebases .NET 3.1 as default functional;
• language: .NET framework: .NET 3.1 and build tool: .NET;
• create repo for create strategy;
• Tekton CI/CD (add review and build pipelines) pipelines available for helm charts;
• check deploy functional;
• check EDP and default versioning approaches;
• update mk-docs screen;

Acceptance Criteria:

• EDP user can put ct-configs to root directory of repository and EDP uses these configs;
• enable helm-docs as mandatory component;

https://www.keycloak.org/server/reverseproxy#_exposed_path_recommendations

Lets expose only recommended endpoints for Keycloak.

Acceptance Criteria:

• EDP scripts and documentation provides only recommended Keycloak endpoints out of the box for better security;

Currently we have random values for example for name of service.

Acceptance Criteria:

• headlamp UI always create kind: Application with correct spec to deploy helm application with with static helm release name;
• get release name from /deploy-templates/Chart.yaml or from codeabase name;
• provide functional to redefine release name;

https://argo-cd.readthedocs.io/en/stable/user-guide/helm/
argoproj/argo-cd#1066

Investigate fullnameOverride parameter in values.yaml.