Referenced resource names can be expressed as templates #610
Conversation
This file contains 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
For following fields: - PolicyRef - KustomizationRef - ValueFrom name can be expressed as a template and instantiate using - cluster namespace: .Cluster.metadata.namespace - cluster name: .Cluster.metadata.name - cluster type: .Cluster.kind It was already possible to leave namespace empty, in which case cluster namespace was used. Sveltos will instantiate name at run-time. This allows different resources to be fetched for different cluster, all while using a single ClusterProfile/Profile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For following fields:
name can be expressed as a template and instantiate using
It was already possible to leave namespace empty, in which case cluster namespace was used.
Sveltos will instantiate name at run-time. This allows different resources to be fetched for different cluster, all while using a single ClusterProfile/Profile