Closed bacongobbler closed 7 years ago
@kmala and @paulczar are potential reviewers of this pull request based on my analysis of git blame
information. Thanks @bacongobbler!
The registry seems to be failing for unrelated reasons, but there's no logs available here other than what's in kubectl describe
:
0s 0s 1 {kubelet gke-bollinger-default-pool-e50d9e9a-ytie} spec.containers{deis-registry} Warning Unhealthy Readiness probe failed: Get http://10.52.3.35:5000/v2/: dial tcp 10.52.3.35:5000: getsockopt: connection refused
closing in favour of #174
It seems that if you connect to a specific region and call conn.lookup(), it will return False and raise an S3ResponseError. However, if you connect without specifying the region info, it will return True.
Related: https://github.com/boto/boto/issues/443