-
Notifications
You must be signed in to change notification settings - Fork 231
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
Kpt should use internal.config.kubernetes.io/* annotations #2478
Comments
Issue on kustomize side: kubernetes-sigs/kustomize#4024 LMK if you plan to take care of it on both sides or I should still work on it. I'm guessing the fix will be in kyaml for both kpt and kustomize. |
I will take a closer look
That's very likely to be the case. |
The fix needs to be done in kyaml (common orchestrator layer) as part of kubernetes-sigs/kustomize#4024. @natasha41575 No plans to address this in the short term on kpt side yet. |
This has been confusing for contributors. We should fix it soon. |
Yes, I can take a look this sprint.
We should do this first, and after some time we can drop support for config.kubernetes.io/* and release 0.12. |
This is updated in kyaml v0.12.0. I will work on a PR to update kpt. |
Closing since the PR has been merged. |
Kpt should use the annotations as specified in https://github.com/kubernetes-sigs/kustomize/blob/master/cmd/config/docs/api-conventions/functions-spec.md#internal-annotations.
For example, kpt currently use
config.kubernetes.io/path
but it should useinternal.config.kubernetes.io/path
.The text was updated successfully, but these errors were encountered: