-
Notifications
You must be signed in to change notification settings - Fork 11
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
[QUESTION] Future of the kustomize exec plugin given their upcoming deprecation? #34
Comments
Reading up a little more on the state of things in kustomize-land, it looks like the latest version of kustomize should already support the container version of the kpt function usage you describe if you pass |
Hey I answered my question! Aside from the possibility of some QoL improvements to the API, this works with the new sort of invocation. I opened a PR with docs and an example: #35 |
@jskrzypek I wasn't aware that kustomize exec plugins are deprectated already but it makes sense to me, given that kustomize also supports KRM functions now. |
So with modern kustomize at least (I think I tested on 4.5) you can get it to work with the --enable-alpha-plugins & --network flags to enable network access. I tested it with the example I provided in #35 |
Thanks for creating the PR. I am going to review it and play a bit with modern kustomize on sunday.
|
The current Kustomize docs say that the previous/existing plugin methods (via
--enable-alpha-plugins
) are going to be deprecated:Clicking through the links to the kustomize plugins KEP PR and the KEP itself, it seems they intend the current plugin ecosystem to be replaced with KRM-style functions (which it that mentions
kpt
also uses).@mgoltzsche Are you aware of these changes? Does the fact that
khelm
is also available as akpt
function mean that it is (in a way) already forward-compatible with the deprecation?The text was updated successfully, but these errors were encountered: