VPA Improving Flags Documentation Generation Process #7779
Labels
area/vertical-pod-autoscaler
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
Currently, the process for generating the flags documentation for the VPA involves running the script: vertical-pod-autoscaler/hack/create-flags-doc-vpa.sh. This script triggers
make document-flags
in each VPA component and then combines the output into a single file: vertical-pod-autoscaler/docs/flags.md.While this method works, we’d like to improve it by adopting a more streamlined approach similar to how the cluster-autoscaler generates its flags documentation. Specifically, we want to leverage the flags package’s auto-generated documentation by simply calling the binaries.
For reference: #7642 (comment)
I’ve made some progress on this, but any additional help would be appreciated (feel free to assign it to yourself).
/assign
/kind documentation
The text was updated successfully, but these errors were encountered: