Skip to content

Move to standardized cluster sizing template #544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 14, 2025
Merged
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
19 changes: 19 additions & 0 deletions content/patterns/ansible-edge-gitops/cluster-sizing.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: Cluster sizing
weight: 50
aliases: /ansible-edge-gitops/cluster-sizing/
---

:toc:
:imagesdir: /images
:_content-type: ASSEMBLY

include::modules/comm-attributes.adoc[]
include::modules/ansible-edge-gitops/metadata-ansible-edge-gitops.adoc[]

The OpenShift cluster is made of 3 Control Plane nodes and 3 Workers for the cluster; 3 workers are standard compute nodes and one is c5n.metal. For the node sizes we used the **m5.4xlarge** on AWS and this instance type met the minimum requirements to deploy the **Ansible Edge GitOps** pattern successfully on the Hub cluster.

This pattern is currently only usable on AWS because of the integration of OpenShift Virtualization; it would be straightforward to adapt this pattern also to run on bare metal/on-prem clusters. If and when other public cloud providers support metal node provisioning in OpenShift Virtualization, we will document that here.

include::modules/cluster-sizing-template.adoc[]

103 changes: 0 additions & 103 deletions content/patterns/ansible-edge-gitops/cluster-sizing.md

This file was deleted.