Ideas for customizing the pattern
This pattern is modular so you can start with a small AAP footprint and add hub, Lightspeed, or Automation Orchestrator through install variants. You can also change CaC content and chart overrides without rewriting the pattern.
Selecting a different variant
Set main.variant in values-global.yaml to one of the following values:
minimal-aapaap-with-hubaap-with-aocomplete-aap-ao
Commit the change to your fork, and reinstall or allow Argo CD to sync.
See Installation details for what each variant deploys.
Replacing CaC content
The aap-config application uses overrides in
overrides/values-aap-config-aeg.yaml.
Point agof.cac_repo and agof.cac_revision at your own Config as Code repository to load controller configuration that matches your environment.
Tuning AAP instance flags
Per-variant instance overrides live under overrides/:
values-aap-instance-minimal.yaml— hub and Lightspeed disabledvalues-aap-instance-with-hub.yaml— hub enabledvalues-aap-instance-complete.yaml— hub and Lightspeed enabled
Fork the pattern and adjust these files when you need a combination that does not match a shipped variant.
Keep the AAP release field aligned with the operator channel (stable-2.7).
Using an external PostgreSQL for Automation Orchestrator
CloudNativePG is convenient for demos and labs, but Red Hat does not support it for Automation Orchestrator databases.
For supported environments, replace or bypass vp-cloudnative-pg-cluster and point the Automation Orchestrator instance at an externally supported PostgreSQL 15 database.
Update Vault secrets and Orchestrator chart values accordingly.
Extending from Ansible Edge GitOps
This pattern focuses on AAP installation and CaC. If you need OpenShift Virtualization edge workloads managed by AAP, start from Ansible Edge GitOps and reuse ideas from that pattern’s customization guide.
