api/krusty: add SuppressDeprecationWarnings option to suppress lib warnings

[santoshguru-11]

Summary

When kustomize is used as a Go library (calling krusty.MakeKustomizer(...).Run(...)), deprecation warnings for fields like bases, vars, patchesJson6902, patchesStrategicMerge, commonLabels, etc. are unconditionally written to os.Stderr. Library consumers that control their own output have no way to silence this noise.

Changes

• Add SuppressDeprecationWarnings bool to krusty.Options
• Thread the option through to KustTarget via a new SetSuppressDeprecationWarnings setter
• Skip the fmt.Fprintf(os.Stderr, ...) calls in KustTarget.Load() when the option is true
• Default is false — no change in behavior for existing callers

Test

Added TestSuppressDeprecationWarnings in api/krusty/kustomizer_test.go that:

1. Builds a kustomization using the deprecated bases field and asserts a warning appears on stderr by default
2. Repeats the same build with SuppressDeprecationWarnings: true and asserts stderr is empty

Fixes

Fixes #5452

[k8s-ci-robot]

Invalid commit message issues detected

Invalid commit messages

Keywords which can automatically close issues and hashtag(#) mentions are not allowed.

• 92c598e api/krusty: add SuppressDeprecationWarnings option to Build API

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @santoshguru-11!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kustomize has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @santoshguru-11. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: santoshguru-11
Once this PR has been reviewed and has the lgtm label, please assign koba1t for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment