Skip to content

Releases: eiffel-community/eiffel-easy2use

Eiffel Easy2Use first stable release

21 Aug 15:33
Compare
Choose a tag to compare

What is new?

  • Eiffel bundle supports Eiffel protocol version Agen

  • Cx bundle supports:

    • CI:

      • 2 Java Microservices included (ms-frontend & ms-backend)
      • CI Engines included with pipeline as code: Jenkins Pipeline (ms-frontend) & Argo CI (ms-backend)
      • Jenkins pipeline shared pipeline code
      • Pre & post-merge pipelines
      • Eiffel event generated
      • CI triggered via webhooks & Eiffel events via RabbitMQ
    • CD:

      • GITOPS With Argo CD (automatically sync configuration in GIT repo with deployment in Kubernetes for specific branches : dev/stage/prod)
      • Promotion between DEV/STAGE/PROD is done by merging deployment GIT repo branches dev/stage/prod
      • Immutable Docker Images are used together with microservices config injection to configure microservices in the different K8S target environments
      • Eiffel Intelligence subscription uploaded via Argo CI pipeline build step
      • Eiffel Intelligence subscription is used to trigger deployment repo updates for microservice builds in Jenkins, when Docker Image artifact is created, published and when confidence level set to "readyforintegration"
      • Argo rollout Canary deployment executed for ms-backend
    • Inner-loop Skaffold:

      • Skaffold files added for inner-loop local dev and deployment to local or remote K8S clusters
        • Included in Gerrit repos: ms-frontend & ms-backend
      • Skaffold file added for multi microservice dev and deployment to local or remote K8S clusters
        • Included in Gerrit repo: deployment (handles build/deployment for both ms-frontend & ms-backend repos)
  • GitLab bundle supports:

    • CI:

      • 2 Java Microservices to be imported (ms-frontend & ms-backend)
      • GitLab CI engine with pipeline as code (.gitlab-ci.yml) in repos ms-frontend & ms-backend
      • Pre & post-merge pipelines
      • Eiffel events generated
    • CD:

      • CD Pipelines with kubectl deployment via HELM templates, helm charts included in ms-frontend & ms-backend repos
      • Pre-merge CD pipeline (merge request) deployment to K8S dev
      • Post-merge CD pipeline (merge request) deployment to K8S stage
      • Deployment to K8S production is triggered via manually decision in GiLab GUI
      • Immutable Docker Images are used together with microservices config injection to configure microservices in the different K8S target environments