Skip to content

Build out cloud-platform-nonlive #8437

Description

Background

We want to have separate instances for ArgoCD, one for live and one for nonlive. This enables changes to ArgoCD to go through nonlive workloads before hitting live workloads, and also we keep the preproduction environment for testing.

Proposed user journey

We use nonlive ArgoCD for nonlive clusters and live ArgoCD for live clusters

Approach

Deploy the nonlive cluster, then deploy ArgoCD to that cluster

Which part of the user docs does this impact

ArgoCD user documentation

Definition of done

  • nonlive cluster deployed
  • readme has been updated
  • user docs have been updated
  • another team member has reviewed
  • smoke tests are green
  • prepare demo for the team

Reference

How to write good user stories

Metadata

Metadata

Type

No type

Projects

Status
🥇 Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions