Is your feature request related to a problem? Please describe.
I use kube-burner-ocp in large part because it bootstraps the prometheus configuration for my cluster, so that I don't need to create a metrics-endpoint.yml.
When I use kube-burner-ocp init, no metrics profiles are used by default and the metrics-endpoint is not bootstrapped.
Describe the solution you'd like
I would like kube-burner-ocp init to have the same behavior as other workloads, which is: generate the metrics-endpoint information if a config is not provided.
Describe alternatives you've considered
Right now, I use cluster-density-v2 subcommand and change the kube-burner config in a local dir to pull the prometheus information dynamically.
afcollins
commented
5 months ago
Is your feature request related to a problem? Please describe. I use
kube-burner-ocpin large part because it bootstraps the prometheus configuration for my cluster, so that I don't need to create a metrics-endpoint.yml.When I use
kube-burner-ocp init, no metrics profiles are used by default and the metrics-endpoint is not bootstrapped.Describe the solution you'd like I would like
kube-burner-ocp initto have the same behavior as other workloads, which is: generate the metrics-endpoint information if a config is not provided.Describe alternatives you've considered Right now, I use cluster-density-v2 subcommand and change the kube-burner config in a local dir to pull the prometheus information dynamically.