Minio: failed DNS can result in Job "success"
Somehow, a failed DNS lookup can actually result in the Job "success". This should not be possible.
$ kubectl logs interesting-lobster-minio-create-buckets.4-p94-z82dn
Connecting to Minio server: http://interesting-lobster-minio-nope:9000
mc: <ERROR> Unable to initialize new config from the provided credentials Get http://interesting-lobster-minio-nope:9000/probe-bucket-sign/?location=: dial tcp: lookup interesting-lobster-minio-nope on 10.96.0.10:53: no such host
Sucessfully connected to Minio server: http://interesting-lobster-minio-nope:9000
Creating bucket 'registry'
Bucket created successfully `myminio/registry`.
Setting policy of bucket 'registry' to 'none'.
Access permission for `myminio/registry` is set to `none`
Note the intentional broken service name for this example. I discovered it by accident during progress on !112 (merged)
Edited by Jason Plum