Skip to content

Conversation

@mbaldessari
Copy link
Contributor

  • Use spec.managedClusterClientConfigs[].url to get the spoke endpoint
  • Reduce the usage of the acm secret filter and support ACM 2.13
  • Fix some ansible linting issues

Since in ACM 2.13 the cluster secrets are no more (in favour of managed
service accounts), let's start using the url from the managedCluster CRs
since those exist both in 2.12 and 2.13. This will simplify our later
work.
ACM 2.13 uses managed service accounts so there is no <spoke>-cluster
secret anymore to parse. Instead we look for a secret called
'application-manager' inside the namespace for the spoke cluster.

That secret contains the bearerToken. We still keep 2.12 compatibility
and only run this when we cannot find the <spoke>-cluster secret.

Tested on both ACM 2.13 and 2.12
@mbaldessari mbaldessari merged commit 80df261 into validatedpatterns:v1 Sep 1, 2025
7 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.

1 participant