Add --feature-gates support to VPA flag generation script

[omerap12]

In #8115, we added support for in-place updates in VPA. This functionality is currently gated behind a feature flag (see the features.md documentation for reference).

However, the generate-flags.sh script—which is used to generate CLI flags for all VPA components does not currently support the --feature-gates flag.

As a result, this flag is missing from the generated documentation, such as flags.md.

We should update the script to handle --feature-gates so that the flag appears correctly in the generated output and users are aware of it.

/good-first-issue
/area vertical-pod-autoscaler
/triage accepted

[k8s-ci-robot]

@omerap12:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

Details

In response to this:

In #8115, we added support for in-place updates in VPA. This functionality is currently gated behind a feature flag (see the features.md documentation for reference).

However, the generate-flags.sh script—which is used to generate CLI flags for all VPA components does not currently support the --feature-gates flag.

As a result, this flag is missing from the generated documentation, such as flags.md.

We should update the script to handle --feature-gates so that the flag appears correctly in the generated output and users are aware of it.

/good-first-issue
/area vertical-pod-autoscaler
/triage accepted

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.

[aman4433]

/assign

[Whitea029]

/assign

[aman4433]

Hey @omerap12 ,

While improving the flags doc generation, I noticed --feature-gates has a multi-line description, which breaks formatting and omits default values in flags.md.

We could:

1. Update the script to handle multi-line descriptions,

2. Add an exception in the script for this flag, or

3. Refactor the description to a single-line string.

Which approach would you prefer? Happy to proceed accordingly.

Thanks!

[omerap12]

Hey @omerap12 ,

While improving the flags doc generation, I noticed --feature-gates has a multi-line description, which breaks formatting and omits default values in flags.md.

We could:

1. Update the script to handle multi-line descriptions,
2. Add an exception in the script for this flag, or
3. Refactor the description to a single-line string.

Which approach would you prefer? Happy to proceed accordingly.

Thanks!

Hey, I think option 1 is the best way :)