Add Annotation to Control Inline List Conversion in Kustomize Resources

[isarns]

This MR introduces a new annotation to Kustomize resources: kustomize.config.k8s.io/convertToInlineList. When set to false, this annotation prevents objects with names ending in "List" from being converted to inline resources, allowing them to be treated at face value.

Changes:

• Added the kustomize.config.k8s.io/convertToInlineList: false annotation.
• Updated the handling logic to respect this annotation and avoid converting specified lists into inline resources.

Example:

For example, the resource definition ManagedPrefixList does not require conversion to an inline list, and with this annotation, Kustomize will respect its original format.

Issues Addressed:

• Fixes issue Custom Resources with a Kind Ending in "List" are Silently Ignored #5042
• Fixes issue krusty Ignores Resources with "List" Suffix in Kind Name Without Warning #5485
• Heavily inspired by issue Don't Remove Kind with Suffix List if Empty #5045

Feedback Request:

As someone new to Golang, I understand that this MR might not be perfect. I welcome any guidance, suggestions, or improvements from the community to refine this feature further.

[k8s-ci-robot]

This PR has multiple commits, and the default merge method is: merge.
You can request commits to be squashed using the label: tide/merge-method-squash

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: isarns
Once this PR has been reviewed and has the lgtm label, please assign koba1t for approval. For more information see the Kubernetes Code Review Process.

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

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

[linux-foundation-easycla]

• ❌ - login: @chkp-isarn . The commit (a311343, 571f3a9) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @isarns!

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 @isarns. 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.

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.

[isarns]

/close

[k8s-ci-robot]

@isarns: Closed this PR.

In response to this:

/close

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.