Skip to content
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

Warning when using kustomize v5 #2701

Closed
khmjp opened this issue Jul 11, 2023 · 0 comments · Fixed by #2702
Closed

Warning when using kustomize v5 #2701

khmjp opened this issue Jul 11, 2023 · 0 comments · Fixed by #2702
Labels
bug Something isn't working

Comments

@khmjp
Copy link
Contributor

khmjp commented Jul 11, 2023

Describe the bug

When using kustomize v5, the following warning message appeared.

# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.

To Reproduce
Steps to reproduce the behavior:

  1. Install kubectl (kustomize v5.0.1).
% curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl"
% chmod 755 kubectl
% ./kubectl version --short --client
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.3
Kustomize Version: v5.0.1
  1. Make manifests using kustomize, then see Warning.
% ./kubectl kustomize manifests/base/ > /dev/null
# Warning: 'patchesStrategicMerge' is deprecated. Please use 'patches' instead. Run 'kustomize edit fix' to update your Kustomization automatically.

Expected behavior
No Warning.


Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@khmjp khmjp added the bug Something isn't working label Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant