peer channel create job just hangs forever for fabric 1.0.4 and gives error on 1.1.0 and later... about blockchain-network-on-kubernetes HOT 10 CLOSED

2018-05-28 18:17:31.561 UTC [msp] GetDefaultSigningIdentity -> DEBU 002 Obtaining default signing identity
2018-05-28 18:17:31.564 UTC [channelCmd] InitCmdFactory -> INFO 003 Endorser and orderer connections initialized
2018-05-28 18:17:31.565 UTC [msp/identity] Sign -> DEBU 004 Sign: plaintext: 0A9C070A5C08011A0C08BB8FB1D80510...BC3C01D4E2FA1A080A000A000A000A00
2018-05-28 18:17:31.565 UTC [msp/identity] Sign -> DEBU 005 Sign: digest: 5ADD54DDD3B3FF34DC14810296180CB2B08F5C2D6E6F2EE5BD9D84D9ABD32F36
2018-05-28 18:17:31.643 UTC [grpc] Printf -> DEBU 006 transport: http2Client.notifyError got notified that the client transport was broken EOF.
Error: proposal failed (err: rpc error: code = Unavailable desc = transport is closing)
Usage:
  peer channel join [flags]

Flags:
  -b, --blockpath string   Path to file containing genesis block

Global Flags:
      --cafile string                       Path to file containing PEM-encoded trusted certificate(s) for the ordering endpoint
      --certfile string                     Path to file containing PEM-encoded X509 public key to use for mutual TLS communication with the orderer endpoint
      --clientauth                          Use mutual TLS when communicating with the orderer endpoint
      --keyfile string                      Path to file containing PEM-encoded private key to use for mutual TLS communication with the orderer endpoint
      --logging-level string                Default logging level and overrides, see core.yaml for full syntax
  -o, --orderer string                      Ordering service endpoint
      --ordererTLSHostnameOverride string   The hostname override to use when validating the TLS connection to the orderer.
      --tls                                 Use TLS when communicating with the orderer endpoint
  -v, --version                             Display current version of fabric peer server

root@blockchain-org1peer1-7c84c7d78f-gcxds:/# command terminated with exit code 137```

And the pod dies...