Value Statement

AutoShiftv2 is an opinionated Infrastructure-as-Code (IaC) framework engineered for Day 2 operations in Red Hat OpenShift environments. It harmonizes Advanced Cluster Management (ACM) and OpenShift GitOps (Argo CD) to automate the lifecycle of platform components.

https://github.com/auto-shift/autoshiftv2

The framework eliminates "operator toil" by replacing manual configurations with a declarative, modular model. It is specifically built to manage the OpenShift Platform Plus stack across hybrid-cloud and multi-cluster footprints.

Core Capabilities

• Unified GitOps Control Plane: Orchestrates RHACM via OpenShift GitOps to manage global resources from a single source of truth.

• Precision Version Control: Provides the ability to "pin" specific Operator versions (e.g., Quay, ACS) via cluster labels, ensuring environment stability while allowing for selective auto-upgrades.

• Risk-Free "Dry Run" Mode: Validates changes against existing policies, reporting violations and intended modifications without impacting live production traffic.

• Full-Stack Management: Native support for MetalLB, OpenShift Logging, Loki, Quay, and OpenShift Data Foundation (ODF).

• Automated Infrastructure Governance: Streamlines node-specific configurations for Master, Infra, Worker, and Storage roles through automated labeling.

The Strategic Case for AutoShiftv2

Why should this framework anchor your product strategy?

• Operational Efficiency: Shifting from manual "click-ops" to declarative GitOps drastically reduces the human overhead required to maintain cluster health.

• Centralized Governance: Leverages RHACM as a "single pane of glass" for visibility and policy enforcement across heterogeneous clusters.

• Production Stability: Features like Gradual Rollouts and Dry Run mode provide the safety nets necessary for high-availability enterprise environments.

• Architectural Flexibility: Highly extensible through feature flags, making it suitable for complex scenarios like disconnected (air-gapped) environments or bare-metal deployments.

• Automated Compliance: Inherently enforces security standards (e.g., STIGs, image registry whitelisting), ensuring every new cluster is "secure by default."

The Analogy: If OpenShift is the General Contractor that builds the house, AutoShiftv2 is the Smart Home OS. It automatically installs the security systems, manages the climate (Operators) at precise settings, and lets you "virtually stage" a renovation (Dry Run) before a single nail is driven.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.