Bill Franklin
Bill Franklin
I hit the same issue. The problem I had was revealed by the nginx and uwsgi logs in the iris container. If you look at `cat var/log/{nginx,uwsgi}/*.log` during the login...
@bla-ckbox This should be fixed now
I hit this issue with OpenShift 4.8 - can confirm the fix in the commit resolves it, thanks @larsks 👍
[`PodMonitor`](https://docs.openshift.com/container-platform/4.7/rest_api/monitoring_apis/podmonitor-monitoring-coreos-com-v1.html) is a CRD installed with the Prometheus operator. Kubeval [doesn't support CRDs](https://www.kubeval.com/#crds). You could use `--ignore-missing-schemas` which will skip `PodMonitor` resources.
ADC VPX. As far as I'm aware it's the latest release we're running, let me check. Forgot to mention that in the GUI we are seeing these stats: ``` Packet...
This is a blocker for configuring PagerDuty in code. It's a tricky one but I'd suggest that the incidents would be resolved automatically (i.e. the effect would cascade).
I can also add `reason` in here, that might be useful
Yes exactly
No stalebot
No worries, FWIW we ended up writing a custom pagerduty controller (like a k8s operator) that reconciles desired config with what is in pagerduty. it was a little tricky since...