Theinstall --generate-custom-yamlcommand is designed to generate a YAML file for customization, assuming it can connect to the API server of the target Kubernetes cluster. While we haven't confirmed the extent of information retrieved from the target cluster, it would be preferable if the command could operate without needing to connect to the API server, if possible.
Describe alternatives you've considered
If it's merely referencing the Kubernetes cluster version, I believe it could be achieved by simply specifying it as an option, something like:
Reducing dependencies on the target environment benefits operational efficiency when operating with GitOps.
Additional context
We also attempted applying patches to YAML files generated from Helm charts, but we weren't satisfied with the results in our environment, so we managed them manually. We're not using the Trident Operator either. Therefore, we're looking for an easy way to obtain detailed YAML files.
Describe the solution you'd like
The
install --generate-custom-yamlcommand is designed to generate a YAML file for customization, assuming it can connect to the API server of the target Kubernetes cluster. While we haven't confirmed the extent of information retrieved from the target cluster, it would be preferable if the command could operate without needing to connect to the API server, if possible.Describe alternatives you've considered
If it's merely referencing the Kubernetes cluster version, I believe it could be achieved by simply specifying it as an option, something like:
Reducing dependencies on the target environment benefits operational efficiency when operating with GitOps.
Additional context
We also attempted applying patches to YAML files generated from Helm charts, but we weren't satisfied with the results in our environment, so we managed them manually. We're not using the Trident Operator either. Therefore, we're looking for an easy way to obtain detailed YAML files.