Simon Pasquier
Simon Pasquier
> The issue seems to be something else from circleci's side, I tried getting api responses when the builds were successful as well. I'll open a ticket on circleci forum...
it really looks like the [CI run](https://app.circleci.com/pipelines/github/prometheus/prometheus/3975/workflows/e3c57254-6ec2-495c-949c-1cde3bcee2b7/jobs/19081/steps) from https://github.com/prometheus/prometheus/pull/6326 got stuck and never completed. Maybe it's happening from time to time but I don't remember anything like this before...
I'm ok to sponsor this.
Yes I see that a consistent and shared CI infrastructure makes it easier to keep up with the changes to the CI provider(s) as it has been experienced with GitHub...
Personally I find that the initiative is very welcomed and would be greatly beneficial the Prometheus project. I like the idea to get inspiration from other projects like @voxpupuli that...
I like the idea that a project needs to be sponsored by the maintainers of the community. I don't think that there's need to be a majority of maintainers actively...
I tried the steps in a local cluster and the PV didn't expand. I think that `.spec.paused: true` isn't necessary but you still need to delete (with orphan mode) the...
~~Ok I'll try again too...~~ @machine424 sorry for the confusion, I was too much focused on the upstream docs and missed that the PR is more about cleaning up the...
@ibihim I vaguely remember from when kube-rbac-proxy was maintained by the monitoring team that the misconfiguration opportunity was the top concern.