Tomáš Kukrál

@lottspot running tests on travis is simple & inexpensive ... I'd recommend to run test on master as well.

How should croc discover latest release? From github API? I think it should be optional parameter as doing another call to github API can be considered harmful.

User story is: I'd like to start the deployment, wait for user to verify it (or do any user testing) and then let the deployment to continue (promote).

Former idea was to have something like wait condition handle from Heat ... user testing is just user story. I wanted to suggest something which is not easy to acomplish...

> @tomkukral would you be able to test this PR? Yes, I will deploy it today or tomorrow.

@SuperQ it doesn't work on my cluster.  I have tried to upgrade to `v2.42.0` but it haven't helped. Kubelet don't accept what auth is Prometheus providing ``` Mar 01...

Ok, no problem. I will try to do research. Do you have any working cluster with this configuration so I can replicate it?

Can you give me dump of clusterroles and service accounts which were created by operator? I'd like to replicate same behavior

 Confirmed working on `kube-prometheus-stack`. Now I will try to investigate which auth is it using. Just a small node for somebody trying to replicate it `helm template test kube-prometheus-stack`...

This command works on testing kind cluster with `kube-prometheus-stack`: ``` curl -k --header "Authorization: Bearer $(kubectl exec -ti prometheus-test-kube-prometheus-stack-prometheus-0 cat /var/run/secrets/kubernetes.io/serviceaccount/token)" https://172.19.0.2:10250/metrics ... got metrics endpoint ``` but baremetal cluster...