blakebarnett

A general error count would be good, but having a breakdown by type/source/sink etc. would be even better :)

Also seeing this. I have a single deployment annotated, the images exist, but it's in a JFrog artifactory container registry. Unable to get it working using polling at all. I'll...

This issue _also_ appears when the AWS resources the controller is trying to reconcile no longer exist. It's a confusing error because it sends you on an IAM policy goose...

We are using it successfully as-is. Some clarity around the patch ordering in documentation and validation that a patch is just not going to work rather than having it fail...

> I'm also thinking it might be helpful to have a "default" or "init" section under spec.environment which can contain a hard-coded set of "defaults" for the environment, which may...

We also encountered this issue. An `Ingress` resource was deleted in `namespace1` and LoadBalancers for 3 ingresses in `namespace2` were deleted. This caused an outage for 3 services, the `Ingress`...

Unfortunately logs for this controller weren't being shipped at the time and the pods were restarted during troubleshooting so we lost them. I do have the CloudTrail events that show...

Oh also, I should note that deleting and recreating the `Ingress` resources fixed it immediately. I've been testing `v2.6.1` in a dev cluster, I manually deleted the AWS LoadBalancer resources,...

I ran into this also, I realized it's failing during the build because builder generates a pod spec that doesn't have the IAM role annotation. The dockerbuilder/slugbuilder podspec would need...

Sorry, we had to stop using deis workflow because of this and a few other reasons.