Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-4333

Migrate CHSRC GitOps service deployments to ArgoCD

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • SRCnet
    • Hide

      Migrating our existing services to ArgoCD will ensure that our procedures (SP-4249) are battle tested and solid. Not just for the deployment, but running all services this way will provide us with experience to keep updating the operational procedures for best practices.

      Show
      Migrating our existing services to ArgoCD will ensure that our procedures ( SP-4249 ) are battle tested and solid. Not just for the deployment, but running all services this way will provide us with experience to keep updating the operational procedures for best practices.
    • Hide
      • Migrate at least external-dns, cert-manager, an ingress controller, and an application that uses these services, such as Harbor.
      • A publicly available repository with these services (and no secrets).
      • (Uncommitted) Migrate skaha platform
      Show
      Migrate at least external-dns, cert-manager, an ingress controller, and an application that uses these services, such as Harbor. A publicly available repository with these services (and no secrets). (Uncommitted) Migrate skaha platform
    • 2
    • 3
    • 0
    • Team_CHOCOLATE
    • Sprint 5

    • PI23 - UNCOVERED

    • PI23 SRC23-PB SRCNet0.1 Team_Chocolate operations-and-infrastructure

    Description

      After having tried to make FluxCD work in past PIs, we have identified several limitations and issues that make it hard to work with for our use case (See https://confluence.skatelescope.org/display/SRCSC/COR-514+CH+-+Testing+of+procedures), and the only satisfying solution we have found is to use ArgoCD instead.

      Therefore in order to come up with a successful GitOps strategy, we will migrate our existing deployments to ArgoCD. This will happen ideally after (but perhaps also in tandem) with SP-4249 (which will produce documentation and for how to run Gitops services in SRCNet).

      Attachments

        Issue Links

          derives

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-4249 Documentation of SRCNet v0.1 compulsory services deployment

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                P.Llopis Llopis, Pablo
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (15.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do714.0
                  In Progress   23.0
                  Complete13.0
                  Total1020.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel