https://pulumi.com logo
#kubernetes
Title
# kubernetes
a

abundant-airplane-93796

08/13/2020, 1:49 PM
URN seems to be too tightly coupled to helm generated resource names. ie. If I'm trying to install the same chart on two clusters - two distinct kubernetes providers - I get URN duplicates unless I start specifying `resourcePrefix`'s for the charts. However If I go that route I end up with names that are are often too long and break the 53 char rule to be passed to the helm
--name-template
arg which Pulumi is using under the hood AND unecessarily convoluted names for resources within the cluster.
w

white-balloon-205

08/13/2020, 2:49 PM
There will ultimately need to have unique names - so something morally Luke
resourcePrefix
will be necessary. Where exactly do you hit the name limit - and are you in control of all parts of that name? Ideally the resource prefix would only need to be used for the Pulumi logical name - and wouldn’t need to be passed to Helm at all.
a

abundant-airplane-93796

08/13/2020, 3:07 PM
I am in full control of the name, and have managed to figure out a workaround using
resourcePrefix
and shortening what I was feeding in. I was actually compounding the problem initially because
resourcePrefix
gets prepended to the
name
given to the Chart resource, and thus gets very long very quickly. As those are fed directly to the
--name-template
arg it's very easy to hit the 53 char limit. Fortunately the charts in question all support a
fullnameOverride
value, so I've been able to utilize that to rename the resources as they appear in the cluster without resorting to more complicated transformations.
3 Views