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 more of a questions. There are more and more CRDs in the wild nowdays and they all come with their own CRs that of course don't come with a Chart.
If I want to keep my helm/helmfile workflow what options do I have to use and parametrize vanilla kubernetes deployment descriptors?
This is what comes into my mind if I want to do that with helmfile
postsync
❓ What about passing values from helmfile to kubernetes deployment descriptors?
This is more of a questions. There are more and more CRDs in the wild nowdays and they all come with their own CRs that of course don't come with a Chart.
If I want to keep my helm/helmfile workflow what options do I have to use and parametrize vanilla kubernetes deployment descriptors?
This is what comes into my mind if I want to do that with helmfile
❓ What about passing values from helmfile to kubernetes deployment descriptors?
🤔 Overkill for a simple CR
😒 raw helm, kind of same as postsync
What options are also possible to accomplish the same goal?
The text was updated successfully, but these errors were encountered: