Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,6 @@ Installs the Automation Controller

## Prerequisites

Do not use the `base` directory directly, as you will need to patch

* the `ConsoleLink`

The current *overlays* available are:

* [default](overlays/default)
Expand All @@ -17,13 +13,13 @@ The current *overlays* available are:
If you have cloned the `gitops-catalog` repository, you can install Logging infrastructure by running from the root `gitops-catalog` directory

```bash
oc apply -k ansible-automation-platform/instance/overlays/default
oc apply -k ansible-automation-platform/controller-instance/overlays/default
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the goal of renaming from instance to controller-instance?

Instance is a common pattern we use throughout the catalog so i am hesitant to deviate from the current pattern without a reason.

Copy link
Copy Markdown
Author

@BBGrimmett2 BBGrimmett2 Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thought behind this was the AnsibleAutomationPlatform custom resource is now the full deployment with AAP 2.5+. Changing the name to controller-instance matches the "plumping in" that we document in adding existing/separate controller instances into the AnsibleAutomationPlatform CR (see here)

Open to changing the names to match the pattern; however I would then change platform-instance to just instance to match the default CR (here)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think that instance would be my preference.

Inside of instance I would recommend something like this:

instance
├── base
├── component
│   ├── feature-1
│   └── feature-2
└── overlays
    ├── deploy-method-1
    └── deploy-method-2

Based off of what you have described you could have the separate examples for each deployment method in the overlays folder. If you have "common" features for those different examples you may consider adding the components folder. The intention of components is that it is a reusable set of patches that you can reuse for many different overlays. Instead of trying to apply the same patch in every overlay you can instead apply the component and keep features more modular.

You can see an example of how I use the components feature here:

https://github.com/redhat-cop/gitops-catalog/tree/main/openshift-ai/instance

```

Or, without cloning:

```bash
oc apply -k https://github.com/redhat-cop/gitops-catalog/ansible-automation-platform/instance/overlays/default
oc apply -k https://github.com/redhat-cop/gitops-catalog/ansible-automation-platform/controller-instance/overlays/default
```

As part of a different overlay in your own GitOps repo:
Expand All @@ -32,5 +28,5 @@ As part of a different overlay in your own GitOps repo:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- github.com/redhat-cop/gitops-catalog/ansible-automation-platform/instance/overlays/default?ref=main
- github.com/redhat-cop/gitops-catalog/ansible-automation-platform/controller-instance/overlays/default?ref=main
```
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,6 @@ kind: AutomationController
metadata:
name: controller
namespace: ansible-automation-platform
annotations:
argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
Comment thread
BBGrimmett2 marked this conversation as resolved.
spec:
create_preload_data: true
route_tls_termination_mechanism: Edge
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,3 @@ kind: Kustomization

resources:
- automationcontroller.yaml
- console-link.yaml
32 changes: 32 additions & 0 deletions ansible-automation-platform/eda-instance/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Ansible Automation Platform instances

Installs the Event Driven Ansible Controller

## Prerequisites

The current *overlays* available are:

* [default](overlays/default)

## Usage

If you have cloned the `gitops-catalog` repository, you can install Logging infrastructure by running from the root `gitops-catalog` directory

```bash
oc apply -k ansible-automation-platform/eda-instance/overlays/default
```

Or, without cloning:

```bash
oc apply -k https://github.com/redhat-cop/gitops-catalog/ansible-automation-platform/eda-instance/overlays/default
```

As part of a different overlay in your own GitOps repo:

```yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- github.com/redhat-cop/gitops-catalog/ansible-automation-platform/eda-instance/overlays/default?ref=main
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
apiVersion: eda.ansible.com/v1alpha1
kind: EDA
metadata:
name: automation-eda
namespace: ansible-automation-platform
spec:
ingress_type: Route
event_stream:
gunicorn_workers: 2
mtls: true
replicas: 1
no_log: true
activation_worker:
replicas: 2
image_pull_policy: IfNotPresent
ui:
replicas: 1
api:
gunicorn_workers: 2
replicas: 1
scheduler:
replicas: 2
database:
postgres_data_volume_init: false
redis:
replicas: 1
admin_user: admin
default_worker:
replicas: 2
worker:
replicas: 2
automation_server_url: http://aap-controller.example.com # Change to URL of the Automation Controller instance to run ansible jobs against (connect directly)
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- automationeda.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
- ../../base
4 changes: 0 additions & 4 deletions ansible-automation-platform/hub-instance/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,6 @@ Installs the Private Automation Hub

## Prerequisites

Do not use the `base` directory directly, as you will need to patch

* the `ConsoleLink`

The current *overlays* available are:

* [default](overlays/default)
Expand Down
11 changes: 0 additions & 11 deletions ansible-automation-platform/hub-instance/base/console-link.yaml

This file was deleted.

Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,3 @@ kind: Kustomization

resources:
- automationhub.yaml
- console-link.yaml
12 changes: 6 additions & 6 deletions ansible-automation-platform/operator/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,16 +4,16 @@ Installs the Ansible Automation Platform operator.

Do not use the `base` directory directly, as you will need to patch the `channel` based on the version of OpenShift you are using, or the version of the operator you want to use.

Please refer to [Ansible Automation Platform Lifecycle](https://access.redhat.com/support/policy/updates/ansible-automation-platform) for Ansible Automation Platform versions matching your OCP version

The current *overlays* available are for the following channels:

* [stable-2.1](overlays/stable-2.1)
* [stable-2.1-cluster-scoped](overlays/stable-2.1-cluster-scoped)
* [stable-2.2](overlays/stable-2.2)
* [stable-2.2-cluster-scoped](overlays/stable-2.2-cluster-scoped)
* [stable-2.3](overlays/stable-2.3)
* [stable-2.3-cluster-scoped](overlays/stable-2.3-cluster-scoped)
* [stable-2.4](overlays/stable-2.4)
* [stable-2.4-cluster-scoped](overlays/stable-2.4-cluster-scoped)
* [stable-2.5](overlays/stable-2.5)
* [stable-2.5-cluster-scoped](overlays/stable-2.5-cluster-scoped)
* [stable-2.6](overlays/stable-2.6)
* [stable-2.6-cluster-scoped](overlays/stable-2.6-cluster-scoped)

## Usage

Expand Down
37 changes: 37 additions & 0 deletions ansible-automation-platform/platform-instance/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Ansible Automation Platform instances

Installs the Automation Platform

## Prerequisites

Do not use the `base` directory directly, as you will need to patch

* the `ConsoleLink`

The current *overlays* available are:

* [default](overlays/default)

## Usage
This is using the default deploy all component CR, please refer to [Ansible Automation Platform 2.6 Docs](https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/installing_on_openshift_container_platform/appendix-operator-crs_appendix-operator-crs#operator-crs) for example custom resources for connecting existing components

If you have cloned the `gitops-catalog` repository, you can install Logging infrastructure by running from the root `gitops-catalog` directory

```bash
oc apply -k ansible-automation-platform/platform-instance/overlays/default
```

Or, without cloning:

```bash
oc apply -k https://github.com/redhat-cop/gitops-catalog/ansible-automation-platform/platform-instance/overlays/default
```

As part of a different overlay in your own GitOps repo:

```yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- github.com/redhat-cop/gitops-catalog/ansible-automation-platform/platform-instance/overlays/default?ref=main
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
apiVersion: aap.ansible.com/v1alpha1
kind: AnsibleAutomationPlatform
metadata:
name: automation-platform
namespace: ansible-automation-platform
spec:
route_tls_termination_mechanism: Edge
no_log: true
redis_mode: standalone
api:
log_level: INFO
replicas: 1
database:
postgres_data_volume_init: false
idle_disabled: false
Loading