You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is another issue around the problem of resulting in duplicate URN's with the usage of helm charts. Previous, similar issues include #489 and #520.
A resourcePrefix option was added to address this in #599, however this occurs even with that fix.
Some helm charts instantiate resources of type: APIService (or other similar types), which will require metadata.name to take on a specific format. An example value for an APIService resource might be v1beta1.metrics.k8s.io. These names are hard coded, and not interpolated based on the release name.
The resourcePrefix only affects the release name, and so does not prevent these resources from colliding if multiple are instantiated.
This is another issue around the problem of resulting in duplicate URN's with the usage of helm charts. Previous, similar issues include #489 and #520.
A
resourcePrefix
option was added to address this in #599, however this occurs even with that fix.Some helm charts instantiate resources of
type: APIService
(or other similar types), which will requiremetadata.name
to take on a specific format. An example value for anAPIService
resource might bev1beta1.metrics.k8s.io
. These names are hard coded, and not interpolated based on the release name.The
resourcePrefix
only affects the release name, and so does not prevent these resources from colliding if multiple are instantiated.The text was updated successfully, but these errors were encountered: