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
... or similar, obviously you'd put your own patch there, I just used a smaller one for the sake of clarity.
In any case, the important point is, the key patches.<component-name> is used to hold the string representation of a "strategic merge patch" that will be applied to "component-name" (though, I'm not 100% sure which component-names, if any, are supported other than vizier-pem).
Is your feature request related to a problem? Please describe.
When deployed to EKS with fargate enabled, the vizier-pem pod is always in
Pending
state because it is scheduled to fargate node.Describe the solution you'd like
We enable deploying pixie-chart from newrelic-bundle chart, it will be great if pixie-chart can respect the value
global.fargate
from that chart.Describe alternatives you've considered
I see pixie operator chart support
patches
, but I can't get it to work, it fails the validation.This is the
patches
value I used.Additional context
Add any other context or screenshots about the feature request here.
Related issues:
The text was updated successfully, but these errors were encountered: