Use lookups to determine the clusterPlatform #18
Merged
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now we set global.clusterPlatform to whatever helm passes on, but
this is conceptually not correct:
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