Skip to content

Comments

WIP: Properly parameterize managed cluster names#9

Merged
mhjacks merged 1 commit intovalidatedpatterns:mainfrom
mhjacks:test_name_change
Feb 23, 2026
Merged

WIP: Properly parameterize managed cluster names#9
mhjacks merged 1 commit intovalidatedpatterns:mainfrom
mhjacks:test_name_change

Conversation

@mhjacks
Copy link
Contributor

@mhjacks mhjacks commented Feb 13, 2026

  • The names ocp-primary and ocp-secondary were hardcoded in various places, which caused issues when trying to install two copies of this pattern into the same DNS domain.
  • Also parameterize the version of edge-gitops-vms chart in case it needs to get updated. It too was hardcoded.
  • Update to ACM 2.14 in prep for 4.20+ testing.

@mhjacks mhjacks changed the title Properly parameterize managed cluster names WIP: Properly parameterize managed cluster names Feb 13, 2026
@mhjacks
Copy link
Contributor Author

mhjacks commented Feb 13, 2026

While here I also want to test 4.20 and the productized ESO, so the core stuff is fixed but it's WIP because of those two things.

Copy link

@nadavleva nadavleva left a comment

Choose a reason for hiding this comment

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

Why not generate random seed to cluster names to avoid naming conflicts

Revert "Test name change"

This reverts commit b451a92.

Parameterize names

Test name parameterization

Unify naming strategy

Factor out cluster names

Upgrade to ACM 2.14

Standardize on RDR structure

Preserve the whole structure to prevent render failures

Parameterize primary/secondary cluster for edge-gitops-vms

Fixups for gitops-vms deployments

Update Changes.md

Commit cursor swing at simplification

Parameterize preferred cluster

Parameterize other DRPC aspects

Consolidate DRPC parameters

Fix template render error

Fix another template render failure

Sanitize install_config

Fixup template again

Update method to retrieve CAs

Update method to retrieve CAs

Update method for editing CAs

Update logging and be more careful in python

Try this approach - watch S3ProfileNames though

Use cluster names

Refactor validation to ensure there are just two profiles as long as the CA material is present

Rebase with main in mind

Try a different approach to validation

Change grep technique

Fix validation

Ensure cluster labels are set

Change label to clusterset for ACM membership

Ensure clusterGroup is set

Enhance merge logic for install config

Enhance merge logic further

Piece out overrides further to ensure machine types and regions are properly handled

Restore default cluster naming

Continue refining override logic

Correct spelling for secondary

Remove RegionalDR from values-hub and move sharedValueFiles to extraValueFiles for apps that matter

Add additional validation scripts

Create script and doc for updating the JSON files

Fix lint error in markdown

Update cluster validation

Revert some bad logic introduced for bad reasons (ODF was not deploying and I thought the script was wrong)

Simplify certificate extraction to only use yq

Avoid overly large shell command

Reformat README to silence super-linter

Specify argocd server to avoid error

Do not exit successfully if both clusters are not deploying

Force sync via gitops-vms namespace

Rationalize cron and non-cron argo monitors, force sync a namespace

Correct namespace

Update changelog
@mhjacks mhjacks merged commit 0d2cdc8 into validatedpatterns:main Feb 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants