When make cluster_resource_apply is run, Parca will be deployed so that the collector can be continuously profiled. I have verified that this works on my end by running the following commands
make cluster_create && make cluster_resource_apply && make node_create && make resource_apply
kubectl get pods # parca is in default namespace
kubectl port-forward services/parca 31802:80 # port forward to see parca ui
after going to localhost:31802/profiles parca ui should be visible and the comparison of the two prometheus instances (1 current stable version, 1 incoming change) should be present
this change also fixes the documentation of running prombench locally because using GITHUB_ORG=prometheus fetches a bad image of prometheus and causes make resource_apply to fail
next changes
change gmp-bot so that PR author is aware that their changes have been profiled and provide instructions for them to see parca UI
When
make cluster_resource_applyis run, Parca will be deployed so that the collector can be continuously profiled. I have verified that this works on my end by running the following commandsafter going to
localhost:31802/profilesparca ui should be visible and the comparison of the two prometheus instances (1 current stable version, 1 incoming change) should be presentthis change also fixes the documentation of running prombench locally because using
GITHUB_ORG=prometheusfetches a bad image of prometheus and causesmake resource_applyto failnext changes