-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ResourceReference should support Alias #4531
Comments
Is alias something that's generally supported by all ARM references? From what I can tell, it is a peculiarity of the PrivateLink API. We may need to introduce a custom version of |
This would break all existing ASO resources using the |
Understood, from a quick research it looks like alias is somewhat unique to Private Link Services as a global identifier. Seeing that I can think of 2 ways of handling it:
|
Current State
The ResourceReference (e.g., in PrivateLinkServiceConnection) currently allows referencing existing resources using group/kind/name or armId. However, our use case requires referencing resources by an alias, as demonstrated in this example. Unfortunately, using an alias as the armId is blocked by the current regex validation.
Proposed Improvement
Add support for using an alias in ResourceReference.
Alternatively, rename armId to id and allow it to accept both armId and aliases.
##Additional Context
A practical example of this requirement is configuring Elastic Cloud with Azure Private Link when accessed from AKS. This scenario is detailed in Elastic’s blog: Secure your deployments on Elastic Cloud with Azure Private Link.
The text was updated successfully, but these errors were encountered: