Skip to content

Use lookups to determine the clusterPlatform#18

Merged
mbaldessari merged 1 commit into
validatedpatterns:mainfrom
mbaldessari:clusterplatform
Sep 30, 2025
Merged

Use lookups to determine the clusterPlatform#18
mbaldessari merged 1 commit into
validatedpatterns:mainfrom
mbaldessari:clusterplatform

Conversation

@mbaldessari
Copy link
Copy Markdown
Contributor

Right now we set global.clusterPlatform to whatever helm passes on, but
this is conceptually not correct:

    - name: global.clusterPlatform
      value: {{ $.Values.global.clusterPlatform }}

If the hub is on AWS and a spoke on Azure, the clusterPlatform on the
spoke needs to look it up locally, otherwise we can't do mixed
platforms.

Tested this on baremetal (where it was both None on hub and spoke) and
on AWS. The lookup works correctly so this should fix things properly.

Closes: #17

Right now we set global.clusterPlatform to whatever helm passes on, but
this is conceptually not correct:

        - name: global.clusterPlatform
          value: {{ $.Values.global.clusterPlatform }}

If the hub is on AWS and a spoke on Azure, the clusterPlatform on the
spoke needs to look it up locally, otherwise we can't do mixed
platforms.

Tested this on baremetal (where it was both None on hub and spoke) and
on AWS. The lookup works correctly so this should fix things properly.

Closes: validatedpatterns#17
@mbaldessari mbaldessari merged commit 24442a1 into validatedpatterns:main Sep 30, 2025
3 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.

clusterPlatform should use a lookup

1 participant